I am using version 6.3 and am having a problem with initial actions executing quicker than the programmed delays. For instance I have some actions set with the following delays 3s, 5s, 7s, 35s, 70s and it is executing the 3s action and 35s action about 1-2 seconds apart and the next action about the same and then things seem to then proceed as programmed. This is bad because I am using these actions to open and close pool valves utilizing an EzFlora which communicates via Altsteon on a Vera 3. If I use a Vera scene with the same actions and delays it works properly and if I manually start the valves in the Vera UI5 it all works properly. Has anyone else had this problem. I currently have two PLEG licenses.
So the actions work properly when run from a scene. What happens if you call the scene from the PLEG action?
i initially had it setup that way but syaryed having issues with commands not executing completely. i thought it was related to my pool pump device that lost connection with vera that i had to reassociate. so i went to each scene and deleted the delay associated with the pool pump device but it didnt fix the problem. so i finally bit the bullet and replicated the actions in pleg. and yes i deleted the run scene actions so i dont have duplicate scenes running
So it didn’t really work correctly as a scene either… We may be able to help if you post the Status report from your PLEG - as a pdf, if you can.
I had it running properly with PLEG and the RunScene command for months and then something went wrong without my intervention. I’m not sure if its related to the PLEG updates or licensing or what.
Is it possible you are running the Action multiple times slightly offset in time while a previous actions is still running ?
This can be a problem with timed commands … Put a notification in the list of actions to see how often your are firing your conditions.
This may be more a problem with your trigger!