Replaced failed PLM, now can't connect to two switches

[jmwking]

I have an ISY 994i (latest firmware), with about a dozen wall switches, a couple thermostats, and an outdoor unit. Nothing complicated.  Everything is run by the 994i; no switches are linked together and no remote controls.

 

I recently replaced a failed PLM, while everything else in the setup remained the same.  I did the 4-quick-taps on the PLM and saw a bright light on my Access Point (both are plugged into the same outlets that they were before). I don't know what colors they are - I'm color blind.

 

After the PLM swap, everything is working except I have two wall switches - a ToggleLinc Dimmer v.41 2466dw and a ToggleLinc Switch v.41 2466sw - with comm issues.  A different switch, in the same wall plate as the TL Switch, is working normally.  Although likely, I haven't investigated to see if they share a circuit.

 

If I delete a switch from the UD console, factory-reset it, and attempt to add it back via "new insteon device" by address, I get beeps from the switch, but then "cannot determine insteon engine".  If I try to add it back via "Start Linking" from the console, sometimes it finds the switch's address and correctly IDs it, but then also ends with "cannot determine insteon engine".  Other times, it just doesn't find the switch.

 

I'm confused.  The only change in the system was the failed PM.  I can even link the two misbehaving switches to eachother (not using the 994i).  I'll have to wait to try linking others...

 

Any ideas on where I should go from here?

 

thanks!,

 

-jk

 

PS: Some log data...

 

This is from a query:

 

Mon 12/21/2015 03:35:00 PM : [iNST-TX-I1  ] 02 62 23 A1 10 0F 19 00
Mon 12/21/2015 03:35:00 PM : [iNST-ACK    ] 02 62 23.A1.10 0F 19 00 06          LTSREQ (LIGHT)
Mon 12/21/2015 03:35:09 PM : [iNST-TX-I1  ] 02 62 23 A1 10 0F 19 00
Mon 12/21/2015 03:35:09 PM : [iNST-ACK    ] 02 62 23.A1.10 0F 19 00 06          LTSREQ (LIGHT)
Mon 12/21/2015 03:35:18 PM : [iNST-TX-I1  ] 02 62 23 A1 10 0F 19 00
Mon 12/21/2015 03:35:18 PM : [iNST-ACK    ] 02 62 23.A1.10 0F 19 00 06          LTSREQ (LIGHT)
Mon 12/21/2015 03:35:20 PM : [iNST-SRX    ] 02 50 23.A1.10 3D.94.20 2B 00 00           (00)
Mon 12/21/2015 03:35:20 PM : [std-Direct Ack] 23.A1.10-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
Mon 12/21/2015 03:35:20 PM : [D2D EVENT   ] Event [23 A1 10 1] [ERR] [0] uom=0 prec=-1
Mon 12/21/2015 03:35:20 PM : [  23 A1 10 1]      ERR   0
Mon 12/21/2015 03:35:20 PM : [D2D EVENT   ] Event [23 A1 10 1] [sT] [0] uom=0 prec=-1
Mon 12/21/2015 03:35:20 PM : [  23 A1 10 1]       ST   0
Mon 12/21/2015 03:35:20 PM : [D2D EVENT   ] Event [23 A1 10 1] [OL] [255] uom=0 prec=-1
Mon 12/21/2015 03:35:20 PM : [  23 A1 10 1]       OL 255
Mon 12/21/2015 03:35:20 PM : [D2D EVENT   ] Event [23 A1 10 1] [RR] [31] uom=0 prec=-1
Mon 12/21/2015 03:35:20 PM : [  23 A1 10 1]       RR  31
 

This is from an "on", which failed (folllowed by a manual turning on), and then three "off"s, all of which failed:

 

Mon 12/21/2015 03:35:51 PM : [iNST-TX-I1  ] 02 62 23 A1 10 0F 11 FF
Mon 12/21/2015 03:35:51 PM : [iNST-ACK    ] 02 62 23.A1.10 0F 11 FF 06          LTONRR (FF)
Mon 12/21/2015 03:35:55 PM : [D2D EVENT   ] Event [23 A1 10 1] [ERR] [1] uom=0 prec=-1
Mon 12/21/2015 03:35:55 PM : [  23 A1 10 1]      ERR   1
Mon 12/21/2015 03:36:02 PM : [iNST-TX-I1  ] 02 62 23 A1 10 0F 13 00
Mon 12/21/2015 03:36:02 PM : [iNST-ACK    ] 02 62 23.A1.10 0F 13 00 06          LTOFFRR(00)
Mon 12/21/2015 03:36:02 PM : [iNST-SRX    ] 02 50 23.A1.10 3D.94.20 AB 13 FF    LTOFFRR(FF)
Mon 12/21/2015 03:36:02 PM : [std-Direct Nack] 23.A1.10-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
Mon 12/21/2015 03:36:15 PM : [iNST-TX-I1  ] 02 62 23 A1 10 0F 13 00
Mon 12/21/2015 03:36:15 PM : [iNST-ACK    ] 02 62 23.A1.10 0F 13 00 06          LTOFFRR(00)
Mon 12/21/2015 03:36:44 PM : [iNST-TX-I1  ] 02 62 23 A1 10 0F 13 00
Mon 12/21/2015 03:36:44 PM : [iNST-ACK    ] 02 62 23.A1.10 0F 13 00 06          LTOFFRR(00)
Mon 12/21/2015 03:36:46 PM : [iNST-SRX    ] 02 50 23.A1.10 3D.94.20 AB 13 FF    LTOFFRR(FF)
Mon 12/21/2015 03:36:46 PM : [std-Direct Nack] 23.A1.10-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
Mon 12/21/2015 03:37:00 PM : [iNST-TX-I1  ] 02 62 23 A1 10 0F 13 00
Mon 12/21/2015 03:37:00 PM : [iNST-ACK    ] 02 62 23.A1.10 0F 13 00 06          LTOFFRR(00)
 

[Techman]

jmwking,

 

After replacing the modem did you first remove power from the ISY?  if not try removing power, wait about 15 seconds then power up the ISY.

 

If that doesn't help then you probably have a communications issue with the devices.

[stusviews]

I have an ISY 994i (latest firmware)

 

That doesn't say much. The latest Beta firmware or latest official firmware. What about the UI. It's always best to specify what you have installed.

[jmwking]

Sorry about the versions:

 

Firmware: Insteon_UD994 v4.3.26 (2015-10-13-11:35:11)

UI: Inseton_UD994 v4.1.1 (2013-12-02-19:13:09)

Product: ISY 994i (1120) - OpenADR (21010)

 

And, yes, the 994i was powered off when I exchanged PLMs. I've power cycled both devices a few times since, sometimes powering up the PLM first, sometimes the 994i.

 

-jk

[Brian H]

The PLM should always be powered up first. So the ISY994i can find it at boot up.

Your UI should match the firmware version.

The instruction to get the proper UI are in the firmware released thread.

Make sure the Java Cache is cleared and you download the correct UI.

 

http://forum.universal-devices.com/topic/17075-release-4326-is-now-official/

[jmwking]

The UI now matches the firmware now.  Same symptoms.  And I'll keep in mind to power up the PLM first (though I haven't noticed any difference between the two startup sequences).

[Michel Kohanim]

Hi jmwking,

 

If you cannot even link a new device, then I suspect either noise or something wrong with that switch. Try linking again using Link Management | Start Linking and see what's going on in the Event Viewer. You can post back the contents.

 

With kind regards,

Michel

[jmwking]

I'll have to put this investigation on hold for a few days.  Thanks for the help so far.

 

-jk