Jump to content

Scenes turn off after reboot


gfridland

Recommended Posts

Posted

I have noticed that 2 scenes turn off after re-boot/ during power-up.

 

Both scenes are ones that are exlusively time triggered (sunrise/sunset). They only contain togglelink relays. One scene contains 3 togglelink relays, the other 2 togglelink relay.

 

All other scenes/devices are not affected.

 

I have looked at the configuration screen and there is a checkbox for "catch up schedules" (not sure on exact wording). This is checked on my ISY. Is this causing my issues?

 

I'm using 2.7.13 firmware, but this issue has persisted through all firmware revisions that I can remember.

 

Any other ideas are welcome!

Posted

Hi gfridland,

 

Catchup schedules would only be the issue if the reboot is within the grace period of your actual timed event.

 

Can you ensure that you do not have the Run at Startup checked (in Program Summary page).

 

With kind regards,

Michel

Posted

Thanks for the reply Michel,

 

I have "run on startup" checked only for non-related programs. The only program that runs at startup is a reboot notifier which sends me notification if the ISY reboots, which helps me follow power failures at the home.

 

Looking at the log file, it appears that during the system query that runs every time the ISY boots up, the scenes in question are toggled a number of times as seen in the copy of log below:

 

Scene:Front Outside Lights / Front Outside Lights Scene Off 0 Tue 2010/03/16 08:23:34 PM Program Log

Scene:Upstairs Hall / Upstairs Hall-Murano Scene Off 0 Tue 2010/03/16 08:23:34 PM Program Log

Rear Outside Lights / Rear Outside Motion Lights On 255 Tue 2010/03/16 08:23:34 PM Program Log

Scene:Upstairs Hall / Upstairs Hall-Murano Scene On 255 Tue 2010/03/16 08:23:34 PM Program Log

Scene:Front Outside Lights / Front Outside Lights Scene On 255 Tue 2010/03/16 08:23:34 PM Program Log

Scene:Alarm / Alarm Query Scene Status Query Tue 2010/03/16 08:23:35 PM Program Log

Alarm / 01.76.85.2 Status Query Tue 2010/03/16 08:23:35 PM Program Log

Alarm / 01.76.85.1 Status Query Tue 2010/03/16 08:23:35 PM Program Log

Rear Outside Lights / Rear Outside Motion Lights Off 0 Tue 2010/03/16 08:23:35 PM Program Log

Scene:Upstairs Hall / Upstairs Hall-Murano Scene Off 0 Tue 2010/03/16 08:23:37 PM Program Log

Rear Outside Lights / Rear Outside Motion Lights On 255 Tue 2010/03/16 08:23:37 PM Program Log

Scene:Upstairs Hall / Upstairs Hall-Murano Scene On 255 Tue 2010/03/16 08:23:37 PM Program Log

Scene:Front Outside Lights / Front Outside Lights Scene On 255 Tue 2010/03/16 08:23:37 PM Program Log

Scene:Rear Outside Lights / Rear Outside Light Button Sce Off 0 Tue 2010/03/16 08:23:39 PM Program Log

Scene:Upstairs Hall / Upstairs Hall-Murano Scene Off 0 Tue 2010/03/16 08:23:39 PM Program Log

Scene:Front Outside Lights / Front Outside Lights Scene Off 0 Tue 2010/03/16 08:23:41 PM Program Log

Scene:Rear Outside Lights / Rear Outside Light Button Sce Off 0 Tue 2010/03/16 08:23:42 PM Program Log

Rear Outside Lights / Rear Outside Motion Lights Off 0 Tue 2010/03/16 08:23:44 PM Program Log

 

 

Interestingly, the only scenes that are affected are those that are timed based on sunset, sunrise.

 

Thanks again.

Posted

I just found a possible cause...

 

I have a program that runs based on the status of my photosensor that is built into the insteon motion sensor.

 

This program turns on/off all the scenes that are in question.

 

What I notice is that when the query occurs on a power up, the motion sensor does not send a status for either the photosensor, motion status. Based on this "no state" condition, would the ISY do with that the prorgram that is based on the photosensor condition? toggle, shut off, or turn on the scenes?

 

If this is the culprit, how would I disable it from happening on startup? Remove the motion sensor from the querry?

 

Thanks

Posted

Hi gfridland,

 

After a reboot the ISY considers any programs using the motion/dusk-dawn and low batt status conditions as false. I had a similar issue with using any status based on the Insteon motion sensors whether it was the motion or dusk/dawn and also with Triggerlinc’s. I found the solution in the Wiki. I created two programs for each function I wanted preserved in the event of a reboot. One program which monitors the status of the event (say dusk/dawn) and another program which when the ISY reboots will turn the first program back to true if its status was true before the reboot.

 

Program: Garage D/D Status

If
       Control 'Garage MS Dusk/Dawn Sensor' is switched On
   And Control 'Garage MS Dusk/Dawn Sensor' is not switched Off

Then
       Set Program 'D/D Status Reboot' To Run At Startup

Else
       Set Program 'D/D Status Reboot' To Not Run At Startup 

 

 

Program: Garage D/D Status Reboot

If
  - No Conditions - (To add one, press 'Schedule' or 'Condition')

Then
       Run Program 'Garage D/D Status' (Then Path)

Else
  - No Actions - (To add one, press 'Action')

 

Use the first program (Garage D/D Status) in any if statements in other programs where the status or control of the dusk/dawn sensor was used. Now those programs will run based on the status of the new program instead of directly by the sensor. If the ISY reboots the Garage D/D Status program will return to its original state before the reboot.

 

Tim

Posted

Well...I tried the solution but the same issue exists...it appears that it is, in fact, the timed events that are causing the scenes to turn off during reboot. If I disable the timed (sunset/sunrise) events, the light do not shut off.

 

