I have an Aqara Hub M3 on firmware 0013 with nine P2 door and window sensors connected via Matter over Thread. Starting October 17th, 2026, all local automations in the Aqara app stopped firing. Example: garage side door automation (trigger: door opened, action: play custom audio on hub) does nothing.
Apple Home automations for the same sensors still work, and the sensors show online with green status in the Aqara app. But the Aqara app’s local event logs have been empty since October 18th 3:02 AM, when the sensors started showing offline-online flips. Home Assistant history confirms the sensors were still reporting opens and closes through today, so the sensors themselves are fine — the M3 is not executing local automations.
I have tried: rebooting both M3 hubs, and re-adding the garage side door P2 to the M3 via Matter pairing code from Apple Home, which failed with “already in use.”
This matches other user reports of 0013 breaking local automation execution on the M3. Any fix or firmware update coming? Logs available if needed.
Hi there, it looks like you’re experiencing a support-related issue. We’ve automatically created a support ticket for you and will reach out via the forum email within the next two business days.
If other members have any suggestions or insights on this topic, feel free to share!
Hi! I encountered this issue specifically with the U600 and U200 lock models. At first, I thought it might be due to an update, but after investigating the root cause, I realized there was a malfunction in my router. I’m not entirely sure why it happened, but my Thread network split, and packet broadcasting was disabled. After reconfiguring the router, I had to re-add the Matter devices. Everything is fine now.
Hey there.well from what i read in internet there is some sort of issue with the 013 firmware on M3 so till my be an update could be rolling out you can try this steeps and see if you can get those automations working again in Aqara home app:
-Open the Agara Home app and go to Automations.
-Find any local automation, toggle it OFF, wait 10 seconds, and toggle it back ON.
-Create a simple temporary cloud-dependent automation (e.g., Trigger:
Manual tap → Action: Push Notification to phone) and execute it. Executing a cloud rule forces the hub’s sync service to restart its background daemon.
-Hard Power Cycle: Unplug the M3 Hub’s power cord (and Ethernet/PoE if applicable), wait full 2-3 minutes to allow the Thread active operational dataset and volatile memory to clear, then plug it back in.
Second try if the abound fails:
-Go to Hub M3 Settings → Hub Cluster /
Multi-hub Lead Settings.
-Temporarily switch or disable the edge leader role, wait 30 seconds, and reenable it. This forces a soft refresh of the local Edge rule engine without wiping child devices.
3th steep if both abound fails:
-In the Agara Home app, go to Profile →
Settings → Clear Cache.
-Force close the Agara Home app completely and reopen it.
-Go into the detail page of one P2 Sensor in the Agara app, open its settings menu, and trigger a Signal Test or edit its device name slightly to force the M3 to push a parameter updates to that specific node.
And if all this fails and you still can’t get your automations running on Aqara home app I suggest to report this issue to Aqara support.