Hi started getting into Home Assistant over Christmas last year.
Spent the best part of the 10 months trying to get a stable zigbee2MQTT up and running.
After 18 wipes and rebuilds going to try something else, ZHA.
I have successfully setup an SMLight coordinator using poe ethernet.
I currently have about 48 zigbee router devices and 12 end devices that I want to have up and running reliably.
ZHA automatically found 12 router devices
And helpfully named after the manufactures device name.
So I current have a load of Aurora devices and ike relays.
I have identified which Aurora device and their locations, I renamed them and applied the room but I am not seeing their names changing in the Home Assistant aha interface.
Some have but most have not and because ti seems to take a prolonged period it is tricky to identify which ones I have named as it it seems to take 10 + minutes or longer of the name change to show.
Is there something else I should be doing to get the rename to occur?
It is making the pairing process very very slow indeed if it takes this long to reflect an naming of a device.
I am adding new devices and it asks me to name them and put them in a room, which I do and it promptly adds them by the manufacturers name and loses the room.
This will make setting up a very long task and make automation very difficult to do with so many devices with the same name.
There must be a way to have them store their assigned names, surely this is not how it works?
I’ve now got 34 router devices into ZHA and as long as you give it 10 mins or so it eventually catches up with the correct names and locations. I’ll finish off th other 16 odd devices tomorrow to get the core system up and running.
I can let it sit for two weeks and if still stable will start adding the rest.
I had got very quick at loading zigbee2MQTT but obviously ZHA just takes a a lot longer to do, but if I don’t have to rebuild it every 13 days it will be worth doing.
I just switched from a Skyconnect coordinator to an SMlight one on ZHA and had to repair all of my 29 Zigbee devices.
They was definitely a slight delay of a minute or so if I enabled disabled entities. But I didn’t have any delays with naming. On pairing I entered the name and location and it showed immediately with that name.
I am running Home Assistant on a VM on an M1 Mac mini 4 processors and 5GB RAM and Home Assistant is reporting a 3% usage of the 5GB RAM and 50% of the 4 processors so it has plenty of headroom
Yeh normally I can pair 50 devices in just over an hour, it took 4 hours with ZHA because of the 10 min delays between pairing and being able to access in ZHA, also it can take a few hours for the device to be available in Home Assistant Automations.
Trying to work out how to use the ZHA devices in Node Red now…
If you’re doing this all in a VM, it may be worth firing up a new VM with a fresh HA install and just install the ZHA integration and check its performance there.
I’ve never heard of such a big delay pairing Zigbee devices before, so it makes me wonder if there’s something in your existing HA setup that may be causing the delay.
After 18 rebuilds of zigbee2MQTT in 10 months, 4 different coordinators, multiple Mqtt brokers, build in Home Assistant in VM, Home Assistant green, knowing I have removed all issues of signal clashing, interference.
And 60+ aha devices fell off the network at 4am this morning.
There is something fundamentally corrupt in the current install.
Did notice the issue with Device/Settings is consistent and noted that the default zigbee2MQTT install sets zigbee2MQTT to use an unsupported mqtt protocol version 4, this may be related to the issues of zigbee2MQTT.
My preference is to use zigbee2MQTT as it much easier to use Node red with than ZHA.
But will return to ZHA if after loading 40 routers and 10 end devices I can get any stability.
