Failing updating a variable using a light sensor

Questions & Help
1

I feel kind of stupid not being able to get this to work. Who can help me out here?

I’ve got a Fibaro Motion Sensor FGMS-001 which only function is to look outside in order to determine if it’s dark (“donker” in Dutch) or not. (I do not want this sensor to look inside the house because once a light is triggered it’s not dark anymore :wink:

The idea is that, if the light is above 500 lux, the variable “Donker” is set to “No” (“Nee”). And if it drops below 500 lux, the variable ‘Donker’ is set to “Yes” (“Ja”). (This variable is used in multiple flows.)

Sounds simple but I can’t get it to work right. The variable does not change when it needs to (dropping or rising above 500 lux) and even seems to change spontaneous to “Yes” in the middle of the day, triggering lights after movement.

Below a screenshot of the flow and of the Fibaro setting. In the last one, the value “300” should send the amount of lux every 5 minutes to Homey.

What am I missing here?

Flow
Fibaro settings

2

For one, you have your cards in the reverse order: when the luminance exceeds 500lx, “Donker” should be set to “Nee”.

Also, are you sure that the luminance value of 500lx is correct for your situation? How did you determine that this is the correct value? Does it take cloudy days into account, for instance?

3

Thanks, Robert. What a dumb mistake on my side. I consequently overlooked that.

As for the 500 lux… That’s a value that needs to be finetuned to personal preferences. In the end it does not matter what time it is or if it’s (really) cloudy, it is the amount of lux available that determines if lights are swithed on (by motion sensors) or not.