Print

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

[Kn0wn1]

Hi everyone,

I have 2 x10 devices in use, 1 Lamp module (LM465 set to A1) and 1 Dimming Wall Switch module (WS467).  I've been controlling them with Slimline Switch (SS13A set to A2), and it has has worked perfectly!

I've recently added the CM15A USB interface and installed the Activehome Professional Software, which is working great.  Unfortunately, since this change the Slimline Switch is no longer reacts, other than the red light when i push a button.  I use this mostly at night, and i've awoken in the morning to either device being on, when i know it was off when i went to bed.

I assume some software macro is causing this, though that doesnt really make sense since the pc the CM15A is connected to is shutdown at night.

Edit:  I realized too late that i put this in the home security section by mistake, admins please feel free to move for me.

[Noam]

Alright, here we go:
From your post, it sounds like you can use the CM15A to control both modules, but you can no longer use the SS13A to control them. That rules out most powerline noise issues. It also rules out SoftStart/Non-SoftStart issues. That leads us to an RF signal issue, most likely.
In order to control the lights from the SS13A, you need a transceiver to pick up the wireless RF signal, and pass it to the Powerline (as a PLC signal), so it can get to the modules.

1. Before you put in the CM15A, how were you getting the signals from the SS13A to the LM465 and WS467? You were probably using either a TM751 or an RR501 (or an equivalent with a different model number). Did you remove that when you plugged in the CM15A? Is the CM15A plugged into the same outlet where the TM751 or RR501 had been?

2. Have you done any programming of timers and/or macros in the CM15A?

3. What HouseCode / UnitCode do you have the WS467 set to? (you indicated the LM465 was on A1).

There are a few things I can see that can cause this:

A. You removed the TM751 or RR501 that was picking up the RF signals and sending them to the Powerline. The CM15A has an RF transceiver in it, but you need to make sure it is set to transceive the correct HouseCodes. If you didn't set the CM15A to transceive those signals, they'll just get lost in "thin air".

B. You DID set the CM15A to transceive those signals, but the CM15A's limited RF reception range is shorter than that of the TM571 or RR501, so it is too far away from the SS13A to hear the RF signal. There are a number of fixes for that, and we can help you with that if it is the case.

As for the second part - the lights being on when they shouldn't be, here are my thoughts:
C. You created some timers and/or macros that address either device, and those are being triggered at night. The CM15A doesn't require the PC to be on, for at least some functions. You can download timers and (some) macros into it, and they will run even if the PC is turned off or disconnected from the CM15A.
If you leave the PC turned on and connected to the CM15A, AHP will record a log of the activity it sees (and sends) on the powerline and RF, and you can view that in the Activity Monitor. That might give you some more clues as to what is happening.

D. You created some macros or timers, and then deleted them. You didn't, however, clear the trash in AHP, and/or download the updated program to the CM15A. Deleted macros and timers have been known to continue to run from the trash.

E. You might have a neighbor who also has X10, and you are both using the same HouseCode. Again, this isn't all that likely, since the problem only started when you added the CM15A. However, the Activity Log should give you some clues about this, too.

F. There is other powerline noise, which the modules are picking up on, and turn on by themselves. I've had this problem before, and I ended up replacing the modules. However, since this wasn't happening before you installed the CM15A, I would consider this theory a real long shot.

The more information you can provide us, the easier it will be for us to work through this, and help you.

[Kn0wn1]

Thank you for your quick, and in-depth reply.  Your summary of my issue is correct.  I've noticed some errors in my explanation that i'll correct below:

WS467 is set to A1
LM465 is set to A2

SS13A is not set to anything of course though by default:
-top on/off controls A1
-middle on/off controls A2
-bottom on/off is controls (not in use)

1.  I do not have a TM751, RR501, or equivilant.  My understanding of how the 3 modules works is not perfect, but assuming from your post, SS13A is RF, and LM465/WS467 are PLC only?  If yes, i'm assuming the CM15A has been acting as a receiver, since it HAS been plugged into an outlet, though the USB was not plugged into a pc.

2.  I have not done any programming, i simply installed the software, played with some on/off's in the application, and tested the SS13A.  When noticing the problem i did move the built-in test macro's to a different "room" in the application to ensure they weren't affecting anything.

3.  see above

Additional info:  CM15A has not been physically moved, other than the USB is now plugged in.

With your scenarios i assume my problem is a software problem, caused by the installation of Activehome Professional Software (SW31A).  It must of changed the CM15A to recieve the wrong house code, or has changed the normal on/off functions of my SS13A to some macro.  I'll do some further research and some trial and error and post back my results this weekend.  Thanks again.

[Noam]

You said in your original post:

I've recently added the CM15A USB interface and installed the Activehome Professional Software, which is working great.

Did you have the CM15A all along, but had never connected it to a PC and installed the software before?

1.  I do not have a TM751, RR501, or equivilant.  My understanding of how the 3 modules works is not perfect, but assuming from your post, SS13A is RF, and LM465/WS467 are PLC only?  If yes, i'm assuming the CM15A has been acting as a receiver, since it HAS been plugged into an outlet, though the USB was not plugged into a pc.

I'm surprised that it ever worked that way.

2.  I have not done any programming, i simply installed the software, played with some on/off's in the application, and tested the SS13A.  When noticing the problem i did move the built-in test macro's to a different "room" in the application to ensure they weren't affecting anything.

Moving the macros to a different room doesn't change anything. The "rooms" are just cosmetic, to make it easier to organize your setup.

Additional info:  CM15A has not been physically moved, other than the USB is now plugged in.

Okay, that's certainly interesting.

With your scenarios i assume my problem is a software problem, caused by the installation of Activehome Professional Software (SW31A).  It must of changed the CM15A to recieve the wrong house code, or has changed the normal on/off functions of my SS13A to some macro. 

Probably. You can try creating a brand new AHX file, and then clearing the interface and re-downloading a new file that has no timers and macros in it (for starters).
Your biggest clues will come from the Activity Monitor. You need to see what's going on.

I'll do some further research and some trial and error and post back my results this weekend.

Okay, keep up posted.

[Kn0wn1]

It's working!  The activity monitor helped me narrow it down.  The SS13A buttons were unresponsive at first but after playing around with it it seems to be working.  I noticed that my button 3 was executing a test macro.  I've deleted the macros completely to ensure it doesnt happen by mistake. 

Only time will tell if things go on by themselves now.  Thanks for help.