How could we club together and get such an app written? I would have thought that Homey themselves might want to commission this as it would make their product that much better.
1 Like
That’s what everybody thinks about all of their unsupported devices.
4 Likes
I have just coded the initial setup for a Homey homekit controller based on a homekit-controller lib with adaptions for homey, detecting the FP2, defining the multiple zones occupancy etc.
able to pair, unpair, subscribe to events etc…
will take me a couple of weeks to iron out issues and make it look better…
20 Likes
Haven’t read about it but i hope they will bring it soon, already have some ideas in mind.
As Robert said, the FP1 uses Zigbee, but as it was never official released in Europe, it hasn’t been added to the Aqara app.
The real solution is for everyone to complain to Aqara and ask for a workable API for the FP2.
Aqara are more concerned about making money out of the API as the rate limits on a free developer account are really poor, and as soon as the account exceeds the limit it costs a lot of money. That’s the other reason I am hesitant about releasing an app that is simple to use as for any chance to stay within the rate limit each user needs to create an Aqara developer account and configure it.
Basically Aqara want you to stay in their ecosystem or make money from anything else.
But then how does Home Assistant achieve this?
I’m no coder in modern languages but I would have thought that if a solution can be coded in HA then it could also be coded in Homey.
Perhaps I’m wrong or maybe in Homey it’s much more difficult.
Home Assistant uses Python, not Javascript (it’s using aiohomekit under the hood).
1 Like
I’d also donate 30$ for a proper Homey-App.
I understand the issue with the messy Aqara API. Embarassing for a company that’s focus is smart homes.
@Adrian: If you could still publish your current version (even if hacky / not stable / etc.) I’d appreciate it.
1 Like
I wouldn’t feel comfortable publishing it as it’s just not reliable enough so I would just get too many users complaining. I got too frustrated myself with having to keep reenabling the webhook because Aqara have deemed that Homey is not responding, so I don’t even use it anymore.
I don’t have issue with any other products that use webhooks, presumably because they use the Athom server. My Lightwave lights rely heavily on them as I use the event from the main kitchen light switching on to trigger all my kitchen lights to come on, and they hardly ever miss a beat. When they do fail to come on, it is normally because the zwave controllers didn’t work rather than Lightwave not reacting.
I see. Thanks for the reply! 
Hi
Maybe my solution is interesting for someone who would like to integrate the FP2 without Home Assistant or Homekit. I got it working with the Aqara App, Alexa (Cheep Gen1 Device) and Homey (and the Homey community app “Virtual Devices”). The delay is about 1-2 seconds (closer to 1s). I configured 12 zones and it works very accurate and reliable with 12 Hue spots. No false detections, ghosts etc.
These are the steps:
- Installation and configuration of zones in the Aqara app, AI learning to eliminate ghosts, upgrading to the newest firmware.
- Synchronization of the zones with Alexa (In the Aqara app in the menu “Profile” - “Connect to other oecosystems” selecting Alexa.
- Create corresponding zones in Homey (I created 12 sub-zones in my living room)
- Adding a virtual sensor in every zone with the app “Virtual Devices” (Type: Device, Device Class: Sensor, Attribute/Type: Motion)
- Creating two advanced flows in Homey for every zone:
6.1. IF: Start button, THEN: Virtual Sensor 1 “Set to ” (In the German version: “Setzen Sie auf ”)
6.2. IF: Start button, THEN: Virtual Sensor 1 “Set to ” - Making the two flows favorite flows so that it can be detected in the Alexa app
- Letting Alexa search for new devices (scenes) by saying the device search command or selecting in the Alexa app: Devices - Scenes - Search Scenes.
- Creating a routine in the Alexa app to set the virtual motion sensors on True (=Motion): In the Alexa App More-Routines-New: IF: Trigger = Smart Home → Zone 1 = Found THEN: Smart Home->Scene “Zone 1 Alarm Motion True” (Starting the flow which has been created in Homey before)
- Creating a second routine to set the virtual motion sensor on False (=No motion): Same as before but instead of “Found” selecting “Not found” for 0 Minutes. (No motion works instantly with 0 Minutes)
- Creating a light flow in Homey: “IF: Zone 1 became active, THEN: Switch on Light 1…” (normal light flow based on zone activity).
Maybe that helps someone. An app would be nice but this works well for me.
Cheers
Gianni
11 Likes
Aren’t these sensors are better option?
Could you tell me if this works even if i don’t have a apple device. Will the homey find the sensor on its own?
As a Google guy I don’t have any Apple devices, and my FP2 is available in Homey.
Pay attention to the fact, that the current software has an alpha status (early software).
The Homey app acts as a Homekit controller. No need to have apple home around.
3 Likes
Hi, Sorry, could you please just explain me how it’s work, you just download Homekit app and that’s it ? Thanks a lot
Hello,i have install the Homekit controller app but it doesn’t find my Fp2 sensor…
I don’t have any Apple devices.
On the other hand,The app found my Tado bridge but ask me a pincode(xxx-xx-xxx) that i don’t have…
Could someone explain how to make Fp2 sensor working please?
Thanks a lot
Have you tried rebooting the FP2, as that worked for me.
