Cannot determine Insteon Engine for device type 2635-222 on/off module

[aaronb]

Getting holiday lights setup today.  I successfully added three 2653-222 modules back to my system that I had used last year (ordered from smarthome.com).  I purchased two more at Tiger Direct today with the same model number and 4613 REV 1.0 firmware.

 

When I try adding either of the new devices, I get the same "Cannot determine Insteon Engine" message.  The log is below.  Any ideas?

 

 

Sun 11/30/2014 01:02:20 PM : [27 CB 85    ] Added to list of devices to link to ISY

Sun 11/30/2014 01:02:20 PM : [iNST-TX-I1  ] 02 62 27 CB 85 0F 0D 00

Sun 11/30/2014 01:02:20 PM : [iNST-ACK    ] 02 62 27.CB.85 0F 0D 00 06                 (00)

Sun 11/30/2014 01:02:21 PM : [iNST-SRX    ] 02 50 27.CB.85 21.31.75 AB 0D FF           (FF)

Sun 11/30/2014 01:02:21 PM : [std-Direct Nack] 27.CB.85-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

Sun 11/30/2014 01:02:21 PM : [iNST-TX-I2CS] 02 62 27 CB 85 1F 09 01 00 00 00 00 00 00 00 00 00 00 00 00 00 F6

Sun 11/30/2014 01:02:21 PM : [iNST-ACK    ] 02 62 27.CB.85 1F 09 01 00 00 00 00 00 00 00 00 00 00 00 00 00 F6 06 LNK-ON (01)

Sun 11/30/2014 01:02:22 PM : [iNST-SRX    ] 02 50 27.CB.85 21.31.75 2B 09 01    LNK-ON (01)

Sun 11/30/2014 01:02:22 PM : [std-Direct Ack] 27.CB.85-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

Sun 11/30/2014 01:02:22 PM : [LNK-BGN     ] 02 64 01 00 06 

Sun 11/30/2014 01:02:26 PM : [27 CB 85 0  ] Failed to add device, reason 3

Sun 11/30/2014 01:02:26 PM : [LNK-END     ] 02 65 06 : : Unexpected, ignored (65)

Sun 11/30/2014 01:02:26 PM : [All         ] Writing 0 bytes to devices

 

 

[LeeG]

The device is not responding as expected.  Note message in Red which identifies device type is not coming back from device.

 

Sun 11/30/2014 02:53:14 PM : [1c fd d5    ] Added to list of devices to link to ISY

Sun 11/30/2014 02:53:14 PM : [iNST-TX-I1  ] 02 62 1C FD D5 0F 0D 00

Sun 11/30/2014 02:53:14 PM : [iNST-ACK    ] 02 62 1C.FD.D5 0F 0D 00 06                 (00)

Sun 11/30/2014 02:53:14 PM : [iNST-SRX    ] 02 50 1C.FD.D5 22.80.0B AB 0D FF           (FF)

Sun 11/30/2014 02:53:14 PM : [std-Direct Nack] 1C.FD.D5-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

Sun 11/30/2014 02:53:14 PM : [iNST-TX-I2CS] 02 62 1C FD D5 1F 09 01 00 00 00 00 00 00 00 00 00 00 00 00 00 F6

Sun 11/30/2014 02:53:14 PM : [iNST-ACK    ] 02 62 1C.FD.D5 1F 09 01 00 00 00 00 00 00 00 00 00 00 00 00 00 F6 06 LNK-ON (01)

Sun 11/30/2014 02:53:15 PM : [iNST-SRX    ] 02 50 1C.FD.D5 22.80.0B 2B 09 01    LNK-ON (01)

Sun 11/30/2014 02:53:15 PM : [std-Direct Ack] 1C.FD.D5-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

Sun 11/30/2014 02:53:15 PM : [LNK-BGN     ] 02 64 01 00 06 

Sun 11/30/2014 02:53:16 PM : [LNK-STAT    ] 02 53 M(01) gid=00 1C.FD.D5 0700 41 

Sun 11/30/2014 02:53:16 PM : [iNST-TX-I1  ] 02 62 1C FD D5 0F 0D 00

Sun 11/30/2014 02:53:16 PM : [LNK-END     ] 02 65 06 

Sun 11/30/2014 02:53:16 PM : [std MH      ] Unexpected Ack imCmd=65 cmd1= 0xD5

[mrbudin]

Dear LeeG,

 

What's the reason? These errors are still happening with my Battery operated insteon devices at previous topics.

[LeeG]

Would need to see an Event Trace at LEVEL 3 to understand what is happening with the battery device.  A battery device sleeps so it will not respond to commands unless manually put into linking mode and be in range of a Dual Band device.  Best to move the battery device near a 2413 Dual Band PLM for testing first.   When verified it works there move it to the original location for more testing.