M3 Hub — HomeKit "Home / Stay Arm" security state won't hold (Away & Night fine)

Apple Home Connect
,
1

Posting in case others can reproduce or have a fix.

My M3 Hub’s HomeKit Security System will not hold the Home (Stay Arm) state. When Home is commanded, it reverts to Disarmed instead of settling on Stay Arm. Away and Night arm correctly in both directions — only Home fails.

What makes this a clean M3 issue:

  • Reproduced with the M3 paired directly to Apple Home — no bridge, no third-party software, nothing else in the path.
  • My other Aqara security accessories on the same account — Camera Hub G3, Camera Hub G350, and Doorbell Camera Hub G410 — all handle Home correctly. So it’s not an account or cloud-side problem.

It’s also not a timing issue — disarming and then arming Home as two separate deliberate actions still fails.

Questions for other M3 owners:

  1. Can you reproduce this — does Home / Stay Arm hold on your M3 over HomeKit?
  2. Is this a known firmware bug, and is there a fix or workaround?
  3. Does Home Arming need at least one sensor assigned before HomeKit reports Stay Arm correctly, or is it independent of Home-mode config?

I’ve also opened a support ticket and will update here if I hear back.

1 Like
2

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!

1 Like
3

Hi there and welcome to the forum .did you try to make an reset?do your zigbee devices are exposed to HomeKit as they should?also before making an reset take it out from the power source and let it for 1min then reconnect it and wait till will reconnect on aqara and HomeKit.see if that works for you.i just had to reset my magic cube as I couldn’t add nothing to activate from HomeKit not sure some word stuff I experience this days :rofl::rofl::rofl: but the cube was added via M3 and didn’t do nothing on HomeKit no matter what I had chose on each side to activate it won’t save it.

1 Like
4
  1. No I can’t reproduce that. It works fine for me in Apple Home
  2. Not sure it’s an actual issue?
  3. No, I can activate “Home Arming” and I do not have any devices selected or being used for that mode even though the Mode is activated.

I would look over your settings again in the Aqara app in the Guard Modes just in case something is off or incorrect.

3 Likes
5

Hi, can’t also reproduce it!
Could you make a video ? I think the support also need one :point_up:

2 Likes
6

Might check your Guard Mode setup in the Aqara app itself, not just the HomeKit side.

@srl77411 is right because Home/Stay Arm not needing assigned devices is easy to misconfigure if you added sensors expecting them to gate it.

If power cycling and a fresh Guard Mode setup doesn’t fix it, I’d bet it’s something specific to your accessory list, not the hub firmware — since two other people can’t reproduce it on the same hardware.

Just out of curiosity, do you run HA at all? I’ve discontinued use of the Guard Mode in AH and set up an alarmo instance in HA. I made a detailed post about this earlier in the year. I have since completely replaced my Simplisafe system with the Alarmo setup in HA and it has way more functionality then Simplisafe ever did. Transitioning from SimpliSafe to Home Assistant + Aqara

1 Like
7

Update — resolved itself, but no explanation.

The M3 problem has gone away. Home / Stay Arm now arms and reports correctly, and changes in Apple Home reflect in the Aqara Hub Guard Modes tile. This happened about two days after I posted here and opened a ticket.

What I did to fix it: nothing. No configuration changes (including nothing touched on alert mode trigger devices), no reset, no re-pair, no power cycle, no firmware update (already on latest), no app or iOS update, no new devices. Worth noting for anyone told this is a trigger device config issue — since I changed no configuration at all, that setting is identical now to what it was while it was broken.

However, I saw a similar fault on a different device. My Camera Hub G350 (paired directly to HomeKit): setting Home in the Aqara app didn’t propagate to it, while Away and Night were fine. The other direction worked — so the behaviour is the opposite of the M3 hub. Both directions had worked on that hub previously.

I’ve since removed the G350 from HomeKit (one security system is enough for my setup), so I’m not chasing that one.

Thank you all for the replies — really appreciate it, and it makes me feel this forum actually helps. I’m thrilled to see responses so fast. Happy smart home, guys!

4 Likes