If you use light level to decide whether lights should turn on, put that sensor where people actually experience the room, not next to or under a lamp.
I had a lux reading under the TV that sat around 300 lx whenever the ambient lights were on. Automations then thought the room was bright enough and refused to help when I walked in from the dark hallway. Moving the sensor to the kitchen sink / walk-in path fixed it overnight.
Same idea for presence: cover the path you walk, not the corner that looks neat on a floor plan.
@matthiaskuehn9 Such a solid StarterTips post—lux placement is everything when you’re using illuminance as an automation gate.
On the Aqara side, this lines up perfectly with the Light Sensor T1 guidance: don’t aim the sensor directly at a light source, otherwise the lux value can get skewed and your automations will make the wrong call (exactly like your “room is bright enough, do nothing” situation).
And your “put it where people actually experience the room” point also helps with reliability in general—especially since sensor-to-hub performance can vary by layout, and Aqara notes it works best with no more than two walls between the sensor and the hub (so moving it to a more practical location can sometimes improve both readings and connectivity).
Curious: after moving it to the sink/walk-path, did you end up adjusting your lux threshold too, or did placement alone fix it?