Hi
I have a weird home setup requiring me to use two ZigBee networks. The first one is using SLZB-07 connected directly via USB to my first Zigbee2MQTT server. Today I received SLZB-06MU, which is using Ethernet. I configured second Zigbee2MQTT network as usual, added my devices, then realized there’s a Zigbee entry in my Home Assistant settings, indicating ZHA. When I go in there, I get “Unknown command”, but it seems to actually be installed? I literally clicked “Ignore” for ZHA and SMLIGHT integrations few minutes before.
I actually switched from ZHA to Z2M a few months ago, and despite the fact I properly removed all ZHA devices + uninstalled the integration I still have this settings item with the same error message described above
Okay! I FINALLY was able to figure out what’s happening!
It turns out I had some “ghost” configuration leftovers in my configuration.yaml file.
If you’re facing this, double-check your config for the zha: block:
The same thing happened to me yesterday. I had installed ZHA about five months ago, got rid of it, installed Z2M and have a very large Z2M install. ZHA totally reinstalled itself out of the blue. It didnt just show up in “discovered.” It fully installed. After all this time, why would a Core upgrade start this nonsense? The last thing I need is my Z2M install go flakey. Anybody else see this? I have NO mention of ZHA in my configs. WTF?
If it is discovered, it is not installed (yet). If you press ignore it will not show up as discovered anymore, and will still not be installed. Unless you press the other button (or install zha though yaml as the previous poster had).
This looks like an ill-advised “upgrade” that was bundled into the latest version. I hope it’s in the rear view mirror after the next upgrade… It’s just the downside of a constantly evolving environment. c’est la vie…