Can't connect any device, but no error logs

[lorenzomartini1]

Hi everyone,
I’d like to describe an issue I’m currently having with Zigbee2MQTT and see if anyone has any ideas.

In my home, I have several automations that trigger when the door opens (for example, indoor cameras switch to privacy mode).
Yesterday, when I got home, I noticed these automations did not trigger. I checked the Zigbee2MQTT UI and the Zigbee network, and I saw that almost all devices were offline or unresponsive, including the door sensor.

I started troubleshooting, but after a full day of frustration and tests, I (possibly mistakenly) decided to completely rebuild the Zigbee network, since I only have fewer than 10 devices.

At first, I tried re-pairing router devices. They would join, but after a while they showed as “online” without actually responding. There was no MQTT activity even when testing commands directly.

Eventually things got worse: I could no longer pair any device at all. Even with devices in pairing mode and “permit join” enabled in Zigbee2MQTT, the pairing process always timed out—even when devices were placed within 1 meter of the coordinator (SONOFF Zigbee 3.0 USB Dongle Lite). No errors appeared in the logs.

After another exhausting half day of testing, I tried a different approach: I took an old Zigbee adapter I used at my parents’ house, a ZBDongle-E, and flashed it with EZSP 7.4.4.0 firmware (latest available from the flasher).

This is my current configuration:

se```
rial:
port: /dev/ttyACM0
adapter: ember
mqtt:
base_topic: zigbee2mqtt
server: mqtt://192.168.1.10
user: mqttuser
password: mqttpassword
version: 5
reject_unauthorized: true
include_device_information: true
frontend:
enabled: true
port: 8080
homeassistant:
enabled: true
ota:
update_check_interval: 1440
disable_automatic_update_check: false
availability:
enabled: true
advanced:
cache_state: true
cache_state_persistent: true
cache_state_send_on_startup: true
channel: 19
transmit_power: 20
log_level: info
log_namespaced_levels:
z2m:mqtt: warning
homeassistant_legacy_entity_attributes: false
legacy_api: false
legacy_availability_payload: false
version: 5
device_options:
legacy: false

Logs during startup and joining:

Using '/app/data' as data directory
Starting Zigbee2MQTT without watchdog.
[2026-05-19 22:01:23] info: z2m: Logging to console, file (filename: log.log)
[2026-05-19 22:01:24] info: z2m: Starting Zigbee2MQTT version 1.39.1 (commit #e132316)
[2026-05-19 22:01:24] info: z2m: Starting zigbee-herdsman (0.55.3)

[2026-05-19 22:01:24] info: zh:ember: Using default stack config.

[2026-05-19 22:01:24] info: zh:ember: ======== Ember Adapter Starting ========

[2026-05-19 22:01:24] info: zh:ember:ezsp: ======== EZSP starting ========

[2026-05-19 22:01:24] info: zh:ember:uart:ash: ======== ASH Adapter reset ========

[2026-05-19 22:01:24] info: zh:ember:uart:ash: RTS/CTS config is off, enabling software flow control.

[2026-05-19 22:01:24] info: zh:ember:uart:ash: Serial port opened

[2026-05-19 22:01:24] info: zh:ember:uart:ash: ======== ASH starting ========

[2026-05-19 22:01:25] info: zh:ember:uart:ash: ======== ASH connected ========

[2026-05-19 22:01:25] info: zh:ember:uart:ash: ======== ASH started ========

[2026-05-19 22:01:25] info: zh:ember:ezsp: ======== EZSP started ========

[2026-05-19 22:01:25] info: zh:ember: Adapter EZSP protocol version (13) lower than Host. Switched.

[2026-05-19 22:01:25] info: zh:ember: Adapter version info: {"ezsp":13,"revision":"7.4.4 [GA]","build":0,"major":7,"minor":4,"patch":4,"special":0,"type":170}

[2026-05-19 22:01:26] info: zh:ember: [STACK STATUS] Network up.

[2026-05-19 22:01:26] info: zh:ember: [INIT TC] Adapter network does not match config. Leaving network...

[2026-05-19 22:01:27] info: zh:ember: [STACK STATUS] Network down.

[2026-05-19 22:01:27] info: zh:ember: [INIT TC] No valid backup found.

[2026-05-19 22:01:27] info: zh:ember: [INIT TC] Forming from config.

[2026-05-19 22:01:27] info: zh:ember: [INIT FORM] Forming new network with: {"panId":6754,"extendedPanId":[221,221,221,221,221,221,221,221],"radioTxPower":5,"radioChannel":19,"joinMethod":0,"nwkManagerId":0,"nwkUpdateId":0,"channels":134215680}

[2026-05-19 22:01:27] info: zh:ember: [STACK STATUS] Network up.

[2026-05-19 22:01:27] info: zh:ember: [INIT FORM] New network formed!

[2026-05-19 22:01:27] info: zh:ember: [CONCENTRATOR] Started source route discovery. 1248ms until next broadcast.

[2026-05-19 22:01:27] info: zh:controller: Wrote coordinator backup to '/app/data/coordinator_backup.json'

[2026-05-19 22:01:27] info: z2m: zigbee-herdsman started (reset)

[2026-05-19 22:01:27] info: z2m: Coordinator firmware version: '{"meta":{"build":0,"ezsp":13,"major":7,"minor":4,"patch":4,"revision":"7.4.4 [GA]","special":0,"type":170},"type":"EmberZNet"}'

[2026-05-19 22:01:27] info: z2m: Set transmit power to '20'

[2026-05-19 22:01:27] info: z2m: Currently 0 devices are joined:

[2026-05-19 22:01:27] info: z2m: Zigbee: disabling joining new devices.

[2026-05-19 22:01:28] info: z2m: Connecting to MQTT server at mqtt://192.168.1.10

[2026-05-19 22:01:28] info: z2m: Connected to MQTT server

[2026-05-19 22:01:28] info: z2m: Started frontend on port 8080

[2026-05-19 22:01:28] info: z2m: Zigbee2MQTT started!

[2026-05-19 22:02:22] info: z2m: Zigbee: allowing new devices to join.

[2026-05-19 22:02:22] info: zh:ember: [STACK STATUS] Network opened.

[2026-05-19 22:06:38] info: zh:ember: [STACK STATUS] Network closed.

[2026-05-19 22:08:27] info: z2m: Zigbee: allowing new devices to join.

[2026-05-19 22:08:27] info: zh:ember: [STACK STATUS] Network opened.

[2026-05-19 22:12:42] info: zh:ember: [STACK STATUS] Network closed.

I’ve also tried:

Different USB ports on the mini PC
Restarting container and coordinator
Pairing devices extremely close to the coordinator
Verifying MQTT connectivity (working correctly)

The coordinator position has not changed (near the WiFi router) and it has worked fine for a long time without any issues.

At this point, I’m running out of ideas. Any help or suggestions would be greatly appreciated.

Thanks!

[bryfur]

Same issue, I was on the latest 2.10.1 container. Rolled back to 2.9.2 and it all started working again.