deconz-rest-plugin: deCONZ wont connect to conbee II in 2.12.4 beta
Describe the bug
2.12.4 does not seem to connect to my conbee II
Steps to reproduce the behavior
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
Screenshots
Environment
- 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
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
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 33 (13 by maintainers)
Small update I could verify the regression on my Raspberry Pi 3 (albeit I think it’s not specific to the Raspberry Pi version). Working on a fix with the plan to get it ready for tomorrow.
Thanks. 2.13.0 works for me again.
Interesting find with the UART, for the ConBee II it isn’t used at all. But it is shared somehow with the Raspberry Pi’s Bluetooth module.
I’m setting up a Raspberry Pi 3 to see if I can reproduce the issue.
Could be related to https://github.com/dresden-elektronik/deconz-rest-plugin/issues/5006
With UART, you need to be a bit careful, this could also unwantedly interfere with your Blutooth. I think it’s a curse that they haven’t shaped that somehow homogeneously…
Ok so I disabled the UART on the pi which is enabled by default and I am all good now, it autodetects fine since its the only device now.
if you arent using those pins, you can do it with:
I suspect there needs to be an additional handshake before deciding the device is a valid device, not just “a technically possible” device