conditions = null

Plugins & Plugin Development Program Logic (PLEG)
1

Hi

a question :
I have an “expression”; in “conditions : Go”; which is empty
because it is launched by a scene (PLEG1 / RunAction / ConditionName: Go)

by cons, I get: state = null
and the “condition Go” is never true nor false
and therefore never launched.

it is not possible to do that?

Thank you

2

I would assume The RunAction command is only for PLEG Actions not Conditions (even thought the Advance scene UI is using the word condition).

To do what you are looking for:
Create a Virtual Switch (free app plug in if you don’t already have it)
Have your Scene turn the switch On for True. Then use the Switch as a Condition in you PLEG, where the switch is On. Then you need to figure out what turns the switch off, either another scene or the PLEG itself.

I had to work arround the fact that you can’t use the light sensor on an HSM200 as a condition because PLEG reads the values wrong, but Vera Scenes do it right. So I just created two scenes that set the virtual switch on and off when it is at the light threshold I want, and then use the virtual switch as the condition in my PLEG.

You can also interact with Counters in PLEG from a scene if you don’t want to use a virtual switch depending on what you are trying to do, I haven’t tried that however.

3

No!
You can RUN the actions directly from another PLEG or a scene … You do not need to have a Virtual Switch trigger in between.
There is some confusion between actions and condition because they are tied together.

When you run the Actions remotely it does NOT effect the value of the condition.

4

Richard, he was putting a Condition (that was blank) into the RunAction command, and hoping that would set the condition to true. That isn’t going to work which is what I was pointing out.

Instead he needs to put the name of the action directly into the RunAction. Or use another mechanism (like a virtual switch). The condition need to have something to evaluate, or you need to trigger the action a directly like the RunAction.

5

It’s the same thing !!
The RUN Acton command Run’s the Actions for Condition XX … it does not set Condition XX to true.

But to have actions on XX you have to have a Condition named XX.

Yes it can be blank !

6

think for reponses

what I was doing

- in scene / advanced

"Alarme"		RunAction		conditionName      Go

- in PLEG “Alarme”

no input

Condition Name Go

no Condition Expression

Actions for conditions Go

Alarme	StartTimer	timerName=Ttot intervalTime=
7

Richard thanks for the correction ;D that makes sense
Minimoibientot, can you attach your status report after to think you have triggered the Go action?
Does Ttot show any start times?

Richard would have to state if Go would ever show true/false in the status, but the timer last run time should revel what is going on.

8

@minimoibientot
Note: You could have just started the timer from the Scene …

9

my status report

timer is started

@ Richard
I had not thought about to this option :-[ :-[