01
Permit join never finds it
Zigbee2MQTT is in permit-join mode, but the device never appears in the interview list.

THE THREE FAILURES WE SEE
01
Zigbee2MQTT is in permit-join mode, but the device never appears in the interview list.
02
The device appears briefly, then the interview stalls or the device is marked unsupported.
03
The device is in the list, but state updates or commands do not reach it.
HOW WE TEST

SERVICE SCOPE
The session covers one agreed device and one verified path. Anything outside the written scope is quoted separately before work starts.
FAQ
No. Pair one known device first so the coordinator, permit-join, and MQTT path are proven before adding more.
The interview may not have completed, or the device is not reaching the coordinator. Check the log and the network path.
No. We isolate coordinator, pairing, and MQTT issues; physical repair or wiring is outside scope.
NEXT STEP
Send the device, software, exact symptom, and what you have already tried. We will confirm scope and a fixed quote before booking.
No passwords. A real reply comes from [email protected].
FROM THE BLOG
Troubleshoot Zigbee2MQTT when messages are not published to the MQTT broker, causing entities to stay unavailable. Step-by-step checks for USB coordinator and new device setup.
Troubleshoot a Zigbee2MQTT router that won't join when the network map shows no coordinator or routers. Step-by-step checks and a verification test.
Troubleshoot Zigbee2MQTT USB adapter permission errors that cause 'coordinator not found' on startup. Step-by-step checks and verification.
Troubleshoot an empty Zigbee2MQTT network map when the coordinator and routers do not appear. Check MQTT topics, adapter state, and map generation, then verify with a test.
Zigbee2MQTT cannot publish to the broker and entities stay unavailable. Check broker settings, credentials, and network reachability to restore MQTT publishing.
All entities become unavailable after a Zigbee2MQTT or broker restart. Learn how to diagnose and restore your device without guesswork.
A newly paired Zigbee device joins Zigbee2MQTT but stops reporting state shortly after. Check link quality, power, and interview completion to restore reliable reporting.
Troubleshoot Zigbee2MQTT when MQTT connection fails and entities stay unavailable. Check broker settings, credentials, and network, then verify with a test publish.
Zigbee2MQTT cannot open your USB coordinator on startup. Follow these checks to confirm the device path, permissions, and port state before pairing a new Zigbee device.
A device joins Zigbee2MQTT then stops reporting state. Follow these checks to confirm the cause and restore reliable reporting.