Cod.m ZigBee Coordinator - LAN - Z2M

RKsHAss · July 10, 2024, 5:35am

Hi,

does anyone have the above running under HA? i want to replace SonoffDongle 3 with z2m.

Is it possible to run 2 coordinators at the same time? Will the mqtt entities be retained after a coordinator switch?
The coordinator runs as zstack not es ezsp, how to change it

cod.mSupport is not very helpful and only sends me links to the videos
The error before I have undone everything

zh:ezsp:ezsp: Connection attempt 2 error: Error: connect ECONNREFUSED 172.30.32.1:9999

no idea where the 127.30.32.1:9999 came from

LOG:

[CODE][13:17:06] INFO: Preparing to start…

[13:17:07] INFO: Socat not enabled

[13:17:09] INFO: Starting Zigbee2MQTT…

Starting Zigbee2MQTT without watchdog.

[2024-07-09 13:17:17] info: z2m: Logging to console, file (filename: log.log)

[2024-07-09 13:17:17] info: z2m: Starting Zigbee2MQTT version 1.39.0 (commit #unknown)

[2024-07-09 13:17:17] info: z2m: Starting zigbee-herdsman (0.50.1)

[2024-07-09 13:17:17] warning: zh:ezsp: Deprecated driver ‘ezsp’ currently in use, ‘ember’ will become the officially supported EmberZNet driver in next release. If using Zigbee2MQTT see Improved Ember (EZSP) driver (experimental) · Koenkk/zigbee2mqtt · Discussion #21462 · GitHub

[2024-07-09 13:17:18] error: zh:ezsp:ezsp: Connection attempt 1 error: Error: connect ECONNREFUSED 172.30.32.1:9999

at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1555:16)

[2024-07-09 13:17:23] error: zh:ezsp:ezsp: Connection attempt 2 error: Error: connect ECONNREFUSED 172.30.32.1:9999

at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1555:16)

[2024-07-09 13:17:33] error: zh:ezsp:ezsp: Connection attempt 3 error: Error: connect ECONNREFUSED 172.30.32.1:9999

at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1555:16)[/CODE]

Config/Yaml

[CODE]data_path: /config/zigbee2mqtt

socat:

enabled: false

master: pty,raw,echo=0,link=/tmp/ttyZ2M,mode=777

slave: tcp-listen:8485,keepalive,nodelay,reuseaddr,keepidle=1,keepintvl=1,keepcnt=5

options: “-d -d”

log: false

mqtt:

base_topic: zigbee2mqtt

user: mqtt

password: mqttxxxx

server: mqtt://192.168.1.155:1883

serial:

port: tcp://192.168.1.150:6638

baudrate: 115200

advanced:

transmit_power: 20[/CODE]

francisp · July 10, 2024, 5:58am

serial:
  port: tcp://192.168.1.150:6638
  adapter: ezsp
  baudrate: 115200

RKsHAss · July 10, 2024, 7:24am

The coordinator runs as zstack not es ezsp, how to change it

and
adapter: zstack does nothing

francisp · July 10, 2024, 7:27am

question was not clear, but if it is this one:

serial:
  port: tcp://192.168.1.150:6638
  adapter: zstack
  baudrate: 115200

RKsHAss · July 10, 2024, 7:34am

thanx, tried it but same errors in the log

[09:32:16] INFO: Preparing to start...
[09:32:16] INFO: Socat not enabled
[09:32:19] INFO: Starting Zigbee2MQTT...
Starting Zigbee2MQTT without watchdog.
[2024-07-10 09:32:25] info: 	z2m: Logging to console, file (filename: log.log)
[2024-07-10 09:32:25] info: 	z2m: Starting Zigbee2MQTT version 1.39.0 (commit #unknown)
[2024-07-10 09:32:25] info: 	z2m: Starting zigbee-herdsman (0.50.1)
[2024-07-10 09:32:26] info: 	zh:zstack:znp: Opening TCP socket with 192.168.1.150:6638
[2024-07-10 09:32:26] info: 	zh:zstack:znp: Socket connected
[2024-07-10 09:32:26] info: 	zh:zstack:znp: Socket ready
[2024-07-10 09:32:26] info: 	zh:zstack:znp: Writing CC2530/CC2531 skip bootloader payload
[2024-07-10 09:32:27] info: 	zh:zstack:znp: Skip bootloader for CC2652/CC1352
[2024-07-10 09:32:45] error: 	z2m: Error while starting zigbee-herdsman
[2024-07-10 09:32:45] error: 	z2m: Failed to start zigbee
[2024-07-10 09:32:45] error: 	z2m: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html for possible solutions
[2024-07-10 09:32:45] error: 	z2m: Exiting...
[2024-07-10 09:32:45] error: 	z2m: Error: Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)
    at ZStackAdapter.start (/app/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:101:27)
    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:32:46] INFO: Preparing to start...
