Morris Hansen Posted December 28, 2007 Posted December 28, 2007 I have noticed that whenever the ISY is powered on or rebooted, it turns all the lights off. I am tyring to troubleshoot a networking issue so I am changing the IP address and rebooting it. Every time it comes up, all the lights turn off. This is a nusance especially when working at night. Is the ISY suppose to do this? If so, is there a way to disable this feature. Quote
yardman 49 Posted December 28, 2007 Posted December 28, 2007 I have noticed that whenever the ISY is powered on or rebooted, it turns all the lights off. I am tyring to troubleshoot a networking issue so I am changing the IP address and rebooting it. Every time it comes up, all the lights turn off. This is a nusance especially when working at night. Is the ISY suppose to do this? If so, is there a way to disable this feature. Did you create any programs in the ISY? It sounds as though you have a program written that turns off all of your lights, and is set to "run at reboot".. Keep in mind that the "Run" command at reboot will jump to the "Then" section and run your program, ignoring the conditional "If" section. So if you have a conditional time for such a program, using "Run at Reboot" will ignore the time condition statement and just run the program's "Then" section. Best wishes, Quote
Morris Hansen Posted December 28, 2007 Author Posted December 28, 2007 I have just started setting up the ISY and only had one program in there just to test the programming. The program was triggered by a Fast On and it would turn on 2 lights. The only other program was the default one that does the status query at 3am. Since hooking up the ISY, I have consistently had random lights come on a different times of the day. I have an ELK M1G also so I left the ISY off for several days and I did not have any random lights coming on. So last night I deleted all the lights in the ELK to see if it was part of the problem. This morning I had random lights on again so it pointed back to the ISY. I have factory reset the ISY and will start over. It seems odd that it would do this but this is not the first odd behavior I have seen with the ISY/99i. Quote
yardman 49 Posted December 28, 2007 Posted December 28, 2007 I have just started setting up the ISY and only had one program in there just to test the programming. The program was triggered by a Fast On and it would turn on 2 lights. The only other program was the default one that does the status query at 3am. Since hooking up the ISY, I have consistently had random lights come on a different times of the day. I have an ELK M1G also so I left the ISY off for several days and I did not have any random lights coming on. So last night I deleted all the lights in the ELK to see if it was part of the problem. This morning I had random lights on again so it pointed back to the ISY. I have factory reset the ISY and will start over. It seems odd that it would do this but this is not the first odd behavior I have seen with the ISY/99i. Hello Mo: Thanks for the update. Boy that does sound like strange behavior. I also didn't know that you had the 99. Since you didn't specify, I thought you had the ISY-26. My ISY-26 did not come with any "default" program that did a system status query at 3 am. Are the 99s coming through this way? Has anyone else seen this? Best wishes, Quote
MikeB Posted December 28, 2007 Posted December 28, 2007 There have been reports on Cocoontech of users with the Elk/PLC combo experiencing random lights coming on. You might want to run a search on there. I have never heard of this with the ISY, so I suspect it is somehow Elk-related. Quote
Morris Hansen Posted December 28, 2007 Author Posted December 28, 2007 That is what I thought as well so I deleted all the lighting in the Elk and I also removed the PLC that was connected to the Elk. It still turned on lights this morning. I would be nice if the log was more specific in what triggered a specific action. ie. Elk triggered action vs. program vs web/user, etc. I will research Cocoontech. Quote
Michel Kohanim Posted December 30, 2007 Posted December 30, 2007 mohansen, Please make sure you do not have any programs with "Run at Reboot" ... if you do, that might explain why all your lights come on when ISY is rebooted. With kind regards, Michel That is what I thought as well so I deleted all the lighting in the Elk and I also removed the PLC that was connected to the Elk. It still turned on lights this morning. I would be nice if the log was more specific in what triggered a specific action. ie. Elk triggered action vs. program vs web/user, etc. I will research Cocoontech. Quote
Morris Hansen Posted December 30, 2007 Author Posted December 30, 2007 Thanks for the tip. I have factory reset the ISY and noticed there are no programs by default. I am adding 1 device at a time instead of having it discover the entire network. I have used Power-Home alot in the past to manage my links. Would you recommend I factory reset every device? I have 36 devices so I was hoping not to have to do this. FYI. When adding back in my Elk configuration, the ISY required a reboot before it would show up. Is this how it is support to work or a bug? Quote
Michel Kohanim Posted December 31, 2007 Posted December 31, 2007 Hello mohansen, Factory reset removes all the schedules. You might want to add back If Time is 3:00 A.M. Then Set My Lighting Query This code makes sure your ISY is in synch with your devices. Adding devices back one at a time and choosing the first option clears each device's database (unless there's a communication error) and, as such, you do not have to do a factory reset on your devices. What do you mean by " ... adding back my ELK configuration"? ISY should not be rebooted at any time and thus I consider this a bug. I'd appreciate as much input as possible. With kind regards, Michel Thanks for the tip. I have factory reset the ISY and noticed there are no programs by default. I am adding 1 device at a time instead of having it discover the entire network. I have used Power-Home alot in the past to manage my links. Would you recommend I factory reset every device? I have 36 devices so I was hoping not to have to do this. FYI. When adding back in my Elk configuration, the ISY required a reboot before it would show up. Is this how it is support to work or a bug? Quote
yardman 49 Posted December 31, 2007 Posted December 31, 2007 Hello mohansen, Factory reset removes all the schedules. You might want to add back If Time is 3:00 A.M. Then Set My Lighting Query This code makes sure your ISY is in synch with your devices. With kind regards, Michel Hello Michel: Did all ISY-26s ship with this program? I don't remember it ever being on my system. Of course, long ago when I first got the ISY, I was having many comm problems. I think I that at that time I performed a factory reset, and thereby may have removed it. But then again, life has been just fine without the "3 am" program. Why add it back and rock the boat? Most PLM-related Comm Errors occur "sporadically" (at least for me), I'd probably rather not run the program, the more that I think about it. For instance, if I do an entire network query, it's not uncommon to have 1 or 2 failures. But if I requery those devices that had a failure, they're usually communicating just fine. I attribute these the the general weakness of the PLMs Insteon communication. Since you've written the code for the ISY such that it "tells" you the failed devices the next time that you log on, why should I want to keep seeing failures that don't amount to anything every time I log on due to the "3 am" query. This brings up another topic that is related, so I'm going to start a new thread for it. Best wishes, Quote
Mark Sanctuary Posted December 31, 2007 Posted December 31, 2007 That program should have been there, I bet you might have nuked it at some point. I have not seem much issue with this running every day. I also added a couple of KPL LED syncing scenes too to make sure every day my LEDs are correct too. Quote
Michel Kohanim Posted December 31, 2007 Posted December 31, 2007 Frank, Yes, all ISYs come with that program preloaded. It's up to you not to re-add it. The worst case scenario is: if you have programs that depend on the correct status of the devices and if those devices do not have the correct status, then your programs will not run as desired. With kind regards, Michel Hello mohansen, Factory reset removes all the schedules. You might want to add back If Time is 3:00 A.M. Then Set My Lighting Query This code makes sure your ISY is in synch with your devices. With kind regards, Michel Hello Michel: Did all ISY-26s ship with this program? I don't remember it ever being on my system. Of course, long ago when I first got the ISY, I was having many comm problems. I think I that at that time I performed a factory reset, and thereby may have removed it. But then again, life has been just fine without the "3 am" program. Why add it back and rock the boat? Most PLM-related Comm Errors occur "sporadically" (at least for me), I'd probably rather not run the program, the more that I think about it. For instance, if I do an entire network query, it's not uncommon to have 1 or 2 failures. But if I requery those devices that had a failure, they're usually communicating just fine. I attribute these the the general weakness of the PLMs Insteon communication. Since you've written the code for the ISY such that it "tells" you the failed devices the next time that you log on, why should I want to keep seeing failures that don't amount to anything every time I log on due to the "3 am" query. This brings up another topic that is related, so I'm going to start a new thread for it. Best wishes, Quote
yardman 49 Posted December 31, 2007 Posted December 31, 2007 Thanks for the replies, Mark and Michel. Quote
Morris Hansen Posted January 2, 2008 Author Posted January 2, 2008 I did a factory reset on the ISY to get back to a known state. I noticed that after the reset, there were no programs. Once I get my devices added and the ISY working reliably, I will start looking at this default program as well as others. You mentioned that when I add the device back into ISY using the first option, it clears the database in the device. Does that mean it deletes any links that are in the device as well as what the ISY may have known about this device (if the ISY previously was configured with this device)? As for the Elk, I have added the Elk configuration 2 different times. The first time was when I originally received the ISY and the second time after I factory reset it. Both times I have had to reboot the ISY for the GUI to show the Elk buttons on top. I saw this in another forum as well that someone suggested rebooting to complete the change. If this is not how it is suppose to work, then I think it is a bug. If you want me to do further testing, let me know what you would like me to try. Thanks. Quote
Michel Kohanim Posted January 3, 2008 Posted January 3, 2008 mohansen, Yes, the first option deletes (logically/22) all the existing links. As far as ELK, this sounds like a bug ... you should never have to reboot ISY. The next time you are going to configure ELK, would you be kind enough to give it at least 30 seconds. Thanks so very much, With kind regards, Michel I did a factory reset on the ISY to get back to a known state. I noticed that after the reset, there were no programs. Once I get my devices added and the ISY working reliably, I will start looking at this default program as well as others. You mentioned that when I add the device back into ISY using the first option, it clears the database in the device. Does that mean it deletes any links that are in the device as well as what the ISY may have known about this device (if the ISY previously was configured with this device)? As for the Elk, I have added the Elk configuration 2 different times. The first time was when I originally received the ISY and the second time after I factory reset it. Both times I have had to reboot the ISY for the GUI to show the Elk buttons on top. I saw this in another forum as well that someone suggested rebooting to complete the change. If this is not how it is suppose to work, then I think it is a bug. If you want me to do further testing, let me know what you would like me to try. Thanks. Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.