123
Senior Member
I've searched Cocoontech and haven't found this problem mentioned so I now have a deep sense of foreboding ... 
I bought several used X10 Keypadlincs from a fellow Cocooner and just got around to installing one of them. It appears to be deaf because it won't accept a primary-address in programming mode.
The patient is a 12073WW X10 Keypadlinc V3.1 (6-button, white LEDs, integrated dimmer, Boosterlinc).
I've reset the little devil several times (Reset = pull out the tab for 5 seconds, push it in for 5 seconds, load comes on) and it *should* default to address A1. I sent an A1 ON with a MaxiController but the Keypadlinc didn't respond. Uh-oh.
I attempted to program its primary address but the tab light just blinks continuously and then times out; it seems to ignore the incoming signal. Another sign of weirdness is that it turns the load OFF in programming mode. That's not right; the documentation claims the load turns ON in programming mode.
It is installed in a 3-way circuit with a Companion switch and everything works perfectly in manual mode. You can control the local load (ON/OFF/DIM) using the Keypadlinc's top and bottom switches and turn it ON/OFF with the Companion switch. The primary problem appears to be an inability to receive an incoming X10 signal ... and it turns the load off, instead of on, while in primary-address programming mode.
Is there a fix for this Keypadlinc or is it toast? Any and all troubleshooting guidance would be greatly appreciated.
PS
There's a signal coupler/repeater installed in the house.
The MaxiController successfully turns on/off other lights so the X10 signal is good.
There's only one other Keypadlinc in the house (same model) and it works well.

I bought several used X10 Keypadlincs from a fellow Cocooner and just got around to installing one of them. It appears to be deaf because it won't accept a primary-address in programming mode.
The patient is a 12073WW X10 Keypadlinc V3.1 (6-button, white LEDs, integrated dimmer, Boosterlinc).
I've reset the little devil several times (Reset = pull out the tab for 5 seconds, push it in for 5 seconds, load comes on) and it *should* default to address A1. I sent an A1 ON with a MaxiController but the Keypadlinc didn't respond. Uh-oh.
I attempted to program its primary address but the tab light just blinks continuously and then times out; it seems to ignore the incoming signal. Another sign of weirdness is that it turns the load OFF in programming mode. That's not right; the documentation claims the load turns ON in programming mode.
It is installed in a 3-way circuit with a Companion switch and everything works perfectly in manual mode. You can control the local load (ON/OFF/DIM) using the Keypadlinc's top and bottom switches and turn it ON/OFF with the Companion switch. The primary problem appears to be an inability to receive an incoming X10 signal ... and it turns the load off, instead of on, while in primary-address programming mode.
Is there a fix for this Keypadlinc or is it toast? Any and all troubleshooting guidance would be greatly appreciated.
PS
There's a signal coupler/repeater installed in the house.
The MaxiController successfully turns on/off other lights so the X10 signal is good.
There's only one other Keypadlinc in the house (same model) and it works well.