Cannot Link Insteon Device

[cestrada]

I get the "Cannot Determine Insteon Engine" error message when trying to link a Load Controller Insteon Device. I believe the device is able to communicate with the network, but cannot link appropriately. Here is what the event viewer states:  

 

 

Mon 06/05/2017 09:07:27 AM : [21 81 3e    ] Added to list of devices to link to ISY

 

Mon 06/05/2017 09:07:27 AM : [iNST-TX-I1  ] 02 62 21 81 3E 0F 0D 00

 

Mon 06/05/2017 09:07:27 AM : [iNST-ACK    ] 02 62 21.81.3E 0F 0D 00 06                 (00)

 

Mon 06/05/2017 09:07:35 AM : [iNST-TX-I1  ] 02 62 21 81 3E 0F 0D 00

 

Mon 06/05/2017 09:07:35 AM : [iNST-ACK    ] 02 62 21.81.3E 0F 0D 00 06                 (00)

 

Mon 06/05/2017 09:07:36 AM : [iNST-SRX    ] 02 50 21.81.3E 2F.B5.C4 A3 0D FF           (FF)

 

Mon 06/05/2017 09:07:36 AM : [std-Direct Nack] 21.81.3E-->ISY/PLM Group=0, Max Hops=3, Hops Left=0

 

Mon 06/05/2017 09:07:36 AM : [iNST-TX-I2CS] 02 62 21 81 3E 1F 09 01 00 00 00 00 00 00 00 00 00 00 00 00 00 F6

 

Mon 06/05/2017 09:07:36 AM : [iNST-ACK    ] 02 62 21.81.3E 1F 09 01 00 00 00 00 00 00 00 00 00 00 00 00 00 F6 06 LNK-ON (01)

 

Mon 06/05/2017 09:07:45 AM : [iNST-TX-I2CS] 02 62 21 81 3E 1F 09 01 00 00 00 00 00 00 00 00 00 00 00 00 00 F6

 

Mon 06/05/2017 09:07:45 AM : [iNST-ACK    ] 02 62 21.81.3E 1F 09 01 00 00 00 00 00 00 00 00 00 00 00 00 00 F6 06 LNK-ON (01)

 

Mon 06/05/2017 09:07:54 AM : [iNST-TX-I2CS] 02 62 21 81 3E 1F 09 01 00 00 00 00 00 00 00 00 00 00 00 00 00 F6

 

Mon 06/05/2017 09:07:54 AM : [iNST-ACK    ] 02 62 21.81.3E 1F 09 01 00 00 00 00 00 00 00 00 00 00 00 00 00 F6 06 LNK-ON (01)

 

Mon 06/05/2017 09:07:58 AM : [21 81 3E 0  ] Failed to add device, reason 3

 

Mon 06/05/2017 09:07:58 AM : [21 81 3e    ] Added to list of devices to link to ISY

 

Mon 06/05/2017 09:07:58 AM : [iNST-TX-I1  ] 02 62 21 81 3E 0F 0D 00

 

Mon 06/05/2017 09:07:58 AM : [iNST-ACK    ] 02 62 21.81.3E 0F 0D 00 06                 (00)

 

Mon 06/05/2017 09:07:58 AM : [All         ] Writing 0 bytes to devices

 

Mon 06/05/2017 09:08:07 AM : [iNST-TX-I1  ] 02 62 21 81 3E 0F 0D 00

 

Mon 06/05/2017 09:08:07 AM : [iNST-ACK    ] 02 62 21.81.3E 0F 0D 00 06                 (00)

 

Mon 06/05/2017 09:08:09 AM : [iNST-SRX    ] 02 50 21.81.3E 2F.B5.C4 A3 0D FF           (FF)

 

Mon 06/05/2017 09:08:09 AM : [std-Direct Nack] 21.81.3E-->ISY/PLM Group=0, Max Hops=3, Hops Left=0

 

Mon 06/05/2017 09:08:10 AM : [iNST-TX-I2CS] 02 62 21 81 3E 1F 09 01 00 00 00 00 00 00 00 00 00 00 00 00 00 F6

 

Mon 06/05/2017 09:08:10 AM : [iNST-ACK    ] 02 62 21.81.3E 1F 09 01 00 00 00 00 00 00 00 00 00 00 00 00 00 F6 06 LNK-ON (01)

 

Mon 06/05/2017 09:08:18 AM : [iNST-TX-I2CS] 02 62 21 81 3E 1F 09 01 00 00 00 00 00 00 00 00 00 00 00 00 00 F6

 

Mon 06/05/2017 09:08:19 AM : [iNST-ACK    ] 02 62 21.81.3E 1F 09 01 00 00 00 00 00 00 00 00 00 00 00 00 00 F6 06 LNK-ON (01)

 

Mon 06/05/2017 09:08:27 AM : [iNST-TX-I2CS] 02 62 21 81 3E 1F 09 01 00 00 00 00 00 00 00 00 00 00 00 00 00 F6

 

Mon 06/05/2017 09:08:27 AM : [iNST-ACK    ] 02 62 21.81.3E 1F 09 01 00 00 00 00 00 00 00 00 00 00 00 00 00 F6 06 LNK-ON (01)

 

Mon 06/05/2017 09:08:31 AM : [21 81 3E 0  ] Failed to add device, reason 3

 

Mon 06/05/2017 09:08:32 AM : [All         ] Writing 0 bytes to devices

 

Mon 06/05/2017 09:13:15 AM : [        Time] 09:14:09 3(0)

 

Mon 06/05/2017 09:22:57 AM : [        Time] 09:24:09 3(0)

 

Mon 06/05/2017 09:32:27 AM : [        Time] 09:34:09 3(0)

 

 

 

The firmware is up to date (4.5.4) and I already made sure the device has power supplied to it and is on the same network. Any ideas?

[larryllix]

Usually just bad comms and you need to move the device closer to the PLM.

 

What is the device and the  model?

[stusviews]

 

The firmware is up to date (4.5.4) and I already made sure the device has power supplied to it and is on the same network. Any ideas?

 

 

Did you update both the firmware and UI. If not, then you can expect unexpected results.

[paulbates]

Hi, welcome to the UDI forums!

Mon 06/05/2017 09:07:36 AM : [Std-Direct Nack] 21.81.3E-->ISY/PLM Group=0, Max Hops=3, Hops Left=0

Bad communications is the correct diagnosis. Hops left of 0 means that it used all 3 hops to get from the PLM to the device.  Ideally you should have 2 hops left.

• What is the load you are trying to control?
• Retry adding it, while keeping the load turned off it it was on. If this works, what ever you are controlling is creating noise and needs to be addressed.
• Have you bridged both legs of your power system with 2 rf devices (following the procedure) or an insteon signalinc bridge?

Paul

[Dr Pepper]

I got in the habit of putting a plug on a device and plugging it in next to the PLM and adding the device.  Every once in a while I get a DOA device so it saves the aggravation of installing and removing.  I also think (my opinion) that you need stronger communication to enroll a device then operate it since a lot more data has to transfer to add the device.

[stusviews]

Dr Pepper, you are absolutely correct. Adding a device is considerably more intensive than using it. Swapping also.

 

BTW, I, too, cut an extension cord in half to test and add new devices. I attached three alligator clips (line, neutral, load) to make testing easier. Ground is not needed. Also, an extension cord had a rib on one side and the other side is smooth. The rib is the neutral (the wider blade).