Changing Your Zigbee2MQTT Channel Without Losing Devices
Zigbee2MQTT broadcasts a channel change to paired devices on zstack and ember adapters. The config edit, sleepy devices, and the backup-file trap.
~/archive $ ls -la
Archive
Setup Guides
Setup guides
-
-
Sonoff ZBBridge to Zigbee2MQTT: Tasmota Flash Guide
Repurpose the original SONOFF ZBBridge with verified UART wiring, separate ESP/NCP firmware steps and a local TCP setup. Check recovery and Wi-Fi limits.
-
Tuya TS0041 1-Button Switch: Zigbee2MQTT & Home Assistant
Pair the Tuya TS0041 single-button Zigbee switch with Zigbee2MQTT, no Smart Life account needed, and set up single/double/hold press automations locally.
-
Sonoff TRVZB Radiator Valve: Zigbee2MQTT + Home Assistant
Pair the Sonoff TRVZB into Zigbee2MQTT with no Sonoff bridge or eWeLink account, set valve opening degree, and drive it off an external room sensor.
-
Sonoff SNZB-01 Wireless Button: Zigbee2MQTT + Home Assistant
Pair a Sonoff SNZB-01 button with Zigbee2MQTT or ZHA, write press automations that survive the Zigbee2MQTT 2.0 action change, and buy the right coin cell.
-
Zigbee2MQTT OTA Update Failed or Stuck? How to Fix It
A Zigbee2MQTT OTA that errors out or freezes at a percentage is rarely a bricked device. Here's what each failure means and which fix actually applies.
-
ZHA to Zigbee2MQTT Migration: Re-Pair or Convert DB
Migrating from ZHA to Zigbee2MQTT: the reliable re-pair method, the two-part no-re-pair shortcut, and how to sequence it without losing your mesh. Stays local.
-
Tuya TS0042 2-Button Switch: Zigbee2MQTT & Home Assistant
Pair the Tuya TS0042 two-button switch with Zigbee2MQTT or ZHA, build button-press automations, and check known battery and action-entity quirks first.
-
tinytuya: Tuya Local Control Without Home Assistant
tinytuya lets you script and verify local control of Tuya Wi-Fi devices directly, without Home Assistant, LocalTuya, or tuya-local in the loop.
-
Zigbee2MQTT \”Failed to Interview\”: Why Pairing Gets Stuck
A Zigbee2MQTT pairing that stalls on \"failed to interview\" usually means the join worked and the discovery queries timed out — not a config mistake.