Zigbee2MQTT on Proxmox High Availability: What Breaks
A USB Zigbee coordinator can't follow a VM around a Proxmox HA cluster. Why migration and failover strand it, the workarounds, and the clean fix.
A USB Zigbee coordinator can't follow a VM around a Proxmox HA cluster. Why migration and failover strand it, the workarounds, and the clean fix.
Switching an Aqara or Mi Home account region disconnects app-linked devices and can strand some hubs. Why Zigbee2MQTT/ZHA devices should be unaffected.

A third-party extension runs automations inside Zigbee2MQTT itself, so triggers keep working when Home Assistant is down. Here's how it works.

Home Assistant's Aqara integration has no setup flow of its own. What it is, how to add Aqara Matter devices locally, and what not to confuse it with.

Zigbee2MQTT cannot run two coordinators in one instance. How a second instance works in Home Assistant, and the identity collision that breaks entities.

Diagnose slow Zigbee2MQTT startup and restart loops. Separate Supervisor monitoring from Z2M recovery, and check logs, device traffic and firmware.

Configure ZHA OTA sources with extra_providers. Check current defaults, the central firmware repository, local files and unknown update versions.

Use Tuya Smart and Smart Life accounts in Home Assistant. Check separate entries, authorization, device visibility, sharing limits and local alternatives.

Your Xiaomi Multimode Gateway or Aqara Hub E1 can be flashed into a Zigbee2MQTT coordinator. Zigbee2MQTT's own docs advise against the setup. Here's why.

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