Can't Enroll KPL-DB to ISY-994i/IR

Miguelito.Loveless · July 24, 2013

Hello all, I'm having trouble resolving an Insteon / ISY situation concerning the new Dual-Band KPLs...

Problem:

Attempts to do basic addition of two new 2334-222 Dual-Band KPL8 rev. 7.0 devices to ISY-994i/IR (4.05) consistently gets "Unsupported Device 1.65" .

Tried:

1) Factory Reset the KPL8DBs

2) Basic Reset the ISY

(above efforts get absolutely no change, still get Unsupported Device 1.65

3) Manual declaration of alternative device type, such as 2486; ISY won't buy it.

Configuration History:

Existing home setup is 90+ device longstanding Insteon network with numerous APs and Dual-Band units;

Home was originally HouseLinc-controlled.

Switched to ISY-9941/IR 6 months ago, upon which I...

...Factory-Reset ALL Insteon devices and redefined the entire network under ISY control with no problems.

All working fine except the ISY-994i/IR (fw 4.05) doesn't recognize the new DB KPLs. (There is no such device offered on the ISY's manual setup list, either.)

I suspect I'll have to wait for a firmware upgrade for the ISY, but haven't seen this issue described yet in the forum.

Help? Comments? Does anyone have these new DB KPLs working properly under ISY-994i control?

TIA!

LeeG · July 24, 2013

They are listed in the New INSTEON Device list of Device Types as [01.41] and [01.42] on 4.0.5. These numbers are in hex. The 1.65 is decimal, [01.41] in hex.

What does Help | About show for the UI line?

Miguelito.Loveless · July 24, 2013

Hello Lee,

Help | About UI Line:

Insteon_UD994 v.3.3.10 ...

LeeG · July 24, 2013

Those devices would not be known to the Admin Console from 3.3.10. Clear the Java cache and make sure the URL being used to invoke the Admin Console points to 4.0.5.

Miguelito.Loveless · July 24, 2013

Thank you (again) Lee, your vector will save me much additional frustration.

"Again": You helped me years ago on another forum re EZSrve, and may recall the "Insteon skills" self-descriptor I offered at that time: "Gorilla with a Nikon."

LeeG · July 24, 2013

Thank you. Happy to help. It is a good habit to check Help | About after upgrading the ISY to a new firmware. Easy to overlook getting the Admin Console to the later level. good luck.

edfinley · July 26, 2013

I was getting unsupported device also, so I just upgraded to the 994i version. I'm still having issues. I can get it to link, it recognizes it ok It shows up as a device in the admin console but when adding it to scenes I get half way through then get an error message that it can't communicate with the device. I bought 2 of them and am having the same issue with both. They are both in different areas close to other devices with no communication issues. I can also control the on/off state of the primary load, it just can't write scene updates or links. I have manually linked it fine with what I want to control and don't have any comm issues with that, it's only when I use the ISY that I can't get a link or scene.

Ed

LeeG · July 26, 2013

Creating Set button links will create problems later. The ISY is not aware of those links and will eventually delete or overlay them.

Suggest running Tools | Diagnostics | Event Viewer with LEVEL 3. Create a Scene or if one is pending click the Primary node and select Write Updates to Device. Link management on these later devices is done with Extended messages. Standard commands may work yet have problems with Extended messages. SignaLincs (black external antenna) and old Insteon devices do not process/repeat Extended messages which can make them unreliable. May not have anything to do with Extended messages.

Post the event trace as it will show what the issue is.

edfinley · July 27, 2013

You guys are quick to get back. I appreciate the great support. I did have some old relay links with the black antenna and when I put other dual band devices in their place was able to link.

Thanks,

Ed

edfinley · July 29, 2013

It's still not able to link scenes or enroll the device. Communications seem fine when manually linking and to devices within about 2 feet of the new keypadlinc. Here's the diagnostics of an attempt to "restore device":

Mon 07/29/2013 09:44:13 : [ 22 F9 73 1] Preparing Device '*Blue Room.1' for Restore

Mon 07/29/2013 09:44:13 : [ 22 F9 73 1] Device '*Blue Room.1' ready for Full Restore

Mon 07/29/2013 09:44:13 : [All ] Writing 84 bytes to devices

Mon 07/29/2013 09:44:13 : [iNST-TX-I1 ] 02 62 22 F9 73 0F 0D 00

