endiablado

Just a follow up, I've been working slowly but surely fixing one scene a a time. I've been following Mark's advice and adding the offending devices into a scene, then removing them. This seems to be working. Is there any documentation on how to wipe every device on the system and start afresh? Thanks for all your help

Thanks all for your help. I've looked into the link tables. Took me a little while to decipher them. After a little digging I discovered that the device in question is in fact erroneously linked to my basement lights. The problem is that when I did a compare it looks as if the ISY is in agreement. I somehow have to remove this link from both the device and the ISY. This raises the question as to why this erroneous link is not shown in the ISY Admin interface? Is there a way to do this? I was looking into "hard resetting" the device. I am assuming this term refers to the procedure described in the "Restoring device to its Factory Defaults Settings" in the Switchlinc manual.

Question : Why would there be any X-10 activity if I've never enabled X10, and do not have a single X-10 device on the system? What would X10 activity look like in the log? Where would I find the instructions to remove the X-10 addresses? The only instructions I found require you to know the X-10 address. Given that I did not add the X-10 address how can I identify it to remove it?

Hi, I'm having a strange problem. I have set up a collection of scenes on my ISY. When a scene is activated by a switch it works fine and only that scene is affected. When a scene is activated programmatically via the admin panel, or from ILinc the scene appears to inadvertently activate other unrelated lights. eg. I turn on a receptacle module in my living room on the main floor and the basement lights come on. There are many scenes that are behaving this way ?! I've tried restore devices from the admin screen. I've done this on all the switches and receivers related to the scenes in question. It does not appear to help. Are there any tips you might provide to help me troubleshoot the source of this issue. Thanks in advance, John

Hi Michael, I can log in to the unit now via the administrative console, but then I do I see nothing but blank pages. I unfortunately do not have a backup of my ISY. I had attempted a backup several times but it always failed, probably due to the networking issues. I did do a factory reset while I was having network issues. Is there any hope of recovery here? IS there at least a way of having the ISY scan existing INSTEON devices?

Thanks for the quick reply. I discovered the switch the ISY was connected to is not working well. I then connected the ISY directly to the router. No blinking error LED's anymore. I can now perform a proper telnet login. The problem with the administrative console interface has not disappeared. I still see a completely blank page where my devices used to be. The same is true for the my programs. Any suggestions as to what the problem might be?

I'm having an issue with my ISY 99. I have been trying to reach my ISY through the Java Administrative Console. The Web interface starts with no problem. When it does start it shows me nothing but blank pages. The login option in the File menu is greyed out. After about a minute of waiting the following appears in a popup dialog: After dismissing the modal dialog by clicking ok. The Logon option is again available from the File menu of the Java app. Selecting this menu option delays indefinitely. The text "System Busy" appears in the status bar throughout this wait. I tried a factory reset in the hopes that there was something that was not being cleared. This made matters worse. The isy is no longer running the programs I had entered (It was before). I also tried logging in from the Telnet interface. The telnet session prompts for for the username then password. The session freezes on submitting the password. I also noted that the mem and error led's are blinking on the unit. According to your troubleshooting guide this is indicative of a network communications issue. Yet I managed to almost complete a telnet login? Do you have any idea what might be wrong? Any help here is appreciated.