
Zigbee2MQTT Battery Device Config Fails? It’s Asleep
A Zigbee2MQTT config change on a battery device reverts because it was asleep. The parent holds it 7.68 seconds. How to land the command first time.

A Zigbee2MQTT config change on a battery device reverts because it was asleep. The parent holds it 7.68 seconds. How to land the command first time.

Understand Zigbee2MQTT MQTT QoS, subscription limits, availability and discovery settings, and why MQTT delivery does not prove Zigbee execution.

Why a Zigbee2MQTT expose becomes a number, a select, or a plain sensor in Home Assistant. The access bitmask and the category attribute, explained.

Zigbee2MQTT devices missing from Home Assistant? Check fresh MQTT reports, entity registration, retained discovery, effective settings and broker permissions.

Zigbee2MQTT extensions change runtime behavior, not device support. Here's how they differ from converters, and how enable_external_js gates both.

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

A slow-updating sensor and a broker-flooding device share the same cause. How Zigbee2MQTT's min/max reporting interval and reportable_change actually work.

Diagnose stuck or implausible Zigbee2MQTT battery values: raw scaling, voltage curves, stale reports and model-specific low flags, with practical checks.

Register a Zigbee2MQTT install code: identify the correct device label, supported adapter and QR format, then verify registration before pairing.

Diagnose Zigbee2MQTT entities unavailable after a restart. Check current bridge-state refresh, MQTT discovery, birth messages and broker persistence.