Trying to add SMLight SLZB-06 to ZHA. Keep getting an error

I’m trying to install a brand new SMLight SLZB-06 via PoE. I’ve got it connected to my network and it’s discoverable on the network and in Home Assistant.

When trying to add the ZHA integration, I follow all steps provided, but at the end of the process I get an Error, but the error window is blank.

I check my Home Assistant logs and nothing appears in there.

Any ideas what I might be missing?

I was having the same issue, and it turned out to be wireless interference.

You can check the home assistant logs by getting the “file editor” add on and opening the home-assistant.log and look for
“Network formation refused: there is too much RF interference”

I solved it by turning off my WiFi and then ran the ZigBee setup. Then changed the ZigBee channel.

I also had issues with pairing devices in z2m which might have been cause by this too but I’ve not confirmed this.

Unfortunately this did not work for me.

I did not find that line in any of my logs and turning off wifi didn’t help. :frowning:
Thank you though.

i had the same problem.
Remove the antenna and repeat the procedure in Homeassistant.
then go through the wizard without any problems.

2 Likes

for me it actually worked out to unplug antenna. Thanks.

Same here, remove antenne to get adapted in HA, then attach antenna. Why does SMLight does not make a note about that?

This worked for me!!! I was smashing the keyboard trying all sort of things to get my zigbee network back up then I removed the antenna on the SLZB-06P7, it instantly configured and everything worked after that!! Thank you.

They do.

" According to the second thread, the users propose to start without antennas or routers nearby: Try unscrewing the antenna during startup. Or unplug any near by routers temporarily. Try to do abovementioned as well as start ZHA just to test your device:"

You guys are life savers! thnx!

Thankyou for this. I’ve spent 4 days going round in circles trying to get HA to add a new ZHA network. It kept coming up with an RF interference error. This fixed it after a wasted weekend.