I have a strange behaviour when trying to use the “Brightness reached” event trigger on a a light sensor device in a scene.
In the trigger definition, I have to specify a “comparrison” (two “r”'s?) value in the GUI, which makes sense. The operators to chose from is < or >.
Which leads me to believe that if I specify “>5”, the scene will trigger whenever the light sensor value exceeds 5.
Well, it doesn’t.
For instance, I specified the scene to trigger at light sensor values >6.
It does not run even if the sensor value is 100. Not even if it goes from 0 to 100.
To debug, I asked for a notification on the event. I then get a bunch of e-mails saying:
[i]MiOS Trigger
Your trigger “Over 6” occured.
The originating device ID:18 _Light Sensor in room:
The ID is: 405141833
Code: CurrentLevel Value:5
[/i]
So:
Why do I get a notification saying 5 is greater than 6?
Why doesn’t the scene run when the value indeed gets higher than 6?
I have a similar scene set to trigger when the brightness value goes below 6. It works fine. So it seems like it’s only the “>” operator that is malfunctioning.
Upload the attached file to Vera ([tt]Apps[/tt] > [tt]Develop Apps[/tt] > [tt]Luup files[/tt] , [tt]Choose file[/tt] , check [tt]Restart Luup after upload[/tt] , [tt]Go[/tt])
Create scenes based on the now-separate ‘>’ and ‘<’ events. (Possibly modifying the existing scenes works by deleting the triggers and adding new ones. Might be safer to just delete existing scenes, then create new ones.)
Has anyone confirmed that the patch supplied by @oTi works or not ? I would like to use the ‘>’ as a scene trigger. Or maybe the up coming firmware upgrade for U5 might include a fix ??
The patch seems to work for me. After uploading the json (Vera 3 @ firmware 1.5.532), the choice for < or > has been replaced with a pull down menu with following options;
“Brightness goes above” and “Brightness goes below” the value specified.
Applied to my low light level scene the trigger seems to work fine when the light level goes below the specified value.
