Of two scenes that use light level as a trigger, only one works. WHY?

I’m using two Aeotec 4-in-1 Multisensors with a Vera 2. One – “the Master Multisensor” – is USB powered, mounted under an eave outside, and all sensors are employed (parm #101=224, parm #111=600). The other is solely used as a motion sensor.

I created two scenes (see below): one arms both motion sensors at nightfall, the other scene is supposed to disarm them at sunrise but fails to yield any results.

Given the two scenes below, can anyone suggest why the “Detect Night” scene works but the “Detect Daylight” scene does not?

"Detect Night" (WORKING SCENE) scene:
Both Motion Sensors on the network have the "Arm" button enabled
Trigger device is Light Sensor (Master Multisensor).
	Type of Event is "Brightness reached"
	Comparison is <
	Level is 5

"Detect Daylight" (NON-WORKING) scene: Both Motion Sensors on the network have the "Bypass" button enabled Trigger device is Light Sensor (Master Multisensor). Type of Event is "Brightness reached" Comparison is > Level is 5

Most nights the light sensor reaches 0 before it’s totally dark outside. If I check the Vera GUI after dark I can see that both motion sensors are armed.

When I check the Vera GUI in the morning, well after it’s full daylight outside, I’ll see that the motion sensors are still armed. At that point if I manually “Run” the “Detect Daylight” scene it will disarm both motion sensors.

BONUS QUESTION: when scenes like these exist, does each scene run only once when the comparison level changes from false to true? So, for example, does the “Detect Daylight” scene run only once when the light level is detected equal to 6 or greater (with parm# 111 = 600, that leaves 10 minutes between light level reports)? For the remainder of daylight is this scene dormant even though the light level is > 5?

Hello,
I do have exactly the same problem.
The trigger is working only when I use the < comparison.
When I use the > nothing happens.
Any idea anyone?

For me, “<” works as expected in these comparisons, but “>” works as if it were “<”. I sent an email to Vera support asking them to file a bug.

I’m glad you brought this up. I use an Everspring light sensor and I thought I was going crazy when I was trying to use the < and > to make things happen. It seemed like one of the operators was working but the other one didn’t work the way I thought it was supposed to. I got around it by doing something like this:

Total light level range is 0-3000. I want something to come on when it gets below 300.
I have one condition to turn lights on when it gets below 300… brightness reached<300
Then I have the condition to turn them off when it goes above 300…brightness reached<3000
I tried doing brightness reached>300 or something similar to turn the lights off and nothing worked. Doing it in this way was the only way I found. I just thought I was crazy lol