Zigbee2mqtt with SLZB-06 Ethernet does not start

deltabert · October 13, 2025, 1:10pm

Hello All,
(Running HAOS on Intel NUC).
I used to have a working Zigbee2MQTT with a SLZB-06 Ethernet coordinator working for more than a year.
But all of a sudden I got errors about the Network Key being not the same as the adapter:active or adapter:preconfigured and adapter:alternate.
I found an post where the author could fix this issue. Followed that but without success.

To be short, I was hopeless and I deleted the Zigbee2MQTT addon AND ALSO the zigbee2mqtt folder (with subfolders) in the HA config directory. and restarted the computer.

So I tried to install Zigbee2MQTT again, following the guide with the SLZB-06 web interface; (BTW i can access te SLZB-06 web interface).

Pay attention, if you use the Z2M addon for HA, it is better to edit Z2M addon yaml configuration file directly (Select the 3 dot menu in the upper right corner → “Edit in YAML”)

serial:

Location of SLZB-06

port: tcp://192.168.178.216:6638
baudrate: 115200
adapter: zstack

Disable green led?

disable_led: false

Set output power to max 20

advanced:
transmit_power: 20

I followed the advice and used the 3-dots menu and used YAML mode.

But when i start zigbee2mqtt i get only this in the log og zigbee2mqtt:

Loading log…

[14:06:48] INFO: Preparing to start…

[14:06:48] INFO: Socat not enabled

[14:06:48] INFO: Starting Zigbee2MQTT…

Starting Zigbee2MQTT without watchdog.

Onboarding page is available at http://0.0.0.0:8099/

[14:08:20] INFO: Preparing to start…

[14:08:20] INFO: Socat not enabled

[14:08:20] INFO: Starting Zigbee2MQTT…

Starting Zigbee2MQTT without watchdog.

Onboarding page is available at http://0.0.0.0:8099/

I tried the same on my ProxMox server with a freshly installed HA and Mosquitto but i got the same rsult.

Please if anyone can shine a light on this, i am already days searching…

fleskefjes · October 13, 2025, 1:55pm

Seems you haven’t done the onboarding. Look at this thread: Getting the Zigbee2MQTT Onboarding

deltabert · October 14, 2025, 8:53am

Thank you @fleskefjes for coming back in my issue. Apreciate it very much.
That link was very helpfull. I was indeed editing the configuration in the z2m add-on page.
Must say, this onboarding is very confusing…

Started al over again; deleted Zigbee2MQTT and everything from file system again. Installed Zigbee2MQTT and followed the on-boarding. That worked partly. In the onboarding i could not specify my mqtt server, user and password. So left it as is and started Z2M.
These fields are preconfigured bur grayed-out. User is addons and password is a large string stars. So I am not able to take this info to add to mu Mosquitto config… Strange

I presses SUBMIT and started z2m and the log seems OK, but when i opend in the sidebar Zigbee2MQTT, i did not see my coordinator (the SLZB-06).
Which should to be the case…

This is the log info:

[10:42:34] INFO: Preparing to start...

[10:42:34] INFO: Socat not enabled

[10:42:34] INFO: Starting Zigbee2MQTT...

Starting Zigbee2MQTT without watchdog.

Onboarding page is available at http://0.0.0.0:8099/

[2025-10-14 10:46:20] info: z2m: Logging to console, file (filename: log.log)

[2025-10-14 10:46:20] info: z2m: Starting Zigbee2MQTT version 2.6.2 (commit #unknown)

[2025-10-14 10:46:20] info: z2m: Starting zigbee-herdsman (6.1.5)

[2025-10-14 10:46:20] info: zh:zstack:znp: Opening TCP socket with 192.168.178.216:6638

[2025-10-14 10:46:20] info: zh:zstack:znp: Socket connected

[2025-10-14 10:46:20] info: zh:zstack:znp: Socket ready

[2025-10-14 10:46:20] info: zh:zstack:znp: Writing CC2530/CC2531 skip bootloader payload

[2025-10-14 10:46:21] info: zh:zstack:znp: Skip bootloader for CC2652/CC1352

[2025-10-14 10:46:49] info: zh:controller: Wrote coordinator backup to '/config/zigbee2mqtt/coordinator_backup.json'

[2025-10-14 10:46:50] info: z2m: zigbee-herdsman started (reset)

[2025-10-14 10:46:50] info: z2m: Coordinator firmware version: '{"meta":{"maintrel":1,"majorrel":2,"minorrel":7,"product":1,"revision":20250325,"transportrev":2},"type":"ZStack3x0"}'

[2025-10-14 10:46:50] info: z2m: Currently 0 devices are joined.

[2025-10-14 10:46:50] info: z2m: Connecting to MQTT server at mqtt://core-mosquitto:1883

[2025-10-14 10:46:50] info: z2m: Connected to MQTT server

[2025-10-14 10:46:50] info: z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/bridge/state', payload '{"state":"online"}'

[2025-10-14 10:46:50] info: z2m: Started frontend on port 8099

[2025-10-14 10:46:50] info: z2m: Zigbee2MQTT started!

[2025-10-14 10:46:55] info: z2m:mqtt: MQTT publish: topic 'homeassistant/binary_sensor/1221051039810110150109113116116_0x00124b002f8e6acd/connection_state/config', payload '{"default_entity_id":"binary_sensor.zigbee2mqtt_bridge_connection_state","device":{"hw_version":"ZStack3x0 20250325","identifiers":["zigbee2mqtt_bridge_0x00124b002f8e6acd"],"manufacturer":"Zigbee2MQTT","model":"Bridge","name":"Zigbee2MQTT Bridge","sw_version":"2.6.2"},"device_class":"connectivity","entity_category":"diagnostic","name":"Connection state","object_id":"zigbee2mqtt_bridge_connection_state","origin":{"name":"Zigbee2MQTT","sw":"2.6.2","url":"https://www.zigbee2mqtt.io"},"payload_off":"offline","payload_on":"online","state_topic":"zigbee2mqtt/bridge/state","unique_id":"bridge_0x00124b002f8e6acd_connection_state_zigbee2mqtt","value_template":"{{ value_json.state }}"}'

I also tried to add my own mqtt-user/password by stopping z2m and in the filesystem opened configuration.yaml.
Replased the mqtt section with this:

mqtt:
    server: '!secret.yaml mqtt_server'
    user: '!secret.yaml mqtt_user'
    password: '!secret.yaml mqtt_password'

And created a secret.yaml file in zigbee2mqtt folder with:

mqtt_server: 'mqtt://localhost:1883'
mqtt_user: hass
mqtt_password: quest3

But that dit not help. Still I can’t find my coordinator in Zigbee2MQTT.

francisp · October 14, 2025, 9:08am

You won’t see it here

only here what coordinator you have

deltabert · October 23, 2025, 3:16pm

Indeed, the coordinator is not seen. My mistake, I just transferred my HA instance from RPI4 to an Intel NUC and finished Z-Wave. With Z-Wave, the coordinator is shown in the UI. And I could not remember if that was also the case in Z2M; but i was mistaken.

I could add devices to my Z2m network, so things are working again!
Next step is to add another SLZB-06M as a Matter over Tread coordinator.

What also helped where 2 video’s from Digiblur on Youtube so I could set the correct WiFi channel in Z2M, not interfering with my normal WiFi.

I would like to thank you both for the help! You realy pointed me in the right direction.

Edit: In the mean time all my zigbee devices are up and running again.
Thank you for pointing me to the Z2M onboarding process
Kind regards, Bert