ZBT-1 ZHA - Unknown command

For some reason my Zigbee network stop working today, appears the Unkown command when I go to :

When I try to select the Options or the Network information options appears a black page without any information.


The logs do not show any error and after enabling Debug logging I cannot identify anything relevant also.

I’ve already tried a few troubleshooting solutions, but without success so far:

  • Reboot HA
  • Reboot HOST
  • Unplugged and replugged the stick on the same USB
  • Unplugged and replugged the stick on different USB
  • Updated Coordinator firmware
  • Checked the device persistance USB path also
  • Rollback the HA to the previous version

Current version:

  • Installation methodHome Assistant OS
  • Core2026.9.0
  • Supervisor2026.08.0
  • Operating System18.2
  • Frontend20260826.4

Zigbee coordinator:
Home Assistant Connect ZBT-1 with Firmware: 7.5.1.0
Also tested with the beta release 9.1.1.0

Any advice?

If I remove the ZHA integration, the devices will be deleted also right? how can I keep the existing devices?

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:

Once you have the long URL use that instead of the ttyxxx one. Zigbee2mqtt will not start , can not find the usb0 port - #5 by Saoshen

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.