Hello, I've had HA running on a Synology Docker container for two years and I replaced the Zigbee coordinator with a SMLight. It worked fine for several weeks, and then one day after what I think was an HA update, I couldn't access the coordinator's socket: SLZB-06M. Configuration failed, retry: ... I tried deleting ZHA and changing the port via the Z2M web interface, but nothing works... I'm devastated... can you help me? I don't know what to do anymore. * Path: socket://192.168.0.24:6638
Speed: 115200
Flow control: none
I have 52 Zigbee devices that are stuck in Home Assistant
Are you running multiple zigbee networks?
If not, only ZHA OR Z2M should be installed. Period.
Otherwise both will try to grab and lock the controller and the first one winning the race that time gets it.
The picture is of ZHA entities.
I only installed ZHA in Home Assistant. My coordinator is a SMLight network key on a PoE port via RJ45. I access the key via its IP address; it is fully functional and in Zigbee coordinator mode. Therefore, I only have one Zigbee instance via ZHA in my Home Assistant Docker container.
And in home assistant integration zha , I have a no access with the key zigbee coordinator on my host
The Zigbee coordinator is no longer reachable since I updated Home Assistant to its Core version: 2026.6.2 User Interface 20260527.5 Companion Application 2026.5.0 (2026.1984) Before that, everything worked perfectly with my 52 Zigbee devices via ZHA.
Check the firmware version on your SMLight. They recently released a dev (beta) version which caused similar issues. If your firmware version says dev in it, then you need to roll it back to the previous one.
Don't have the link handy, but there was a similar thread here on these forums about it a couple of weeks ago.
I followed your advice and migrated the Smartlight firmware to older versions, but nothing changed; it still refuses to connect to the coordinator via ZHA in Home Assistant. I don't know what to do anymore. Everything had been working fine for several months, and then one update and it's dead... that's not normal. Especially since it was Home Assistant that suggested I update the coordinator.
Like I said in this other thread, it's not HA pushing the upgrade. Looks like SMLight released a beta version to the stable branch, and HA simply let you know an update was available.
Follow the rest of the thread to see what you can adapt from the Z2M fix into ZHA.
I tried changing the speed to 480800, but nothing changed. I loaded an older Home Assistant backup, but it still gets stuck trying to access the SMLight key. The logs show SMLight key rejections, and even downgrading the firmware doesn't change anything; it's a connection refusal.
needs answered to move forward because you most likely have a port conflict.