Zigbee2MQTT: no frontend (other than onboardoing)

I installed Zigbee2MQTT to drive a second ZIgbee network (the main one is ZHA). The add-on shows it’s runnin:

Starting Zigbee2MQTT without watchdog.
Onboarding page is available at http://0.0.0.0:8099/
[14:02:45] INFO: Preparing to start...
[14:02:45] INFO: Socat not enabled
[14:02:46] INFO: Starting Zigbee2MQTT...
Starting Zigbee2MQTT without watchdog.
Onboarding page is available at http://0.0.0.0:8099/```

But I don't get the frontend, it always shows the same Onboarding page, but not the one where I (supposedly) can permit devices to connect

The add-on config:

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:
server: mqtt://localhost:1883
serial:
port: tcp://192.168.0.6:6638
baudrate: 115200
adapter: ember
disable_led: false
advanced:
transmit_power: 20
frontend:
enabled: true



HA does see the SLZB-06M device (under Devicec and Services) and I can also talk to the 06M directly via the IP port


My MQTT integration shows 


core-mosquitto
No devices or entities


WHat am I missing?

Did you go through onboarding already ? And check if you can connect to Mosquitto without user and password.

Yes, The device was not shown (and now that field cannot even be edited),




Starting Zigbee2MQTT without watchdog.
Onboarding page is available at http://0.0.0.0:8099/
[15:20:21] INFO: Preparing to start...
[15:20:21] INFO: Socat not enabled
[15:20:21] INFO: Starting Zigbee2MQTT...
Starting Zigbee2MQTT without watchdog.
Onboarding page is available at http://0.0.0.0:8099/```


But when i try to access the frontend from the sidebar, it shows the same onboarding message again

Apparently not. I installed MQTT explorer and get these errors

[16:02:57] INFO: Successfully send service information to the Supervisor.
2025-06-22 16:03:00: New connection from 192.168.0.115:34307 on port 1883.
2025-06-22 16:03:00: New client connected from 192.168.0.115:34307 as 2WBBeQcN3Pt9u8F7w0v3af (p2, c1, k60, u'homeassistant').
2025-06-22 16:03:02: New connection from 172.30.32.1:48728 on port 1883.
error: received null username or password for unpwd check
2025-06-22 16:03:02: Client mqtt-explorer-8d4e1514 disconnected, not authorised.
time="2025-06-22T16:03:05+08:00" level=error msg="http request error: Post \"http://127.0.0.1:80/superuser\": read tcp 127.0.0.1:34612->127.0.0.1:80: read: connection reset by peer"
2025-06-22 16:03:33: New connection from 172.30.32.1:49340 on port 1883.
2025-06-22 16:03:33: Client mqtt-explorer-8d4e1514 disconnected, not authorised.
2025-06-22 16:04:23: New connection from 172.30.32.1:51316 on port 1883.
2025-06-22 16:04:23: Client mqtt-explorer-8d4e1514 disconnected, not authorised.
 Live

when trying to connect:

The broker config is

Create a MQTT user with password in HA, then add that user to the Zigbee2MQTT configuration.

Done that, but no change:

socat: (do I need that? It’s set to false)

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:

server: mqtt://localhost:1883
user: ha-mqtt
password: $vXREADCTED&-JK

And the config of the MQTT broker is

logins: []
require_certificate: false
certfile: fullchain.pem
keyfile: privkey.pem
customize:
  active: false
  folder: mosquitto

But i thought the config was to require ‘no userid and password’?

Also now I get

