Hi,
I’ve got an FP300 setup in my living room. I’ve setup an automation that when presence is detected and light is below a certain level that the lights in the room should turn on. This doesn’t work when I’m in the room and the criteria is met, but if I leave the room and re enter, then it activates.
I also have another automation that is set to turn the lights off when no presence is detected for 10 minutes. But this will turn off regardless of me being in the room or not.
Can anyone give some advice on how best to setup a routine like this please ?
2 Likes
It sounds like the primary trigger for your automation should be lux with presence as a condition, so that as the room darkens the automation runs. Is this the case? You can share a screenshot of your automation. If the automation starts with occupancy, you’ll need to trigger presence to kick off the automation.
1 Like
Hello, welcome to the forum. Here I created a lesson on creating automation for this sensor. Use it as a sample. Automation 2.0, lesson 22, FP300 sensor, creating On/Off automations for lamps
Complete the IF section with the room lighting condition.
1 Like
I’ve just updated it to how you say, see attached screenshot. Hopefully this will work.
Can you advise how an automation to turn the lights off should work? I have one that says when their is no presence for 20 minutes to turn the lights off. However if I leave the room for a short period and return, then the automation will run 20 minutes after if left the room - regardless of I was still in the room
1 Like
Hi, swap the WHEN and IF conditions. Then the automation will work fine.
Hello, @andymacrae78.
To avoid making mistakes in the future, watch my lesson on automation 2.0. It will take a little of your time but will be very useful in the future. Automation 2.0, lesson 1 (continued), description of the algorithm for transitioning automation 1.0 to 2.0
1 Like
It generally works ok. But when the room is empty and I walk in, it takes several minutes for the routine to run. Despite the sensor acknowledging there is presence in the room and that the lights level is low enough.
The lag you’re describing sounds like it’s happening on the automation engine side rather than the sensor. That automation runs through Aqara Cloud it looks like, so you’ve got a round trip of: sensor reports up to the cloud, gets evaluated, then a command comes back down, and under any load that adds up fast.
A local/Zigbee-direct automation, if your hub supports it, should fire close to instant by comparison. Worth checking whether you’re on the newer Automation 2.0 engine too, since that’s come up elsewhere as having different latency behavior than the older one.
If you can pull up the automation log and check the timestamp between when the sensor reported presence and when the routine actually executed, that’d tell us whether the sensor itself is slow to report or if it’s sitting in a queue somewhere after the fact — two different problems with two different fixes.
To be transparent, I have the FP300 devices exposed to Home Assistant via Matter, the automations run in HA and not in Aqara Home. That being said, here are my trace logs from a few automation runs today with one of my FP300s
In every case the light-service call itself goes out within 2-3 milliseconds of the state change, and the whole automation (including a timer-cancel step) wraps up in under 100ms. Nowhere close to “several minutes.”
2 Likes
Hello, show all the automations (On, Off) that you use for the light bulb that you described. Thank you.
