Hi Ted @TedTolboom,
I noticed the official Aqara app’s supported devices list only includes the Presence Sensor FP1E(lumi.sensor_occupy.agl1), not the original Aqara FP1 (lumi.motion.ac01). This matches what’s been reported in the forum before — e.g. this thread from March 2025, where a user was told the FP1 isn’t supported and would need an Aqara hub + Matter as a workaround, losing native Zigbee integration.
Since I own an FP1 and couldn’t find official support for it, I built a small standalone Homey app for it, reverse-engineering Aqara’s manufacturer-specific cluster (manuSpecificLumi, 0xFCC0) for presence, temperature and power-outage-count reporting.
I tried publishing it on the Homey App Store, but it didn’t pass certification as a standalone single-device app (Homey’s guidance is to avoid single-device apps when a brand already has broader official coverage). So sharing the code here seemed like the better path — at least other FP1 owners can use it, or you can fold whatever’s useful into the official app.
It’s MIT-licensed, so feel free to use/adapt any part of it — no strings attached. The relevant protocol implementation is in lib/AqaraLumiCluster.js.
One thing I couldn’t get working: zone/region mapping, like the official Aqara app has. The write side of the protocol (creating/deleting regions) is there, but I never found a way to read back live zone-detection events for a configuration/preview screen — the FP1 doesn’t seem to expose that over standard Zigbee the way the official app’s UI implies it can. If you know how that’s done, I’d genuinely like to know — happy to add it if so.
Thanks for maintaining the Aqara app — it covers a huge range of devices!
Gabriel
