Scene trigger on device value change (true/false)

[squirblej 2]

Hi folks: I have a scene triggering on a motion event from a device which changes the value to "true" (motion detected) and "false" (end of motion event).

 

Please login or register to see this code.

This trigger works perfectly but it's rather duplicative.

 

I was expecting to be able to trigger based on a simple change of value like in HC2.  I can't find a way to do it.  If it were a global variable, I could compare against a random value: 

Please login or register to see this code.

But I can't find a version of this that works for the logical comparison in my device-triggered scene.

 

Ideas?

[jgab 1,565]

15 minutes ago, squirblej said:

Hi folks: I have a scene triggering on a motion event from a device which changes the value to "true" (motion detected) and "false" (end of motion event).

 

Please login or register to see this code.

This trigger works perfectly but it's rather duplicative.

 

I was expecting to be able to trigger based on a simple change of value like in HC2.  I can't find a way to do it.  If it were a global variable, I could compare against a random value: 

Please login or register to see this code.

But I can't find a version of this that works for the logical comparison in my device-triggered scene.

 

Ideas?

 

No, it's not possible. I have had many rants in this forum how badly the conditions "thingy" is implemented.

First it's not made for humans - it's a hack to easily compile block scenes too. That programmers would get access to this must have been an after thought. As you say, the syntax is repetitive and  and prone to errors if typed by humans. It's also semantically iffy, look at the 'cron' expressions and greater and less operators...

And then the lack of essential operators like if an expression has been true for a given time. The possibility to have variables in expression substituting for values (I don't mean the global-variable' but having the value field fetching it's value from a variable.) Then why can't custom-events match against the userDescription field etc etc.

No, how 'conditions' were implemented is probably the worst design mistake in the HC3. Because it could have been great feature done right.

 

[cag014 585]

+1

[squirblej 2]

Ok, good to know.  Thanks guys.