Starting Zigbee2MQTT without watchdog.
[2025-06-22 19:55:00] info: 	z2m: Logging to console, file (filename: log.log)
[2025-06-22 19:55:00] info: 	z2m: Starting Zigbee2MQTT version 2.4.0 (commit #unknown)
[2025-06-22 19:55:00] info: 	z2m: Starting zigbee-herdsman (4.1.0)
[2025-06-22 19:55:01] info: 	zh:ember: Using default stack config.
[2025-06-22 19:55:01] info: 	zh:ember: ======== Ember Adapter Starting ========
[2025-06-22 19:55:01] info: 	zh:ember:ezsp: ======== EZSP starting ========
[2025-06-22 19:55:01] info: 	zh:ember:uart:ash: ======== ASH Adapter reset ========
[2025-06-22 19:55:01] info: 	zh:ember:uart:ash: Socket ready
[2025-06-22 19:55:01] info: 	zh:ember:uart:ash: ======== ASH starting ========
[2025-06-22 19:55:01] error: 	zh:ember:uart:ash: Port Error: read ECONNRESET
[2025-06-22 19:55:01] info: 	zh:ember:uart:ash: Port closed.
[2025-06-22 19:55:03] info: 	zh:ember:uart:ash: ======== ASH Adapter reset ========
[2025-06-22 19:55:03] info: 	zh:ember:uart:ash: Socket ready
[2025-06-22 19:55:03] info: 	zh:ember:uart:ash: ======== ASH starting ========
[2025-06-22 19:55:04] error: 	zh:ember:uart:ash: Port Error: read ECONNRESET
[2025-06-22 19:55:04] info: 	zh:ember:uart:ash: Port closed.
[2025-06-22 19:55:06] info: 	zh:ember:uart:ash: ======== ASH Adapter reset ========
[2025-06-22 19:55:06] info: 	zh:ember:uart:ash: Socket ready
[2025-06-22 19:55:06] info: 	zh:ember:uart:ash: ======== ASH starting ========
[2025-06-22 19:55:06] error: 	zh:ember:uart:ash: Port Error: read ECONNRESET
[2025-06-22 19:55:06] info: 	zh:ember:uart:ash: Port closed.
[2025-06-22 19:55:08] info: 	zh:ember:uart:ash: ======== ASH Adapter reset ========
[2025-06-22 19:55:08] info: 	zh:ember:uart:ash: Socket ready
[2025-06-22 19:55:08] info: 	zh:ember:uart:ash: ======== ASH starting ========
[2025-06-22 19:55:09] error: 	zh:ember:uart:ash: Port Error: read ECONNRESET
[2025-06-22 19:55:09] info: 	zh:ember:uart:ash: Port closed.
[2025-06-22 19:55:11] info: 	zh:ember:uart:ash: ======== ASH Adapter reset ========
[2025-06-22 19:55:11] info: 	zh:ember:uart:ash: Socket ready
[2025-06-22 19:55:11] info: 	zh:ember:uart:ash: ======== ASH starting ========
[2025-06-22 19:55:12] error: 	zh:ember:uart:ash: Port Error: read ECONNRESET
[2025-06-22 19:55:12] info: 	zh:ember:uart:ash: Port closed.
[2025-06-22 19:55:13] error: 	z2m: Error while starting zigbee-herdsman
[2025-06-22 19:55:13] error: 	z2m: Failed to start zigbee-herdsman
[2025-06-22 19:55:13] error: 	z2m: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start_crashes-runtime.html for possible solutions
[2025-06-22 19:55:13] error: 	z2m: Exiting...
[2025-06-22 19:55:13] error: 	z2m: Error: Failed to start EZSP layer with status=HOST_FATAL_ERROR.
    at EmberAdapter.initEzsp (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/adapter/ember/adapter/emberAdapter.ts:666:19)
    at EmberAdapter.start (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/adapter/ember/adapter/emberAdapter.ts:1548:24)
    at Controller.start (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/controller/controller.ts:133:29)
    at Zigbee.start (/app/lib/zigbee.ts:71:27)
    at Controller.start (/app/lib/controller.ts:102:13)
    at start (/app/index.js:149:5)

My SLZB-06M is running firmware v2.9.2, if I switch from ember to EZSP I don’t get the serrors but a message that that driver is only for older firmware?

Ok. i read somewhere that 2.9 is not working well, aso i downgraded to 2.7.1 but the same. With Ember or ezsp.

[2025-06-22 20:24:03] error: 	z2m: Exiting...
[2025-06-22 20:24:03] error: 	z2m: Error: Failed to start EZSP layer with status=HOST_FATAL_ERROR.
    at EmberAdapter.initEzsp (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/adapter/ember/adapter/emberAdapter.ts:666:19)
    at EmberAdapter.start (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/adapter/ember/adapter/emberAdapter.ts:1548:24)
    at Controller.start (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/controller/controller.ts:133:29)
    at Zigbee.start (/app/lib/zigbee.ts:71:27)
    at Controller.start (/app/lib/controller.ts:102:13)
    at start (/app/index.js:149:5)
[20:25:21] INFO: Preparing to start...
[20:25:21] INFO: Socat not enabled
[20:25:22] INFO: Starting Zigbee2MQTT...

with EZSP:

Starting Zigbee2MQTT without watchdog.
[2025-06-22 20:25:22] info: 	z2m: Logging to console, file (filename: log.log)
[2025-06-22 20:25:23] info: 	z2m: Starting Zigbee2MQTT version 2.4.0 (commit #unknown)
[2025-06-22 20:25:23] info: 	z2m: Starting zigbee-herdsman (4.1.0)
[2025-06-22 20:25:23] warning: 	zh:ezsp: 'ezsp' driver is deprecated and will only remain to provide support for older firmware (pre 7.4.x). Migration to 'ember' is recommended. If using Zigbee2MQTT see https://github.com/Koenkk/zigbee2mqtt/discussions/21462
[2025-06-22 20:25:23] error: 	zh:ezsp:uart: Port error: Error: read ECONNRESET
/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/ezsp.ts:343
            throw new Error("Failure to connect");
                  ^
Error: Failure to connect
    at SerialDriver.resetForReconnect (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/ezsp.ts:343:19)
    at SerialDriver.emit (node:events:518:28)
    at SerialDriver.onPortClose (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/uart.ts:396:18)
    at Object.onceWrapper (node:events:633:26)
    at Socket.emit (node:events:518:28)
    at TCP.<anonymous> (node:net:351:12)

Your mosquitto.conf file should have allow_anonymous true to allow no uid/pass

Are you sure ZHA (zigbee home automation) is not running.

Thanks. I didn’t find that mentioned in any of the guides.

Sorry, but what does that have to do with it? I selected Zigbe2MQTT especially for the second Zigbee network, as I already have one running under ZHA

I am also not sure what you are saying, whether ZHA should or should NOT be running to make the Zigbee2MQTT work??

It’s not ideal to have ZHA and Z2M run simultaneously. It requires advanced setup skills and unnecessary for most use cases.

You’ll run into port conflicts, channel and device interference(especially with multiple USB devices), and a list of other issues.

  1. Can you elaborate a little on why you are choosing to run two ZigBee coordinators/networks from the same HA device?

  2. How many of your devices are repeaters vs end devices?

ZigBee is a mesh network and uses repeaters to extend the network’s range to include coverage for thousands of square ft/m.

**On a side note…**You can run multiple instances of Z2M

Because that error is often caused by ZHA trying to access the same port.

We are on the same page!

We are on the same page!