Anyone have any ideas why some fairly standard PLEG schedules are sporadically being missed or just not being started. Attached are two files that illustrate:
This one shows the configured schedules (temp1.jpg) that I’m expecting to work, most of the time they do work, but sometimes some get skipped. PLEG never realises they’ve been missed and carries on with life.
This one (temp.jpg) shows the errors circled where something is not firing. The actual time for the screenshot is around 1600 and the 1500 schedule has just not started, yesterday it worked fine. You can also see a weekend schedule that was missed (also circled).
Do you know if your Vera is restarting a LOT.
If Vera is restarting during an “Absolute” time … the event is lost until the NEXT absolute time.
Unless you are Very stable I do not recommend ABSOLUTE OFF times. You would be more reliable with an INTERVAL.
Even if Vera restarts during the OFF time … it will fire when Vera restarts … because the Interval is exceeded.
Thanks Richard,
My Vera is not restarting a LOT, perhaps a few times a day whilst I play with some things - however, the chances of a restart during the ‘off time’ is slim as it’s only for 1 second before the next ‘on time’ PLEG is missing schedules ‘probably’ once a day, maybe more.
Ironically, I only added the ‘Off time’ to each Schedule to see if this would fix the problem. In my conditions, I’m only checking for the latest timestamped ON event and have no interest in the OFF time anywhere. I had the exact same symptoms with only the ON schedule 
I’m wondering if PLEG is missing some schedules because of the CPU load, which can reach > 80% on my Vera lite ?? Just thinking that if PLEG is waiting for 15:00:00 and there’s something going on that causes latency around that time, when PLEG checks the time at the next interrupt, it’s now 15:00:01 (or later) which doesn’t match and therefore nothing is fired. Is there a way I can configure PLEG to have a schedule fired if time is >= 15:00:00 and not time = 15:00:00 ?
Cheers
David
Are you on UI5, UI6 or UI7 ?
On UI5 I have never seen a schedule missed because of load.
But I have personally never seen a Vera with an 80% cpu load … What are you doing ?
Actually the probability of Vera restarting 1 second from another interval is very high if Vera is not in a stable configuration. Any action has a good probability of causing a restart.
PLEG does NOT wait on anything … it does not POLL … It asks Vera to call it at the appropriate time (i.e. when device variables change or schedules occur)
it asks Vera to call it at the appropriate time (i.e. when device variables change or schedules occur)
- aha, that explains another question I had about all these Z wave jobs that are created by the PLEG device when it starts up. Don't these jobs get reset/cancelled when Vera restarts ?
Am on UI5, really racking my brain as to why this is happening as most of the time it’s fine. I’m going to remove the OFF schedules now and leave it for a day or two to see if it makes any difference - will report back on here so others may learn from my situation.
Cheers
David
PLEG will only cause a Z-Wave commands to be sent … when an Action fires.
You will see the time of this in the Status report.
If you have actions with delays that are started before Vera restarts, the delayed part of the actions will still happen after Vera restarts.
There is a lot of Z-Wave stuff happening when Vera restarts … but that is Vera initializing itself.