Aqara M100 + HomeKit: Alarm triggers in Aqara app but never becomes “Triggered” in Apple Home

Hi all,

I’m trying to confirm whether this is a known limitation or a bug specific to the Aqara M100.

Setup

  • Aqara Hub M100
  • Firmware 4.5.20_0027.0017
  • Connected to Apple Home via HomeKit (not Matter-only)
  • Door / motion sensors visible in both Aqara app and Apple Home

What works

  • Arming / disarming syncs correctly to Apple Home
  • HomeKit automations trigger correctly on Alarm Arms (Away/Home)
  • Sensor events (door open/close, motion) appear in Apple Home activity

What does NOT work

  • When the system is armed (Away) and a sensor triggers:
    • Alarm does trigger in the Aqara app (siren + notifications)
    • Apple Home never changes alarm state to “Triggered”
    • Home app activity log shows:
      • Alarm armed
      • Sensor opened
      • No “Alarm Triggered” event
  • Any HomeKit automation based on “Alarm System → Triggers” never fires

Key observation

  • In Apple Home hub settings, there is no “Alarm Trigger Devices” section.
  • Because of this, HomeKit never correlates sensor events with the security system.

Expected behavior

  • When armed and a permitted sensor is triggered, Apple Home should enter the Triggered state (as seen with older Aqara hubs like M1/M2), allowing trigger-based automations.

Question

  • Is this a known limitation of the M100 HomeKit integration, or
  • Is there a firmware update / configuration missing that enables alarm trigger propagation to HomeKit?

If other M100 users can confirm whether their alarm ever shows Triggered in Apple Home, that would be very helpful.

Thanks!

2 Likes

@nsdonev You seem to be experiencing an issue with the alarm not showing as “Triggered” in Apple Home when triggered in the Aqara app. You can contact customer support for assistance. Contact the Aqara Home App Customer Service Team (Profile> Help & Feedback > Customer Service) or scan the QR code:


This will be more efficient. If you do not have an Aqara Home account, “Please click here” to create a ticket.

Hello,

I’m having the same issue and found this post trying to figure it out. Have you had any luck or heard if there will be a future update? I’ve seen that it works properly on older hubs such as the M1S and M2, so I’d imagine it has to be something that can be fixed by a firmware update.