Mimiix
August 13, 2021, 8:22am
1
Hi all
There seems to be an issue with 2.12.4 in which the Conbee / Raspbee isn’t found / selected properly. This seems mostly affecting Raspberry Pi’s. The issue is under investigation. A work around / fix can be found here (Thanks @senilio ):
Issue tracking here:
opened 04:59PM - 11 Aug 21 UTC
Bug report
<!--
- Use this issue template to report a bug in the deCONZ REST-API.
- I… f you want to report a bug for the Phoscon App, please head over to: https://github.com/dresden-elektronik/phoscon-app-beta
- Make sure not to remove any headers and fill the template completely. If you remove the headers, the issue will be auto-closed.
- If you're unsure if the bug fits into this issue tracker, please ask for advise in our Discord chat: https://discord.gg/QFhTxqN
- Please make sure sure you're running the latest version of deCONZ: https://github.com/dresden-elektronik/deconz-rest-plugin/releases
-->
## Describe the bug
<!--
Describe the issue you are experiencing here to communicate to the
maintainers. Tell us what you were trying to do and what happened.
Help us understand the issue by providing valuable context.
-->
2.12.4 does not seem to connect to my conbee II
## Steps to reproduce the behavior
<!--
If the problem is reproducable, list the steps here:
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. Observed error
If the problem can't be reproduced and is sporadic, please provide some details
on how often and when the issue happens.
-->
I was on 2.12.3 with a conbee II on a raspberry pi with the deCONZ_ConBeeII_0x266f0700.bin.GCF firmware
I upgraded to 2.12.4 and the new firmware deCONZ_ConBeeII_0x26700700.bin.GCF and deconz does not seem to be connecting to the gateway, it is shown as not connected in phoscon.
I then tried 2.12.4 with the previous firmware deCONZ_ConBeeII_0x266f0700.bin.GCF with the same result
I downgraded to 2.11.5 stable and all is well again, I then tried 2.12.4 again with the same result so now I am staying on 2.11.5 for now
## Expected behavior
<!--
If applicable, describe what you expected to happen.
-->
## Screenshots
<!--
If applicable, add screenshots to help explain the problem.
-->
## Environment
<!--
The deCONZ and firmware versions are found in the Phoscon App: Menu -> Settings -> Gateway,
as well as in the deCONZ GUI: Menu > Help > About deCONZ.
-->
- Host system: (Raspberry Pi / PC / NAS) raspberry pi
- Running method: (Raspbian / Ubuntu / Home Assistent deCONZ Add-on / Marthoc Docker container / Windows / Virtual Machine) Raspbian, .deb/apt installation
- Firmware version: (26xxyy00) in steps above
- deCONZ version: (2.xx.yy) in steps above
- Device: (ConBee I / ConBee II / RaspBee I / RaspBee II) CONBEE II
- Do you use an USB extension cable: (yes / no) -- only relevant for ConBee I/II YES
- Is there any other USB or serial devices connected to the host system? If so: Which? NO
## deCONZ Logs
<!--
Debug logs can help to investigate certain problems like device pairing and communication issues.
Logging can be enabled on the command line as described in:
https://github.com/dresden-elektronik/deconz-rest-plugin/wiki/deCONZ-debug-flags
Secondly, for versions above 2.05.87: In the deCONZ GUI: click Help > debug view. Output of APS,ZDP, ZCL and INFO can be handy.
-->
Seeing this constantly in the logs, seems to be trying to connect to the wrong device
```
09:54:12:482 device state timeout ignored in state 1
09:54:12:967 COM: /dev/ttyAMA0 : (0x0000/0x0000)
09:54:12:967 dev /dev/ttyAMA0 (/dev/ttyAMA0)
09:54:12:969 COM: /dev/ttyACM0 : ConBee II (0x1CF1/0x0030)
09:54:12:973 auto connect com /dev/ttyAMA0
09:54:14:550 Serial com connected
09:54:14:631 device state timeout ignored in state 2
09:54:14:790 device state timeout ignored in state 2
09:54:14:953 device state timeout ignored in state 2
09:54:15:113 device state timeout ignored in state 2
09:54:15:274 device state timeout ignored in state 2
09:54:15:434 device state timeout ignored in state 2
09:54:15:594 device state timeout ignored in state 2
09:54:15:754 device state timeout ignored in state 2
09:54:15:916 device state timeout ignored in state 2
09:54:16:073 device state timeout ignored in state 2
09:54:16:234 device state timeout ignored in state 2
09:54:16:394 device state timeout (handled)
```
## Additional context
<!--
If relevant, add any other context about the problem here, like network size, number of routers and end-devices
and what kind of devices/brands are in the network.
-->
That’s it for now!
