ISY994i v3.3.3 - RemoteLinc problems

petermadams · November 5, 2012

Hello,

I have two RemoteLinc devices and they behave differently. My ISY994i keeps losing its connection DeviceB. Both were Linked at one time.

I have both devices on the desk beside me and a dual-band light module plugged that is 6ft away.

As a newcomer to ISY and Insteon, I am not sure of the correct procedure to re-connect to my device. I have tried WriteUpdates (fails), RestoreDevice (no response). Delete and Re-link (works, then I get back to this red exclamation mark state).

And the odd thing (to be at least) is that it works. It does control the scenes where I have added it.

Or, do I just have a bad device? How to tell? They are both new.

Thanks for any pointers

-PeterM

LeeG · November 5, 2012

Are these RemoteLincs or RemoteLinc 2 devices?

Before a Write Update to Device or Restore Device can be done the RemoteLinc (2?) must be put into linking mode. For a RemoteLinc press the Dim/Bright buttons until the RemoteLinc LED blinks continuously. For a RemoteLinc 2 press the Set button until the LED blinks continuously.

Only one RF device can be done at a time. If two RF devices are put into linking mode at the same time one will link with the other, cancelling both out of linking mode.

petermadams · November 5, 2012

These are RemoteLinc devices, not RemoteLinc-2.

Thanks for the note that there can only be one RF device at a time. That may explain some of my problems.

I understand about putting the device into Linking mode by pressing Dim/Bright together until the LED flashes.

Device-A responds, I see the Events in the Event log.

Device-B does not. Yet everything seems to be the same as Device-A.

And, on top of that, Both Devices work. I have programmed them with the same set of Scenes, and both "work". The only problem I see reported is in the ISY admin, where red exclamation marks tell me there is a communication problem.

Before I claim it is broken (yet is seems to be working) and send it back, I would like to be sure that I debug the ISY connection fully. Please tell me how I might diagnose this further.

-PeterM

LeeG · November 5, 2012

Put the one with the Red ! into linking mode, right click the RemoteLinc Primary node and select Write Updates to Device. Sounds like the ISY has a pending update that fails because the RemoteLinc is not in linking mode when the ISY tries to write the update. The update remains queued which causes the Red ! later when the update is attempted and fails. Scenes can work even with broken links. May not be as reliable as they should/could be but they work.

petermadams · November 8, 2012

Thanks for the note Lee,

I did try that. Several times, without success. Eventually, after leaving things alone overnight, it worked. I wish I understood more about "a pending update".

Now I have the RemoteLinc devices responding properly, I have a similar problem with a red ! on a 2475SDB Dual Band InlineLinc On/Off Switch v.3B. I try the same Write Updates to the Device - but that does not work. AND YET, when I turn it on/of using the RemoteLinc, it does work. Also, I can turn it on/off from the admin console. What is the explanation for being able to communicate with the module, but the ISY cannot Write the Update?

Here is the Device Communication Log, I hope it helps.

Thu 11/08/2012 08:10:56 AM : [iNST-TX-I1 ] 02 62 1D 5F BC 0F 28 0F

Thu 11/08/2012 08:10:56 AM : [iNST-ACK ] 02 62 1D.5F.BC 0F 28 0F 06 SET-MSB(0F)

Thu 11/08/2012 08:11:05 AM : [iNST-TX-I1 ] 02 62 1D 5F BC 0F 28 0F

Thu 11/08/2012 08:11:05 AM : [iNST-ACK ] 02 62 1D.5F.BC 0F 28 0F 06 SET-MSB(0F)

Thu 11/08/2012 08:11:07 AM : [iNST-SRX ] 02 50 1D.5F.BC AA.AA.AA 27 28 0F SET-MSB(0F)

Thu 11/08/2012 08:11:07 AM : [std-Direct Ack] 1D.5F.BC-->ISY/PLM Group=0, Max Hops=3, Hops Left=1

Thu 11/08/2012 08:11:07 AM : [iNST-TX-I1 ] 02 62 1D 5F BC 0F 2B E0

