Issues with Z2M and Zigbee ethernet coordinator

[shaikedem]

Hello all!

I have for few months 2 Zigbee ethernet gateways, running with 2 Z2M instances (lets call them Z2M1 and Z2M2)
Most time its working, but 2 main stability issues which i cant seem to resolve!
Hope someone can help me

the Tasmota device I use, its same device for both Z2M1 and Z2M2, they have same f/w version AFAIK.

https://www.aliexpress.com/item/1005004958650903.html

My HA is running latest version (problems I describe here are from day 1 of adding the Z2M instances and devices, so its not tied to specific version)

My HA is running on Debian VM on UTM hypervisor on macbook pro (2022 version). Its connected to my home network via LAN cable. Rest of integrations of my HA instance are working fine, including local tuya, Tao cameras, 2 ESP devices and various other cloud based integrations.

Issue 1:
Z2M1 connects to few devices ( motion, presence, button switch, flood sensor) which are physically close to the coordinator
the coordinator itself, is connected to the same switch the Mac is connected, with short cables (both Mac and coordinator) and both are practically 10cmm within each other.
This Z2M1 gives lots of errors of connectivity to gateway in Z2M log.
After it have few of these in a row, Z2M1 just hangs!

The tasmota coordinator is avail and i can ping it constantly even when Z2M1 reports connections errors

The heartbeat supervisor is turned on for this addon but it never triggers…
I wrote a simple automation that monitors the Z devices connected to Z2M1 and the service and if it detects sensors “unavail” for few mins it will restart the addon and that solves this until next time.
Problem is this happens up to 15 times a day. sometimes its OK for hours, sometimes it hangs and restarts every 5 mins…

this is example addon log section when it hangs

