Zigbee2MQTT Green Power Won’t Pair: Coordinator Explained
Green Power switch won't pair in Zigbee2MQTT? Your coordinator decides it: Z-Stack sticks pair GP directly, EmberZNet ones need a proxy router nearby.
Green Power switch won't pair in Zigbee2MQTT? Your coordinator decides it: Z-Stack sticks pair GP directly, EmberZNet ones need a proxy router nearby.

Zigbee2MQTT won't start with ASH_ERROR_TIMEOUTS after a Node.js update? The cause is a serialport bug on Node 26.3+, and Zigbee2MQTT 2.14.0 patched it.

A failed coordinator flash isn't automatically a brick. Here's how to identify what happened and pick the right recovery tool for your chip family.

Understand Zigbee2MQTT adapter_concurrent, adapter-specific defaults and active outgoing tasks. Check slow multi-device commands before changing the setting.

Create and verify a Zigbee2MQTT data backup, check adapter-specific radio export limits, and plan coordinator migration and identity recovery.

Zigbee2MQTT broadcasts a channel change to paired devices on zstack and ember adapters. The config edit, sleepy devices, and the backup-file trap.

SkyConnect/ZBT-1 promised Zigbee and Thread on one radio. Home Assistant now calls multiprotocol experimental and is retiring it. What to run instead.