I just realized I posted this in the wrong forum yesterday...

 

I just acquired an on/off outdoor module (2634-222) and when trying to link it to my ISY991 Pro (firmware 3.3.10), I get an "Cannot determine Insteon Engine" error.

 

From some forum posts it looks like a 4.xx firmware is needed in an ISY994x series to use this module, yet it is listed in my device list when I go to add it.

 

I have moved it indoors to a known good circuit to link but got the same result.

 

I did some serious rewiring to accommodate this module (due to unreliability of a standard switch in a very cold garage attic) and really need this to function in its place.

 

Any ideas?

Run Tools | Diagnolstics | Event Viewer at LEVEL 3. Add the 2634-222 and post the trace. It sounds like the 2634-222 is not answering the "What Insteon Engine" command question.

Here is the trace:

 

Mon 02/24/2014 03:19:02 PM : [27 BC 10 ] Added to list of devices to link to ISY

 

Mon 02/24/2014 03:19:03 PM : [iNST-TX-I1 ] 02 62 27 BC 10 0F 0D 00

 

Mon 02/24/2014 03:19:03 PM : [iNST-ACK ] 02 62 27.BC.10 0F 0D 00 06 (00)

 

Mon 02/24/2014 03:19:11 PM : [iNST-TX-I1 ] 02 62 27 BC 10 0F 0D 00

 

Mon 02/24/2014 03:19:11 PM : [iNST-ACK ] 02 62 27.BC.10 0F 0D 00 06 (00)

 

Mon 02/24/2014 03:19:20 PM : [iNST-TX-I1 ] 02 62 27 BC 10 0F 0D 00

 

Mon 02/24/2014 03:19:20 PM : [iNST-ACK ] 02 62 27.BC.10 0F 0D 00 06 (00)

 

Mon 02/24/2014 03:19:24 PM : [27 BC 10 0 ] Failed to add device

 

Not sure if the rest of this is relevant or not... it appeared after I saved the first trace:

 

Mon 02/24/2014 03:19:50 PM : [iNST-SRX ] 02 50 27.B7.F2 00.00.01 CB 11 01 LTONRR (01)

 

Mon 02/24/2014 03:19:50 PM : [std-Group ] 27.B7.F2-->Group=1, Max Hops=3, Hops Left=2

 

Mon 02/24/2014 03:19:50 PM : [ 27 B7 F2 1] DON 1

 

Mon 02/24/2014 03:19:50 PM : [iNST-SRX ] 02 50 27.B7.F2 00.00.01 CB 11 01 LTONRR (01)

 

Mon 02/24/2014 03:19:50 PM : [std-Group ] 27.B7.F2-->Group=1, Max Hops=3, Hops Left=2

 

Mon 02/24/2014 03:19:50 PM : [iNST-DUP ] Previous message ignored.

 

Mon 02/24/2014 03:19:51 PM : [iNST-SRX ] 02 50 27.B7.F2 11.00.01 CB 06 00 (00)

 

Mon 02/24/2014 03:19:51 PM : [std-Group ] 27.B7.F2-->11.00.01, Max Hops=3, Hops Left=2

 

Mon 02/24/2014 03:19:51 PM : [iNST-SRX ] 02 50 27.B7.F2 11.00.01 CB 06 00 (00)

 

Mon 02/24/2014 03:19:51 PM : [std-Group ] 27.B7.F2-->11.00.01, Max Hops=3, Hops Left=2

 

Mon 02/24/2014 03:19:51 PM : [iNST-DUP ] Previous message ignored.

That was the expected results. The device did not respond to Query Insteon Engine request. No 02 50 response from any of the three request for the Insteon Engine information.

 

Mon 02/24/2014 03:19:03 PM : [iNST-TX-I1 ] 02 62 27 BC 10 0F 0D 00

Mon 02/24/2014 03:19:03 PM : [iNST-ACK ] 02 62 27.BC.10 0F 0D 00 06 (00)

 

Mon 02/24/2014 03:19:11 PM : [iNST-TX-I1 ] 02 62 27 BC 10 0F 0D 00

Mon 02/24/2014 03:19:11 PM : [iNST-ACK ] 02 62 27.BC.10 0F 0D 00 06 (00)

 

Mon 02/24/2014 03:19:20 PM : [iNST-TX-I1 ] 02 62 27 BC 10 0F 0D 00

Mon 02/24/2014 03:19:20 PM : [iNST-ACK ] 02 62 27.BC.10 0F 0D 00 06 (00)

 

Mon 02/24/2014 03:19:24 PM : [27 BC 10 0 ] Failed to add device

 

Try moving the device closer to the PLM.

Thanks, LeeG, but still no luck. I put the device one plug over from the PLM. It bombs out at 7% of "Initializing Device' every time. Could I have a faulty device?

It sounds like the symptom changed when moved near the PLM. Run another Event Viewer at LEVEL 3 with it plugged near the PLM.

Actually, the symptoms are the same. It always bombed out at 7% with that error message about the Insteon engine. Nevertheless, here is the log with the module plugged very near the PLM:

 

Mon 02/24/2014 08:52:22 PM : [27 BC 10 ] Added to list of devices to link to ISY

 

Mon 02/24/2014 08:52:22 PM : [iNST-TX-I1 ] 02 62 27 BC 10 0F 0D 00

 

Mon 02/24/2014 08:52:22 PM : [iNST-ACK ] 02 62 27.BC.10 0F 0D 00 06 (00)

 

Mon 02/24/2014 08:52:30 PM : [iNST-TX-I1 ] 02 62 27 BC 10 0F 0D 00

 

Mon 02/24/2014 08:52:30 PM : [iNST-ACK ] 02 62 27.BC.10 0F 0D 00 06 (00)

 

Mon 02/24/2014 08:52:39 PM : [iNST-TX-I1 ] 02 62 27 BC 10 0F 0D 00

 

Mon 02/24/2014 08:52:39 PM : [iNST-ACK ] 02 62 27.BC.10 0F 0D 00 06 (00)

 

Mon 02/24/2014 08:52:43 PM : [27 BC 10 0 ] Failed to add device

I don't keep much track of what devices are supported by what versions of ISY software. I am also unclear which method you are using in an attempt to add the new module. Are you using the "start linking" option, or something else?

 

My working theory is that you are trying to add an unsupported device. Let's assume, for a minute, that your newly-acquired outdoor module is NOT supported by the software version on your ISY-99. Still, the ISY shows an outdoor outlet with an identical part number.

 

Have you tried manually adding the device, inputting address and selecting the outdoor module from the drop-down box?

"Have you tried manually adding the device, inputting address and selecting the outdoor module from the drop-down box?"

 

Yes, this is always the way I add devices. I have had complete success in the past with this method.

Well, then. Have you tried the "start linking" option and letting ISY try to figure it out?

Hello bfish,

 

It very much looks like communication issue (no response from the device).

 

If you are still having problems, please do not hesitate to submit a ticket (links below) and we'd be delighted to help you out.

 

With kind regards,

Michel