I have a two FP2 (latest firmware) and setup automation to only switch on the light when it’s occupied and lux is low. However, the automation still runs when it’s very bright in those two rooms.
Does anyone have the same issue? Is it a known issue? Any fixes?
As far as I know, this is not possible with the Apple Home app. With the “When” condition, you can only select either the presence sensor or the light sensor, but not both. I use the Aqara Home app for this.
Hi. I have the FP2 in Homekit. Several devices are displayed there. A presence sensor for each zone and a light sensor (that shows the light intensity). When I create an automation, I can select “when a sensor detects something” and then I have to select the sensor, but I can only select one sensor at a time. There is no IF block. There is only a WHEN block (where you can only select one option) and a THEN block (where you can select multiple devices or scenes).
It is possible to make another automation (for lighting) that will control (Off/On) the automation that turns on the light when it is moving. Does Homekat have an On/Off automation function?
Good idea, but unfortunately you can’t control the automations. In the THEN block, you can only select devices or scenes. And you can only control devices in the scenes. The automations can only be activated or deactivated manually.
That gives me another idea. Maybe it works with the shortcut app. I’ll try it out later and get back to it.
You can set the two conditions for light and presence using the Shortcuts app, but only for personal automations and not for home automation. This would make it possible to do something like, when the alarm clock rings, it’s bright, and someone is in the kitchen, then open the roller blind. But that is not something we wanted to do
My conclusion: It doesn’t work without an additional app like the Aqara Home app.
The pencil icon in the top-right corner, above the message, is used for viewing changes only. Another grey pencil can be found under the post to edit it.
Could this feature be unavailable to new users? I cannot edit my own topics.
I can only edit my comments in topics.
It looks like you’ve set up the automation correctly — I use similar conditional setups myself. The key question now is whether your lux readings are accurate. Is the automation actually running when the sensor reports more than 16 lux?
What I’m getting at is whether the light sensor’s placement reflects the true lighting conditions of the room. Could it be partially blocked or facing the wrong direction? Pictures would help if you can share them.
Here’s a quick way to test: when you feel it’s not dark enough (the situation you’re troubleshooting), check the lux reading before walking into the room — so you don’t trigger presence. See if the reading matches what you’d expect.
HomeKit is a framework, and Apple Home is just one app that uses it. You can use free apps like Eve or paid apps like Controller to build these automation with conditions for HomeKit specifically. Based on OP’s screenshot I’m guessing this is what he did.
Indeed, I’m aware. Apple is strategically retiring the more technical “HomeKit” name. As of iOS 26, they are emphasizing “Apple Home” as the unified brand for the entire smart home platform across all user menus.
Do you know a way to set the two conditions for light intensity and presence using the Apple Home app?
I think you may be missing my larger point. You can’t do this in the Apple Home app, but you can do it in 3rd party HomeKit apps as conditions are part of the framework [this is different than if you were to build the automation in the Aqara app]. And OP must know this since he has shown he has the automation properly built with Presence as a trigger and Lux as a condition.
When you build your automations you first choose the trigger (Occupancy Yes or No), then the Condition (Lux <= x), and then the action (turn on lights, trigger scene).