Zigbee2MQTT MAC_NO_ACK (233): Why Commands Fail to Send
Zigbee2MQTT logs MAC_NO_ACK (233) and the device ignores your command? Learn how it differs from MAC_CHANNEL_ACCESS_FAILURE and what to check first.
~/archive $ ls -la
Archive
mesh-health
-
-
Zigbee2MQTT Ping Spam From an Absent Device? The Backoff Bug
Zigbee2MQTT pinging a long-gone device every 12 seconds? A setTimeout overflow in the availability backoff. How 2.14.0 fixes it, and a workaround.
-
Zigbee2MQTT OTA Failing on Multiple Devices? A Rogue Server
OTA checks failing on several unrelated Zigbee2MQTT devices at once? One misbehaving device can hijack OTA server discovery. How to spot and remove it.
-
Zigbee2MQTT Slow Startup: Watchdog Restart Loop Explained
Diagnose slow Zigbee2MQTT startup and restart loops. Separate Supervisor monitoring from Z2M recovery, and check logs, device traffic and firmware.
-
Zigbee2MQTT Transmit Power: Why It Might Do Nothing
Understand Zigbee2MQTT transmit power by adapter and firmware, why LQI is not an RF-output measurement, and what current settings and logs can establish.
-
Zigbee2MQTT Network Map Explained: Reading LQI and Depth
Zigbee2MQTT's map shows LQI, depth and zero-value links with no legend. What each number means, which ones are cosmetic, and the few that need action.
-
Zigbee2MQTT linkquality Explained: What the Number Means
Zigbee2MQTT's linkquality is a single-hop number measured at the coordinator. What it really tracks, why the network map disagrees, and when to act.
-
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.
-
Aqara/Xiaomi Zigbee Router Compatibility Explained
Some Zigbee routers can't keep Aqara or Xiaomi sensors connected. Which brands are documented as failing, why it happens, and the fix to try first.
-
Zigbee2MQTT OTA Update Failed or Stuck? How to Fix It
Diagnose Zigbee2MQTT OTA failures and stalled progress: current abort/retry steps, battery checks, firmware sources and coordinator errors.