I’ve built an app for Aqara devices in Homey and would like to share it with the community. My aim was to make it as simple and convenient as possible for everyday use, while making as many device features available as I could.
I took inspiration from Zigbee2MQTT and Homey Zigbee Driver. A big thank you to their authors for all their work! For my part, I’ve tried to rework and rewrite as much as I could myself.
The app was tested on my Homey Pro with the following Aqara/LUMI devices. I’ve grouped duplicate devices and included their Zigbee model IDs to help identify the exact models:
Two-button wireless switch, 2016 version — lumi.sensor_86sw2
H1M wireless switch, single button — lumi.remote.acn008
LED strip drivers in RGBW and 2 CCT configurations — lumi.dimmer.rcbac1
These are the devices used during testing, but inclusion in this list doesn’t mean that every feature and every possible scenario has been verified.
The app also includes definitions for other models. I’ve tried to make those as complete as possible, but I don’t have every device available to test personally, so I can’t guarantee that all of them will work fully.
Please feel free to report issues directly in this topic. It helps to include the exact device model, what you were trying to do, what you expected to happen, and what actually happened. Suggestions for improvements are welcome too.
For now, the project is only in my local Git repository. If there’s interest from the community, I’m happy to publish it on GitHub.
I’d love to hear your feedback! Would this app be useful to you, and which Aqara devices would you like to use with it?
My own substantially reworked versions of the Zigbee libraries. The app uses my versions of homey-zigbeedriver and zigbee-clusters, based on Athom’s libraries. I’ve reworked significant parts of the implementation and fixed several issues I encountered. I’ve also reported the bugs I found to Athom.
Additional Aqara models. Examples include H1M wireless switches, Opple MX480/MX960 lights, the L1-350 ceiling light, and the Aqara Lunar sleep sensor (lumi.lunar.acn01). Lunar exposes bed occupancy, heart rate and respiratory rate, with the numerical readings recorded in Homey Insights.
Colour effects for T1/T1M ceiling lights. For lumi.light.acn031 and lumi.light.acn032, the main light and RGB ring can be controlled separately. There are also nine ring presets available through Flow: Dinner, Sunset, Autumn, Galaxy, Dream, Holiday, Party, Meteor and Alert.
Two profiles for the lumi.dimmer.rcbac1 LED strip controller. There are separate drivers for RGBW and 2 CCT. In 2 CCT mode, both channels have independent on/off, brightness and colour temperature control. Each channel also has its own minimum/maximum brightness and on/off transition settings.
Configurable lighting transitions. Supported lights and dimmers have settings for brightness and colour temperature transition times. A duration explicitly set in a Flow takes priority over the device setting.
Reworked E1 radiator thermostat handling (lumi.airrtc.agl001). I’ve put considerable effort into mode changes, temperature control and restoring state after an app restart. For example, the last confirmed manual temperature setpoint is preserved separately, so off/frost-protection temperature reports don’t overwrite it. In my own setup, the E1 has been more reliable across the scenarios I tested. That’s my experience.
FP2 support via HomeKit over the local network. This includes overall presence, illuminance, and Flow triggers and conditions for individual zones. Zones are configured in the Aqara app first; Homey uses those existing zones. FP2 is currently the only supported HomeKit model. I may expand HomeKit support later.
More attention to FP300 configuration. The app exposes separate PIR motion and presence readings, target distance, PIR/radar/combined detection modes, and detection ranges entered as intervals such as 0-2.25, 3-4. This is one example of how I’m trying to make the device’s capabilities easier to use.
I too would like to test this app’s support of the FP2 presence sensor and see what the difference is with this and the HomeKit app
EDIT: I have just seen and installed the new version with the better device model naming, and the additional devices, including the FP2… I will start testing it this weekend. Thank you for adding this, much appreciated.
As an avid but never over enthusiastic Aqara user, many thanks for this… great to have an alternative to the official app that, good as it is, is missing elements
Hi! I saw your message about the FP300 in the other Aqara app thread. Could you try pairing one of your FP300 sensors through the Aqara Community app and see whether it works more reliably?
I have four FP300 sensors and haven’t encountered any issues during a week of testing so far.
I am currently in the process of trying to significantly reduce apps and resources used on my HP26, as it is struggling to keep up at times. Perhaps if I manage to have some significant success there, I might consider trying another app. But to be perfectly honest, I have 86 Zigbee devices (most of which are Aqara) and 237 Flows (the majority of which use those Aqara sensors and devices) that I would have to re-do if I switched apps… and that thought makes my head want to explode.
I am trying a Lafaer LWR02 multi-sensor along side one of my FP300’s… and to be frank, so far, it has been way more reliable.
If I do manage to rescue my HP26 from the edge of the precipice it is currently balanced on, I will give the community app a try and let you know.
Hello,
Thanks for your app. I visited the app’s Homey page recently and suggested inclusion of Aqara’s various camera, including camera doorbells. I’m not sure this is possible, but, I hope it can be done.
Hi! Thanks for the suggestion. I’m currently testing camera integration through HomeKit, but the functionality available this way is quite limited at the moment.
explode.