
Zigbee2MQTT Event Entities vs Legacy Action Sensor Explained
Zigbee2MQTT 2.0 switched off the sensor.*_action entity your button automations used. Here's what replaced it, and which local path to rebuild on.

Zigbee2MQTT 2.0 switched off the sensor.*_action entity your button automations used. Here's what replaced it, and which local path to rebuild on.

Separate MQTT retain, state.json cache and availability when Home Assistant, Zigbee2MQTT or the broker restarts. Includes current replay behavior and checks.

Zigbee2MQTT names multi-gang switch entities switch_l1, switch_l2, or switch_left. What an endpoint is, why naming varies, and how to map each gang.

Map Zigbee2MQTT state, SET/GET, availability and bridge topics. Check supported properties, retained data and advanced.output formats for your MQTT clients.

Renaming a Zigbee2MQTT device changes its MQTT topic instantly but not its Home Assistant entity IDs. What breaks, what doesn't, and how to rename safely.

Zigbee2MQTT lost every device after a restart, or database.db is 0 bytes? What the file stores, why it happens, and how to recover before re-pairing.

Zigbee2MQTT has five per-device options for noisy state updates. What debounce, throttle, and the filter options each do, and which one fits your device.

Zigbee2MQTT 2.0 removed permanent permit_join. What the 254-second join window still exposes, and how a device passlist controls membership locally.

Understand Zigbee2MQTT's last_seen timestamp, distinguish communication from fresh sensor reports, and build a Home Assistant communication-age alert.

Troubleshoot Zigbee2MQTT interview failures by checking the failed discovery stage, reset state, battery, interference and model-specific pairing instructions.