Odd behaviour of Schedules on reboot.

Plugins & Plugin Development Program Logic (PLEG)
#1

I’ve been having odd behaviour when rebooting.

I have a pleg scene set up that will turn on a light when a motion sensor is triggered but only between certain times. All works well normally but in a reboot it will turn the light on even outside of the time range. It will continue to do this until the time has passed the stop time. I also have other lights that do the same odd behaviour.

It’s like pleg does not know what time it is even though the time is right on Vera.

Now I’m sure this will be user error but this is reasonably new behaviour…,any ideas where I’m going wrong or what I need to change ?

#2

If the schedule is an absolute schedule, and Vera is restarting/rebooting during the time when that schedule should have started or stopped, then the schedule won’t change properly. Look under the Examples sub-forum and Richard has a thread called “Fault Tolerant Schedules” that deals with this.

#3

In the instances ive had vera is rebooted outside of the time periods in the schedule but when booted back upmseems to think that time period is active even when it’s quite a few hours away. Now that time period has com and gone it’s back to normal. It’s quite strange hence wanted to see if anyone else had experienced the same issues.

#4

I still seem to be getting this issue after reboots. Sometimes it just takes a few days for the schedules to cycle through start stop before everything goes back to normal and weirdly some devices “resolve” faster than others. I have a sensor on the stairs that after a reboot will turn the light on at anytime but after the schedule time has started / stopped on that day then its fine.

My window lights however just don’t resolve themselves as quickly. Following a reboot at the weekend for firmware upgrade the window lights are still coming on when the home / away status changes despite being outside the time of the schedule. I believe its setup correctly and I’ve not changed the schedules since they were originally set up and were working (copy report attached).

Anyone seen this or got any ideas ?.

#5

If Vera is OFF (boot or reload) when an ABSOLUTE time happens … it will not trigger until the NEXT scheduled time.

PLEG does NOT know about being between an interval … it only knows to set an input to TRUE at the beginning of the schedule and to OFF at the end of the Schedule.

But it can also be toggled by logic or by you manually performing “DO IT NOW”

I always recommend using intervals when possible …

#6

[quote=“mzpost, post:4, topic:189445”]I still seem to be getting this issue after reboots. Sometimes it just takes a few days for the schedules to cycle through start stop before everything goes back to normal and weirdly some devices “resolve” faster than others. I have a sensor on the stairs that after a reboot will turn the light on at anytime but after the schedule time has started / stopped on that day then its fine.

My window lights however just don’t resolve themselves as quickly. Following a reboot at the weekend for firmware upgrade the window lights are still coming on when the home / away status changes despite being outside the time of the schedule. I believe its setup correctly and I’ve not changed the schedules since they were originally set up and were working (copy report attached).

Anyone seen this or got any ideas ?.[/quote]

I would be concerned you might be having a lot more re-loads than you think. You mention re-boots, but how often is Vera re-loading?

#7

Interestingly the reboot I did was not during the time the trigger was active (as they run from early evening to late evening and the reboot was done during the day hence I did not think it would have any effect at all.

I don’t think I’m getting any reboots the restart was done by me as part of a firmware update. If I was getting restarts the other units would show the same behaviour. This is more of a puzzle as it’s impacting some scenes and not others hence it looks weird rather than being an “expected” behaviour.

#8

I don’t follow. If this particular VERA has something causing it to be unstable, it could be reloading (AKA restarting different from rebooting) every few minutes and produce what I think you are describing here. Do you have a way to track reloads to confirm? (VeraAlerts process notifications, LuaUPnP.log, startup LUA script to track restarts, etc)