Scene triggering by variables

[tnesheim 8]

I have a scene that behaves strange. The IF-conditons consists of "static variables"(Dognfase, PersonStatus, HusStatus) and a "counter variable"(HusstatusTeller). The counter is the only triggering variable.

Please login or register to see this attachment.

The counter variable rarely reaches 0 but the scene triggers anyway. (The counter variables counts down towards 0 but is reset to 300 by motions sensors, basically a presence detector that times out when reaches 0)

Please login or register to see this image.

/monthly_2017_09/triggered.png.20f0f2fad8a3bd11f907fd52946cf6ed.png" alt="triggered.png.20f0f2fad8a3bd11f907fd52946cf6ed.png" />

According to my knowledge (or lack of it) the scene should be triggered by the "HusststusTeller" which is specified to be the trigger variable. But otherwise seems to happen. Help!

 

[pos 22]

If you have a variable as trigger to a scene, it will trigger the scene every time the variable change. When the scene triggers, you have to take care of its value if you want to do something with that particular value. For example... A scene trigger with a Fibaro motion sensor will trigger the scene every time it breaches AND every time it restores. If you do not want to use restore, you could check for its value in the start of the scene and simply exists.

 

It sounds as per your description that the trigger variable is continuously changing and therefor will trigger the scene v e r y often (i.e at every step of the counter). Actually... that sounds like a sub optimal setup and unnecessarily aggressive to the system. Or I maybe misunderstood you there... If you have a "max scenes" count, it could be so that it wont trigger the next scene as there are already "max num" scens running. I think 2 is default. Maybe it therefor missed the "0" as you already have max amount of scenes running that hasn't already exited due to your aggressive scene triggering. I can understand strange behaviour with such setup. I suggest you do a re-design.

 

I do similar stuff. For example I trigger a scene when a motions sensor in the hallway sees somebody and the light level is low enough. After that the scene runs continuously in a controlled loop as long as the light is on. If new motion is seen within a certain time a global variable is updated with current time. If no motion for xx minutes (compare current time with global variable time) the scene exists completely. The loop is not to agressive to the system as it is more than enough to loop every 5s. But... this requires some LUA skills.

 

There are many good people on the forum that has posted and shared a lot of nice code. You can have a few ideas of such scenes here from me: 

Please login or register to see this link.

 Maybe other sees this and give you even more

 

/Peo

 

[tnesheim 8]

Aha, thanks!! It makes sense that the scene is triggered with every parameter change to check of any of the conditions are meet.  My counter decreases value every 10 Seconds, and is also reset to a predefined value when movement is registered by a sensor. The down counting is done in LUA-code. I should probably scale the down counter to change every minute, this will reduce the "check the conditions" significantly...