X10 Community Forum
🖥️ActiveHome Pro => ActiveHome Pro General => Topic started by: Adkuz on January 13, 2022, 11:37:55 AM
-
I have a standard wall switch module that doesn't want to turn on at the CM15A programmed time. If I connect a PC to the CM15A and turn on the switch, the lamp works. If I us a RF remote to turn on the switch, it works. It's programmed to turn on at dusk, but it doesn't. I use the exact same code for 4 other wall switches and they all work at the right time. That particular module works fine for everything but the programmed time. It turns on and off from the CM15A via computer command and turns on and off via RF command to the CM15A. The signal is being sent twice for redundancy and it clearly shows the correct programmed time. Any thoughts??
-
I am attaching the code being used for reference.
-
I notice your timer is set to dim not turn on. If your module is not setup correctly in AHP some functions will fail.
What windows version is AHP installed in, and is it 64 bit?
-
Thanks for your reply Tuicemen, I am using Windows 10 version 21H1 and yes, it's 64 bit. So since the timer description box says turn on and then dim, are you saying that by showing the dimmer at 60%, it won't follow the instruction? Curious. I'm doing the same on other modules that work correctly. I changed the device number in case I had some random noise blocking the signal or perhaps the transmitter had a problem with that number and that didn't help. What confuses me is that the module works from the power line when I toggle the PC connection to the transmitter. It also works with RF remotes that ultimately send a line signal, so I know the module works. I also know the transmitter works, but this one unique device doesn't. Hmmm
-
So since the timer description box says turn on and then dim, are you saying that by showing the dimmer at 60%, it won't follow the instruction?
No, What I'm saying is the module has to be configured correctly in AHP.
If the module is not a softstart lamp it has to be set as older non softstart light not light. Some modules except extended commands for dimming and some do not. If AHP is configured to a module that excepts code that the module actual won't except it won't perform.
Also Windows updates have added additional security for software running in Program files X86 folder which affect newly added things in AHP. If the AHP folder is there move it to out of that folder and just under C:/
As well I noticed your timer is set to store on the interface have you tested without that checked or do you run the CM15 disconnected from the PC normally?
-
I always run the Cm15 disconnected from the PC. I've tried both softstart and non soft start and nether works. BTW.... all this used to work. One day it stopped and I haven't been able to get it back no matter what. I even changed modules. Why does the CM15 control it when I give it an RF command or via the PC but not by itself??
-
When you disconnect from the PC do you move it to another location?
Do you remove the USB from the CM15 or just the PC?
-
I remove it from the wall in an adjacent room and connect it to the original receptacle with an extension cord so that I can plug it into my PC. Seems worst case for signal in doing that, yet it works fine. I always unplug the USB from the CM15 before the PC after I've logged out of AHP.
-
Do you check the 'Repeat' box in all of your timers when you set them up (under 'Store in Interface)? DO you need to send multiple commands usually? Is there a new phone charger or something else on the same circuit as the offending module? Anything else that would be a signal sucker or blocker for that particular spot?
I do not and all of my timers work in AHP (all set for a Dusk -60 turn on) from the CM15a running stand alone. I have old and new modules and wall switches...
-
I have checked the repeat button on my circuits for many years. Not sure if I need to, but can't hurt. I know of nothing new on that circuit. I just replaced the switch with a new WS467 and it still doesn't work. Everything turns it on including RF commands to the to the CM15A, and PC commands to the CM15A, but it just won't turn on at the assigned time. I deleted the module and re-entered it. I changed the module number. I'm totally out of ideas.
-
Does it turn on at the set time if you leave the cm15 connected? It doesn't have to be a new thing on that circuit, things get noisy with age. Check to see what may be on at the time the timer is to fire that is on the same circuit.
-
Just a few thoughts-
Are you turning anything else on at the same time or earlier - like an LED light? They can throw noise even if they haven't before.
Will it turn on the switch if you set the time to something else i.e. 2PM when other lights are off?
Do other lights come on at dusk? If not, have you verified time zone and lat/long settings for sunset calculations?
-
All good suggestions. I will try them tomorrow. Really nothing else is on. I'll have to verify what all is on that breaker. I can try with the PC connected and I'll also try a different time. Stay tuned. And BTW, no LED's. Yes, other lights come on at dusk as scheduled. There are 5 others all on separate switches and they all work daily. The timer is right.
-
If the CM15A is on the same circuit as the computing equipment.
Computer power supplies are many times a noise maker or signal sucker.
-
Nope, the computer is typically not connected to the CM15A but it's not on the same circuit anyway. I understand the noise potential, but why does it work so perfectly when I send commands t the CM15A via RF or by connecting it to the computer?? Surely the noise is the same when the CM15A send the powerline command.
-
I don't believe AHP or the timer is the issue but a noise or signal sucker issue.
If the timer works from the PC then it is possible the timer isn't actually getting downloaded to the CM15 may be the USB cord has become faulty. Have you tried a different USB cable.
I once had a lamp (with a incandescent bulb) when it was turned on, only 1 other X10 device on that circuit would respond (on but not off). It took a bit of time to route that one out. ::) :' luckily having the house just rewired I knew the path the wire traveled. A module just before it worked but nothing after it.
I'd check for things that are on the same circuit as timer controlled light.
-
The more I think about this the more I think it's a signal issue. Can you move the CM15A to a different outlet today? Ideally it'd be an outlet on the same leg as the light that won't turn on and located near your electrical panel.
-
Well I guess the plot thickens. Yesterday, I connected the CM15A to the outlet it's usually plugged into with an extension cord as I've done before. I verified that the unit is plugged in the receptacle with neutral wire intact (in other words to be sure I wasn't inverting the device in the socket). This time the module that's been the problem did not turn on from the PC as before. I tried to unplug everything on that breaker to be sure there wasn't any interference and no change. I could however control another wall receptacle in the same room 100%. Always on and off as instructed by the PC. No dimming, but that's OK. So, I decided to make that lamp my scheduled device. I deleted the programming on the previous lamp (a wall switch) and programmed the lamp (a wall receptacle) with the commands to turn on at dusk. All other lamps programmed to turn on at dusk did, but that one did not! What the...?
-
This might be a long shot but try removing things on the circuit that serves the wall switch. That may entail unscrewing some bulbs but it's worth a try.