gfridland

Works well here!!!

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.

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!

Sent...Thanks for your help!

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.

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...

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.

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.

Sonuds like a good solution Tim...I will give it a try. I guess that this is where variables would be helpful. Thanks for the help.

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

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.

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!

Running XP-pro and 2.7.12 firmware. I do not save the log files...this was the file that was downloaded directly from the ISY. After clearing the log, all current events began to appear once again. I have not looked at the log file in quites ome time...longer than March 6th. I tried to look at the file a few times with similar results. I even ran a system query and re-opened the log file to see if the query results were logged and none were logged. After clearing the log file, all returned to normal funtion.

Is there a reccomended interval for the log file to be cleared? This morning I ran into a new (to me) situation. I noticed that my outside lights remained on beyond the set conditions that were programmed into the system. I have both time and light dependendant conditions for outside lights to turn on/off using both sunrise/sunset as well as the photosensor that is built into the motion detector. Interestingly, upon opening the ISY interface, my motion sensor was reporting that it is dark and the there is motion...neither of which are true. I waited for a change/reset with no results. I queried the system with no change. Until today, my configuration worked without error. So I decided to check out the log file to see what I can find... The log file opened properly, but did not contain any entries after march 6, 2010. Today is the 12th and there are no entries for any events since the 6th. All programs have been working during this logging outage. Is it possible that the log file was too big? Is there something else I should check? I cleared the log file and proper logging of events resumed. SO...was the ISY "stuck" or is there something more here?

From my experience, firmware 2.7.10 restores the button toggle mode, but not 6 or 8 button setting. If I recall correctly, 2,7,7 and below did not restore toggle mode or brightness....

As long as they have their own insteion addresses, then they should be able to be reprogrammed to work as desired by using the ISY. I believe that the "paired" switches are preconfigured for convenience. ......if they each have a unique insteon address, they are completely configurable.

Thank you for the reassurance...

Michel, I just read this comment you made in a different discussion area... As you can see, I have had issues with unexpected triggering of scenes. I just checked and the loads are controlled by Version 2D KPLs. Now...I haven't seen this occur since I reset a non-related togglelinc dimmer, but I am still not comfortable that I have found the solution. Just interested if the above statement may shed more light on my past (hopefullly) issue with unexplained scene triggers. Thanks for your input...

Delston... I am running an IRlinc receiver with the ISY and an MX900 form universal remotes...I initially had communication issues with the IRLinc-->ISY due to location... In my case, the IR linc is located in a logical place...my AV closet. I have a whole lot of components/ups/noisy equipment that interfered with the signal back from the IRLinc. I also was able to program it without problem, but when i went to use it, it would not transmit. The IRLinc...depending on how you program it will toggle the input. So you can test it right from the Java console. After linking, you may want to unplug/plug in the IRlinc. Not sure if it was relevant, but I may have also done that at some point. I put a filterlinc in the AV closet and Isolated the noise and all works great. Good luck!

geekdoc... I also went though a learning curve early on with Insteon controllers and devices. What I have learned is exactly what oberkc is saying. That is that everything can be done from the ISY. I used to use a different Insteon controller....the EZServe. The reason I went to the UD ISY is that I had the same frustration as you are experiencing when programmin devices. While using the EZServe, I had no ability to reliably create/contol scenes. So I ended up linking manually devices to "duplicate" what the EZServe was supposed to write into the devices. It ended up being a real waste of time and effort. After finally realizing that I was not getting anywhere but back to the beginning with the EZServe, I ended up buying the ISY. Best thing I did as with the ISY I was able to use it a THE interface to control all devices in my home. Any issue I had experienced initially had to do with either poor communication with my devices or the Firewall/Internet Antivirus software. Once resolved, the system is very robust. Issues with KPL's may also be related to the frimware on the specific KPL's and so the dimmin control, led brightness, etc. may be more a KPL issue than the ISY Bottom line...look at communication integrity and the firewall settings if programming issues may again arise.

Michel, Both newely provided links seem to work properly. I have been using HTTP://xxx.xxx.xxx.xxx/admin I will continue to monitor. Thanks for the help!

I have noticed an interesting situation in 2.7.10 while trying to create programs: 1. I first log into the Java console, everything works as it should. 2. Navigate to the "program details" tab 3. I get a quich flash from a progress window and am now int the program window. 4. I click on create new program..."New Program" is created in the program list. 5. I make changes, etc...and save changes...all good. 6. Now...I try to create another "New Program" by clicking on the New Program button...nothing happens. 7. Itry to create a new program form the left click drop down menu...same nothing happens. 8. I go to the "Program Summary" tab and I see two new unsaved programs in the list after refresh 9. I go back to the Program Details and don't see the programs (save or unsaved) I log out, clear java cache, log back in and can repeat about 50% of time. All other functions continue to work and update including device status, program refresh, etc. I have used both XP-Pro and Windows 7 64 bit with similar results. Thanks for reading!!!

Thanks Michel... Does this mean that, under normal conditions (or in 2.7.7), that a query would not be necessary for the EZIO's? Currently, I have set up a program that seems to work for me. The query occurs any time a state changes and also at timed intervals (1hr). Since doing this, I have not seen any upopulated status results. Once this bug is addressed, should I be able to remove the query programs?

I am not sure if this is related to the firmware upgrade. I have an EZIO2x4 that monitors my alarm panel. It has been working well for the past 6 months. Recently , I have noticed that upon logging into the console, some states of inputs and outputs are blank. If I switch an input state, only that input status gets updated (correctly). The others remain blank until they either get switched or I query the device. After a query, it will be populated for some time, however, frequently, when I log into the java console, the states are again blank, requiring another query to corret the status. I do not believe this a communication issue as there are never delays, or errors associated with the device when querying or testing scenes. I have not needed to query in the past to see all fieds correctly populated. As this unit is connected to an alarm panel, the status of each input is very important as I trigger programs based on the input status. At the moment, I have created a query on the device every time an input state changes, but I am not really certain that this is the right solution. If this is my best option, at what frequency should the query execute without bogging down the ISY?

I have had strange behavior in the past similar to this. What helped me was to add the unintended device to the scene and then remove it from that scene. This process will remove all links assosiated with the uninteneded device from that scene. Also, and I am not sure if this can be of issue, perhaps restore the PLM to ensure there are no Group mixups.