Any other ideas?

 

Thanks in advance.

Posted

Hi gfridland,

 

Are you rebooting the system during those times +/- the grace period? Or, do they run regardless of the time. Furthermore, can you tell me whether or not you have Run at Reboot set for this program?

 

With kind regards,

Michel

Posted

Hi Michel,

 

I do not have the Run at startup set for these programs.

 

I do a reboot during the grace period. But it is not during a condition change. The reboot is done through the admin console. The same effect is seen during a power glitch when the ISY reboots on its own.

 

The grace period that I have set is 10 min.

 

The conditions for te sunrise/sunset are only time based and each have a minor time offset (2-10 minutes)

 

Thanks for your help.

Posted

I have a similar issue but assumed that was the way it was supposed to work so have ignored it.

 

I have a program that runs every time I reboot. It is not set to run at startup. It is set to run if the status of a keypadlinc is off which it always is when I reboot.

 

If I change it to run only if the condition of the button is set off it does not run at startup.

 

It happens to be the only program that checks the status of buttons, all other programs use timed events or condition changes.

Posted

Hi stevehoyt,

 

I think the problem with your system is because of the initial Query which changes the status of all your devices and thus the programs get re-evaluated for those that have conditions dependent on that device.

 

gfridland,

 

Do you have any other programs dependent on this program?

 

With kind regards,

Michel

Posted

Michel,

 

The sunset / sunrise programs are independant. They are not if/then/else conditions for any other programs.

 

there is a whole lot of scene activity for the only the related scenes...off-on-off-on-off.

 

All but the "Rear Outside Light Button Sce" were ON prior to reboot. After reboot, all are OFF. All scenes affected are sunset/sunrise triggered.

 

Scene:Front Outside Lights / Front Outside Lights Scene Off 0 Sat 2010/03/20 08:13:20 PM Program

Scene:Upstairs Hall / Upstairs Hall-Murano Scene Off 0 Sat 2010/03/20 08:13:20 PM Program

Rear Outside Lights / Rear Outside Motion Lights On 255 Sat 2010/03/20 08:13:20 PM Program

Scene:Upstairs Hall / Upstairs Hall-Murano Scene On 255 Sat 2010/03/20 08:13:20 PM Program

Scene:Front Outside Lights / Front Outside Lights Scene On 255 Sat 2010/03/20 08:13:20 PM Program

Scene:Alarm / Alarm Query Scene Status Query Sat 2010/03/20 08:13:21 PM Program

Alarm / 01.76.85.2 Status Query Sat 2010/03/20 08:13:22 PM Program

Alarm / 01.76.85.1 Status Query Sat 2010/03/20 08:13:22 PM Program

Scene:Upstairs Hall / Upstairs Hall-Murano Scene On 255 Sat 2010/03/20 08:13:24 PM Program

Rear Outside Lights / Rear Outside Motion Lights Off 0 Sat 2010/03/20 08:13:24 PM Program

Scene:Upstairs Hall / Upstairs Hall-Murano Scene Off 0 Sat 2010/03/20 08:13:24 PM Program

Rear Outside Lights / Rear Outside Motion Lights On 255 Sat 2010/03/20 08:13:24 PM Program

Scene:Upstairs Hall / Upstairs Hall-Murano Scene On 255 Sat 2010/03/20 08:13:24 PM Program

Scene:Front Outside Lights / Front Outside Lights Scene On 255 Sat 2010/03/20 08:13:24 PM Program

Scene:Front Outside Lights / Front Outside Lights Scene On 255 Sat 2010/03/20 08:13:25 PM Program

Scene:Rear Outside Lights / Rear Outside Light Button Sce Off 0 Sat 2010/03/20 08:13:25 PM Program

Scene:Upstairs Hall / Upstairs Hall-Murano Scene Off 0 Sat 2010/03/20 08:13:26 PM Program

Scene:Front Outside Lights / Front Outside Lights Scene Off 0 Sat 2010/03/20 08:13:28 PM Program

Scene:Rear Outside Lights / Rear Outside Light Button Sce Off 0 Sat 2010/03/20 08:13:29 PM Program

Rear Outside Lights / Rear Outside Motion Lights Off 0 Sat 2010/03/20 08:13:31 PM Program

 

Makes no sence to me...

Posted

Well...I had a power failure last night that lasted about 1 hour in the evening. When the power was restored, the scenes in question toggled on-off 4 times and then ultimately shut off. The events all occurred after sunset trigger, and before the sunrise trigger.

 

This should not be happening based on the conditions.

 

What is peculiar and may be relevant to the experts is the fact that all affected scenes toggle on-off during the boot process.

 

Any help would be appreciated.

Posted

Hi gfridland,

 

The Catchup Schedules at restart box on the configuration page indicates that when the ISY is restarted, all schedules for the current day are run (starting from just after midnight the night before up until the current time).

 

The Grace period is used during regular operation, and only in the unlikely case where the ISY does not test a time condition at the exact moment specified in the condition.

 

Therefore, as you mentioned in your original post, you should uncheck the Catchup Schedules at restart box to prevent those programs from running when the ISY restarts.

Posted

Chris...If this is true, then this can certainly cause the issues that I am seeing.

 

I misunderstood what the "Catchup Schedules" funtion was.

 

It appears that all timed events are running upon reboot. Coincidentally, all my time-triggered events are for sunset/sunrise lighting controls so I would not notice other issues during reboot.

 

I will try to uncheck the and hopefully resolve the issue.

 

THANK YOU!

Posted

The issue has been resolved by un-checking the "Catchup Schedules upon Reboot" in the configuration screen.

 

All scenes come up as they were prior to reboot.

 

Thanks to all for your help.

Guest
This topic is now closed to further replies.

×
×
  • Create New...