Cannot communicate with Remotelinc2s

[MisterVapor]

I have two remotelinc2's that I am unable to communicate with. Both devices will control the devices they are currently configured to control but for some reason, I cannot communicate with the devices to add more instructions. Can anyone PLEASE help me understand how I can troubleshoot this issue? I tried last night and exported the event viewer information to a log file...perhaps someone can point me in the right place to understand how to read this...

 

Wed 04/09/2014 09:17:56 PM : [ 1C 34 76 5] Preparing Device 'RemoteLinc2 Mini01 -' for Restore

Wed 04/09/2014 09:17:56 PM : [ 1C 34 76 5] Device 'RemoteLinc2 Mini01 -' ready for Full Restore

Wed 04/09/2014 09:18:21 PM : [iNST-TX-I1 ] 02 62 1C 34 76 0F 0D 00

Wed 04/09/2014 09:18:21 PM : [iNST-ACK ] 02 62 34.76.0F 0D 00 00 06 (00)

Wed 04/09/2014 09:18:30 PM : [iNST-TX-I1 ] 02 62 1C 34 76 0F 0D 00

Wed 04/09/2014 09:18:30 PM : [iNST-ACK ] 02 62 1C.76.0F 0D 00 00 06 (00)

Wed 04/09/2014 09:18:39 PM : [iNST-TX-I1 ] 02 62 1C 34 76 0F 0D 00

Wed 04/09/2014 09:18:39 PM : [iNST-ACK ] 02 62 1C.34.76 0F 0D 00 06 (00)

Wed 04/09/2014 09:18:40 PM : [iNST-SRX ] 02 50 1C.34.76 18.D1.1D 23 0D 01 (01)

Wed 04/09/2014 09:18:40 PM : [std-Direct Ack] 1C.34.76-->ISY/PLM Group=0, Max Hops=3, Hops Left=0

Wed 04/09/2014 09:18:40 PM : [1C 34 76 0 ] Calibrating engine version

Wed 04/09/2014 09:18:40 PM : [iNST-TX-I2 ] 02 62 1C 34 76 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0

Wed 04/09/2014 09:18:40 PM : [uNKNOWN ] 02 1C

Wed 04/09/2014 09:18:49 PM : [iNST-TX-I2 ] 02 62 1C 34 76 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0

Wed 04/09/2014 09:18:50 PM : [iNST-ACK ] 02 62 1C.34.76 1F 2F 00 00 00 01 00 00 00 00 00 00 00 00 D0 CD 00 06 (00)

Wed 04/09/2014 09:18:58 PM : [iNST-TX-I2 ] 02 62 1C 34 76 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0

Wed 04/09/2014 09:18:58 PM : [iNST-ACK ] 02 62 1C.34.2F 00 00 00 00 (00)

Wed 04/09/2014 09:18:59 PM : [iNST-ACK ] 02 62 1C.34.2F 00 00 00 00 (00): Duplicate or ACK for a different device

Wed 04/09/2014 09:19:02 PM : [1C 34 76 0 ] i2 data transfer commands do not work. Reverting to i1

Wed 04/09/2014 09:19:02 PM : [iNST-TX-I1 ] 02 62 1C 34 76 0F 28 0F

Wed 04/09/2014 09:19:03 PM : [iNST-ACK ] 02 62 1C.34.76 0F 28 0F 06 SET-MSB(0F)

Wed 04/09/2014 09:19:11 PM : [iNST-TX-I1 ] 02 62 1C 34 76 0F 28 0F

Wed 04/09/2014 09:19:11 PM : [iNST-ACK ] 02 62 1C.34.76 0F 28 0F 06 SET-MSB(0F)

Wed 04/09/2014 09:19:20 PM : [iNST-TX-I1 ] 02 62 1C 34 76 0F 28 0F

Wed 04/09/2014 09:19:20 PM : [iNST-ACK ] 02 62 1C.34.76 28 0F 00 06 PING (00)

Wed 04/09/2014 09:19:21 PM : [iNST-ACK ] 02 62 1C.34.76 28 0F 00 06 PING (00): Duplicate or ACK for a different device

 

I tried to update Remotelinc #1 by clicking the Link button on the bottom but had no luck. Then, I stopped it from linking mode and tried the second remotelinc thinking I might have somehow got things confused. But it still wouldn't communicate with the devices. Again, any advice or suggested documents to understand how to read this log file is greatly appreciated.

 

Thanks in advance.

[LeeG]

The RemoteLinc2 is not responding to commands. Out of all the attempts to send it commands the RemoteLinc2 responded to one command with a Hops Left=0 which is at the extreme end.

 

First step in communicating with a battery device is to put it into linking mode by pressing the Set button until the LED blinks Green continuously. Insure the RemoteLinc2 is near a Dual Band device. Now do a Restore Device or whatever Scene creation/update.

 

When complete be sure to take the RemoteLinc2 out of linking mode or allow it to timeout of linking mode before moving to the next RemoteLinc2.

[mwester]

Had similar troubles with my RemoteLinc2 -- after fighting with it for weeks, I'm embarrassed to report that it turned out to be as simple as weak batteries.

 

It seems that a low battery allows the RemoteLinc2 to illuminate it's LED, and send/respond to short Insteon commands but for whatever reason it would fail whenever it had to send more than a few bytes at a time. The result was that it continued to work for the devices with which it was linked, but I lost control of it with the ISY. New batteries were an instant fix.