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.