Sometimes if you use the generic path for the serial data, it flips and you loose connection.
Check this:
The TTY ports can sometimes change internally, so it is suggested to use the /serial/by-id/ URL that always talks to your dongle by serial number so it is always right.
You can find out what that is by using:
and looking for it under all hardware, something like this:
If you are using a Container installation, this is how to see the /serial/by-id/ URL: ls -l /dev/serial/by-id Be sure to include the ‘/dev/serial/by-id/’ in front of the response as you need to tell it the full path.
Thanks for the tip, I had already tried that and didn’t work.
I solved the problem by replacing the ZBT-1 with the new ZBT-2 model and rebuilding the network from scratch (removing the integration with ZHA), since the migration also didn’t work. I suspect the database was corrupted.