[09:55:10] INFO: Preparing to start...
[09:55:10] INFO: Socat not enabled
[09:55:11] INFO: Starting Zigbee2MQTT...
Starting Zigbee2MQTT without watchdog.
[2024-08-01 09:55:12] info: 	z2m: Logging to console, file (filename: log.log)
[2024-08-01 09:55:12] info: 	z2m: Starting Zigbee2MQTT version 1.39.0 (commit #unknown)
[2024-08-01 09:55:12] info: 	z2m: Starting zigbee-herdsman (0.50.1)
[2024-08-01 09:55:12] warning: 	zh:ezsp: Deprecated driver 'ezsp' currently in use, 'ember' will become the officially supported EmberZNet driver in next release. If using Zigbee2MQTT see https://github.com/Koenkk/zigbee2mqtt/discussions/21462
[2024-08-01 09:55:25] error: 	zh:ezsp:uart: --> Error: Error: {"sequence":7} after 4000ms
[2024-08-01 09:55:25] error: 	zh:ezsp:uart: -!- break waiting (7)
[2024-08-01 09:55:25] error: 	zh:ezsp:uart: Can't send DATA frame (6,2,0): 260001630004
[2024-08-01 09:55:27] error: 	zh:ezsp:uart: Port error: Error: read ECONNRESET
[2024-08-01 09:55:30] error: 	zh:ezsp:uart: --> Error: Error: {"sequence":7} after 4000ms
[2024-08-01 09:55:30] error: 	zh:ezsp:uart: -!- break rewaiting (7)
[2024-08-01 09:55:30] error: 	zh:ezsp:uart: Can't resend DATA frame (6,2,1): 260001630004
[2024-08-01 09:55:30] error: 	z2m: Error while starting zigbee-herdsman
[2024-08-01 09:55:30] error: 	z2m: Failed to start zigbee
[2024-08-01 09:55:30] error: 	z2m: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html for possible solutions
[2024-08-01 09:55:30] error: 	z2m: Exiting...
[2024-08-01 09:55:30] error: 	z2m: Error: Failure send getMulticastTableEntry:{"type":"Buffer","data":[38,0,1,99,0,4]}
    at /app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/ezsp.ts:686:23
    at Queue.execute (/app/node_modules/zigbee-herdsman/src/utils/queue.ts:35:20)
    at Ezsp.getMulticastTableEntry (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/ezsp.ts:542:21)
    at Multicast._initialize (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/multicast.ts:30:27)
    at Multicast.startup (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/multicast.ts:42:9)
    at Driver.startup (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/driver.ts:276:9)
    at Controller.start (/app/node_modules/zigbee-herdsman/src/controller/controller.ts:129:29)
    at Zigbee.start (/app/lib/zigbee.ts:63:27)
    at Controller.start (/app/lib/controller.ts:139:27)
    at start (/app/index.js:154:5)
[09:55:31] INFO: Preparing to start...
[09:55:31] INFO: Socat not enabled
[09:55:31] INFO: Starting Zigbee2MQTT...
Starting Zigbee2MQTT without watchdog.
[2024-08-01 09:55:32] info: 	z2m: Logging to console, file (filename: log.log)
[2024-08-01 09:55:32] info: 	z2m: Starting Zigbee2MQTT version 1.39.0 (commit #unknown)
[2024-08-01 09:55:32] info: 	z2m: Starting zigbee-herdsman (0.50.1)
[2024-08-01 09:55:33] warning: 	zh:ezsp: Deprecated driver 'ezsp' currently in use, 'ember' will become the officially supported EmberZNet driver in next release. If using Zigbee2MQTT see https://github.com/Koenkk/zigbee2mqtt/discussions/21462
[2024-08-01 09:55:45] error: 	zh:ezsp:uart: Port error: Error: read ECONNRESET
Error: Failure to connect
    at SerialDriver.resetForReconnect (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/ezsp.ts:347:19)
    at SerialDriver.emit (node:events:517:28)
    at SerialDriver.onPortClose (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/uart.ts:393:18)
    at Object.onceWrapper (node:events:632:26)
    at Socket.emit (node:events:517:28)
    at TCP.<anonymous> (node:net:350:12)

Can someone help me with how to solve or debug this?

Issue 2 is with Z2M2:
This coordinator is installed in a different floor in my house, and also connect by LAN cable to the home network.

This coordinator connected to something like 20 devices - motion, presence, temp, button switches, contact etc.

Unlike Z2M1, surprisingly it does not have any connectivity issues or hangs like Z2M1!

But its same device, and even though its LAN connection to the home network is even “longer” then Z2M1 (since they are in different house floors) its very stable in that perspective.

But the issue i see here sometimes is that zigbee sensors stops updating their status. I only spot this if I actively login in HA UI and see in dashboard for example outdoor temperature sensor reporting flat value for few hours

example screen shot how i detect it

In the addon log of Z2M2 - nothing…
If I restart manually Z2M2 - problem is solved until it happens next time
it can work ok for days and then it can happen again
I don’t have any good automation to detect this automatically
any idea how to debug this issue as well is appreciated

[francisp (Francis)]

@shaikedem

both Mac and coordinator) and both are practically 10cmm within each other.

Move the coordinator at least a half meter away from the Mac.

[shaikedem]

I tried this already
I put in in another room in same floor
same behavior though …

[Floppymonster]

The first problem, definitely try what francisp suggests, get some free space around the Z2M1 coordinator.

The second problem, I would like to know:

• Does it happen on 1 sensor specifically
  – If yes: sensor error?
  – If no: are the other sensors it happens on all the same type/brand?
  — if yes: Maby the sensors all have the same bug, is there an OTA available?
  — if no: Probably a problem with the coordinator, can you get an update or try a different brand?

And a question out of curiosity, why do you use multiple z2m instances anyway, why not just one zigbee network/coordinator?

[shaikedem]

hi thank you for your reply
Ill try move the coordinator again. BTW , if its near a Wifi access point could that also hinder its operation?

for your suggestions:

1. I noticed the problem in sensors that report changing data overtime. in my case the only thing i can monitor easily is temperature since tis changing over the day so its easy to detect.
   But i also saw it happen in door / presence contact sensors, when i opened the door and sensor reported it closed
   There is no error in Z2M log or sensor AFAIK. it just stays flat data. Also - how can check for sensor errors besides Z2M logs ?

2. Sensors were purchased at different times long before i had HA, they are all basic tuya zigbee sensors, they worked well under tuya cloud app, using tuya zigbee coordinator. I never saw flat temp reported for example.

3. I am not aware of OTA to these sensors. not sure how to check it as well. They are relatively cheap tuya devices bought from Ali Express different sellers overtime

4. Different brand ethernet based coordinator - I purchased something that was recommended in various HA guides.
   will glad to have recommendations for something else
   I will check for tasmota f/w and OTA updates for the ones I got

for your question about multiple instances:
I have a house with 3 main floors which is narrow and long
not good reception of Wifi/Zigbee between floors , i am using several wifi access points devices connected via LAN cabling to my home network at LAN ports which were pre-installed at time of building the house.

i don’t have a lot of good places for repeaters. My Z2M1 devices are in my work room in basement, with closed doors hardly a reception there of wifi

anyway, issue one on Z2M1 existed before I installed the 2nd instance of Z2M2.

[francisp (Francis)]

@shaikedem

if its near a Wifi access point could that also hinder its operation?

Yes. Wifi interference is bad for Zigbee

There is new firmware here:

GitHub - xsp1989/zigbeeFirmware

[shaikedem]

thanks!
how do i do OTA update to this new version?
is there special install procedure?

[shaikedem]

one more thing about Z2M1 connection errors
AFAIU, the addon of Z2M uses TCP to connect to the coordinator
since both Ha and the coordinator are using LAN, the connections errors I see could not because of Wifi / Zigbee networks in that area? its not supposed to interfere with LAN cabling?

[francisp (Francis)]

See here for flashing instructions:

EmberZNet 7.3.2.0/7.4.0.0 firmware

[francisp (Francis)]

Read this:

Zigbee networks: how to guide for avoiding interference + optimize using Zigbee Router devices (repeaters/extenders) to get a stable mesh network with best possible range and coverage

Who is this guide for? I have tried to make this guide to be a comprehensive collection of the most basic yet essential tips with a set of actions and best practice steps that should be applicable to all types of Zigbee setups, regardless of what type of Zigbee adapter/gateway/hub/bridge/devices that you are using. This guide is meant for both those who are new to Zigbee as well as those who been using Zigbee devices for years but might not been aware of the underlying prerequisites to optimiz…

[shaikedem]

thanks i will try that
i have nothing to loose, right?
if it goes badly in the process, i can always restore the original f/w with config reset ?

[shaikedem]

Hi
so I upgraded both Z2M1 and Z2M2 with OTA
Indeed the issues of connectivity with Z2M1 seems to disappear and much less frequent - Thank you!

But I need to keep monitoring this for few days to say its good

But Problem in Z2M2 of sensors not updating keeps popping up
Its in various sensors now - contact, temp, power monitoring. Each time different sensors.
like a virus its spreading …
It started about 2 weeks ago - I dont recall anything special in Z2M2 devices done
any idea how to debug it? in Tasmota console, Z2M device console, or in HA ?
while not updating, the sensors shows its valid …
shall I try to remove sensors?

[francisp (Francis)]

Do they update in the Z2M frontend ?

[shaikedem]

no
I keep getting old values there
but its never shown as offline
if i try to turn on/off for example a power monitoring switch , it will not do anything
i now see this error in Z2M device log after trying to refresh the power status

error 2024-08-02 11:43:57z2m: Publish 'get' 'state' to 'Tuya_Plug2_Washer' failed: 'Error: ZCL command 0xa4c138370ed73cf3/1 genOnOff.read(["onOff"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Timeout - 47721 - 1 - 81 - 6 - 1 after 10000ms)'

[francisp (Francis)]

This error happens when the device does not respond to the coordinator. Could it be that these devices are out of range?

[shaikedem]

no, they are in range
they worked very well until few days ago
ill try to re-add them to Z2M

[Floppymonster]

Do you have enough lightbulbs/Zigbee repeaters, or mainly battery-powered sensors that are only endpoints?

As for suggestions, I have no experience with Ethernet-based Zigbee coordinators. I use USB dongles that I attach to my Home Assistant computer. I just switched over from a Sonoff dongle to the Home Assistant SkyConnect and am quite happy with it so far. (The Sonoff is great as well, but as I’m migrating, I needed two dongles at the same time and I wanted to support Home Assistant).

Even though they are simple USB dongles, they are more expensive than the Ethernet coordinator you linked. I would think the Ethernet coordinators are more complex and should be more expensive? Maybe it is a quality issue with the coordinator?

[shaikedem]

yes, i have several power plugs that act as repeaters
total of 20 devices are on this zigbee network
the thing is everything worked well until few days ago, all sensors reported ok
not sure what happened, now some of them (temp, contact, power monitor) stop
reporting with no apparent reason
I had troubles setting USB dongle zigbee stick - I run HA on UTM hypervisor on Mac, and apparently the USB sticker driver is having issues on MAC, its not detected well by Mac or the hypervisor
also, my HA machine is in basement currently, a USB stick will only cover wel the basement,
so I have to have several coords on network in order to cover my house floors

[francisp (Francis)]

Neighbour changed Wifi channel ?

[shaikedem]

i did zigbee map scan
it took a while, and not all sensors got reported - not sure why
I was able before to do full map
it looks odd as it shows all sensors connected to coordinator directly, while in past they used repeaters/plugs

smart plug 4 is midway between floors and used to bridge between coord on 1st floor to washer/dryer plugs in 2nd floor
not sure how i can control this?