Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[michael g]

so. got my new LM14A, two-way lamp module. go X10 crazy sales.

Installed it in an outlet with a lamp connected to it. Set it to an unused code (the code of the older lamp module it replaced).

Here's the deal:
1. Find remote (i'm using the 5-in-1 platinum/silver remote)
2. Hit number of module. Hit "On."
3. Lamp turns on. Now, hit "On" again.
4. Lamp stays on. All other lights in house turn off.

Sending a command to turn the lm14a on when it's already on turns off all my other modules. Why?!

[Brian H]

I have a few of them on order from this weekend sale. When I get them; I will do some tests and see if I see anything. I do have signal monitors and should be able to see the powerline messages.
So maybe we can see something in a few days.

[roger1818]

Sending a command to turn the lm14a on when it's already on turns off all my other modules. Why?!

When the LM14A receives a command, it sends a command to report its status.  It is possible that this status report is somehow being corrupted to an "All Units Off" command.  Have you tried changing the address of the LM14A to see what happens?

[Brian H]

The software must be resetting the LM14A as on power up it will respond to status requests, but not send a status change on its own unless it is reprogrammed to do it. Or so the X10 technical paper said. Since mine where never shipped; due to an over sold web sale. I never got any to play with; just the AM14As shipped.

[Charles Sullivan]

Assuming  your transceiver is a CM15A, try running Tools > Clear interface memory in ActiveHome Pro to make sure there's not some stray code in the CM15A's
memory which is acting as a macro.