Mon 07/29/2013 09:44:13 : [iNST-ACK ] 02 62 22.F9.73 0F 0D 00 06 (00)

Mon 07/29/2013 09:44:14 : [iNST-SRX ] 02 50 22.F9.73 0D.4F.45 23 0D 02 (02)

Mon 07/29/2013 09:44:14 : [std-Direct Ack] 22.F9.73-->ISY/PLM Group=0, Max Hops=3, Hops Left=0

Mon 07/29/2013 09:44:14 : [22 F9 73 0 ] Calibrating engine version

Mon 07/29/2013 09:44:14 : [iNST-TX-I2CS] 02 62 22 F9 73 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0

Mon 07/29/2013 09:44:14 : [iNST-ACK ] 02 62 22.F9.73 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00)

Mon 07/29/2013 09:44:14 : [iNST-SRX ] 02 50 22.F9.73 0D.4F.45 23 2F 00 (00)

Mon 07/29/2013 09:44:14 : [std-Direct Ack] 22.F9.73-->ISY/PLM Group=0, Max Hops=3, Hops Left=0

Mon 07/29/2013 09:44:15 : [iNST-ERX ] 02 51 22 F9 73 0D 4F 45 12 2F 00 00 01 0F FF 00 A2 28 0D 4F 45 FF 1F 05 34

Mon 07/29/2013 09:44:15 : [Ext-Direct ] 22.F9.73-->ISY/PLM Group=0, Max Hops=2, Hops Left=0

Mon 07/29/2013 09:44:15 : [22 F9 73 1 ] Link 0 : 0FF8 [A2280D4F45FF1F05] Writing [A2280D4F45FF1F05]

Mon 07/29/2013 09:44:15 : [iNST-TX-I2CS] 02 62 22 F9 73 1F 2F 00 00 02 0F FF 08 A2 28 0D 4F 45 FF 1F 05 2B

Mon 07/29/2013 09:44:15 : [iNST-ACK ] 02 62 22.F9.73 1F 2F 00 00 02 0F FF 08 A2 28 0D 4F 45 FF 1F 05 2B 06 (00)

Mon 07/29/2013 09:44:17 : [iNST-SRX ] 02 50 22.F9.73 0D.4F.45 23 2F 00 (00)

Mon 07/29/2013 09:44:17 : [std-Direct Ack] 22.F9.73-->ISY/PLM Group=0, Max Hops=3, Hops Left=0

Mon 07/29/2013 09:44:17 : [MNG-LNK-RSP ] 02 6F 40 E2 28 22 F9 73 01 42 43 15

Mon 07/29/2013 09:44:17 : [PLM ] Group 40 : Writing Controller Link matching [22 F9 73 1 ] Link 0 : 0FF8 [A2280D4F45FF1F05]

Mon 07/29/2013 09:44:17 : [22 F9 73 1 ] Link 1 : 0FF0 [A201192B3DFF1F05] Writing [A201192B3DFF1F05]

Mon 07/29/2013 09:44:17 : [iNST-TX-I2CS] 02 62 22 F9 73 1F 2F 00 00 02 0F F7 08 A2 01 19 2B 3D FF 1F 05 7A

Mon 07/29/2013 09:44:18 : [iNST-ACK ] 02 62 22.F9.73 1F 2F 00 00 02 0F F7 08 A2 01 19 2B 3D FF 1F 05 7A 06 (00)

Mon 07/29/2013 09:44:18 : [iNST-SRX ] 02 50 22.F9.73 0D.4F.45 27 2F 00 (00)

Mon 07/29/2013 09:44:18 : [std-Direct Ack] 22.F9.73-->ISY/PLM Group=0, Max Hops=3, Hops Left=1

Mon 07/29/2013 09:44:18 : [22 F9 73 1 ] Link 2 : 0FE8 [A2000D4F45FF1F01] Writing [A2000D4F45FF1F01]

Mon 07/29/2013 09:44:18 : [iNST-TX-I2CS] 02 62 22 F9 73 1F 2F 00 00 02 0F EF 08 A2 00 0D 4F 45 FF 1F 01 67

Mon 07/29/2013 09:44:19 : [iNST-ACK ] 02 62 22.F9.73 1F 2F 00 00 02 0F EF 08 A2 00 0D 4F 45 FF 1F 01 67 06 (00)

Mon 07/29/2013 09:44:19 : [iNST-SRX ] 02 50 22.F9.73 0D.4F.45 23 2F 00 (00)

