Note, that as per Hubitat standard capabilities convention all mmWave sensors are presented as motion sensors. This applies for both the HE stock drivers and for all custom community drivers. What is called 'presence' in Aqara is 'motion' in HE.
From the commands (the buttons) visible on the main device, only the 'Refresh' button may have some useful functionality. The rest of the buttons are commands needed for the Replica integration.
After installing the driver, it will create automatically child devices of a type 'Generic Component Motion Sensor' for each of the zones configured in Aqara Home app:
The zones occupancy is again presented as Hubitat standard 'motion' capability.
If you have any ideas for improvements, let me know (before I forget the Replica drivers specifics ) .
I am planning to add a threshold preference for the illuminance updates, my FP2 cycles too frequently +/- 4 lux readings, so a default threshold of 5 lux will greatly reduce the info logs.
It appears that the Samsung app captures movement direction and zones that have been setup within the aqara device. Would be great if those could be part of the device variables/states.
Sorry about that. My bad. Should pay closer attention. Did not realize from your original post that you created a separate driver for the FP2. I originally used the default Replica Presence driver which did not include all the device attributes/states.
I installed your driver and all the other device attributes/states and child zones populated. Everything appears to be in sync with one exception. The main device "presence" is not triggering. The Smartthings App does show a presence state based upon someone being or not being in the room. When I originally used the default Replica Presence driver the "presence" state was activating.
Wow... This is pretty awesome, but the requirement for an ST hub kills it for me. Am I correct in thinking that these aren't being manufactured any more?
Both old Samsung hubs and the new brand Aeotec hubs are available on Amazon, but don't buya ST hub just because of the Aqara FP2 integration!
I have published a minor update of the driver, ver. 1.0.2 2022-10-16 :
added illuminance threshold (default 5 lux)
zone child devices logs use the device name
I added a short note in the top post explaining that in Hubitat, we use the motion capability and attribute instead of 'presence'. This has been discussed in many threads in this forum in the past years.
@kkossev. Thank you for the explanation and your hard work. It is very much appreciated. My apologies for the oversight in missing those threads. I will continue to play with the driver and integration and advise on any improvements/medications.
Note that there is an alternative solution—use Mira for fully local communication between ST and HE. It requires manually creating virtual switches, and the illuminance can not be transferred as an analogue value to HE but is a local integration.
I am using this driver and if you own a Samsung TV you don't need a hub for ST as long as your not using anything that requires radio waves. So with the FP2 being wifi, my TV is working as the hub. Now I just gotta figure out what I am doing wrong. Maybe I had to much debugging going on last night and was seeing duplicate replicas, have this saving app thing showing up and zones aren't triggering. They are acutally being ignored. Maybe its cause I added the mode along with the main. Last night the zones were reporting too many requests and now one of them just doesn't report. I do seem to have zones from one sensor being tied to a different FP2 than they are. I think I am going to try again with only just one sensor being implemented to ST and go from there
I forgot to post an update. I did get them working and the issue I had at first and its just the replica app is circular or counter intuitive to set up. Once you get it all set up it closes you out and you have to go back into the app (circular part) and then create a smarthings device (this is the counterintuitive part) "Like I am trying to access a smarthings device not make one, oh yeah its a replica so yep. The driver works great but it still sucks that these FP2's can't be brought into hubitat natively which makes them slow. I have an FP1E directly hooked up thanks to @kkossev and that grabs you the second you walk in a room. I can get halfway across a room before the FP2 does. But all the access to those zones is awesome.
) .
