Jump to content

Problem with KeypadLinc

jday

By jday
in INSTEON Communications Issues

Recommended Posts

jday Newbie

jday

Posted
Posted

I control many Insteon devices with my isy994i, including several dual band devices and I have two new access points installed. I just installed a FanLinc to control a ceiling fan and light. The FanLinc itself works fine and I can control it properly with both the UD Administrative Console and from Mobilinc on both my iPhone and iPad. I can also control it with a RemoteLinc2. My issue is trying to get a KeypadLinc to work with the isy.

 

Based on information from the Smarthome Insteon forums I installed the KeypadLinc (KPL) without connecting its load wire so that I could just program all the buttons via the isy Administrative Console. When I try to add the KPL as a new Insteon device, the software DOES find it, correctly identifies it and add the appropriate number of devices in the left hand column. However, as it tries to write to the KPL it cannot communicate with it and I receive an error message telling me it can't communicate and to check the connection.

 

My first question is, "is it normal for the software to find the device and correctly identify it but not be able to communicate with it? Does this indicate that the KPL might be defective? If not, it must be a wiring problem. Any help/suggestion would be greatly appreciated.

jday Newbie

jday

Posted
  • Author
Posted

I'm still struggling with this. To maybe help someone determine my problem, I deleted the KPL from the ISY (since it wasn't communicating anyway) and added it back in while using the logging the actions. As before, the ISY did find the KPL and lists it properly but then cannot communicate with it. Here is a copy of the event log:

 

Thu 08/01/2013 08:55:18 AM : [19 3D 1A ] Added to list of devices to link to ISY

 

Thu 08/01/2013 08:55:18 AM : [iNST-TX-I1 ] 02 62 19 3D 1A 0F 0D 00

 

Thu 08/01/2013 08:55:18 AM : [iNST-ACK ] 02 62 19.3D.1A 0F 0D 00 06 (00)

 

Thu 08/01/2013 08:55:19 AM : [iNST-SRX ] 02 50 19.3D.1A 22.FE.10 2B 0D 01 (01)

 

Thu 08/01/2013 08:55:19 AM : [std-Direct Ack] 19.3D.1A-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

 

Thu 08/01/2013 08:55:19 AM : [iNST-TX-I1 ] 02 62 19 3D 1A 0F 10 00

 

Thu 08/01/2013 08:55:19 AM : [iNST-ACK ] 02 62 19.3D.1A 0F 10 00 06 ID-REQ (00)

 

Thu 08/01/2013 08:55:21 AM : [iNST-SRX ] 02 50 19.3D.1A 22.FE.10 2B 10 00 ID-REQ (00)

 

Thu 08/01/2013 08:55:21 AM : [std-Direct Ack] 19.3D.1A-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

 

Thu 08/01/2013 08:55:21 AM : [iNST-SRX ] 02 50 19.3D.1A 01.1C.40 8B 01 00 (00)

 

Thu 08/01/2013 08:55:21 AM : [std-Broadcast] 19.3D.1A-->01.1C.40, Max Hops=3, Hops Left=2

 

Thu 08/01/2013 08:55:21 AM : [19 3D 1A 0 ] Calibrating engine version

 

Thu 08/01/2013 08:55:21 AM : [19 3D 1A 0 ] May not fully support i2, reverting to i1

 

Thu 08/01/2013 08:55:21 AM : [19 3D 1A 0 ] Using Database Link Table offset 0x0FF8 (reported 0x0000)

 

Thu 08/01/2013 08:55:21 AM : [19 3D 1A 1 ] Start : Adding device to ISY

 

Thu 08/01/2013 08:55:21 AM : [19 3D 1A 1 ] Finish : Adding device to ISY was Successful

 

Thu 08/01/2013 08:55:21 AM : [19 3D 1A 1 ] Link 0 : 0FF8 [A20022FE10FF1F01] Saving [A20022FE10FF1F01]

 

Thu 08/01/2013 08:55:21 AM : [19 3D 1A 1 ] Link 1 : 0FF0 [E20122FE10FF0001] Saving [E20122FE10FF0001]

 

Thu 08/01/2013 08:55:21 AM : [iNST-TX-I2 ] 02 62 19 3D 1A 1F 2E 00 01 00 00 00 00 00 00 00 00 00 00 00 00 D1

 

