Constantly echoing command

[kimnach]

I have recently begun to have issues with my AHP (v3.318) and think it may be a failing CM15A.  However, before I purchase a new one I would like to ask if anyone had isolated the following as being caused by the CM15A

When I issue a command (whether from a controller or wifi), the Activity Monitor shows that the command is constantly asserted.  I do not have any repeaters and unplugged the only other controller (Radio Shack Mini Timer).  I have deleted all but one of the rooms and there are no macros.  The code is down to one room with four simple X10 modules (four Pro inline modules for ceiling fixtures).  I have unplugged and removed the batteries from the CM15A, then purged all delayed macro events (tools menu), cleared the interface, and uploaded the simple room to the interface.  Yet, when I issue a command (e.g., F1 ON), the light turns on and the Activity Monitor continues to show the command being asserted every second.  Then asserting another command (e.g., F2 ON) results in it not actually turning the device ON but it (F2 ON) echoing constantly in the Activity Monitor.

BTW, "Find other computers" shows only F1, F2, F3, and F4, and the CM15A is ok according to Windows' device manager.

Failed CM15A? 

Thanks in advance.
greg

[Tuicemen]

Have you tried a different house code?
I've experiance a cm15a continously sending x10 commands but they were related to a plc repeater.
You don't  state how your issuing commands.  Does the activity monitor show only send commands repeated or are there recieved command mixed in.

[kimnach]

Thanks, Tuicemen.

I typically would send commands either via wall switches, the Radio Shack Mini Timer, Melloware's X10 Commander, or macros/timers in AHP/CM15.  But, in order to debug, I reduced the AHP to a single room without timers/macros and unplugged the mini timer.  The echoing persists.  I don't have any RF remotes on which a key may be stuck.  I long ago unplugged all transceivers (e.g., TM751 and PSX01) and have not reinstalled motions sensors since getting new siding on our house last year.

Unfortunately, I cannot change the house code on the four ceiling light fixtures.  I really blundered when I installed them.  When I redid my older son's room's floor about 20yrs ago, it was a good time to add can lights to the family room which is below his.  So I opened up the floor, ran electrical, and installed the inline modules.  The can light boxes are not readily accessible from the ceiling.  (Rushed to do the job without forthought--big mistake.)

There is another oddity which is probably due to the echoing: for a long time there have been time slots during the day during which commands are completely ignored.  (This really annoys the wife when I would tell her that you can't turn on the family lights, using the Mini Timer buttons, between 5:30pm and 7pm.)  I have noted that during these times slots hundreds of the same command are repeated every second according to the Activity Monitor (AM).  As an example, last night I cleared the AM and just checked it. During the course of the night "F1 ON" sent was echoed 6000+ times.   Interestingly, the light never turned on--or at least no F1 OFF command in the AM.  No reception of the ON command in the AM.

Our neighbors do not use X10 or any other automation so a need for a blocking filter is not "necessary."  (I couldn't install the PZZ01 20yrs ago because the 4/0 Aluminum wire will not fit the opening.)

Since the AHP/CM15 is really not doing anything now (other than allowing me to use X10 Commander on my phone), I am going to unplug it and see if the "time slot" issue is eliminated.

[brobin]

I used to have a mini-controller that would do the same thing. It would send a constant string of F1 commands that would overwhelm everything else. Tru unplugging ALL other controllers to see what happens.

[gadgetboy]

YES. My first palmpad controller (bought new in 1984) had the little metal disks floating under the keys. A fall off of a desk dislodged a disk and shorted a contact. This caused a continuious "off" signal to one module. Very aggrivating and caused me to stop using x10 for a while. Eventually I found the problem and upgraded the controller. No problems since but now I use RPi and android for controls.

[Tuicemen]

I have a box full of x10 gear. Occasionally I'd get  x10 rf on or off signals ( can't remember if it was always same unit number) the culprit was a old remote someone had tossed into the bin without removing the batteries.

[kimnach]

Well, I'm going to order a new mini controller to see whether that fixes at least some of the issues.  (The Radio Shack mini timer is probably 35+ yrs old!)  However, the time slots throughout the day during which commands are absolutely ignored are another matter.

Thanks all.

[Tuicemen]

If there is a time slot which commands don't  work have a look at what is on during this slot. It is possible a signal sucker is the culprit in this case. I once had a incandescent light that once turned on no other signals would work on that circuit.

[Brian H]

Also.
Do you have any X10 signal coupling between the two incoming power lines?
If so do you know what it is?
We have seen reports of some repeaters starting to get into a constantly sending the code it recently received.

Its possible you do have a signal sucker or power line noise maker and have a weak X10 signal on the effected devices.
Possible also some device in the home has deteriorated and is now effecting the X10 operation.