i only have few sensors with Z2M1. I did all of them
1 failed to re- interview
another paired but i keep getting errors on connections and its status is “unknown”
You’ve powered off the other coordinator and disabled that instance of Z2M?
No, I will try This
tried it but it didnt help for adding the last sensor
I will keep looking into this
Ill check now with moving zigbee channel of Z2M2
So …
For Z2M1 - i thought the problem of coord disconnects and hang disappeared after upgrade to f/w
now it came back, i get Z2M1 addon hang often
Its possible this coordinator is faulty, I will try to check this with friends
what i dont understand is how this addon works - lets assume it has temp disconnections, why would the addon hang and stop? its TCP connection to the coord, its supposed to have some fault tolerance and re-open connection without addon being stopped
furthermore, the addon is configured to be auto restart with watchdog - yet it does not seems to happen. I had to write my own automation to restart it
see pic of config
log from when it fails
[2024-08-03 08:00:23] error: zh:ezsp:uart: --> Error: Error: {"sequence":2} after 4000ms
[2024-08-03 08:00:23] error: zh:ezsp:uart: -!- break waiting (2)
[2024-08-03 08:00:23] error: zh:ezsp:uart: Can't send DATA frame (1,7,0): 3100010500
[2024-08-03 08:00:27] error: zh:ezsp:uart: --> Error: Error: {"sequence":2} after 4000ms
[2024-08-03 08:00:27] error: zh:ezsp:uart: -!- break rewaiting (2)
[2024-08-03 08:00:27] error: zh:ezsp:uart: Can't resend DATA frame (1,7,1): 3100010500
[2024-08-03 08:00:27] error: zh:ezsp:ezsp: Watchdog heartbeat timeout Error: Failure send nop:{"type":"Buffer","data":[49,0,1,5,0]}
at /app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/ezsp.ts:675:23
at Queue.execute (/app/node_modules/zigbee-herdsman/src/utils/queue.ts:35:20)
at Ezsp.watchdogHandler (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/ezsp.ts:781:13)
[2024-08-03 08:00:53] error: zh:ezsp:uart: Port error: Error: read ECONNRESET
[2024-08-03 08:00:57] error: zh:ezsp:uart: --> Error: Error: {"sequence":4} after 4000ms
[2024-08-03 08:00:57] error: zh:ezsp:uart: -!- break waiting (4)
[2024-08-03 08:00:57] error: zh:ezsp:uart: Can't send DATA frame (3,7,0): 2b00010500
[2024-08-03 08:01:01] error: zh:ezsp:uart: --> Error: Error: {"sequence":4} after 4000ms
[2024-08-03 08:01:01] error: zh:ezsp:uart: -!- break rewaiting (4)
[2024-08-03 08:01:01] error: zh:ezsp:uart: Can't resend DATA frame (3,7,1): 2b00010500
[2024-08-03 08:01:01] error: zh:ezsp:ezsp: Watchdog heartbeat timeout Error: Failure send nop:{"type":"Buffer","data":[43,0,1,5,0]}
at /app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/ezsp.ts:675:23
at Queue.execute (/app/node_modules/zigbee-herdsman/src/utils/queue.ts:35:20)
at Ezsp.watchdogHandler (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/ezsp.ts:781:13)
[2024-08-03 08:01:12] error: zh:ezsp:uart: Port error: Error: read ECONNRESET
[2024-08-03 08:01:16] error: zh:ezsp:uart: --> Error: Error: {"sequence":1} after 4000ms
[2024-08-03 08:01:16] error: zh:ezsp:uart: -!- break waiting (1)
[2024-08-03 08:01:16] error: zh:ezsp:uart: Can't send DATA frame (0,0,0): 00000004
[2024-08-03 08:01:17] 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:341:19)
at SerialDriver.emit (node:events:517:28)
at SerialDriver.onPortClose (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/uart.ts:389:18)
at Object.onceWrapper (node:events:632:26)
at Socket.emit (node:events:517:28)
at TCP.<anonymous> (node:net:350:12)
[08:10:00] INFO: Preparing to start...
Double check if your coordinator is using the ethernet port or Wifi. It should not broadcast a Wifi signal.
And if you upgraded the Zigbee firmware to 7.4, you can change the Zigbee2MQTT configuration to ember
Replace
adapter: ezsp
with
adapter: ember
1 Like
the gateway supports connecting with both ethernet and wifi
I never configured wifi for it. My assumption its entering to some wifi router mode for first connect and stays that way. I dont know how to disable it
see pic from tasmota config screen
i changed interface to embr, now checking overtime to see how it behaves
In the Tasmota console:
Wifi 0
backlog rule2 on system#boot do Wifi 0 endon ; rule2 1
1 Like
Hi
Updating that since switching the adapter to ember , the errors in Z2M1 completely stopped! thank you @francisp ! You are the Z2M master!
i still get occasional connections errors msgs in Z2M1 logs, but it does not fail the Z2M1 instance addon like bofore.
I modified both Z2M1 and Z2M2 to use ember
Z2M1 is now using channel 15 and Z2M2 I kept for now at channel 11
I am still monitoring Z2M2 for sensors who stopped updating.
While at first i thought it was just for sensors with low linkquality,
I saw it happening also for sensors that are very in within good range of Z2M2 coordinator
For example I have 2 temp sensors, both on same floor as Z2M2 coord and in range of 4-5 meters and have direct LOS to the coord. So it does not make sense its related to range
And as I posted in past, restarting the Z2M2 addon would cause the sensors to start updating again, so it looks like some s/w issue (either in HA or in the coord/sensors) but i cant put the finger on exact cause
Will keep monitoring
Hi there, i had the similar issue about connecting ethanet zigbee gateway. i have trouble setting up the the Zigbee2MQTT configuration
can anyone share the Zigbee2MQTT coordinator configuration setting?
i had the similar issue about connecting ethanet zigbee gateway. i have trouble setting up the the Zigbee2MQTT configuration
can you share the coordinator configuration setting?
What ethernet coordinator do you have?
i am using this one, QIACHIP matter zigbee bridge hub. already tried all the method to bridge the coordinator to HA system, but I cant find a way to connect the HA server
do you mean the zigbee2mqtt official website? I tried that configuration but i fail to start the add-on.
[21:03:45] INFO: Preparing to start...
[21:03:45] INFO: Socat not enabled
[21:03:46] INFO: Starting Zigbee2MQTT...
Starting Zigbee2MQTT without watchdog.
[2024-09-20 21:03:47] info: z2m: Logging to console, file (filename: log.log)
[2024-09-20 21:03:47] info: z2m: Starting Zigbee2MQTT version 1.40.1 (commit #unknown)
[2024-09-20 21:03:47] info: z2m: Starting zigbee-herdsman (0.57.3)
[2024-09-20 21:03:48] info: zh:ember: Using default stack config.
[2024-09-20 21:03:48] info: zh:ember: ======== Ember Adapter Starting ========
[2024-09-20 21:03:48] info: zh:ember:ezsp: ======== EZSP starting ========
[2024-09-20 21:03:48] info: zh:ember:uart:ash: ======== ASH Adapter reset ========
[2024-09-20 21:03:48] info: zh:ember:uart:ash: RTS/CTS config is off, enabling software flow control.
[2024-09-20 21:03:48] info: zh:ember:uart:ash: ASH COUNTERS since last clear:
[2024-09-20 21:03:48] info: zh:ember:uart:ash: Total frames: RX=0, TX=0
[2024-09-20 21:03:48] info: zh:ember:uart:ash: Cancelled : RX=0, TX=0
[2024-09-20 21:03:48] info: zh:ember:uart:ash: DATA frames : RX=0, TX=0
[2024-09-20 21:03:48] info: zh:ember:uart:ash: DATA bytes : RX=0, TX=0
[2024-09-20 21:03:48] info: zh:ember:uart:ash: Retry frames: RX=0, TX=0
[2024-09-20 21:03:48] info: zh:ember:uart:ash: ACK frames : RX=0, TX=0
[2024-09-20 21:03:48] info: zh:ember:uart:ash: NAK frames : RX=0, TX=0
[2024-09-20 21:03:48] info: zh:ember:uart:ash: nRdy frames : RX=0, TX=0
[2024-09-20 21:03:48] info: zh:ember:uart:ash: CRC errors : RX=0
[2024-09-20 21:03:48] info: zh:ember:uart:ash: Comm errors : RX=0
[2024-09-20 21:03:48] info: zh:ember:uart:ash: Length < minimum: RX=0
[2024-09-20 21:03:48] info: zh:ember:uart:ash: Length > maximum: RX=0
[2024-09-20 21:03:48] info: zh:ember:uart:ash: Bad controls : RX=0
[2024-09-20 21:03:48] info: zh:ember:uart:ash: Bad lengths : RX=0
[2024-09-20 21:03:48] info: zh:ember:uart:ash: Bad ACK numbers : RX=0
[2024-09-20 21:03:48] info: zh:ember:uart:ash: Out of buffers : RX=0
[2024-09-20 21:03:48] info: zh:ember:uart:ash: Retry dupes : RX=0
[2024-09-20 21:03:48] info: zh:ember:uart:ash: Out of sequence : RX=0
[2024-09-20 21:03:48] info: zh:ember:uart:ash: ACK timeouts : RX=0
[2024-09-20 21:03:48] info: zh:ember:uart:ash: ======== ASH stopped ========
[2024-09-20 21:03:48] error: zh:ember:uart:ash: Failed to init port with error Error: Error: No such file or directory, cannot open tcp://192.168.1.89
[2024-09-20 21:03:48] error: z2m: Error while starting zigbee-herdsman
[2024-09-20 21:03:48] error: z2m: Failed to start zigbee
[2024-09-20 21:03:48] error: z2m: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html for possible solutions
[2024-09-20 21:03:48] error: z2m: Exiting...
[2024-09-20 21:03:48] error: z2m: Error: Failed to start EZSP layer with status=HOST_FATAL_ERROR.
at EmberAdapter.initEzsp (/app/node_modules/zigbee-herdsman/src/adapter/ember/adapter/emberAdapter.ts:701:19)
at EmberAdapter.start (/app/node_modules/zigbee-herdsman/src/adapter/ember/adapter/emberAdapter.ts:1708:24)
at Controller.start (/app/node_modules/zigbee-herdsman/src/controller/controller.ts:138:29)
at Zigbee.start (/app/lib/zigbee.ts:64:27)
at Controller.start (/app/lib/controller.ts:140:27)
at start (/app/index.js:154:5)
I don’t think you can add this one to HA as a Zigbee coordinator. With a bit of luck maybe as a Matter OTBR.
1 Like
Should probably be tcp://192.168.1.89:8888
2 Likes
thanks for the advice Francis 
no luck for me tho.
you are right, this coordinator can only be zigbee coordinator, i just don’t understand why the product support matter protocol for.
-----------------------------------------------------------
Add-on: OpenThread Border Router
OpenThread Border Router add-on
-----------------------------------------------------------
Add-on version: 2.10.0
You are running the latest version of this add-on.
System: Home Assistant OS 13.1 (aarch64 / raspberrypi5-64)
Home Assistant Core: 2024.9.2
Home Assistant Supervisor: 2024.09.1
-----------------------------------------------------------
Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
s6-rc: info: service banner successfully started
s6-rc: info: service universal-silabs-flasher: starting
[22:26:21] INFO: The selected serial port is not a USB device.
[22:26:21] WARNING: No firmware found for the selected device, assuming firmware is installed.
s6-rc: info: service universal-silabs-flasher successfully started
s6-rc: info: service otbr-agent: starting
[22:26:21] INFO: Setup OTBR firewall...
[22:26:21] INFO: Starting otbr-agent...
open uart failed: Device or resource busy
[NOTE]-AGENT---: Running 0.3.0-b66cabf-dirty
[NOTE]-AGENT---: Thread version: 1.3.0
open uart failed: Device or resource busy
[NOTE]-AGENT---: Thread interface: wpan0
open uart failed: Device or resource busy
[NOTE]-AGENT---: Radio URL: spinel+hdlc+uart:///dev/ttyAMA10?uart-baudrate=115200&uart-flow-control
[NOTE]-AGENT---: Radio URL: trel://end0
[NOTE]-ILS-----: Infra link selected: end0
25d.08:48:49.654 [C] Platform------: Init() at spinel_driver.cpp:70: Failure
[22:26:21] WARNING: otbr-agent exited with code 1 (by signal 0).
Chain OTBR_FORWARD_INGRESS (0 references)
target prot opt source destination
DROP all -- anywhere anywhere PKTTYPE = unicast
DROP all -- anywhere anywhere match-set otbr-ingress-deny-src src
ACCEPT all -- anywhere anywhere match-set otbr-ingress-allow-dst dst
DROP all -- anywhere anywhere PKTTYPE = unicast
ACCEPT all -- anywhere anywhere
otbr-ingress-deny-src
otbr-ingress-deny-src-swap
otbr-ingress-allow-dst
otbr-ingress-allow-dst-swap
Chain OTBR_FORWARD_EGRESS (0 references)
target prot opt source destination
ACCEPT all -- anywhere anywhere
[22:26:21] INFO: OTBR firewall teardown completed.
s6-svlisten1: fatal: /run/s6-rc/servicedirs/otbr-agent failed permanently or its supervisor died
s6-rc: warning: unable to start service otbr-agent: command exited 1
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service universal-silabs-flasher: stopping
s6-rc: info: service mdns: stopping
/run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information.
/run/s6/basedir/scripts/rc.init: fatal: stopping the container.
Default: mDNSResponder (Engineering Build) (Aug 26 2024 16:52:48) stopping
s6-rc: info: service universal-silabs-flasher successfully stopped
s6-rc: info: service banner: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service banner successfully stopped
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
[22:26:21] INFO: mDNS ended with exit code 4 (signal 0)...
s6-rc: info: service mdns successfully stopped
Tried, HA can not find the coordinator. Tried with ember and ezsp. Still can’t 