Thu 08/01/2013 08:55:21 AM : [iNST-ACK ] 02 62 19.3D.1A 1F 2E 00 01 00 00 00 00 00 00 00 00 00 00 00 00 D1 06 (00)

 

Thu 08/01/2013 08:55:25 AM : [iNST-ERX ] 02 51 19 3D 1A 22 FE 10 13 2E 00 01 01 00 00 20 20 1C FE 3F 00 23 00 00 00

 

Thu 08/01/2013 08:55:25 AM : [Ext-Direct ] 19.3D.1A-->ISY/PLM Group=0, Max Hops=3, Hops Left=0

 

Thu 08/01/2013 08:55:25 AM : [ 19 3D 1A 1] OL 255

 

Thu 08/01/2013 08:55:25 AM : [ 19 3D 1A 1] RR 28

 

Thu 08/01/2013 08:55:25 AM : [iNST-TX-I1 ] 02 62 19 3D 1A 0F 1F 00

 

Thu 08/01/2013 08:55:25 AM : [iNST-ACK ] 02 62 19.3D.1A 0F 1F 00 06 GOF (FLAGS)

 

Thu 08/01/2013 08:55:26 AM : [iNST-SRX ] 02 50 19.3D.1A 22.FE.10 27 1F 00 GOF (FLAGS)

 

Thu 08/01/2013 08:55:26 AM : [std-Direct Ack] 19.3D.1A-->ISY/PLM Group=0, Max Hops=3, Hops Left=1

 

Thu 08/01/2013 08:55:26 AM : [19 3D 1A 3 ] Start : Adding device to ISY

 

Thu 08/01/2013 08:55:26 AM : [19 3D 1A 3 ] Finish : Adding device to ISY was Successful

 

Thu 08/01/2013 08:55:26 AM : [19 3D 1A 3 ] Link 2 : 0FE8 [E20322FE10FF0003] Saving [E20322FE10FF0003]

 

Thu 08/01/2013 08:55:26 AM : [19 3D 1A 4 ] Start : Adding device to ISY

 

Thu 08/01/2013 08:55:26 AM : [19 3D 1A 4 ] Finish : Adding device to ISY was Successful

 

Thu 08/01/2013 08:55:26 AM : [19 3D 1A 4 ] Link 3 : 0FE0 [E20422FE10FF0004] Saving [E20422FE10FF0004]

 

Thu 08/01/2013 08:55:26 AM : [19 3D 1A 5 ] Start : Adding device to ISY

 

Thu 08/01/2013 08:55:26 AM : [19 3D 1A 5 ] Finish : Adding device to ISY was Successful

 

Thu 08/01/2013 08:55:26 AM : [19 3D 1A 5 ] Link 4 : 0FD8 [E20522FE10FF0005] Saving [E20522FE10FF0005]

 

Thu 08/01/2013 08:55:26 AM : [19 3D 1A 6 ] Start : Adding device to ISY

 

Thu 08/01/2013 08:55:26 AM : [19 3D 1A 6 ] Finish : Adding device to ISY was Successful

 

Thu 08/01/2013 08:55:26 AM : [19 3D 1A 6 ] Link 5 : 0FD0 [E20622FE10FF0006] Saving [E20622FE10FF0006]

 

Thu 08/01/2013 08:55:26 AM : [iNST-TX-I1 ] 02 62 19 3D 1A 0F 19 00

 

Thu 08/01/2013 08:55:26 AM : [iNST-ACK ] 02 62 19.3D.1A 0F 19 00 06 LTSREQ (LIGHT)

 

Thu 08/01/2013 08:55:28 AM : [iNST-SRX ] 02 50 19.3D.1A 22.FE.10 27 00 FE (FE)

 

Thu 08/01/2013 08:55:28 AM : [std-Direct Ack] 19.3D.1A-->ISY/PLM Group=0, Max Hops=3, Hops Left=1

 

Thu 08/01/2013 08:55:28 AM : [ 19 3D 1A 1] ST 255

 

Thu 08/01/2013 08:55:28 AM : [ 19 3D 1A 1] OL 255

 

Thu 08/01/2013 08:55:28 AM : [ 19 3D 1A 1] RR 28

 

Thu 08/01/2013 08:55:28 AM : [iNST-TX-I2 ] 02 62 19 3D 1A 1F 2E 00 01 00 00 00 00 00 00 00 00 00 00 00 00 D1

 

Thu 08/01/2013 08:55:28 AM : [iNST-ACK ] 02 62 19.3D.1A 1F 2E 00 01 00 00 00 00 00 00 00 00 00 00 00 00 D1 06 (00)

 

Thu 08/01/2013 08:55:31 AM : [iNST-ERX ] 02 51 19 3D 1A 22 FE 10 12 2E 00 01 01 00 00 20 20 1C FE 3F 00 23 00 00 00

 

Thu 08/01/2013 08:55:31 AM : [Ext-Direct ] 19.3D.1A-->ISY/PLM Group=0, Max Hops=2, Hops Left=0

 

Thu 08/01/2013 08:55:31 AM : [ 19 3D 1A 3] ST 0

 

Thu 08/01/2013 08:55:31 AM : [ 19 3D 1A 4] ST 0

 

Thu 08/01/2013 08:55:31 AM : [ 19 3D 1A 5] ST 0

 

Thu 08/01/2013 08:55:31 AM : [ 19 3D 1A 6] ST 255

 

Thu 08/01/2013 08:55:31 AM : [19 3D 1A 0 ] Successfully added device

 

Thu 08/01/2013 08:55:32 AM : [All ] Writing 48 bytes to devices

 

Thu 08/01/2013 08:55:32 AM : [19 3D 1A 1 ] Link 0 : 0FF8 [A20022FE10FF1F01] Writing [A20022FE10FF1F01]

 

Thu 08/01/2013 08:55:32 AM : [iNST-TX-I1 ] 02 62 19 3D 1A 0F 28 0F

 

Thu 08/01/2013 08:55:32 AM : [iNST-ACK ] 02 62 19.3D.1A 0F 28 0F 06 SET-MSB(0F)

 

Thu 08/01/2013 08:55:41 AM : [iNST-TX-I1 ] 02 62 19 3D 1A 0F 28 0F

 

Thu 08/01/2013 08:55:41 AM : [iNST-ACK ] 02 62 19.3D.1A 0F 28 0F 06 SET-MSB(0F)

 

Thu 08/01/2013 08:55:50 AM : [iNST-TX-I1 ] 02 62 19 3D 1A 0F 28 0F

 

Thu 08/01/2013 08:55:50 AM : [iNST-ACK ] 02 62 19.3D.1A 0F 28 0F 06 SET-MSB(0F)

 

Thu 08/01/2013 08:55:50 AM : [iNST-SRX ] 02 50 19.3D.1A 22.FE.10 2B 28 0F SET-MSB(0F)

 

Thu 08/01/2013 08:55:50 AM : [std-Direct Ack] 19.3D.1A-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

 

Thu 08/01/2013 08:55:50 AM : [iNST-TX-I1 ] 02 62 19 3D 1A 0F 2B F8

 

Thu 08/01/2013 08:55:50 AM : [iNST-ACK ] 02 62 19.3D.1A 0F 2B F8 06 PEEK (F8)

 

Thu 08/01/2013 08:55:51 AM : [iNST-SRX ] 02 50 19.3D.1A 22.FE.10 27 2B 00 PEEK (00)

 

Thu 08/01/2013 08:55:51 AM : [std-Direct Ack] 19.3D.1A-->ISY/PLM Group=0, Max Hops=3, Hops Left=1

 

Thu 08/01/2013 08:55:51 AM : [iNST-TX-I1 ] 02 62 19 3D 1A 0F 29 A2

 

Thu 08/01/2013 08:55:51 AM : [iNST-ACK ] 02 62 19.3D.1A 0F 29 A2 06 POKE (A2)

 

Thu 08/01/2013 08:55:55 AM : [19 3D 1A 1 ] Link 0 : 0FF8 [A20022FE10FF1F01] *Failed Writing [A20022FE10FF1F01]

 

Thu 08/01/2013 08:55:55 AM : [ 19 3D 1A 1] ERR 1

LeeG Advanced

LeeG

Posted
Posted

The KeypadLinc is pre I2CS. The event trace shows erratic communication with the KeypadLinc location. Some command exchanges have a Max Hops=3 Hops Left=2 which is as good as it gets.

Other exchanges have a Max Hops=3 Hops Left=0 which is as bad as it gets. The exchanges at the end of the trace show the KeypadLinc failed to respond at all (no 02 50 inbound from device).

 

This could be a poor phase coupling situation or some form of interference on that circuit.

 

This is what good Insteon Mesh network response looks like. All the exchanges have Max Hops=3 Hops Left=2..

 

Thu 08/01/2013 10:43:06 AM : [1B 57 F8 1 ] Link 1 : 0FF0 [A25122800BFF1F04] Writing [A25122800BFF1F04]

 

Thu 08/01/2013 10:43:06 AM : [iNST-TX-I1 ] 02 62 1B 57 F8 0F 28 0F

 

Thu 08/01/2013 10:43:06 AM : [iNST-ACK ] 02 62 1B.57.F8 0F 28 0F 06 SET-MSB(0F)

 

Thu 08/01/2013 10:43:06 AM : [iNST-SRX ] 02 50 1B.57.F8 22.80.0B 2B 28 0F SET-MSB(0F)

 

Thu 08/01/2013 10:43:06 AM : [std-Direct Ack] 1B.57.F8-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

 

Thu 08/01/2013 10:43:06 AM : [iNST-TX-I1 ] 02 62 1B 57 F8 0F 2B F0

 

Thu 08/01/2013 10:43:06 AM : [iNST-ACK ] 02 62 1B.57.F8 0F 2B F0 06 PEEK (F0)

 

Thu 08/01/2013 10:43:07 AM : [iNST-SRX ] 02 50 1B.57.F8 22.80.0B 2B 2B A2 PEEK (A2)

 

Thu 08/01/2013 10:43:07 AM : [std-Direct Ack] 1B.57.F8-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

 

Thu 08/01/2013 10:43:07 AM : [iNST-TX-I1 ] 02 62 1B 57 F8 0F 28 0F

 

Thu 08/01/2013 10:43:07 AM : [iNST-ACK ] 02 62 1B.57.F8 0F 28 0F 06 SET-MSB(0F)

 

Thu 08/01/2013 10:43:07 AM : [iNST-SRX ] 02 50 1B.57.F8 22.80.0B 2B 28 0F SET-MSB(0F)

 

Thu 08/01/2013 10:43:07 AM : [std-Direct Ack] 1B.57.F8-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

 

Thu 08/01/2013 10:43:07 AM : [iNST-TX-I1 ] 02 62 1B 57 F8 0F 2B F1

 

Thu 08/01/2013 10:43:07 AM : [iNST-ACK ] 02 62 1B.57.F8 0F 2B F1 06 PEEK (F1)

 

Thu 08/01/2013 10:43:08 AM : [iNST-SRX ] 02 50 1B.57.F8 22.80.0B 2B 2B 50 PEEK (50)

 

Thu 08/01/2013 10:43:08 AM : [std-Direct Ack] 1B.57.F8-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

 

Thu 08/01/2013 10:43:08 AM : [iNST-TX-I1 ] 02 62 1B 57 F8 0F 29 51

 

Thu 08/01/2013 10:43:08 AM : [iNST-ACK ] 02 62 1B.57.F8 0F 29 51 06 POKE (51)

 

Thu 08/01/2013 10:43:08 AM : [iNST-SRX ] 02 50 1B.57.F8 22.80.0B 2B 29 51 POKE (51)

 

Thu 08/01/2013 10:43:08 AM : [std-Direct Ack] 1B.57.F8-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

 

Thu 08/01/2013 10:43:08 AM : [iNST-TX-I1 ] 02 62 1B 57 F8 0F 2B F2

 

Thu 08/01/2013 10:43:08 AM : [iNST-ACK ] 02 62 1B.57.F8 0F 2B F2 06 PEEK (F2)

 

Thu 08/01/2013 10:43:09 AM : [iNST-SRX ] 02 50 1B.57.F8 22.80.0B 2B 2B 22 PEEK (22)

 

Thu 08/01/2013 10:43:09 AM : [std-Direct Ack] 1B.57.F8-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

 

Thu 08/01/2013 10:43:09 AM : [iNST-TX-I1 ] 02 62 1B 57 F8 0F 28 0F

 

Thu 08/01/2013 10:43:09 AM : [iNST-ACK ] 02 62 1B.57.F8 0F 28 0F 06 SET-MSB(0F)

 

Thu 08/01/2013 10:43:09 AM : [iNST-SRX ] 02 50 1B.57.F8 22.80.0B 2B 28 0F SET-MSB(0F)

 

Thu 08/01/2013 10:43:09 AM : [std-Direct Ack] 1B.57.F8-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

 

Thu 08/01/2013 10:43:09 AM : [iNST-TX-I1 ] 02 62 1B 57 F8 0F 2B F3

 

Thu 08/01/2013 10:43:09 AM : [iNST-ACK ] 02 62 1B.57.F8 0F 2B F3 06 PEEK (F3)

 

Thu 08/01/2013 10:43:10 AM : [iNST-SRX ] 02 50 1B.57.F8 22.80.0B 2B 2B 80 PEEK (80)

 

Thu 08/01/2013 10:43:10 AM : [std-Direct Ack] 1B.57.F8-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

 

Thu 08/01/2013 10:43:10 AM : [iNST-TX-I1 ] 02 62 1B 57 F8 0F 28 0F

 

Thu 08/01/2013 10:43:10 AM : [iNST-ACK ] 02 62 1B.57.F8 0F 28 0F 06 SET-MSB(0F)

 

Thu 08/01/2013 10:43:10 AM : [iNST-SRX ] 02 50 1B.57.F8 22.80.0B 2B 28 0F SET-MSB(0F)

 

Thu 08/01/2013 10:43:10 AM : [std-Direct Ack] 1B.57.F8-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

 

Thu 08/01/2013 10:43:10 AM : [iNST-TX-I1 ] 02 62 1B 57 F8 0F 2B F4

 

Thu 08/01/2013 10:43:10 AM : [iNST-ACK ] 02 62 1B.57.F8 0F 2B F4 06 PEEK (F4)

 

Thu 08/01/2013 10:43:11 AM : [iNST-SRX ] 02 50 1B.57.F8 22.80.0B 2B 2B 0B PEEK (0B)

 

Thu 08/01/2013 10:43:11 AM : [std-Direct Ack] 1B.57.F8-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

 

Thu 08/01/2013 10:43:11 AM : [iNST-TX-I1 ] 02 62 1B 57 F8 0F 28 0F

 

Thu 08/01/2013 10:43:11 AM : [iNST-ACK ] 02 62 1B.57.F8 0F 28 0F 06 SET-MSB(0F)

 

Thu 08/01/2013 10:43:11 AM : [iNST-SRX ] 02 50 1B.57.F8 22.80.0B 2B 28 0F SET-MSB(0F)

 

Thu 08/01/2013 10:43:11 AM : [std-Direct Ack] 1B.57.F8-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

 

Thu 08/01/2013 10:43:11 AM : [iNST-TX-I1 ] 02 62 1B 57 F8 0F 2B F5

 

Thu 08/01/2013 10:43:11 AM : [iNST-ACK ] 02 62 1B.57.F8 0F 2B F5 06 PEEK (F5)

 

Thu 08/01/2013 10:43:12 AM : [iNST-SRX ] 02 50 1B.57.F8 22.80.0B 2B 2B FF PEEK (FF)

 

Thu 08/01/2013 10:43:12 AM : [std-Direct Ack] 1B.57.F8-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

 

Thu 08/01/2013 10:43:12 AM : [iNST-TX-I1 ] 02 62 1B 57 F8 0F 28 0F

 

Thu 08/01/2013 10:43:12 AM : [iNST-ACK ] 02 62 1B.57.F8 0F 28 0F 06 SET-MSB(0F)

 

Thu 08/01/2013 10:43:12 AM : [iNST-SRX ] 02 50 1B.57.F8 22.80.0B 2B 28 0F SET-MSB(0F)

 

Thu 08/01/2013 10:43:12 AM : [std-Direct Ack] 1B.57.F8-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

 

Thu 08/01/2013 10:43:12 AM : [iNST-TX-I1 ] 02 62 1B 57 F8 0F 2B F6

 

Thu 08/01/2013 10:43:12 AM : [iNST-ACK ] 02 62 1B.57.F8 0F 2B F6 06 PEEK (F6)

 

Thu 08/01/2013 10:43:13 AM : [iNST-SRX ] 02 50 1B.57.F8 22.80.0B 2B 2B 1F PEEK (1F)

 

Thu 08/01/2013 10:43:13 AM : [std-Direct Ack] 1B.57.F8-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

 

Thu 08/01/2013 10:43:13 AM : [iNST-TX-I1 ] 02 62 1B 57 F8 0F 28 0F

 

Thu 08/01/2013 10:43:13 AM : [iNST-ACK ] 02 62 1B.57.F8 0F 28 0F 06 SET-MSB(0F)

 

Thu 08/01/2013 10:43:13 AM : [iNST-SRX ] 02 50 1B.57.F8 22.80.0B 2B 28 0F SET-MSB(0F)

 

Thu 08/01/2013 10:43:13 AM : [std-Direct Ack] 1B.57.F8-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

 

Thu 08/01/2013 10:43:13 AM : [iNST-TX-I1 ] 02 62 1B 57 F8 0F 2B F7

 

Thu 08/01/2013 10:43:13 AM : [iNST-ACK ] 02 62 1B.57.F8 0F 2B F7 06 PEEK (F7)

 

Thu 08/01/2013 10:43:14 AM : [iNST-SRX ] 02 50 1B.57.F8 22.80.0B 2B 2B 04 PEEK (04)

 

Thu 08/01/2013 10:43:14 AM : [std-Direct Ack] 1B.57.F8-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

 

Thu 08/01/2013 10:43:14 AM : [MNG-LNK-RSP ] 02 6F 40 E2 51 1B 57 F8 01 1C 40 15

oberkc Advanced

oberkc

Posted
Posted

My first inclination would be to ensure that you have the latest version of ISY software. My second thought would be to try a different method of linking. Put the ISY into linking mode, then walk over to the newdevice and put that device into linking mode. Does this work?

 

If yor devices are powered and contolling the loads properly, then I would tend to discount wiring problems, other than the possibility of a loose connection that is causing communication errors.

 

I am not an expert reading these logs, but the line regarding i2 versus i1 makes me suspect that device was initially misidentified. This can happen when manually choosing a device from a dropdown box during the initial linking process.

 

Otherwise, I suspect communication problems.

jday Newbie

jday

Posted
  • Author
Posted

Thanks for the reply. I do have a couple of questions based on your response. You said that the KeypadLinc is pre 12CS. What exactly does that mean other than it is an older KeypadLinc? Would I newer KeypadLinc possibly solve the problem? As to the poor phase coupling, although it is possible, I have almost a dozen dual band devices installed in my house and 2 access points so I would not think that would be the problem. That leaves some form of interference on that circuit and I'll have to figure out how to determine that.

 

Can you explain why the ISY "discovers" the KeypadLinc, correctly identifies it and creates appropriate devices for the different buttons, BUT then cannot "communicate"? To me, if it never discovered it, then I would understand there is something wrong either with the KPL or the wiring. Thanks again for the response.

LeeG Advanced

LeeG

Posted
Posted

The KeypadLinc is an I2 device. Just means it is not the newest I2CS variation. A new KeypadLinc might work because they are now Dual Band. Communication with the KeypadLinc location varies from command to command. The initial two commands that identify the type of Insteon Engine (I2 versus I2CS) and query the device type work. Commands later in the sequence get a response but at the very edge of reliability. Eventually commands get no response at which point the process stops.

 

Have you verified the KeypadLinc is being powered from unswitched 120v?

 

The KeypadLinc can be tested by connecting it to an Appliance cord (plug on one end, bare wires on the other) and plug it into the PLM plug point. That would insure the device is functional.

jday Newbie

jday

Posted
  • Author
Posted

The KPL is being powered from unswitched 120v and is replacing a single pole switch that used to control the ceiling fan/light together. I went ahead and ordered a new 2487S KeypadLinc so once I get it I will see if it works. Right now since the currently installed KPL won't control anything I'm controlling my ceiling fan and light with a RemoteLinc2 that I have. It will work until I can get this figured out.

LeeG Advanced

LeeG

Posted
Posted

"The KPL is being powered from unswitched 120v "

 

How was this verified?

 

EDIT: the reason I ask is how the commands progressed from good to poor to no response. That in combination with a single event trace to evaluate makes me think all the bases should be covered.

jday Newbie

jday

Posted
  • Author
Posted

I might not understand switched vs unswitched. This was just a standard light switch box so I assumed it was unswitched. After your question I decided to learn the difference and am confused, so I don't really know. Here is some clarification/additional information. The KPL does get power since the lights on the buttons do work. Both the line and load wires in the switch box are connected together with the line wire from the KPL. The load wire on the KPL is capped/not connected.

 

One other thing that might or might not be affecting this (unlikely, but I don't know). As I mentioned above there is NO red wire in the switch box. However, there is another switchbox about 6 inches away that has a regular light switch (not 3-way). Where that light switch would normally have only two wires (plus the ground) connected, that box has the extra red wire and it is connected along with the line wire to the switch (the red wire is stuck in the hole in the back of the switch and the line wire is connected by the screw on the same end of the switch). The load wire is connected to the other screw on the switch. I'm not sure why there is a red wire connected to this switch (and since it's connected WITH the line wire, I assume it is always hot). That switch simply control a light in the closet. Do you think it's possible that that red wire (although not in the switch box with the fan switch) is actually from the fan/light? If so, should I simply disconnect it and cap it since the KPL should be controlling the fan/light? I hope this all made some sense.

LeeG Advanced

LeeG

Posted
Posted

I would not make any changes to the switch 6 inches away. I was hoping the power to the KeypadLinc had been verified with a meter to be nominally 120v throughout the process of commands working versus not working.

 

TFitz made an assumption about the color of the wires. The lack of a red wire from the switch to the Fan location is not unusual. The assumption is a Black/White pair in one cable supplies power to the box. Another Black/White pair in its own cable goes from the box to the Fan location. The Whites (Neutral) would have been connected together with a wire nut. The Black Line would go to one side of the original mechanical switch. The switched Black load was connected to the other terminal of the mechanical switch which supplied switched power to the Fan.

 

The two Black wires that had been connected to the switch have been connected together to provide unswitched power to the Fan location with the Black wire from the KeypadLinc attached to the same Black pair to provide unswitched power to the KeypadLinc. The White wire from the KeypadLinc is connected to the White pair in the box.

 

Analyzing/diagnosing through someone else’s eyes is always a challenge. I try to verify circumstances by checking the same thing different ways.

jday Newbie

jday

Posted
  • Author
Posted

Lee, thanks for your patience and explanations. I DID verify the 120V line wire using a multimeter before I installed the switch. My situation and connections are exactly like you described in your last post. So, I'm confident that my original connections are done correctly. The problem is simply a communication problem between the KPL and the ISY. I'm hoping that the new KPL I ordered will fix this.

 

Since, I don't plan on doing any "programming" of the KPL and ceiling fan/light, I suppose I do have one other possible thing to try. I could remove the cowling from the ceiling fan and try to link the KPL buttons directly with the FanLinc (bypassing the ISY). In your opinion, do you think this might work?

LeeG Advanced

LeeG

Posted
Posted

That is not a good idea. Neither the KeypadLinc nor FanLinc can be restored by the ISY should something happen to the links. Specially a problem with the FanLinc because of its physical location. Better to find and fix the powerline problem.

jday Newbie

jday

Posted
  • Author
Posted

SUCCESS! Although I thought the KPL could have been bad and ordered a new one, while waiting for it I tried something else (without much hope). Much to my surprise, it worked and now my KPL is properly controlling my ceiling fan and light. I had 2 access points properly bridged already, but decided to move one of them to an outlet in the same room at the KPL and ceiling fan. That was all it took. All other devices in the house still work properly. This was frustrating, but there is always a rush of excitement when something you've been trying to figure out finally works. Thanks again for all the help.

Archived

This topic is now archived and is closed to further replies.

Go to topic listing
×
×
  • Create New...