-
Notifications
You must be signed in to change notification settings - Fork 482
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ConBee II disconnects every hour (since 2.05.73?) #2463
Comments
This looks like the firmware watchdog gets triggered if no serial communication is received for a while (I think it's an hour). It also seems that deCONZ selects the wrong device to auto-reconnect to /dev/ttyS0 (albeit it should also cycle through the device list and try with the next after an timeout of 15–20 seconds. Does this happen for /dev/ttyACM0? If not that would be a deCONZ core bug and and a good explanation why some networks go down, I need to check the code here. If the cycling does not happen, can you please try to pin the device via
To be honest I'm not sure, there is some isCoordinator() magic in the code and the REST-API plugin which might lead to different code paths. I haven't tested the router configuration in a while now. |
Indeed. That explains the deconz-rest-plugin/change_channel.cpp Lines 443 to 447 in edf380f
|
OK, had another disconnect/reconnect, but the
|
Definitely related. After reconfiguring the ConBee II to its original settings, I no longer see the disconnect messages. |
Good catch, I think this should be fixed later on. The router configuration is quite useful at times. For the reconnect issue I have checked the code and found some spots which were causing the cycling through all devices to stop. This is fixed now and available in the next build. |
Since two days, the ConBee II on my RaspBerry Pi 4 (running Buster) disconnects every hour. I'm seeing the messages below in the syslog, and the deCONZ GUI shows the device as not in network. After pressing Join, it joins the network again. I double-checked the old logs: the messages didn't appear earlier.
I think this has started after installing 2.05.73. I did a
sudo apt update; sudo apt upgrade
to install the latest beta, and also got a load of Raspbian updates. I don't see anything similar on the RaspBee on Raspberry 3B+ (still running Stretch).Not sure if this is related, but I've been playing with emulating the Hue bridge to get the Lutron Aurora to work. After updating, I configured the ConBee II as router, with a custom mac address of 0x0017880101000001 and nwk address of 0x0001 and joined it to my test network.
Here's the first occurrence:
And the two most recent ones (I did reboot in between):
After each reconnect, deCONZ tries to pick up, but fails:
The text was updated successfully, but these errors were encountered: