I know that having scenes call other scenes with LUUP code is not recommended because of some inherent unreliability of the actions only being attempted once.
There is nothing wrong with calling a scene from another scene. MCV did not provide an easy way to do this without using LUUP. The PLEG and PLTS provide an action that you can use in the Advanced Tab of a Scene ... select any PLEG/PLTS device ... then the Action is RunScene.
The limitation with Scenes has to do with Delayed actions. If Vera restarts during the delay part of the scene … anything that was delayed is lost. If you have an immediate mode turn on your sprinkler system and a delayed cycle turn it off 1 hour later … You could be surprised to come home to a soggy yard, and high water bill … and the green police all over your case … because Vera restarted during that period!
However, I noticed that within PLEG, I can reference a condition name in the advanced tab within the Actions generator. It seems this would allow me to have Actions evaluate conditions which trigger further actions.
This does NOT actually evaluate conditions ... it uses the results of the previous evaluation of the conditions. It will evaluate an expression. It is true that an Action can trigger an input to PLEG ... and cause it to do more work.
I am realizing that the PLEG itself could all but replace every scene logic that I have.
PLEG is designed to replace all of the Automation Logic that was previously split between multiple scenes and multiple plugins to accomplish a single task. I still use scenes for things I want to initiate manually.
I am doing something wrong here.
When ever the Event TurnLightsOn has occured and it is Midnight (schedule starting at 0:00). I want the below condition be true and switch off the lights after 5 min. It just does not work
Well I am not sure what you really want to do … But I know what you supplied is probably not going to do it. Midnight is TRUE ONLY at Midnight and false every other time (unless you provided an interval in the timer).
So this condition would only be TRUE at Midnight if the light was turned ON during the 5 minutes before midnight.
Midnight is a schedule which should go off after 6 hrs. The goal is to switch off the light after 5 minutes, when it was turned on because of another trigger. This should only happen from 0:00 till 06:00
Next time send the WHOLE report!
But there is enough there to SEE that the timer is NOT setup to turnoff after 6 Hours.
It is only on for a single point in time! And in this case it’s: 22:19:00
What makes you think it should go off after 6 Hours ?
Maybe you made a change and forgot to save it ?
It was in the release notes …
I released the OFF in one version (Delta time only supported)
In the next release I generalized the implementation and indicated that you needed to enter the OFF times again.
I finally could find a way to get this :
Condition = AND (Condition;NOW>timer) assuming ‘timer’ is over one minute…
I called it ‘debounce’ condition… It works well.
[quote=“RichardTSchaefer, post:70, topic:175016”]It was in the release notes …
I released the OFF in one version (Delta time only supported)
In the next release I generalized the implementation and indicated that you needed to enter the OFF times again.[/quote]
Can you clarify what you mean by this? I have a condition where one of the inputs is a schedule trigger. I reset some virtual switches at 5am. Originally, I had the trigger ON at 5:00:00 and OFF at 5:01:00. I found that this didn’t reset my virtual switches.
I made it so that the schedule just has an ON time and it works fine now.
Are you saying that with 5.2, schedule triggers should always have an OFF?
Are you saying that with 5.2, schedule triggers should always have an OFF?
NO
If you defined a timer with OFF semantics prior to 5.2 you need to re-define the OFF time in 5.2.
There was only about a 2 week window between the two releases. So this should not effect very many people.
I just updated apps to 5.2 (they all say 5.2 in Vera) BUT when I open any PLEG devices, and choose Inputs tab I get…
“Version mismatch! PLEG Version: 5.1 PLC Version: 5.2”
Then you will have to update PLEG again. It must have failed …
The error is telling you that incompatible versions are loaded.
Since PLEG is at 5.1 and PLC is at 5.2 … you should be able to figure out which to load.