[RELEASE] Aqara Multi-Sensor FP300 (PS-S04D)

⚙️ Custom Apps and Drivers Custom Drivers
183

Well, I got the driver installed, but somehow I'm not seeing most of the settings choices like I see in this thread. I think I paired it twice, but still something feels wrong. I'm trying to keep the light on so long as someone is in the kitchen, whether moving around or seated.

I also want the light to come on any time of day if a person is present/moving and the lux is less than 8000.

I have to work on the rules a bit, but for now it seems like I need to ensure that I'm able to use the features of the FP300 to know when the room becomes "occupied" rather than just sensing "motion".

image
image2980×1667 276 KB

184

Push the button on the device briefly (to wake it up), then go into Commands and click Configure.

You should end up seeing something like this (on the Commands page):

image
image454×764 49.3 KB

Then you can write rules and triggers based on roomState, which can be either occupied or unoccupied.

185

For some reason, your FP300 was not paired correctly, the Zigbee Model has an extra symbol at the end and as a result the AqaraModel is not recognized, this is why it doesn't work...

image

You have to delete (REMOVE) the device, then pair it again to your hub at a close distance.

186

i have been using motion as trigger. please advise where can i find the roomstate trigger in hubitat?

187

‘motion’ is a standard Hubitat capability and attribute, easily used from all HE apps.

The difference with the custom non-standard ‘roomState’ attribute is that the latest is activated a bit slower, probably a second later after the ‘motion’ becomes active, triggered quicker by the PIR sensor.

So, normally, there are no reasons to choose the custom attribute over the standard ‘motion’ attribute.

2 Likes
188

What's the purpose of roomState then? FWIW, I'm not seeing any delay.

I tried the Track Target Distance command, but I don't see where anything is being reported, not even in the debug logs.

189

Total guess here, but perhaps "motion" is PIR detection and "roomState" is mmw detection?

For rule-trigger purposes (presumably to turn on lights), PIR is commonly a bit faster than mmW, but that obviously can vary on a ton of different variables.

190

I believe “motion” is the combination of the FP300’s PIR and mmWave sensors. Either one will trigger “motion active”. Both need to be inactive for the “motion inactive” event to be raised.

4 Likes
191

This :point_up:

3 Likes
192

So roomState is only the mmWave sensor?

193

Yes

1 Like
194

Thanks. Is the Track Target Distance command working? I see "target distance tracking enabled for 5 minutes" in the logs, but where are the results displayed?

195

Yes, spot on! Now I have a lot of options I did not have before. Thanks!

Now I'm just trying to figure out why the light turns off while I'm still in the room. I would think that "motion" (now just being in the room) would keep the light on. Something more to puzzle over.

Still, it's rather a win to have lots of new options with this sensor! :slight_smile:

196

Currently showing available on Amazon - better be quick!

1 Like
197

Thanks, saw that and snagged one more a little while ago. Trying not to go crazy putting these things all over the house. Looks like they're still available.

198

I grabbed 3 to cover my current thinking on where to deploy them. This will guarantee Aqara will release the FP400 in the next few days. :wink:

3 Likes
199

Aqara FP400 is coming, but it is more of a successor to the FP2 model than the battery-powered FP300.

2 Likes
200

Yeah, I missed the fact the FP400 is corded. Pretty much a show stopper due to WAF.

201

I just snagged an FP300 from Amazon.

3 Likes
202

Lucky you. I have checked Amazon.ca every few days and it's always sold out.
Today it's not even list. :frowning: