← all designs · 3c — Niche specialist (smart-home interop)

Sensors · Presence

Aqara FP2 — does it actually work with Home Assistant + HomeKit?

Tested over 6 weeks against our standard interop rig. Last refresh Apr 2026.

Placeholder — sample interop deep-dive showing the niche specialist format.
HomeKit (native) Works
Home Assistant (HomeKit Controller) Works · all zones exposed
Home Assistant (Aqara cloud) Partial · 3-zone limit
Matter No · firmware 1.2.7 lacks bridging
Local-only operation Yes via HomeKit Controller
Latency (motion → automation) ~280ms median (n=400)

How we tested

Rig: Home Assistant 2026.4 on a Pi 5 + SkyConnect, paired against Apple TV 4K (HomeKit hub) and a fresh Aqara M3. Latency measured by triggering a controlled IR-pulse light and timestamping the HA event log. 400 trials over 14 days, two homes (1200 sq ft and 2400 sq ft).

What broke

Working HA configuration

homekit_controller:
  # No YAML needed — pair via UI after factory reset.

automation:
  - alias: "FP2 zone 1 lights"
    trigger:
      - platform: state
        entity_id: binary_sensor.fp2_zone_1_motion
        to: "on"
        for: "00:00:00"
    action:
      - service: light.turn_on
        target: { entity_id: light.living_room }