#Zigbee problems

1 messages · Page 1 of 1 (latest)

random crow
#

Hi all,
I have been running zigbee2mqtt (and mosquitto) on a standalone Rocky Linux server for years, using the SkyConnect adapter to control my 30+ zigbee devices. It has been working really fine, with no dropouts in years.
When the ZBT-2 adapter was released, I wanted to help fund the OHF and got one adapter the first day.
I then moved the zigbee2mqtt (and mosquitto) into my Home Assistant RaspberryPi 5 (8gb) device and now I run it as the default configuration in the HA ecosystem.
I have taken care to separate the wifi 2.4GHz channel (1) from the zigbee channel (26) and I'm also using the SkyConnect adapter as a thread radio (channel 20).
I'm living in an area with very little other wifi's in the neighborhood. So no other wifi is "seen" by my system.
But, since moving the zigbee2mqtt to the Rpi HA system, the devices has started to disconnect. Every day, approx 5-10 devices needs to be re-paired with z2m. I junst can't understand why this happens. I have 30+ zigbee devices around my house and 25 of those are "routers". Lightbulbs mostly with always-on power. The devices that disconnects are located a few centimeters from a working router. So it can't be a weay signal.
I dont't know if the move of z2m program has caused the instability, or it's the change of adapter from SkyConnect to ZBT-2.
Has anyone any tips on what to do to understand why devices disconnect?
I'm getting frustrated.

/Johan

gloomy wing
#

Hello @random crow,
Is your dongle on a 1 or 2 meter extension to get it away from the PI's noise and any other radio sources?

random crow
#

I use the cable that was included in the package. The antenna is as far away from the Rpi as possible (ca 1m).

white night
#
  1. Do other devices keep working when some loose connection?
  2. If it's battery-powered devices/sensors that loose connection, did you try replacing the battery?
  3. When you switched from SkyConnect to ZBT-2, did you migrate your network or did you set up a fresh Z2M instance and re-paired all devices? (migrations with Z2M may require extra steps to rewrite the IEEE onto the new SiLabs adapter in most cases)
  4. Is there anything in Z2M logs?
random crow
#

Thanks for your help, I'll try to answer your qeustions:

  1. Yes - other devices continue to work fine, even if some of the devices disconnect.
  2. Mostly mains-powered devices disconnect, this morning, 12 (of 34) devices was diconnnected. Only routers. No battery powered devices.
  3. I copied the configuration.yaml file so I wouldn't have to repair my devices. Some of the devices are located behind closed spaces in the kitchen (i.e. flood sensor under the dish washer). I haven't seen any info about the problem of migrating the z2m program. Where can I find this information?
  4. The log file is not showing any hint on why the devices disconnect, it just says the devices are not responding to requests. I have been running the log as info. I will increase the logging to debug. I'll be back.
random crow
#

I have now migrated from the HA addon z2m to the previous z2m running on a standalone linux server. Just like I had it before all these problems started.
But - the same problem shows. 50% of my mains-powered devices has now gone disconnected after a few hours.
I think the only thing that has changed is that I have started using the SkyConnect adapter as a thread radio. The thread radio is using channel 15, the zigbee adapter is using channel 20. The wifi is using channel 1.
I really don’t understand what the problem is. Why is the whole house broken because I started using matter o er thread. It’s not logical.

random crow
#

I have now found in the zigbee2mqtt log file that the process is restarting every five minutes.
It's right after a load of these messages:
zh:ember:ezsp: Received network/route error ROUTE_ERROR_ADDRESS_CONFLICT for "0".
Does someone know what these messages mean?

random crow
#

This morning, all my router devices was offline.
85% of all my devices are now offline. My zigbee network is strong. The devices has over 200 LQI. But still, they disconnect. I don’t understand.

random crow
#

When the error message ROUTE_ERROR_ADDRESS_CONFLICT show in the log file, the zigbee2mqtt process crashes, and it restarts. This is the situation where the devices loose connection to the controller. It happens a few times every hour, so more and more devices is lost during a day.

serene crescent
#

Somewhere you have an IEEE address collision

random crow
#

I use the ZBT-2 for zigbee2mqtt, and the ZBT-1 is now used (only) for Thread radio. The ZBT-2 adapter has been running fine for a month, then I moved the zigbee2mqtt software from a linux installation into HA (as the official addon). This was when I started using thread (also in HA). Now - I have moved the ZBT-2 adapter back to the linux machine. Using the same software installation as before, but now the error message is showing every 10 minuters or so. So - I have no conflict.

#

Is the IEEE address specified in the configuration.yaml file ? In that case, I have copied it across from the linux machine, to the HA system and back again. Could this affect my stability?

random crow
#

I was talking to chatgpt and it suggest I have duplicate entries of a ieeeAddr in my databse.db file, but I have verified that there are no duplicates in this file.

serene crescent
#

Does the ZBT-2 have a feature which lets you change the address?

#

In other words is that how you migrated or did you have to re-pair

random crow
#

I don't know of any way I could change the address. I didn't change anything. The same ZBT-2 adapter was running fine for months before I moved it over to HA and back again.

#

I would rather not change the encryption keys and re-pair the whole lot of devices. Most of them are easy to re-pair, but a few are really hard.

random crow
#

I have tried running the SILabs utlity to change the ieee adrress, but it doesn't run on python3.12, which is the version I have.

random crow
#

I have now started to re-pair all my 35 devices. 23 of them were easy to re-pair. But it looks like there is no more errors in the log file anymore. Let's see in the morning.

random crow
#

And Im now back to having full converage on my estate for all my 30+ devices. Rock solid and good response times.
What did I do ? Started with a fresh installation of z2m.

serene crescent
#

Ghosts (or a duplicate entry buried down there somewhere)