I have now integrated 60 identical Zigbee sockets (the cheap ones from ALI) into ZHA.
This has always worked without problems.
All entities except LQI and RSSI were always enabled immediately.
For about two weeks now – unfortunately, I can’t say after which update – all entities have been disabled after pairing. Not even the ON/OFF function is enabled.
It’s really annoying to have to click through until you at least activate ON, consumption, and ON status.
Can anyone tell me where this changed behavior comes from and how to possibly get it back?
The fact you don’t know which update caused this makes it hard to pinpoint, however, 2025.6 was released 2 weeks ago. Assuming that version is what caused your issues, the changes to ZHA were merged in here.
I’m hardly competent when it comes to reading code and have very little familiarity with how ZHA works under the hood. However, I suspect this commit caused it. It removed the Diagnostic, Config & Standard Entity types with no apparent side effects, but it seems that something in ZHA/HA was using those entity types to determine whether the entity was enabled or disabled by default.
I was going to suggest you create an issue in ZHA github, but before you do, check your coordinator - that “zNR01 generic zigbee coordinator” doesn’t sound like a fully supported coordinator.
“zNR01 generic zigbee coordinator” is a “ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2”.
I believe this is supported and very common - isn’t it?
It’s supported, though I’m not quite sure why it’s not recognised as such.
Btw, forgot to add in my earlier post - it’s called “pairing”, not “training”. You might want to edit your post & title if you want more help
“zNR01…” is a name I gave him - I use a scheme for the names (z=zigbee, NR=Network, 01=the first and only one)
I changed training to pairing - thank you.
1 Like
I have opend Issue #473 for ZHA