#New to Zigbee2MQTT

1 messages · Page 1 of 1 (latest)

balmy crypt
#

The recent update broke my ZHA and I've decided to try out Z2M. I'm stuck in an onboarding boot loop though. I've tried to repair this on my own for hours and now turn to you professionals for help.
I have a SLZB-06P10 I am attempting to setup via Z2M. I have checked all the settings in the config file for Z2M and they are correct. However, when I startup Z2M the onboarding comes up and changes my user name and password for the Mosquitto broker.
I'm thinking this is what's breaking? I either get a onboarding loop or an error "Bad Gateway". I can use any advice here, this is driving me mad.

Thank you in advance.

#

[2025-08-09 10:44:15] info: zh:zstack:znp: Opening TCP socket with 10.86.1.4:6638
[2025-08-09 10:44:15] info: zh:zstack:znp: Socket connected
[2025-08-09 10:44:15] info: zh:zstack:znp: Socket ready
[2025-08-09 10:44:15] info: zh:zstack:znp: Writing CC2530/CC2531 skip bootloader payload
[2025-08-09 10:44:15] debug: zh:zstack:unpi:writer: --> buffer [239]
[2025-08-09 10:44:16] info: zh:zstack:znp: Skip bootloader for CC2652/CC1352
[2025-08-09 10:44:16] debug: zh:zstack:znp: --> SREQ: SYS - ping - {"capabilities":1}
[2025-08-09 10:44:16] debug: zh:zstack:unpi:writer: --> frame [254,0,33,1,32]
[2025-08-09 10:44:22] debug: zh:zstack:znp: --> SREQ: SYS - ping - {"capabilities":1}
[2025-08-09 10:44:22] debug: zh:zstack:unpi:writer: --> frame [254,0,33,1,32]
[2025-08-09 10:44:28] debug: zh:zstack:znp: --> SREQ: SYS - ping - {"capabilities":1}
[2025-08-09 10:44:28] debug: zh:zstack:unpi:writer: --> frame [254,0,33,1,32]
[2025-08-09 10:44:34] error: z2m: Error while starting zigbee-herdsman
[2025-08-09 10:44:34] error: z2m: Failed to start zigbee-herdsman
[2025-08-09 10:44:34] error: z2m: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start_crashes-runtime.html for possible solutions
[2025-08-09 10:44:34] error: z2m: Exiting...
[2025-08-09 10:44:34] error: z2m: Error: Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)

#

I'm able to reach the UI via IP though it fails to connect

#

These settings were also copied directly from the SLZB-06P10 control panel

#

SLZB-06P10 set to Zigbee Coordinator

#

Connected via Ethernet

pseudo hazel
#

is ZHA still enabled?

balmy crypt
#

No sir, I deleted it as it came up with an error "Unknown error occurred" and I couldn't figure out the cause.

#

It's currently sitting in settings as an option to add or ignore

#

This occurred after the recent core update

#

I did delete both devices (ZHA and the SLZB-06P10) along with their config files. HA found the SLZB and reinstalled without issue. ZHA still has the same error when I attempted to reinstall and for the life of me can't get Z2M to work 🙂

#

Checking the config after starting up Z2M again, it again reverted my username and password to default

pseudo hazel
#

I suggest power cycling the coordinator

balmy crypt
#

🫡 Doing so now

#

Rebooted and back online

#

Still stuck in a Z2M onboarding loop

#

Something new happened. Restarted the service again and an update for Z2M popped up

#

Did the update no more onboarding loop. Now just an error: "502: Bad Gateway"

#
[2025-08-09 11:05:04] info:     z2m: Logging to console, file (filename: log.log)
[2025-08-09 11:05:05] info:     z2m: Starting Zigbee2MQTT version 2.6.0 (commit #unknown)
[2025-08-09 11:05:05] info:     z2m: Starting zigbee-herdsman (5.0.4)
[2025-08-09 11:05:05] info:     zh:zstack:znp: Opening TCP socket with 10.86.1.4:6638
[2025-08-09 11:05:05] info:     zh:zstack:znp: Socket connected
[2025-08-09 11:05:05] info:     zh:zstack:znp: Socket ready
[2025-08-09 11:05:05] info:     zh:zstack:znp: Writing CC2530/CC2531 skip bootloader payload
[2025-08-09 11:05:06] info:     zh:zstack:znp: Skip bootloader for CC2652/CC1352
[2025-08-09 11:05:24] error:     z2m: Error while starting zigbee-herdsman
[2025-08-09 11:05:24] error:     z2m: Failed to start zigbee-herdsman
[2025-08-09 11:05:24] error:     z2m: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start_crashes-runtime.html for possible solutions
[2025-08-09 11:05:24] error:     z2m: Exiting...
[2025-08-09 11:05:24] error:     z2m: Error: Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)
#

