Help understanding Zigbee2MQTT instabilities

Third party integrations
,
1

Hello,

I am experiencing instabillities with the zigbee2mqtt add-on.

I noticed this after adding 9 new devices, bringing the total number of devices handled by Zigbee2Mqtt to 18.

Sometime, everything is working as exected and then, at some point, devices stop responding.
Sometime only some devices are irresponsive, sometime all of them are.

Restarting the zigbee2mqtt can solve the issue but it is not always the case. I may need to restart it several time in order to be in a functionnal state again.
Until the issue appears again…

When in the “broken” state, there are no particular logs outputed bu zigbee2mqtt. When trying to change the state of a device I see a log signaling the change of state but the state never changes.

Here is my setup:

  • Home assistant using HassOS image with the following versions:
    • Core 2023.11.2
    • Supervisor 2023.11.0
    • Operating System 11.1
    • user interface 20231030.2
  • Zigbee2Mqtt v 1.33.2
  • Zigbee coordinator : efr32mg21 based with firmware EZSP v9
  • Raspberry Pi 3

I have found an in-depth guide giving advice to improve the stabillity.

However, there are a lot of suggestions and I would like to identify the root cause of my problems before investing in a solution.

Here are some points of attention I noticed:

  • “Raspberry Pi 3 may give bad performance”
  • efr32mg21 are experimental and not recommended adapters
  • Maybe I have too many end-devices compared to the number of routers i have.

I already tried multiple orientation of my adapter and is using a extension cable as advised.

Here is the device map of my devices when everything is working fine:

image
image1133Ă—739 102 KB

In the end, my question is the following : how can I understand what is happening to narrow down the root cause of my issue and try to fix it?

As I said, the logs are not helpfull. However I will copy them next time I am in a broken state.

Thank you!

2

Check cpu and memory usage from time to time. zigbee2mqtt use very small amount of memoy and has low cpu usage. The same goes for mqtt. But maybe you have some addon that is using a lot of memory or cpu and that might give you instability.

1 Like
3

I did not think about that!

I will check that next time I encounter the issue.

Thank you for the suggestion.

4

I would say this is your problem. Zigbee2mqtt supports more devices then zha and has more powerful features, but it’s fussier with adapters. I use zigbee2mqtt and never had luck with an adapter that wasn’t on the “recomended” list.

1 Like