Thu 11/08/2012 08:11:07 AM : [iNST-ACK ] 02 62 1D.5F.BC 0F 2B E0 06 PEEK (E0)

Thu 11/08/2012 08:11:07 AM : [iNST-SRX ] 02 50 1D.5F.BC AA.AA.AA 27 2B 00 PEEK (00)

Thu 11/08/2012 08:11:07 AM : [std-Direct Ack] 1D.5F.BC-->ISY/PLM Group=0, Max Hops=3, Hops Left=1

Thu 11/08/2012 08:11:07 AM : [iNST-TX-I1 ] 02 62 1D 5F BC 0F 28 0F

Thu 11/08/2012 08:11:07 AM : [iNST-ACK ] 02 62 1D.5F.BC 0F 28 0F 06 SET-MSB(0F)

Thu 11/08/2012 08:11:16 AM : [iNST-TX-I1 ] 02 62 1D 5F BC 0F 28 0F

Thu 11/08/2012 08:11:16 AM : [iNST-ACK ] 02 62 1D.5F.BC 0F 28 0F 06 SET-MSB(0F)

Thu 11/08/2012 08:11:16 AM : [iNST-SRX ] 02 50 1D.5F.BC AA.AA.AA 23 28 0F SET-MSB(0F)

Thu 11/08/2012 08:11:16 AM : [std-Direct Ack] 1D.5F.BC-->ISY/PLM Group=0, Max Hops=3, Hops Left=0

Thu 11/08/2012 08:11:16 AM : [iNST-TX-I1 ] 02 62 1D 5F BC 0F 2B D8

Thu 11/08/2012 08:11:16 AM : [iNST-ACK ] 02 62 1D.5F.BC 0F 2B D8 06 PEEK (D8)

Thu 11/08/2012 08:11:25 AM : [iNST-TX-I1 ] 02 62 1D 5F BC 0F 28 0F

Thu 11/08/2012 08:11:25 AM : [iNST-ACK ] 02 62 1D.5F.BC 0F 28 0F 06 SET-MSB(0F)

Thu 11/08/2012 08:11:26 AM : [iNST-SRX ] 02 50 1D.5F.BC AA.AA.AA 23 28 0F SET-MSB(0F)

Thu 11/08/2012 08:11:26 AM : [std-Direct Ack] 1D.5F.BC-->ISY/PLM Group=0, Max Hops=3, Hops Left=0

Thu 11/08/2012 08:11:26 AM : [iNST-TX-I1 ] 02 62 1D 5F BC 0F 2B D8

Thu 11/08/2012 08:11:26 AM : [iNST-ACK ] 02 62 1D.5F.BC 0F 2B D8 06 PEEK (D8)

Thu 11/08/2012 08:11:26 AM : [iNST-SRX ] 02 50 1D.5F.BC AA.AA.AA 23 2B 00 PEEK (00)

Thu 11/08/2012 08:11:26 AM : [std-Direct Ack] 1D.5F.BC-->ISY/PLM Group=0, Max Hops=3, Hops Left=0

Thanks again,

-PeterM

LeeG · November 8, 2012

The event log does help, thanks.

The communication with 1D 5F BC is unreliable. Could be some form of interference on that circuit or at the PLM plug point. With earlier problems with a RemoteLinc it might be good to look at what is on the PLM circuit. Any other electronic devices, UPS, etc that is not on a FilterLinc. Also verify with the 4 tap Set button test that phase coupling is working.

To the specifics of the event trace

The following outbound command to 1D 5F BC got no response at all (no inbound 02 50 message)

Thu 11/08/2012 08:10:56 AM : [iNST-TX-I1 ] 02 62 1D 5F BC 0F 28 0F

Thu 11/08/2012 08:10:56 AM : [iNST-ACK ] 02 62 1D.5F.BC 0F 28 0F 06 SET-MSB(0F)

The Hops Left count is varying which is another indication of comm. problems. The following two commands got a response with Hops Left=1. That is not the best but okay if consistent which it is not. Later some inbound messages have Hops Left=0. That is as bad as it gets and still working. The next step from Hops Left=0 is no response at all.