Cannot Determine Insteon Engine Error Message

pfergy · January 27, 2014

I installed a ISY994i and PLM this weekend as well as an Insteon toggle switch (2466-SW). When I attempt to link the toggle switch, I receive an error message 'Cannot determine Insteon Engine'. What does this mean? I searched the forum and found where it came up, but never a clear resolution (at least that I could follow). Any help is greatly appreciated - nothing is worse than getting a new toy but not being able to get it to work

Thanks in advance for your help.

LeeG · January 27, 2014

The message normally means the device did not respond to the command that is asking what Insteon Engine the device supports. A system containing a PLM and a ToggleLinc is not coupled. A house normally has two phases (not technically correct but often that way the two 120 volt legs are described). For a PLM to communicate with a device on the opposite phase a pair of Access Points are used to couple Insteon messages from one phase to the other. A ToggleLinc is not Dual Band so if the PLM is on the opposite phase to the ToggleLinc the PLM will not be able to talk to the ToggleLinc.

pfergy · January 27, 2014

Thanks. Quick question: do I need two couplers or just one since my PLM (dual band) is already on one phase?

Brian H · January 27, 2014

Two 2443 Access Points is the best choice.

One Access Point and the 2413S PLM should also work, but finding a place for the Access Point on the other phase. In RF distance to the PLM can sometimes be an issue.

m_later · February 6, 2014

I'm getting this error on 2 new Switchlincs that I'm trying to install to replace two very old ones that no longer respond to local control.

Here's an example log. I've already tried factory reset on both switches. Any more ideas?

Thu 02/06/2014 03:20:06 PM : [25 3c e7 ] Added to list of devices to link to ISY

Thu 02/06/2014 03:20:06 PM : [iNST-TX-I1 ] 02 62 25 3C E7 0F 0D 00

Thu 02/06/2014 03:20:06 PM : [iNST-ACK ] 02 62 25.3C.E7 0F 0D 00 06 (00)

Thu 02/06/2014 03:20:15 PM : [iNST-TX-I1 ] 02 62 25 3C E7 0F 0D 00

Thu 02/06/2014 03:20:15 PM : [iNST-ACK ] 02 62 25.3C.E7 0F 0D 00 06 (00)

Thu 02/06/2014 03:20:24 PM : [iNST-TX-I1 ] 02 62 25 3C E7 0F 0D 00

Thu 02/06/2014 03:20:24 PM : [iNST-ACK ] 02 62 25.3C.E7 0F 0D 00 06 (00)

Thu 02/06/2014 03:20:26 PM : [iNST-SRX ] 02 50 25.3C.E7 0E.DA.3C A3 0D FF (FF)

Thu 02/06/2014 03:20:26 PM : [std-Direct Nack] 25.3C.E7-->ISY/PLM Group=0, Max Hops=3, Hops Left=0

Thu 02/06/2014 03:20:26 PM : [iNST-TX-I2CS] 02 62 25 3C E7 1F 09 01 00 00 00 00 00 00 00 00 00 00 00 00 00 F6

Thu 02/06/2014 03:20:26 PM : [iNST-ACK ] 02 62 25.3C.E7 1F 09 01 00 00 00 00 00 00 00 00 00 00 00 00 00 F6 06 LNK-ON (01)

Thu 02/06/2014 03:20:28 PM : [iNST-SRX ] 02 50 25.3C.E7 0E.DA.3C 20 F6 C1 (C1)

Thu 02/06/2014 03:20:28 PM : [std-Direct Ack] 25.3C.E7-->ISY/PLM Group=0, Max Hops=0, Hops Left=0

Thu 02/06/2014 03:20:28 PM : [iNST-DUP ] Previous message ignored.

Thu 02/06/2014 03:20:37 PM : [iNST-TX-I2CS] 02 62 25 3C E7 1F 09 01 00 00 00 00 00 00 00 00 00 00 00 00 00 F6

Thu 02/06/2014 03:20:37 PM : [iNST-ACK ] 02 62 25.3C.E7 1F 09 01 00 00 00 00 00 00 00 00 00 00 00 00 00 F6 06 LNK-ON (01)

Thu 02/06/2014 03:20:46 PM : [iNST-TX-I2CS] 02 62 25 3C E7 1F 09 01 00 00 00 00 00 00 00 00 00 00 00 00 00 F6

Thu 02/06/2014 03:20:46 PM : [iNST-ACK ] 02 62 25.3C.E7 1F 09 01 00 00 00 00 00 00 00 00 00 00 00 00 00 F6 06 LNK-ON (01)

Thu 02/06/2014 03:20:50 PM : [25 3C E7 0 ] Failed to add device, reason 3

Thu 02/06/2014 03:20:50 PM : [All ] Writing 0 bytes to devices

Brian H · February 6, 2014

ISY26;ISY99i or ISY994i?

What firmware revision are you using.

The new Switchlincs are probably too new to be supported by an older firmware version.

LeeG · February 6, 2014

The old devices may not be bad as comm to the new devices is at the outer edge. It took three attempts before the device response was received by the PLM and then the Hops Left=0 which is bad as comm gets and still work.