You open permit_join, the bulb or sensor blinks as if pairing, status: ok comes back — but nothing appears in Zigbee2MQTT. No device_joined, no device_interview, no new device in Home Assistant. Factory-resetting the device doesn’t help. The network works fine for existing devices.
If coordinator_check shows missing_routers in your network, the new device is likely trying to associate through a router with a stale coordinator table entry. The fix is to force pairing directly through the coordinator.
Environment
- Zigbee2MQTT 2.14.3
- Coordinator: SMLIGHT SLZB-06, adapter
zstack
Problem
Two new Lexman ENKI RGBW A60 E27 (IA-CDZOTAAA007MA-MAN) bulbs refused to join the existing Zigbee network.
Standard permit_join via Home Assistant UI or MQTT returned status: ok, but no device_joined or device_interview events ever appeared in Z2M logs — even after multiple factory resets of the bulbs.
mosquitto_sub \
-h emqx.internal.mateuszholowieszko.com \
-t 'zigbee2mqtt/bridge/event' -v
# ... silence. No device_joined, no device_interview.Additional diagnostics that did not solve the problem:
- Touchlink scan →
{"data":{"found":[]},"status":"ok"} coordinator_checkreported 9missing_routers— details below- Upgrading Z2M from 2.12.1 → 2.14.3
- Enabling
availabilitymonitoring
Missing Routers
Run coordinator_check to see which routers have stale entries in the coordinator’s table:
mosquitto_pub \
-h emqx.internal.mateuszholowieszko.com \
-t 'zigbee2mqtt/bridge/request/coordinator_check' \
-nSubscribe to the response in a second terminal:
mosquitto_sub \
-h emqx.internal.mateuszholowieszko.com \
-t 'zigbee2mqtt/bridge/response/coordinator_check' \
-C 1 -vIn my case the response listed 9 devices:
{
"data": {
"missing_routers": [
{"ieeeAddr": "0xf074bffffee10190", "modelID": "E22xx"},
{"ieeeAddr": "0xf074bffffeea46c4", "modelID": "E22xx"},
{"ieeeAddr": "0xf074bffffee0a278", "modelID": "E22xx"},
{"ieeeAddr": "0x348d13fffec76b1e", "modelID": "E22xx"},
{"ieeeAddr": "0xdc8e95fffe5a82e8", "modelID": "IM-CDZDGAAG005KA-MZN"},
{"ieeeAddr": "0xdc8e95fffe5a62f4", "modelID": "IM-CDZDGAAG005KA-MZN"},
{"ieeeAddr": "0x84b4dbfffe23ecc8", "modelID": "IM-CDZDGAAG005KA-MZN"},
{"ieeeAddr": "0xf84477fffe797217", "modelID": "IM-CDZDGAAG005KA-MZN"},
{"ieeeAddr": "0xa4c1383f011a0b87", "modelID": "ZY-M100-24GV3"}
]
},
"status": "ok"
}E22xx— IKEA INSPELNING smart plugs (×4)IM-CDZDGAAG005KA-MZN— Lexman ENKI GU10 (×4)ZY-M100-24GV3— Tuya mmWave presence sensor (×1)
Once each device had mains power, all nine showed availability: online — yet they still appeared on the missing_routers list. missing_routers and availability online are independent — a device can be reachable and still have a stale coordinator table entry. There is no need to remove and re-pair these devices.
Fix
Open permit_join exclusively through the coordinator, bypassing all routers:
Terminal 1 — subscribe first:
mosquitto_sub \
-h emqx.internal.mateuszholowieszko.com \
-t 'zigbee2mqtt/bridge/response/permit_join' \
-C 1 -vTerminal 2 — open the join window:
mosquitto_pub \
-h emqx.internal.mateuszholowieszko.com \
-t 'zigbee2mqtt/bridge/request/permit_join' \
-m '{"time":254,"device":"coordinator"}'Expected response:
{"data":{"device":"Coordinator","time":254},"status":"ok"}Power-cycle the bulb, leave it under power, and wait. The first bulb joined ~118 seconds after the window opened — don’t reset it repeatedly while waiting.
Z2M logs on success:
z2m: Zigbee: allowing new devices to join via Coordinator.
zh:controller: Interview for '0xcc36bbfffe9a8e8b' started
z2m: Device '0xcc36bbfffe9a8e8b' joined
z2m: Starting interview of '0xcc36bbfffe9a8e8b'
z2m: Successfully interviewed '0xcc36bbfffe9a8e8b', device has successfully been paired
z2m: Device '0xcc36bbfffe9a8e8b' is supported, identified as: ADEO ENKI LEXMAN E27 7.2 to 60W LED RGBW (IA-CDZOTAAA007MA-MAN)Why This Works
Without the device field:
{"time": 254}Z2M allows joining through the coordinator and any available router. In a network with routers listed as missing_routers, devices may try to associate through a problematic path and silently fail.
With "device":"coordinator":
{"time": 254, "device": "coordinator"}Z2M restricts association to the coordinator only, eliminating the broken router path entirely.
The missing_routers list is separate from availability online — a router can respond to availability pings while still having a stale entry in the coordinator’s internal table. No need to remove those devices; just use this pairing method.