configure zigbee2mqtt's pan_id, ext_pan_id, channel, and network_key advanced settings
domain: zigbee2mqtt.io · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Open configuration.yaml and locate (or add) the advanced: section.
Set pan_id to a specific value or GENERATE to have Zigbee2MQTT generate one on next start.
Set ext_pan_id as an 8-byte array, or GENERATE, and channel to one of the recommended values (11, 15, 20, or 25) to avoid interference.
Set network_key to a 16-value array or GENERATE to create a new encryption key.
Restart Zigbee2MQTT, keeping in mind that changing pan_id, ext_pan_id, channel, or network_key after devices are already joined will require re-pairing them.
Known gotchas
Changing the network_key or ext_pan_id after a network is established invalidates existing device pairings, requiring a full re-pair of the mesh.
Non-recommended channels can overlap with 2.4GHz Wi-Fi channels in use, causing intermittent Zigbee packet loss that looks like flaky devices rather than an RF conflict.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?