[09:32:47] INFO: Socat not enabled
[09:32:49] INFO: Starting Zigbee2MQTT...
Starting Zigbee2MQTT without watchdog.
[2024-07-10 09:32:56] info: 	z2m: Logging to console, file (filename: log.log)
[2024-07-10 09:32:56] info: 	z2m: Starting Zigbee2MQTT version 1.39.0 (commit #unknown)
[2024-07-10 09:32:56] info: 	z2m: Starting zigbee-herdsman (0.50.1)
[2024-07-10 09:32:56] info: 	zh:zstack:znp: Opening TCP socket with 192.168.1.150:6638
[2024-07-10 09:32:56] info: 	zh:zstack:znp: Socket connected
[2024-07-10 09:32:56] info: 	zh:zstack:znp: Socket ready
[2024-07-10 09:32:56] info: 	zh:zstack:znp: Writing CC2530/CC2531 skip bootloader payload
[2024-07-10 09:32:57] info: 	zh:zstack:znp: Skip bootloader for CC2652/CC1352```

francisp · July 10, 2024, 7:38am

See this link : Zigbee2MQTT fails to start | Zigbee2MQTT

Error: `SRSP - SYS - ping after 6000ms`

5 common reasons of this error:

The port of your serial adapter changed. Check this to find out the port of your adapter.
If you are using a CC2530 or CC2531; it is a common issue for this adapter to crash (due to its outdated hardware). Reflashing the firmware should fix the problem. If it happens often consider flashing the source routing firmware
or upgrade to a more powerful adapter.

Your adapter requires additional configuration parameters. Check supported Adapters section to find out if your adapter requires extra parameters (eg. ConBee II / RaspBee II).
Home Assistant’s “Zigbee Home Automation” (ZHA) integration is enabled. Try to disable the ZHA integration and restart the Zigbee2MQTT add-on.
Your hardware adapter is flashed with the router firmware and not with the coordinator firmware.
Your network Zigbee adapter is not accessible over the LAN network

RKsHAss · July 10, 2024, 7:42am

The cod.m zigbee koordinator is connected over LAN

francisp · July 10, 2024, 7:43am

Any of these true ?

RKsHAss · July 10, 2024, 7:48am

ZHA is enabled and serves > 30 devices
But i’ll give it a try

and yes the network zb adapter is accessible

francisp · July 10, 2024, 7:49am

IF ZHA is enabled and tries to use the same Cod.m, Zigbee2MQTT will not start. You could uses your Sonoff dongle with ZHA, and your cod.m with Zigbee2MQTT, or vice versa.

RKsHAss · July 10, 2024, 7:50am

tried it , no changes, but i see in the log

[2024-07-10 09:48:54] info:	zh:zstack:znp: Opening TCP socket with 192.168.1.150:6638
[2024-07-10 09:48:54] info:	zh:zstack:znp: Socket connected
[2024-07-10 09:48:54] info:	zh:zstack:znp: Socket ready
[2024-07-10 09:48:54] info:	zh:zstack:znp: Writing CC2530/CC2531 skip bootloader payload
[2024-07-10 09:48:55] info:	zh:zstack:znp: Skip bootloader for CC2652/CC1352

RKsHAss · July 10, 2024, 8:01am

no for ZHA i’m using the Sonoff Coordinator

RKsHAss · July 10, 2024, 8:04am

no idea why it works now,
ZHA disabled, enabled, HA booted, cod.m reconnected and cod.m zigbee restarted …

thx for your help

now i restored the database.db and all devices must be re-pair-ed, as expected