jtara92101 Posted January 5, 2011 Posted January 5, 2011 I am replacing my V.35 Switchlincs, and am not having much luck. I was able to replace one by doing a lot of experimenting and fiddling around, but at this rate it is going to take 1-2 hours to replace each one. I suppose, though, it might be done by the time I get a call back from tech support, which is an exercise in futility. I had to follow some threads here, because as far as I can tell, this isn't in the manual at all, and the Wiki seems to be down. The replacement seems to have worked initially - I watched the messages, and it said the replacement was complete, but then I was not able to communicate with the device. That is, couldn't turn it on or off, query, etc. The messages didn't even show an attempt to communicate. After a reboot I finally was able to communicate with the device. Is it necessary to reboot after each device replacement? Can we PLEASE have a definitive, step-by-step procedure for replacing devices? If possible, for non-Pro as well as Pro. (I just upgraded to Pro hoping it would gain me something,, but doesn't seem to be helping the extremely drawn-out process.) This wasn't what I was planning on spending my ENTIRE day on today!
TJF1960 Posted January 5, 2011 Posted January 5, 2011 What model is your ISY? What version does it report in the admin console (admin console>Help>about)?
LeeG Posted January 5, 2011 Posted January 5, 2011 From the UDI Wiki ... The Process of Replacing a Device Use the "Logon to My INSTEON ISY Now!" weblink, enter your user name and password when prompted to get logged in. Frist add a device that will be the new device. Both devices have to be the same type of device in order for the new device to be displayed in the replace menu. If the device is used in any programs: Click on the Program Details tab. Use Find/Replace to Replace in All Programs the old device with the new device. Be sure to Save your program changes. Under the "Main Tab" expand the Tree "Network --> My Lighting -->" and right click the device that is being replaced. The device must be removed from any folder it is in. Select the new device that was added in the earlier step to start the process.
Brian H Posted January 6, 2011 Posted January 6, 2011 I wounder if part of the problem is the other V.35 SwitchLincs still in the system. Slowing thing down. I thought when I did a replacement. After the replacement was done. It rebooted all by itself.
TJF1960 Posted January 6, 2011 Posted January 6, 2011 Newer versions will automatically fix the programs so you don't have to use find/fix and newer version will reboot automatically when everything is completed.
jtara92101 Posted January 6, 2011 Author Posted January 6, 2011 Thanks - I was able to replace all of my V35 Switchlincs. It didn't help that the Wiki was down when I started this (it seems to be down often lately). Sure wish they would just document everything in the manual! I think as BrianH suggested, the problem might have been the remaining V.35 devices making it difficult to communicate. Probably a good idea to disable all them when you start the process. What happened on the first one is that the Administrator got "stuck" with the little 101010 tags pending and it never did reboot itself. But it was OK after a manual reboot. It seems it DID do the replacement, but somehow got out of sync with the Administrator application.
jtara92101 Posted January 6, 2011 Author Posted January 6, 2011 Thanks - I was able to replace all of my V35 Switchlincs. It didn't help that the Wiki was down when I started this (it seems to be down often lately). Sure wish they would just document everything in the manual! I think as BrianH suggested, the problem might have been the remaining V.35 devices making it difficult to communicate. Probably a good idea to disable all them when you start the process. What happened on the first one is that the Administrator got "stuck" with the little 101010 tags pending and it never did reboot itself. But it was OK after a manual reboot. It seems it DID do the replacement, but somehow got out of sync with the Administrator application.
Recommended Posts