Jump to content

Insteon 2744S On/Off switch


Carey737

Recommended Posts

Posted

Hi,

 

New to isy.  I have an isy99i loaned to me to try out the system.  I purchased a couple of 2744S light switches to get started.  When I try to link switch to isy I get the error message "can not determine insteon engine".  The firmware for the isy99i is 3.3.10.  Is this a compatibility with the switch and the 99i?  I have been able to link a motion sensor, and the switch is fairly close to PLM (25'). 

 

Thanks for any assistance,

Carey

Posted

The 99i is an older device and no new firmware is available. Newer INSTEON devices are unlikely to be supported.

Posted

I called Insteon tech support and they said that particular switch should still work with the 99i  Can someone take a look at the event log and give me any more insight?  I would really like to use the 99i for a bit longer to see if this is something I want to continue before I drop the cash for a new isy.

 

Thanks in advance,

Carey

 

Sat 08/23/2014 11:52:15 AM : [20 8B C4    ] Added to list of devices to link to ISY
 
Sat 08/23/2014 11:52:15 AM : [iNST-TX-I1  ] 02 62 20 8B C4 0F 0D 00
 
Sat 08/23/2014 11:52:15 AM : [iNST-ACK    ] 02 62 20.8B.C4 0F 0D 00 06                 (00)
 
Sat 08/23/2014 11:52:15 AM : [iNST-SRX    ] 02 50 20.8B.C4 2F.BA.C4 AB 0D FF           (FF)
 
Sat 08/23/2014 11:52:15 AM : [std-Direct Nack] 20.8B.C4-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
 
Sat 08/23/2014 11:52:15 AM : [iNST-TX-I2CS] 02 62 20 8B C4 1F 09 01 00 00 00 00 00 00 00 00 00 00 00 00 00 F6
 
Sat 08/23/2014 11:52:15 AM : [iNST-ACK    ] 02 62 20.8B.C4 1F 09 01 00 00 00 00 00 00 00 00 00 00 00 00 00 F6 06 LNK-ON (01)
 
Sat 08/23/2014 11:52:24 AM : [iNST-TX-I2CS] 02 62 20 8B C4 1F 09 01 00 00 00 00 00 00 00 00 00 00 00 00 00 F6
 
Sat 08/23/2014 11:52:24 AM : [iNST-ACK    ] 02 62 20.8B.C4 1F 09 01 00 00 00 00 00 00 00 00 00 00 00 00 00 F6 06 LNK-ON (01)
 
Sat 08/23/2014 11:52:33 AM : [iNST-TX-I2CS] 02 62 20 8B C4 1F 09 01 00 00 00 00 00 00 00 00 00 00 00 00 00 F6
 
Sat 08/23/2014 11:52:33 AM : [iNST-ACK    ] 02 62 20.8B.C4 1F 09 01 00 00 00 00 00 00 00 00 00 00 00 00 00 F6 06 LNK-ON (01)
 
Sat 08/23/2014 11:52:33 AM : [        Time] 11:52:34 1(0)
 
Sat 08/23/2014 11:52:33 AM : [iNST-SRX    ] 02 50 20.8B.C4 2F.BA.C4 2B 09 01    LNK-ON (01)
 
Sat 08/23/2014 11:52:33 AM : [std-Direct Ack] 20.8B.C4-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
 
Sat 08/23/2014 11:52:33 AM : [LNK-BGN     ] 02 64 01 00 06 
 
Sat 08/23/2014 11:52:34 AM : [LNK-STAT    ] 02 53 M(01) gid=00 20.8B.C4 022A 42 
 
Sat 08/23/2014 11:52:34 AM : [iNST-TX-I1  ] 02 62 20 8B C4 0F 0D 00
 
Sat 08/23/2014 11:52:34 AM : [LNK-END     ] 02 65 06 
 
Sat 08/23/2014 11:52:34 AM : [std MH      ] Unexpected Ack imCmd=65 cmd1= 0xC4
 
Sat 08/23/2014 11:52:35 AM : [iNST-ACK    ] 02 62 20.8B.C4 0F 0D 00 06                 (00)
 
Sat 08/23/2014 11:52:36 AM : [iNST-SRX    ] 02 50 20.8B.C4 2F.BA.C4 2B 0D 02           (02)
 
Sat 08/23/2014 11:52:36 AM : [std-Direct Ack] 20.8B.C4-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
 
Sat 08/23/2014 11:52:39 AM : [iNST-TX-I1  ] 02 62 20 8B C4 0F 0D 00
 
Sat 08/23/2014 11:52:39 AM : [iNST-ACK    ] 02 62 20.8B.C4 0F 0D 00 06                 (00)
 
Sat 08/23/2014 11:52:39 AM : [iNST-SRX    ] 02 50 20.8B.C4 2F.BA.C4 2B 0D 02           (02)
 
Sat 08/23/2014 11:52:39 AM : [std-Direct Ack] 20.8B.C4-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
 
Sat 08/23/2014 11:52:39 AM : [iNST-TX-I1  ] 02 62 20 8B C4 0F 10 00
 
Sat 08/23/2014 11:52:39 AM : [iNST-ACK    ] 02 62 20.8B.C4 0F 10 00 06          ID-REQ (00)
 
Sat 08/23/2014 11:52:48 AM : [iNST-TX-I1  ] 02 62 20 8B C4 0F 10 00
 
Sat 08/23/2014 11:52:48 AM : [iNST-ACK    ] 02 62 20.8B.C4 0F 10 00 06          ID-REQ (00)
 
Sat 08/23/2014 11:52:57 AM : [iNST-TX-I1  ] 02 62 20 8B C4 0F 10 00
 
Sat 08/23/2014 11:52:57 AM : [iNST-ACK    ] 02 62 20.8B.C4 0F 10 00 06          ID-REQ (00)
 
Sat 08/23/2014 11:53:01 AM : [20 8B C4 0  ] Cannot determine device type
 
Sat 08/23/2014 11:53:01 AM : [20 8B C4 0  ] Failed to add device
Posted

That is an I2CS device.   It did not answer the request for it to identify itself (tried three times).

 

Sat 08/23/2014 11:52:39 AM : [iNST-TX-I1  ] 02 62 20 8B C4 0F 10 00
Sat 08/23/2014 11:52:39 AM : [iNST-ACK    ] 02 62 20.8B.C4 0F 10 00 06          ID-REQ (00)
 
Sat 08/23/2014 11:52:48 AM : [iNST-TX-I1  ] 02 62 20 8B C4 0F 10 00
Sat 08/23/2014 11:52:48 AM : [iNST-ACK    ] 02 62 20.8B.C4 0F 10 00 06          ID-REQ (00)
 
Sat 08/23/2014 11:52:57 AM : [iNST-TX-I1  ] 02 62 20 8B C4 0F 10 00
Sat 08/23/2014 11:52:57 AM : [iNST-ACK    ] 02 62 20.8B.C4 0F 10 00 06          ID-REQ (00)
 
Sat 08/23/2014 11:53:01 AM : [20 8B C4 0  ] Cannot determine device type
Sat 08/23/2014 11:53:01 AM : [20 8B C4 0  ] Failed to add device
 
Later ISY firmware may issue a different sequence of commands.  Overall comm with the device is good.
Posted

Sorry for the ignorance, but shouldn't an I2CS device be compatible with the isy99i running 3.3.10?  Will upgrading to the 994i fix this specific issue? Or is there possibly something else going on?

 

Once again, I appreciate the responses,

Carey

Posted (edited)

I cannot answer that question.   The device did not respond to the three commands.   Would it respond to a 994i with later firmware I have no way of knowing.

 

There were Insteon devices moved to I2CS after 3.3.10.   I know for sure that later KPLs are not handled by 3.3.10 but that is the result of SmartLabs changing the device type.    

Edited by LeeG
Posted

At the end of the day purchasing a 994 Series Controller is the only solution moving forward. As it supports all current and future generation of Insteon devices that may be released in the future.

 

Staying with the 99 Series Controller will limit you to what device(s) you can add, support, and ultimately control with all feature sets.

Posted

Hello Carey737,

 

Please look at the end of the events:

Sat 08/23/2014 11:53:01 AM : [20 8B C4 0 ] Cannot determine device type

Sat 08/23/2014 11:53:01 AM : [20 8B C4 0 ] Failed to add device

 

It seems that ISY cannot determine the device type. There are two cases: ISY does not understand the type (it's old) or that the device is not returning a type that ISY understands. I suspect it's the 3.3.10 firmware.

 

With kind regards,

Michel

Guest
This topic is now closed to further replies.

  • Recently Browsing

    • No registered users viewing this page.
  • Forum Statistics

    • Total Topics
      37k
    • Total Posts
      371.5k
×
×
  • Create New...