Really, can I hide it?
Perhaps my joke with the new Fibaro wallplugs was also not so smart “now you now when the washing machine is ready 
1 Like
You really don’t like your current wife eh? 
1 Like
I love here, was just a joke she could handle, but the FP2 full in side is not a discussing. I will try to hide it now
1 Like
Has anyone had this happen with an FP2 before: My flow on my basement presence was not working, and when I went to the flow it said “card not available”. Well it turns out one of my two FP2s now has fewer cards available. See the screenshots of the difference in cards with the sensors. I made sure they were both up to date, and even removed and re-added the basement one that had less cards, but still no luck. Anyone experienced this before? I can no longer have it trigger an event after zone becomes inactive after X minutes.
Do you have at least one zone defined?
I had the same issue and the zone occupied card appeared after I set at least one zone.
You were correct, thanks for the recommendation! For some reason the default detection zone on the FP2 wasn’t showing up so I created a second zone that covered the entire room to replicate the first zone and then they both showed up in the Homey app and the cards appeared. Appreciate the help!
If you have no zones, it should just show standard Homey motion detected cards. Though in the FP2 case it will be presence.
Couple of questions to you guys:
-
I restarted my Homey and one of the sensors is not coming online anymore while its online in the aqara-app and the remaining 7 sensors are just working. Is it somehow based on IP which is not updated if it gets a new IP? Or any other suggestions.
-
I still have one sensor that doesn’t want to pair. I tried every trick, while the 7 other sensors are working. Any suggestions?
-
How is your experience regarding detection and ghosting? I notice that small rooms like a bathroom and toilet its not working properly. While larger rooms its working amazing. Do you guys know any blogs/video’s on how to improve it?
Hey! Now i have been trying multiple times adding my 2 FP2 to homey with homekit app…i cant find it whatever how many times i try…i just got the screen on homey that there is now devices to add…i have earlier been using rphi4 with HA on to include them that way but for a couple days ago i setup new mesh internet type (tp-link x20) and after that i lose connection with both of the FP2 sensors i guess because of other ip-adress😅 but now im thinking i want to get them directly in to homey, if i manage to do it i will install one i just have i a shelf on my dads system. But back to the case… i have performed a factory reset of sensor, setup in aqara app and im running samsung phone so it should not be possible to get into apple home iguess? Please help🙈
Check the app topic for a howto
Running the app version 1.1.15. Presence is broken again. When i enter or leave the room these cards never get hit.
Can you look into it?
Can you reproduce with latest test version?
How do i change from the live to the test version? I dont wanna redo all my cards logic by uninstalling the live version first.
no need to redefine. just install, if you need to go back to live, just install live version from app store.
“normal” way to goto test version, go to the app in the app store and goto the changelog section, click test if available.
To put it this way: after i installed 1.27 the room i was in actually turned on the light as it was occupied. I’ll keep an eye on the ‘became free’ part i coded in the above cards as it should turn itself off after 5 minutes.
@Martin_Verbeek update: lights dont get disabled after 5 minutes. The kitchen lights/sensor dont work on arrival of the zone anymore either.
Using these cards myself in a number of rooms without issues. Can you trigger occupancy / no occupancy according to the aqara app in a room and PM me the log? Thanks!
move for room occupied/free to the standard motion alarm on and off cards (without zone naming in it) this will trigger room free/occupied. For room active/inactive you can also use the standard Homey active/inactive cards for these.
For specific parts of a room (FP2 zones) use the zone cards…
Posting for other folks here if they search for setup or Android with the FP2. I was able to get this working without too much effort. I was worried after looking around that I’d have to use MQTT, Home Assistant (HA), or worse some other hub to integrate. That’s not the case and only Aqara App and Homey are required. My steps were:
- Install the HomeKit Controller App on Homey
- Remove each FP2 sensor already setup in the Aqara App
- On each sensor hold the button for 10 seconds to reset (This may not be needed, but did it anyway since my sensors automatically re-entered pairing mode after removing them)
- Add the sensor back into the Aqara App as before. If you had any previous zones setup, you may want to remove them because the names will not get saved upon adding to Homey, but if you recently setup the zones and know the order it’s probably fine since you may have to rename the zones in Homey.
- Go to Homey App, add a device, select HomeKit controller, HomeKit IP → Connect.
- If everything went well you’ll see your sensor and any other homekit compatible devices listed (See attached).
- Choose your sensor and you’ll be prompted to enter the pin (See attached)
- If it’s successful your sensor is ready to go for flows
- From there you can open the device settings and rename the zones if you want so they show up in the HomeKit flow cards correctly.
Hope this helps someone else out 
1 Like
The app is very buggy. Not sure what’s going on. I can reach the sensors just fine using the Aqara app, but the logs say they are unreachable at times.
undefined2024-04-10T03:48:41.040Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D setupHeartBeat error, Bonjour update broadcast ............, Error: connect ETIMEDOUT 192.168.68.50:56355
2024-04-10T03:48:41.039Z [err] [ManagerDrivers] [Driver:hapIP] [Device:5837430a-9e86-4588-aa23-87353af0545d] Presence-Sensor-FP2-968B setupHeartBeat error, Bonjour update broadcast ............, Error: connect ETIMEDOUT 192.168.68.57:50517
2024-04-10T03:48:41.022Z [err] [ManagerDrivers] [Driver:hapIP] [Device:888040ce-08ec-4a95-baff-0038e2f51a1a] Presence-Sensor setupHeartBeat error, Bonjour update broadcast ............, Error: connect ETIMEDOUT 192.168.68.58:56889
2024-04-10T02:41:32.849Z [err] [ManagerDrivers] [Driver:hapIP] [Device:888040ce-08ec-4a95-baff-0038e2f51a1a] Presence-Sensor setupHeartBeat error, Bonjour update broadcast ............, Error: connect EHOSTUNREACH 192.168.68.58:56889
2024-04-10T02:41:12.133Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D listenToEvents.event-disconnect recovery error, Bonjour update broadcast ............, Error: connect ETIMEDOUT 192.168.68.50:56355
2024-04-10T02:40:41.393Z [err] [ManagerDrivers] [Driver:hapIP] [Device:888040ce-08ec-4a95-baff-0038e2f51a1a] Presence-Sensor setupHeartBeat error, Bonjour update broadcast ............, Error: connect EHOSTUNREACH 192.168.68.58:56889
2024-04-10T02:40:38.331Z [err] [ManagerDrivers] [Driver:hapIP] [Device:888040ce-08ec-4a95-baff-0038e2f51a1a] Presence-Sensor setupHeartBeat error, Bonjour update broadcast ............, Error: connect EHOSTUNREACH 192.168.68.58:56889
2024-04-10T02:40:32.848Z [err] [ManagerDrivers] [Driver:hapIP] [Device:5837430a-9e86-4588-aa23-87353af0545d] Presence-Sensor-FP2-968B setupHeartBeat error, Bonjour update broadcast ............, Error: connect EHOSTUNREACH 192.168.68.57:50517
2024-04-10T02:39:35.861Z [err] [ManagerDrivers] [Driver:hapIP] [Device:5837430a-9e86-4588-aa23-87353af0545d] Presence-Sensor-FP2-968B listenToEvents.event-disconnect recovery error, Bonjour update broadcast ............, Error: connect EHOSTUNREACH 192.168.68.57:50517
2024-04-10T02:39:32.811Z [err] [ManagerDrivers] [Driver:hapIP] [Device:5837430a-9e86-4588-aa23-87353af0545d] Presence-Sensor-FP2-968B setupHeartBeat error, Bonjour update broadcast ............, Error: connect EHOSTUNREACH 192.168.68.57:50517
2024-04-10T01:15:11.639Z [log] [ManagerDrivers] [Driver:hapIP] [Device:5837430a-9e86-4588-aa23-87353af0545d] Presence-Sensor-FP2-968B listenToEvents.event-disconnect subscribe success
2024-04-10T01:15:10.896Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D listenToEvents.event-disconnect subscribe success
2024-04-10T01:14:33.267Z [err] [ManagerDrivers] [Driver:hapIP] [Device:888040ce-08ec-4a95-baff-0038e2f51a1a] Presence-Sensor setupHeartBeat error, Bonjour update broadcast ............, Error: connect EHOSTUNREACH 192.168.68.58:56889
2024-04-10T01:14:30.206Z [err] [ManagerDrivers] [Driver:hapIP] [Device:888040ce-08ec-4a95-baff-0038e2f51a1a] Presence-Sensor listenToEvents.event-disconnect recovery error, Bonjour update broadcast ............, Error: connect EHOSTUNREACH 192.168.68.58:56889
2024-04-09T20:50:54.468Z [log] [ManagerDrivers] [Driver:hapIP] [Device:5837430a-9e86-4588-aa23-87353af0545d] Presence-Sensor-FP2-968B listenToEvents.event-disconnect subscribe success
2024-04-09T01:07:20.463Z [log] [ManagerDrivers] [Driver:hapIP] [Device:888040ce-08ec-4a95-baff-0038e2f51a1a] Presence-Sensor setupAccessory Supported Service public.hap.service.sensor.occupancy
2024-04-09T01:07:20.460Z [log] [ManagerDrivers] [Driver:hapIP] [Device:888040ce-08ec-4a95-baff-0038e2f51a1a] Presence-Sensor setupAccessory Supported Service public.hap.service.sensor.occupancy
2024-04-09T01:07:20.458Z [log] [ManagerDrivers] [Driver:hapIP] [Device:888040ce-08ec-4a95-baff-0038e2f51a1a] Presence-Sensor setupAccessory Supported Service public.hap.service.sensor.light
2024-04-09T01:07:20.456Z [log] [ManagerDrivers] [Driver:hapIP] [Device:888040ce-08ec-4a95-baff-0038e2f51a1a] Presence-Sensor setupAccessory Supported Service public.hap.service.accessory-information
2024-04-09T01:07:20.415Z [log] [ManagerDrivers] [Driver:hapIP] [Device:5837430a-9e86-4588-aa23-87353af0545d] Presence-Sensor-FP2-968B setupAccessory Supported Service public.hap.service.sensor.occupancy
2024-04-09T01:07:20.399Z [log] [ManagerDrivers] [Driver:hapIP] [Device:5837430a-9e86-4588-aa23-87353af0545d] Presence-Sensor-FP2-968B setupAccessory Supported Service public.hap.service.sensor.occupancy
2024-04-09T01:07:20.397Z [log] [ManagerDrivers] [Driver:hapIP] [Device:5837430a-9e86-4588-aa23-87353af0545d] Presence-Sensor-FP2-968B setupAccessory Supported Service public.hap.service.sensor.light
2024-04-09T01:07:20.392Z [log] [ManagerDrivers] [Driver:hapIP] [Device:5837430a-9e86-4588-aa23-87353af0545d] Presence-Sensor-FP2-968B setupAccessory Supported Service public.hap.service.accessory-information
2024-04-09T01:07:20.356Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D setupAccessory Supported Service public.hap.service.sensor.occupancy
2024-04-09T01:07:20.327Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D setupAccessory Supported Service public.hap.service.sensor.occupancy
2024-04-09T01:07:20.322Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D setupAccessory Supported Service public.hap.service.sensor.light
2024-04-09T01:07:20.310Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D setupAccessory Supported Service public.hap.service.accessory-information
2024-04-09T01:07:19.189Z [log] [ManagerDrivers] [Driver:hapIP] discoveredHapBonjour devices Ready start browsing your network
2024-04-09T01:07:19.111Z [log] [ManagerDrivers] [Driver:hapIP] [Device:888040ce-08ec-4a95-baff-0038e2f51a1a] Presence-Sensor initialized
2024-04-09T01:07:19.110Z [log] [ManagerDrivers] [Driver:hapIP] [Device:888040ce-08ec-4a95-baff-0038e2f51a1a] Presence-Sensor setupConnection for E1:B5:ED:79:4D:FA on 192.168.68.58:56889, existing client false
2024-04-09T01:07:19.109Z [log] [ManagerDrivers] [Driver:hapIP] [Device:5837430a-9e86-4588-aa23-87353af0545d] Presence-Sensor-FP2-968B initialized
2024-04-09T01:07:19.107Z [log] [ManagerDrivers] [Driver:hapIP] [Device:5837430a-9e86-4588-aa23-87353af0545d] Presence-Sensor-FP2-968B setupConnection for F4:A8:5D:C7:B3:8E on 192.168.68.57:50517, existing client false
2024-04-09T01:07:19.107Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D initialized
2024-04-09T01:07:19.102Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D setupConnection for 92:9A:0A:4B:48:D6 on 192.168.68.50:56355, existing client false
2024-04-09T01:07:19.100Z [log] [ManagerDrivers] [Driver:hapIP] [Device:888040ce-08ec-4a95-baff-0038e2f51a1a] Presence-Sensor Driver ready listen for Browser events
2024-04-09T01:07:19.099Z [log] [ManagerDrivers] [Driver:hapIP] [Device:5837430a-9e86-4588-aa23-87353af0545d] Presence-Sensor-FP2-968B Driver ready listen for Browser events
2024-04-09T01:07:19.098Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D Driver ready listen for Browser events
2024-04-09T01:07:18.817Z [log] [ManagerDrivers] [Driver:hapIP] hapIP driver has been initialized
2024-04-09T01:07:18.813Z [log] [ManagerDrivers] [Driver:hapIP] discoverDevicesBonjour
2024-04-09T01:07:18.004Z [log] [MyApp] Homekit Controller 1.2.8 has been initialized
2024-04-09T01:07:17.987Z [log] capturing stderr
2024-04-09T01:07:17.975Z [log] capturing stdout
2024-04-09T01:06:10.003Z [log] [MyApp] app unload called
Are they changing ip-adresses or port? Version 1.28 (test)
Ports, but not all the time. Continuously fine tuning the timeouts, unreachables the fp2 gives. Next update will give improvements
2 Likes