Mon 07/29/2013 09:44:19 : [std-Direct Ack] 22.F9.73-->ISY/PLM Group=0, Max Hops=3, Hops Left=0

Mon 07/29/2013 09:44:19 : [MNG-LNK-RSP ] 02 6F 40 E2 00 22 F9 73 01 42 43 15

Mon 07/29/2013 09:44:19 : [PLM ] Group 0 : Writing Controller Link matching [22 F9 73 1 ] Link 2 : 0FE8 [A2000D4F45FF1F01]

Mon 07/29/2013 09:44:19 : [22 F9 73 1 ] Link 3 : 0FE0 [E2010D4F45FF0001] Writing [E2010D4F45FF0001]

Mon 07/29/2013 09:44:19 : [iNST-TX-I2CS] 02 62 22 F9 73 1F 2F 00 00 02 0F E7 08 E2 01 0D 4F 45 FF 00 01 4D

Mon 07/29/2013 09:44:20 : [iNST-ACK ] 02 62 22.F9.73 1F 2F 00 00 02 0F E7 08 E2 01 0D 4F 45 FF 00 01 4D 06 (00)

Mon 07/29/2013 09:44:20 : [iNST-SRX ] 02 50 22.F9.73 0D.4F.45 23 2F 00 (00)

Mon 07/29/2013 09:44:20 : [std-Direct Ack] 22.F9.73-->ISY/PLM Group=0, Max Hops=3, Hops Left=0

Mon 07/29/2013 09:44:20 : [MNG-LNK-RSP ] 02 6F 41 A2 01 22 F9 73 01 42 43 15

Mon 07/29/2013 09:44:20 : [PLM ] Group 1 : Writing Responder Link matching [22 F9 73 1 ] Link 3 : 0FE0 [E2010D4F45FF0001]

Mon 07/29/2013 09:44:21 : [22 F9 73 1 ] Link 4 : 0FD8 [E2030D4F45FF0003] Writing [E2030D4F45FF0003]

Mon 07/29/2013 09:44:21 : [iNST-TX-I2CS] 02 62 22 F9 73 1F 2F 00 00 02 0F DF 08 E2 03 0D 4F 45 FF 00 03 51

Mon 07/29/2013 09:44:21 : [iNST-ACK ] 02 62 22.F9.73 1F 2F 00 00 02 0F DF 08 E2 03 0D 4F 45 FF 00 03 51 06 (00)

Mon 07/29/2013 09:44:21 : [iNST-SRX ] 02 50 22.F9.73 0D.4F.45 00 E8 40 (40)

Mon 07/29/2013 09:44:21 : [std-Direct ] 22.F9.73-->ISY/PLM Group=0, Max Hops=0, Hops Left=0

Mon 07/29/2013 09:44:30 : [iNST-TX-I2CS] 02 62 22 F9 73 1F 2F 00 00 02 0F DF 08 E2 03 0D 4F 45 FF 00 03 51

Mon 07/29/2013 09:44:30 : [iNST-ACK ] 02 62 22.F9.73 1F 2F 00 00 02 0F DF 08 E2 03 0D 4F 45 FF 00 03 51 06 (00)

Mon 07/29/2013 09:44:39 : [iNST-TX-I2CS] 02 62 22 F9 73 1F 2F 00 00 02 0F DF 08 E2 03 0D 4F 45 FF 00 03 51

Mon 07/29/2013 09:44:39 : [iNST-ACK ] 02 62 22.F9.73 1F 2F 00 00 02 0F DF 08 E2 03 0D 4F 45 FF 00 03 51 06 (00)

Mon 07/29/2013 09:44:43 : [22 F9 73 1 ] Link 4 : 0FD8 [E2030D4F45FF0003] *Failed Writing [E2030D4F45FF0003]

Mon 07/29/2013 09:44:43 : [ 22 F9 73 1] ERR 1

LeeG · July 29, 2013

Communication with device 22.F9.73 is very poor. The Max Hops=3, Hops Left=0 is as bad as it can get and still work. Both Standard and Extended messages are having problems. Eventually one of the device responses was garbled at which point the device stopped responding at all. Look for some form of interference on the circuit or perhaps a phase coupling issue if this circuit is on the opposite phase to the PLM circuit. Try unplugging appliances on this circuit to see if the problem can be identified to a specific appliance.