#One instance of zigbee2mqtt won't Start after update

1 messages · Page 1 of 1 (latest)

icy hearth
#

I have 2 instances of z2mqtt running and one is fine, but one won't start. I'm using the SLZB_06 as a coordinator. Here are the logs from z2mqtt...

[17:41:50] INFO: Socat not enabled
[17:41:50] INFO: Enabled Zigbee2MQTT watchdog with value '1,2,4,8,10'
[17:41:50] INFO: Starting Zigbee2MQTT...
Starting Zigbee2MQTT with watchdog (60000,120000,240000,480000,600000).


Failure page is available at http://0.0.0.0:8099/
[17:49:22] INFO: Preparing to start...
[17:49:22] INFO: Socat not enabled
[17:49:22] INFO: Enabled Zigbee2MQTT watchdog with value '1,2,4,8,10'
[17:49:22] INFO: Starting Zigbee2MQTT...
Starting Zigbee2MQTT with watchdog (60000,120000,240000,480000,600000).
[11-28-2025 17:49:23] info:     z2m: Logging to console, file (filename: log.log)
[11-28-2025 17:49:23] info:     z2m: Starting Zigbee2MQTT version 2.6.3 (commit #unknown)
[11-28-2025 17:49:23] info:     z2m: Starting zigbee-herdsman (6.3.2)
[11-28-2025 17:49:23] info:     zh:zstack:znp: Opening TCP socket with 10.0.0.177:6638
[11-28-2025 17:49:23] error:     zh:zstack:znp: Socket error Error: connect ECONNREFUSED 10.0.0.177:6638
[11-28-2025 17:49:23] error:     z2m: Error while starting zigbee-herdsman
[11-28-2025 17:49:23] error:     z2m: Failed to start zigbee-herdsman
[11-28-2025 17:49:23] error:     z2m: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start_crashes-runtime.html for possible solutions
[11-28-2025 17:49:23] error:     z2m: Exiting...
[11-28-2025 17:49:23] error:     z2m: Error: Error while opening socket
    at Socket.<anonymous> (/app/node_modules/.pnpm/zigbee-herdsman@6.3.2/node_modules/zigbee-herdsman/src/adapter/z-stack/znp/znp.ts:160:24)
    at Socket.emit (node:events:530:35)
    at emitErrorNT (node:internal/streams/destroy:170:8)
    at emitErrorCloseNT (node:internal/streams/destroy:129:3)
    at processTicksAndRejections (node:internal/process/task_queues:90:21)```
#

I'm pulling my hair out with this.

grim wharf
#

What did you update?

icy hearth
grim wharf
#

You could go to http://10.0.0.177 and see if the ip is still valid and restart it and the zigbee module too.

icy hearth
#

The coordinator ip address is valid and I've restarted it.

grim wharf
#

Both SLZB-OS and Zigbee?

icy hearth
#

Yeah, both

grim wharf
#

Try

nc -w3 -vz 10.0.0.177 6638
icy hearth
#

Where would I put that, in the z2mqtt yaml file?

grim wharf
#

Run it via SSH on the server Z2M runs on.

icy hearth
#

I'm lost man. Is that something that I should run from the black screen where you can only enter commands?

grim wharf
#

Yeah it's a command.

#

It checks if the port is reachable/open. If it is not then I'd unplug the coordinator for a moment.

icy hearth
#

I did unplug the coordinator for about 10 seconds already.

#

When I tried to ssh into it with Putty, it says connection refused. I've always had trouble with ssh.

grim wharf
#

You can use the web CLI right now. Otherwise I'd need to see the SSH add-on config,

icy hearth
#

I don't like asking dumb questions man, but how do I get to the web CLI?

grim wharf
#

The terminal should be in the sidebar if you installed the SSH add-on.

icy hearth
#

Can I restore Z2MQTT to the old version?

grim wharf
#

If you have a backup I don't see why not but right now it looks more like the issue is on the coordinator side. Hence why I want to check the command.

icy hearth
#

I brought up the terminal and put in the command and it says ccommand not found

grim wharf
#

Please show me a screenshot.

icy hearth
#

I got it to take and it said operation timed out. I guess that means the port isn't open?

grim wharf
#

I need to see what you see to tell for certain.

icy hearth
#

ok

grim wharf
#

You can also try ping 10.0.0.177.

icy hearth
#

It's receiving data, but how do I stop it from pinging now?

grim wharf
#

CTRL+C.

icy hearth
#

Do you still need to see the other part?

grim wharf
#

I'd like to see all the command outputs.

icy hearth
#

Ok

grim wharf
#

I can't see the ping result here and you wrote the port wrong.

icy hearth
#

I'm sorry, I did...smh

grim wharf
#

Okay so pinging/connectivity works but the port is not listening for some reason.

icy hearth
#

The only thing between the 2nd pic and the 1st, is more ping results.

#

Any ideas?

grim wharf
#

I assume you didn't change anything on the SLZB side until the Z2M error occurred?

icy hearth
#

Correct

grim wharf
#

Can you check and share the mode page in the interface of the SLZB?

icy hearth
#

OK

#

Which mode do you want, the zigbee hub, the dashboard or another one?

grim wharf
#

The whole page basically.

icy hearth
#

It only lets me see one of what I was saying at a time. I can send each, if you need.

grim wharf
#

Either zoom out or do that. I don't really care which method you use.

icy hearth
grim wharf
#

HUB seems wrong. Should be Zigbee Coordinator.

icy hearth
grim wharf
#

If you save, perhaps also reboot/restart, is the nc command now able to connect?

icy hearth
#

I'll check

#

That may have done it. Z2MQTT started and on the coordinator page the Z2M/ZHA button is green now!

grim wharf
#

I just wonder why it was in that HUB mode.

icy hearth
#

Because I screwed up. After it stopped working I was looking around to see what I could do and I changed it thinking that it was just another page to look at...smh.

#

I did have to add something from the github article about breaking changes from the old version to the new one. That was all that I really had to do, at least until I screwed up...lol