You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When my Conbee2 is connected to my Synology NAS, and the device reboots (software update, whatever), Docker images lose contact with the device.
The device still shows up as: /dev/ttyACM0
And Synology Info shows the device info as connected i.e ConBee2 etc. But none of the HomeAssistant docker images, despite full access to the device, can find it.
Only physically unplugging and reconnecting it works. ( No need to issue any commands or restart any docker images ) Then the device shows up in ZHA Home Assistant etc.
So warm reboot - device no longer available.
Cold reboot or hot-plug - device available.
Is there an available command to 'reboot' the USB device?
I do not understand the implications of 0x26 | Watchdog TTL
"By writing a lower value like 2 seconds, the firmware can be rebooted."
Which firmware? The ConBee?
The text was updated successfully, but these errors were encountered:
When my Conbee2 is connected to my Synology NAS, and the device reboots (software update, whatever), Docker images lose contact with the device.
The device still shows up as:
/dev/ttyACM0
And Synology Info shows the device info as connected i.e ConBee2 etc. But none of the HomeAssistant docker images, despite full access to the device, can find it.
Only physically unplugging and reconnecting it works. ( No need to issue any commands or restart any docker images ) Then the device shows up in ZHA Home Assistant etc.
So warm reboot - device no longer available.
Cold reboot or hot-plug - device available.
Is there an available command to 'reboot' the USB device?
I do not understand the implications of
0x26 | Watchdog TTL
"By writing a lower value like 2 seconds, the firmware can be rebooted."
Which firmware? The ConBee?
The text was updated successfully, but these errors were encountered: