Keypadlinc 3 way behavior

[BCreekDave]

I have a 8 button keypadlinc in my mudroom where button A controls the ceiling light in the room.  On the other side of the room is an Insteon togglelinc in a 3-way companion to the ceiling light.  Button A is the controller for the load.  Button B on the keypadlinc opens the garage door via an iolinc system.  When the garage door is closed, Button B is illuminated ("on") and one press will raise the door.  When the door is open, Button B is not illuminated ("off") and one press will close the door.

 

The problem is when the togglelinc is used to turn off the ceiling light, it also turns off button B (and correctly Button A), thus requiring now two presses to raise the door (one press will re-illuminate the button (arming it) and then another press to activate the door open program).  This is not a rare event but happens with complete consistency.  Really, the way it is working is Button B's illumination is following Button A's.  This is the only button on the keypadlinc that does this.  The other buttons on the keypadlinc are completely independent of the togglelinc.  So, in summary, from the togglelinc when you turn on the ceiling light, both button A and button B illuminate and when you turn off the ceiling light from the togglelinc both button A and button B turn off.

 

In the event log, when I toggle off the togglelinc I am seeing traffic such as this:

Togglelinc turn off:

Sat 05/02/2015 04:16:33 PM : [iNST-SRX    ] 02 50 17.AE.2F 00.00.01 CB 13 00    LTOFFRR(00)

Sat 05/02/2015 04:16:33 PM : [std-Group   ] 17.AE.2F-->Group=1, Max Hops=3, Hops Left=2

Sat 05/02/2015 04:16:33 PM : [D2D EVENT   ] Event [17 AE 2F 1] [DOF] [0] uom=0 prec=-1

Sat 05/02/2015 04:16:33 PM : [  17 AE 2F 1]      DOF   0

Sat 05/02/2015 04:16:33 PM : [iNST-SRX    ] 02 50 17.AE.2F 1C.F9.D3 41 13 01    LTOFFRR(01)

Sat 05/02/2015 04:16:33 PM : [std-Cleanup ] 17.AE.2F-->ISY/PLM Group=1, Max Hops=1, Hops Left=0

Sat 05/02/2015 04:16:33 PM : [iNST-DUP    ] Previous message ignored.

Sat 05/02/2015 04:16:34 PM : [X10-RX      ] 02 52 65 00 

Sat 05/02/2015 04:16:34 PM : [         X10]       A7

Sat 05/02/2015 04:16:34 PM : [X10-RX      ] 02 52 63 80 

Sat 05/02/2015 04:16:34 PM : [         X10]       A7/Off (11)

Sat 05/02/2015 04:16:34 PM : [X10-RX      ] 02 52 63 80 

Sat 05/02/2015 04:16:34 PM : [         X10]       A7/Off (11)

 

Togglelinc turn on:

Sat 05/02/2015 04:36:13 PM : [        Time] 16:36:14 3(0)

Sat 05/02/2015 04:36:25 PM : [iNST-SRX    ] 02 50 17.AE.2F 00.00.01 CB 11 00    LTONRR (00)

Sat 05/02/2015 04:36:25 PM : [std-Group   ] 17.AE.2F-->Group=1, Max Hops=3, Hops Left=2

Sat 05/02/2015 04:36:25 PM : [D2D EVENT   ] Event [17 AE 2F 1] [DON] [0] uom=0 prec=-1

Sat 05/02/2015 04:36:25 PM : [  17 AE 2F 1]      DON   0

Sat 05/02/2015 04:36:25 PM : [D2D EVENT   ] Event [19 40 C2 1] [sT] [255] uom=0 prec=-1

Sat 05/02/2015 04:36:25 PM : [  19 40 C2 1]       ST 255

Sat 05/02/2015 04:36:25 PM : [D2D EVENT   ] Event [17 AE 2F 1] [sT] [255] uom=0 prec=-1

Sat 05/02/2015 04:36:25 PM : [  17 AE 2F 1]       ST 255

Sat 05/02/2015 04:36:25 PM : [iNST-SRX    ] 02 50 17.AE.2F 1C.F9.D3 41 11 01    LTONRR (01)

Sat 05/02/2015 04:36:25 PM : [std-Cleanup ] 17.AE.2F-->ISY/PLM Group=1, Max Hops=1, Hops Left=0

Sat 05/02/2015 04:36:25 PM : [iNST-DUP    ] Previous message ignored.

Sat 05/02/2015 04:36:25 PM : [X10-RX      ] 02 52 65 00 

Sat 05/02/2015 04:36:25 PM : [         X10]       A7

Sat 05/02/2015 04:36:26 PM : [X10-RX      ] 02 52 65 00 

Sat 05/02/2015 04:36:26 PM : [         X10]       A7

Sat 05/02/2015 04:36:26 PM : [X10-RX      ] 02 52 62 80 

Sat 05/02/2015 04:36:26 PM : [         X10]       A7/On (3)

 

The garage door program I am using, if it matters, was taken from this posting:

http://forum.universal-devices.com/topic/11099-garage-door-control-with-kpl-and-mobilinc/

 

but i think it would not matter if Button B was controlling a garage door or even another type of load/function.

 

It really works pretty good except for this idiosyncrasy.

 

I have tried erasing and resetting the togglelinc and the behavior continues.  Any suggestions on where to start troubleshooting this?

 

I will also add that the control of the ceiling light is correct from both the keypadlinc and the togglelinc.  

 

One more thing that may be important, when Button A is used to turn on/off the ceiling light, the state of Button B goes unchanged.

 

Thanks in advance for any help that anyone can provide.

[stusviews]

The most likely culprit is a scene error. View the scene for the ceiling light. Is the ToggleLinc a controller? (Controllers are red, responders are blue.)

 

Also, select button B in the device tree. The right side panel will show any scenes that the button is a member of.

 

Edit: color corrected.

[BCreekDave]

The scene "Mudroom Lights" for the lights shows two devices;  "Mudroom togglelinc" and "A Mud Room Entry Keypad".

When I select button B in the device tree, for membership it shows "Is a Controller for GaragedoorMain" and "is a Responder for Garagedoormain".

 

Garagedoormain is a scene with "Garagedoormain-Sensor" from the iolinc and "B Openclose Garagedoor" as a controller-responder from button B on the keypadlinc.

 

One other thing I want to clarify, even though the button B light is going on and off via the togglelinc, it is not activating the garage door.

[stusviews]

Have you tried factory resetting the ToggleLinc (i.e., using the air-gap) and then restoring it (after ensuring that the ToggleLinc no longer controls button ?

[BCreekDave]

Yes. Twice.

 

 

Sent from using Tapatalk

[oberkc]

Is it possible that this keypad began life as a six-button version and later converted to eight? (When one factory resets a six button keypad that was converted to eight, it reverts back to six.)

[BCreekDave]

No. It has always been an 8 key.

 

 

Sent from using Tapatalk

[stusviews]

Yes. Twice.

 

 

Sent from using Tapatalk

 

And each time the ToggleLinc did NOT control button B after a factory reset but did after a restore?

[BCreekDave]

Yes, both times it had to be re-associated to the keypadlinc A button to work as a 3 way switch.

 

 

Sent from using Tapatalk

[stusviews]

So, with a factory reset, the ToggleLinc does not control button B (nor button A). but after you use the ISY to restore the ToggleLinc it controls both button A and button B.  Is restore what you mean by, "re-associated to the keypadlinc?"

[BCreekDave]

Yes. Exactly. Restore is a better description. I used the ISY 994 to restore the togglelinc. I suppose the next step may be to move button b to perhaps button e (not used currently) to see if it follows the button

 

 

Sent from using Tapatalk

[stusviews]

Disable the garage door program(s). What's the result?

[BCreekDave]

Disabled the garage door programs. No change except now of course when I press button b nothing happens except the button light toggles on and off. When I use the togglelinc button b still does the same thing.

 

 

Sent from using Tapatalk

[stusviews]

What are you using X10 house/unit code A7 for?

[BCreekDave]

I have an old Powerhouse mini-controller in the bedroom and I use it for an all-off or all-on type of command.  Also for the bedroom cans.

[stusviews]

The log shows A7 off (11) and on (3) as being assigned to the ToggleLinc. You may have inadvertently given button B an X10 address.

[BCreekDave]

I think you are correct.  It does have an x10 A7 address assigned.  Probably not an easy way through the ISY to delete this is there?

[BCreekDave]

nevermind...used the Powerhouse controller and removed the x10 address and everything seems to be working well!

 

Thanks stusviews and oberkc for the great help!

[oberkc]

What remains unclear to me is why the factory reset of the switch did not clear the x10 address

[Brian H]

A factory reset should remove everything. Including an X10 addresses in a module.

I have in tests. Has a different X10 address on each button on a KPL and a factory reset removed all of them.

Though mine are older and who knows exactly what the latest firmware does.

[BCreekDave]

Sorry if I created confusion. The factory reset I did on the togglelinc, not the keypadlinc. Both the togglelinc and the keypadlinc had x10 addresses. What fixed it was removal of the x10 address from the keypadlinc. I did this manually without doing a reset. Actually, the togglelinc still has the x10 address and everything is working ok. I can still issue an all lights off from the x10 powerhouse mini controller and shut off the ceiling light (via the togglelinc) and the keypadlinc ignores this command as it does not respond to x10 commands now. I don't recall adding the x10 address to the keypadlinc, but I must have at some point. Thanks again everyone for your help on this annoyance. I was living with it, but my wife was really annoyed. She wanted ( and rightfully so) to be able to just push the button and the door to work. Explaining to her " if the light is off and you want to open the door, than push the button twice" wasn't impressing her!

 

 

Sent from my iPad using Tapatalk

[oberkc]

The factory reset I did on the togglelinc, not the keypadlinc.

 

Yes, I misunderstood.  Thanks for clearing that up.