I have confirmed my MQTT broker is running and working as I have other devices using MQTT

balmy crypt
#

Onboarding sees the device /dev/ttyUSB0 but doesn't connect

pseudo hazel
#

that makes no sense. This is an Ethernet coordinator, right?

#

[2025-08-09 11:05:05] info: zh:zstack:znp: Opening TCP socket with 10.86.1.4:6638

balmy crypt
#

Yessir

cyan olive
#

AFAIK it can be used via ethernet, WiFi and USB. Maybe it's in the wrong mode?

balmy crypt
#

Setup as coordinator

#

network showing ethernet

pseudo hazel
#

then this doesn't make sense:

Onboarding sees the device /dev/ttyUSB0 but doesn't connect

balmy crypt
cyan olive
#

Can you try to manually put in the values from here?

balmy crypt
#

This does not allow me to change the values

#

Only copy to clipboard

cyan olive
#

Yeah, copy the port value for example and place it into the field manually.

balmy crypt
#

I understand. Doing so now

pseudo hazel
#

it seems like you have the coordinator plugged into a USB port

balmy crypt
#

I think I know what's happening here.... You just gave me a light bulb. I don't have a PoE switch so I'm using USB-C as power. It is in fact plugged in via USB

#

I'm an idiot :/

#

Moved over to just power via plug

cyan olive
#

I'm guessing it sees the USB chip but there's nothing answering to it because it's in ethernet mode.
I'm also guessing using it manually via tcp:// as above will still work.

balmy crypt
#

It booted back up, no longer found in devices

#

Attempting to add manually

#

Back to onboarding loop

cyan olive
cyan olive
balmy crypt
#

Removed. Restarting service

#

Onboarding again

#
Onboarding page is available at http://0.0.0.0:8099/
[2025-08-09 11:46:39] info:     z2m: Logging to console, file (filename: log.log)
[2025-08-09 11:46:39] info:     z2m: Starting Zigbee2MQTT version 2.6.0 (commit #unknown)
[2025-08-09 11:46:39] info:     z2m: Starting zigbee-herdsman (5.0.4)
[2025-08-09 11:46:39] info:     zh:zstack:znp: Opening TCP socket with 10.86.1.4:6638
[2025-08-09 11:46:39] info:     zh:zstack:znp: Socket connected
[2025-08-09 11:46:39] info:     zh:zstack:znp: Socket ready
[2025-08-09 11:46:39] info:     zh:zstack:znp: Writing CC2530/CC2531 skip bootloader payload
[2025-08-09 11:46:40] info:     zh:zstack:znp: Skip bootloader for CC2652/CC1352
[2025-08-09 11:46:59] error:     z2m: Error while starting zigbee-herdsman
[2025-08-09 11:46:59] error:     z2m: Failed to start zigbee-herdsman
[2025-08-09 11:46:59] error:     z2m: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start_crashes-runtime.html for possible solutions
[2025-08-09 11:46:59] error:     z2m: Exiting...
[2025-08-09 11:46:59] error:     z2m: Error: Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)
    at ZStackAdapter.start (/app/node_modules/.pnpm/zigbee-herdsman@5.0.4/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:114:27)
    at Controller.start (/app/node_modules/.pnpm/zigbee-herdsman@5.0.4/node_modules/zigbee-herdsman/src/controller/controller.ts:134:29)
    at Zigbee.start (/app/lib/zigbee.ts:67:27)
    at Controller.start (/app/lib/controller.ts:101:13)
    at start (/app/index.js:149:5)```
cyan olive
#

I assume the ip is in the same range as your HAOS? Anything in the SLZB log? Coordinator firmware installed?
You can check if you can reach the web and "serial" port with something like this via the SSH addon

nc -w3 -zv 10.86.1.4 80
nc -w3 -zv 10.86.1.4 6638
balmy crypt
#

I don't have the network segregated so yes in range

#

Installing SSH addon

pseudo hazel
#

It says the socket is connected and ready

balmy crypt
#

I go to open the SSH addon and...

pseudo hazel
#

You need to follow the instructions

balmy crypt
#

Sorry, fustration kicking in. I'm reading through the instructions

#

I appreciate your patience 🙂

#

Both commands come back as "open"

cyan olive
#

Yeah as rob pointed out it could connect to it. Unfortunately I don't have any other ideas at the moment.

balmy crypt
#

Ok no problem. I really do appreciate your time.

brisk vortex
#

Hi I got the same problems any news to solve it?

humble robin
#

'Did a reboot of coordinator?

keen bone
#

I have the same loop. Tried restarting, and changing the port