X10 Community Forum
🖥️ActiveHome Pro => ActiveHome Pro General => Software Problems & Bugs => Topic started by: wchever on February 07, 2017, 06:51:08 PM
-
OK, I had some controllers, TM751's and Appliance modules lying around so I thought I'd set up some in my home.
I had a fan in my bedroom set to A3. Sometime during the day, that appliance module would turn on. No macros were ever set up for that House/Unit code. I just used a Palmpad to turn it on/off. I got tired of trying to figure out what time of day this was happening and took the easy way out by just changing that module to A9.
Now my appliance module at B3. connected to Rocketfish wireless speakers, is exhibiting the same behavior. I'll take a look at AHP or X10 Commander and that module will be ON.
Before I change that module and then see my outdoor speaker on C3 come on, has anyone ever seen this. Recycle bin is empty, there are no timers or macros associated with B3.
-
Got any X10 neighbors?
-
No X10 neighbors. It happened again. When I got to the computer today, B3 was on. B:( OK, I'm going to change that module and see what happens.
-
Although most of the links are no longer active, this may help a bit...
https://www.laser.com/dhouston/noise.html (https://www.laser.com/dhouston/noise.html)
This link still works and may be the most pertinent...
https://groups.google.com/forum/#!msg/comp.home.automation/HJOVTh8Y_Ps/6vX-Nood1GIJ (https://groups.google.com/forum/#!msg/comp.home.automation/HJOVTh8Y_Ps/6vX-Nood1GIJ)
-
Thanks for the additional information. However, while the first issue with A3 involved a 467 wall switch activating a lamp, B3 was simply an appliance module that turned on the speakers. And the Activity Log just shows the ON command being issued at random times. I'll keep playing with it and report back.
-
Other switches and modules were prone to the same phenomenon. X10's designs were extremely sloppy with unused MCU pins floating and without bypass capacitors.
However, since you are seeing ON commands in the log, you need to look for what might be issuing or triggering those commands. What switches, modules, motion detectors etc. are in use?
-
Since all your issues seem to be on unit code 3, look to see if you have a old motion sensor laying around.
When the batteries start to go they float all over the place before finally reverting to A1 and the batteries die. :o
I had one go this way and it took forever to figure it out.
I finally remembered setting it on top of an old dresser without removing the batteries before taking it out of service.