swbrains

Thanks techman -- i have been entering the device address in all attempts, both with auto-detect and without auto-detect. Seems to be a comm issue... I'm just not sure anything has changed since initial installation so I'll need to start eliminating things...

Gary, I am trying to add a new 2477S that is having trouble linking (couldn't determine insteon device type). One of the diagnostic measures was to specify the device type and also try auto-detect. Since auto-detect wasn't working, I was trying to add it (attempted several times before giving up). Each time I had to reselect the device type and it was difficult to find int the long list. Stu, Perhaps we're talking about a different list? I have no column headers to click on. I'll attach a screenshot...

A request for the admin console: Would it be possible to change the device type selection list to be ordered by the actual Insteon product model, such as 2477, etc.? The list is extremely long and ordering by the current method (whatever the codes in brackets are) doesn't really help one find the desired item. When you're doing this over and over to add new devices, it gets quite frustrating trying to find the desired device. Thanks!

I tried to load the admin console via my IP address as I always do in Chrome (Win 10) and it told me Java was out of date. So I updated Java and now I can't get into the admin console in MS Edge, Chrome, or Firefox. I tried the various links documented in the stickjy post here but when I triy to load the jlnp in Chrome it comes up displaying an XML file and says "This XML file does not appear to have any style information associated with it. The document tree is shown below." Firefox downloads the jlnp and asks what I want to open it with and lets me choose Chrome but not Firefox itself. In MS Edge, going to http://isy/admin.jnlpresults in a "hmm.... we can't find this page" error. In Chrome, it results in "page not found" error. Firefox says "unable to connect". Any ideas how I can get back into my ISY admin console again so I can make adjustments? Thanks. UPDATE: I ended up uninstalling and re-installing Java on that PC (My other PC worked fine). It still wanted to download the JLNP file rather than run it. Finally I ended up right clicking on the JLNP file in Explorer and told it to open it with JAVAWS.EXE in the Java directory. That ran the JLNP file and created the shortcut on the desktop which does launch the admin console properly now.

If I do a hard reset, the Liv Rm SL does not show the symptom any more. It no longer works as a slave to its master on the other side of the LR, but at least the symptom goes away. When I restore the device in the UI, the symptom returns. I just replaced it with a new 2477D -- same issue. Hard reset -- no more problem but switch no longer controls any load. Using set button, cross-link it to the master switch (done from master and from slave). Now slave switch will only turn on load if double clicked, but will turn off load if single clicked. (weird!) Still does not show symptom of LED following nook light, but also not part of any the required scenes in ISY UI, After restore device in UI, symptom with LED returns and slave controls load normally (doesn't need double click either).

I have two switchlinc 2477Ds in a single gang box. I noticed when I turn on or off the Nook light switch, the Living Room switch's LED moves quickly up or down depending on whether the Nook light was turned on/off (to match it), I checked every scene and in no scene does the Living Room switch have a ramp rate of less than 4.5 seconds so I don;t know why the Living Room SL LED moves fast ever. I actually deleted the Living Room SL device entirely in the ISY UI and the same symptoms with the LED persist. Note that the Living Room light never responds when using the Nook switch, even though the Nook switch causes the Living Room light LED to move in tandem. Also, the Living Room SL in this case is a slave -- does not connect to the actual load -- just linked to the Living Room "load" switch across the room. The odd part is that even if the Living Room SL slave is deleted from the ISY, its LED still moves quickly in response to the Nook switch action. The Nook switch ramp rate is also set to 4.5 so they don't really move in tandem with speed, just up and down together when the Nook light is used. If I do a hardware reset on both, then the Living Room SL does not respond to the Nook SL. Finally, using the Living Room slave SL does not have the same effect on the Nook SL"s LED. Any idea why the Living Room SL's LED would respond to the Nook switch? Thanks for any ideas you may have...

Well, I'm not sure what caused it, but I ended up deleting both the Kitchen SL dimmer and the cabinet light SL relay and re-adding them as new devices and then adding them back into their respective scenes and that seems to have resolved it.

I just did an ISY Link Table for the Kitchen light SL, and it does have a link record with the address of the cabinet light relay in Line 15 (see attached). I have no idea where that link is coming from. Are there any docs on decoding the codes in each line? I searched the site but couldn't seem to find a reference guide for the link table record layout and what each position means. I can see the device address in each line, but don't know what the other columns represent.

Ok, I got the links but I'm not sure what I'm looking for... I compared it to the ISY Links Table and they are identical. FWIW, here's the level 3 diagnostic output when I turn on the kitchen SL and the undercabinet SL relay turns off: (24.80.14 = Kitchen SL dimmer) Mon 02/16/2015 12:57:09 AM : [iNST-SRX ] 02 50 24.80.14 00.00.01 CF 11 00 LTONRR (00) Mon 02/16/2015 12:57:09 AM : [std-Group ] 24.80.14-->Group=1, Max Hops=3, Hops Left=3 Mon 02/16/2015 12:57:09 AM : [D2D EVENT ] Event [24 80 14 1] [DON] [0] uom=0 prec=-1 Mon 02/16/2015 12:57:09 AM : [ 24 80 14 1] DON 0 Mon 02/16/2015 12:57:10 AM : [iNST-SRX ] 02 50 24.80.14 11.01.01 CF 06 00 (00) Mon 02/16/2015 12:57:10 AM : [std-Group ] 24.80.14-->11.01.01, Max Hops=3, Hops Left=3 Mon 02/16/2015 12:57:10 AM : [iNST-INFO ] Previous message ignored.

I've got a problem that I just noticed today that I can't seem to figure out, or even how to diagnose: I have a switchlinc dimmer as a controller for my kitchen lights. I have a switchlinc relay controlling my undercabinet lights. When I click on or off the kitchen SL dimmer, it causes the undercabinet light switch to turn off. If I fast-double-click (on or off) the kitchen SL dimmer, it doesn't do anything to the undercabinet lights. If I hold (brighten/dim) the kitchen SL, that also does not affect the undercabinet lights. Only single press on/off causes the undercabinet lights to turn off every time. I tried removing the kitchen SL from all scenes and it still happens. I factory reset the kitchen SL and undercabinet light switch and restored them from the ISY interface, but it still happens. I then turned on my undercabinet lights and opened a diagnostic trace in the ISY interface and turned on the kitchen SL dimmer. Here are the resulting events: Sun 02/15/2015 10:24:24 PM : [ 24 80 14 1] DON 0 Sun 02/15/2015 10:24:24 PM : [ 29 49 FF 1] ST 255 Sun 02/15/2015 10:24:24 PM : [ 24 71 BA 1] ST 140 Sun 02/15/2015 10:24:24 PM : [ 24 17 5E 3] ST 255 Device 24.80.14 is the kitchen SL dimmer The other three addresses are 2 SL dimmers and a keypadlinc that also act as controllers/responders to the kitchen SL dimmer. They are all in a scene together (but not the undercabinet lights) so that several switches can control the kitchen lights. Undercabinet lights are: 1F.B8.33 which doesn't seem to appear in the events that occur when I turn on/off the kitchen SL dimmer and the undercabinet SL relay turns off. Not sure if it matters, but another SL relay that is linked to the "main" undercabinet light relay doesn't change its state when the undercabinet lights turn off due to the kitchen light SL being pressed. It stays on even though the actual SL relay controlling the undercabinet lights turns off when the kitchen light switchlinc is pressed. Since it's not showing the undercabinet light device anywhere in the event log -- but it's turning off nonetheless -- what should I be looking for as the cause for it turning off when the kitchen light is turned on or off? Thanks in advance for any advice...

Xathros, I'm glad I had that backup. I've actually been in the habit of doing backups on the device any time I make a significant change, so this one was only a month or two old. It shouldn't need much tweaking now.

LeeG, On my first go around this afternoon after receiving the new PLM, I actually printed out the Wiki page and followed those steps exactly (see my post from 11:47 AM earlier in this thread). I'm pretty sure I followed the steps correctly. I'm starting to think there was a problem with the ISY info since the backup restoration on the ISY config allowed the same restore process to work properly the first time. Seems strange that the PLM hardware failed at the same time the ISY data may have been corrupted. In any event, I do think the ISY config restore seems to have been the missing piece in my particular case.

I saw that option earlier and clicked it but when I read the warning popup that said it was only to be used if you're never going to remove the ISY permanently from the network, I decided NOT to do that, even though I was running out of ideas. I know for sure I never executed it.

The ISY backup and Restore process(es) seems to have worked. I got my scene control back. Not sure why the ISY data was corrupt though and the backup was necessary. Anyway, thanks to everyone for all your help. I'm just restoring the remotes now since they need to be updated one at a time, but at least the keypad/scene buttons appear to be working again.

I just tried restoring the backup although I chose Restore Devices as the device link tables showed the old PLM addresses. Does Restore PLM also update the devices themselves with the new PLM address? I can always restore the backup again and then do Restore PLM if that's better.

Ok, so I read elsewhere here about a similar problem with scenes not working after a PLM swap. I tried deleting a device from a non-working scene and adding it back to the scene and now that device works with the scene. I noticed before deleting it that there was no record in the device links table referencing the scene ID as described in the other thread. After deleting/re-adding the device to the scene, the scene ID record was in the device's link table so it seems that is the problem. Please don't tell me my only solution is to delete about a hundred scene devices and re-add them all back in one at a time, trying to replicate the exact setup I had before. There must be an automated way for the system to handle re-writing the required scene ID records to each of the devices through something like the File->Restore Devices menu option. Shouldn't it do that since the ISY knows what scenes these devices are a part of and that process is essentially rewriting each devices link table, no? I think I'd rather pull out all my insteon devices and reinstall regular switches than have to essentially recreate every one of my scenes from scratch in the admin interface. Please tell me there's a better way to resolve this issue.

I also just tried File->Restore Devices and it ran (for quite a while) and then I followed this with updating the battery powered devices. Everything completed. I unplugged the ISY and PLM, plugged the PLM back in, waited 10 seconds and then plugged in the ISY. Same issue. No scene response from the devices or from the admin interface if I turn no a scene there. I can, however, turn on/off actual devices from the admin interface, just not scenes. I ran a test on one of my scenes and got the following: Thu 02/12/2015 03:02:13 PM : [GRP-RX ] 02 61 1B 13 00 15 <html><font color="red">----- Night Watch Test Results -----</font></html> <html><font color="red">[Failed]</font> Kitchen Cabinet Lights (1F B8 33 1)</html> <html><font color="red">[Failed]</font> Kitchen (Slave 2) (24 71 BA 1)</html> <html><font color="red">[Failed]</font> Island (24 91 7C 1)</html> <html><font color="red">[Failed]</font> Living Room (Slave 1) (24 82 AF 1)</html> <html><font color="red">[Failed]</font> Living Rm Keypad - Island (24 17 5E 4)</html> <html><font color="red">[Failed]</font> Living Rm Keypad - Cabinets (24 17 5E 5)</html> <html><font color="red">[Failed]</font> Kitchen Keypad - Island (29 49 FF 4)</html> <html><font color="red">[Failed]</font> Kitchen Keypad - Living Room (29 49 FF 5)</html> <html><font color="red">[Failed]</font> Living Rm Keypad - Living Roo (24 17 5E 2)</html> <html><font color="red">[Failed]</font> Living Rm Keypad - Kitchen (24 17 5E 3)</html> <html><font color="red">[Failed]</font> Laundry Hall - Master (24 0 7 1)</html> <html><font color="red">[Failed]</font> Living Room (24 91 87 1)</html> <html><font color="red">[Failed]</font> Butler Pantry Cabinet Lights (28 89 E 1)</html> <html><font color="red">[Failed]</font> Foyer - Master (1F B8 86 1)</html> <html><font color="red">[Failed]</font> Dining Room (24 7C 3C 1)</html> <html><font color="red">[Failed]</font> Kitchen (24 80 14 1)</html> <html><font color="red">[Failed]</font> Nook (24 9C 94 1)</html> <html><font color="red">----- Night Watch Test Results -----</font></html> Thu 02/12/2015 03:02:22 PM : [iNST-TX-I1 ] 02 62 00 00 1B CF 13 00 Thu 02/12/2015 03:02:22 PM : [iNST-ACK ] 02 62 00.00.1B CF 13 00 06 LTOFFRR(00) Thu 02/12/2015 03:02:50 PM : [ Time] 15:02:52 0(0) Attached is a device links table from one of the devices in a scene. It has a line for the new PLM and a few other lines, none of which reference the old PLM. I'm at a complete loss and completely frustrated at this point. I now have a bunch of keypads around my house that do absolutely nothing as they were all connected to scenes that no longer work.

Ok, I did another Restore Modem but it only flashed the progress window for a second or two saying "reset plm" then I think I saw writing 0 bytes for a split second, then it disappeared. The device links remained the same after that with the 00.00.00 records. It seems like it really didn't do the whole process as I would have thought it would take a few minutes and show errors for the battery powered devices again since they're not in "set" mode, but nothing really changed.

This scene (most of them actually) are invoked with a device and/or programmatically. I've attached a screenshot of Show Device Links Table for one device in the scene. The new PLM is 30.6B.4C. I also attached a screenshot of the device info (2477D v4.1).

I tried this on several devices in the scene and noticed one record in each (at random positions in the list) that contained the address of the new PLM.

Ok, got the remotes to update and also finally got the other devices to update by doing manual updates on them a couple of times. But now none of my scenes work. All the devices linked directly to a single device work fine, including from remotes. But anything that triggers a scene doesn't work. Any ideas what I should be looking at? I've rebooted both the PLM and ISY but it didn't help. Thanks!

Got the new PLM and did a factory reset on it first thing. Then I attached the ethernet cable and plugged it in. Then I plugged in ISY99. Loaded admin inteface and it started automatically doing a bunch of updates. When that completed, most devices has 1011 icons next t them. I then started the Restore Modem operation and as expected the remotelincs failed, but then I'm also getting a number of "cannot communicate with device" errors for a number of the regular devices like switchlincs and keypads. Some are updating properly though. All these devices worked prior to replacing the PLM. Any ideas why they wouldn't accept an update now, or special steps I should follow to help correct the failures on these devices? Do I simply try the manual update on each one after the whole process completes?

Thanks Lee. That's what I was kind of thinking I would end up doing. I had used "Write Updates to Device" via the right-click menu in the past so I was wondering if that's how I'd do it if it failed for the other remotes after Restore Modem. The new modem should arrive tomorrow so hopefully it will go smoothly. I printed out the Wiki page for replacing a modem/PLM and intend to follow the steps there for this process. The "old" one is going back to SmartHome under warranty... only 18 months old and the LED won't even come on. From what I've read from other users, PLM failure in less than three years is fairly common. I also read a rumor that UD was possibly going to produce their own PLM in the near future. Any truth to that? Thanks again!

I don't have the Pro version. Will it still allow me to restore the modem and skip the devices not in programming mode so I can go back and restore them one at a time? After clicking the menu option "Restore Modem (PLM)" a large popup window appears with a message about placing all battery-operated devices in programming mode. I don't know if it said "at the same time", but since the restore PLM is a single operation, I figured it's going to issue errors when it hits a device not ready to receive programming data.

Hi, When using the Restore Modem (PLM) option, it tells you to place all battery-powered devices in programming mode first. How can you set multiple RemoteLincs (for example) into programming mode without the devices thinking they are linking to each other? I hold down Set on one remote for three seconds and it beeps and starts flashing. Then I press Set on the second remote for three seconds and they both beep and stop blinking. How do I set multiple battery-powered Insteon devices into programming mode at the same time so I can complete the Restore Modem operation successfully? Thanks, Vinnie