Print

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

[lee911]

- Using a CM15A with AHP version 3.271
- various WS12A's that all work via Macros, Timers and PalmPad Remotes

The problem is with the TWO WS13A's (for CFL's). One is installed in a detached garage (approx 50 feet ffrom house) and the other is in the basement. When installed they both worked manually at the switch AND with the PalmPad. But I wanted them setup with timers and macros, which wouldn't work. I then investigated line noise and found the culprit (Monster surge bar and tv)- I removed the surge bar and put a noise filter on the tv. Now we're getting somewhere!! I set up a test macro (B4 trigger= turns on B2, 2 second delay, turn on B3, 5 minute delay, turn off B2, 2 second delay turn off B3). They power on and five minutes later ONLY B2 (basement) turns off, while the garage on B3 doesn't turn off. Same goes with a timer, the B3 switch at the garage does not turn off. I have "repeat" set with "store in interface".

What could be causing this??

[dave w]

Try substituting an incandescent bulb in B3 fixture.

[Dan Lawrence]

I suspect it's 3.271.   All 3.271 is 3.236 (Known Buggy version) with support for the CM19A added, so you get a buggy version that causes timers and macros to not work properly.    Check the Forums for how to downgrade to 3.228, the last good version of AHP.

[lee911]

- Dan I will try 3.228, thanks.

- Dave I put an Incadescent in B3 and the Macros did NOT turn off B3 after 5 minutes. However, the daily timer I have set for B3 did turn off as scheduled. Something it didn't do before. What's the difference with the bulbs? I did install the WS13A's specifically for the CFL's.

[Brian H]

Some brand CFLs can make power line noise or their input may have a capacitor in it for noise. When the WS13A is On the bulb could be killing the X10 signal enough for it not to go Off.
You may want to try a different brand CFL.
They also make small X10 filters that can be used between the switch and the CFL load.

[dave w]

- Dan I will try 3.228, thanks.

- Dave I put an Incadescent in B3 and the Macros did NOT turn off B3 after 5 minutes. However, the daily timer I have set for B3 did turn off as scheduled. Something it didn't do before. What's the difference with the bulbs? I did install the WS13A's specifically for the CFL's.

Brian already explained what I was thinking...a noisy CFL. I would try changing CFL brands as a start.

FWIW I use GE CFLs and although noisy, they are not an issue for X10 signal. Sams Club has them faily cheap.

[Noam]

I suspect it's 3.271.   All 3.271 is 3.236 (Known Buggy version) with support for the CM19A added, so you get a buggy version that causes timers and macros to not work properly.    Check the Forums for how to downgrade to 3.228, the last good version of AHP.

Does anyone here know why Dan always goes to the version first? That isn't always the correct answer. In fact, I haven't seen very many cases lately where it WAS the correct answer. Most of the problems I've seen lately have been signal propagation or noise issues, for which changing the software would not be the proper fix.

Try substituting an incandescent bulb in B3 fixture.

I will put in another vote for "it might be a noisy CFL bulb).
If you've read some of my other posts lately, you'd know that a bad CFL (my neighbor's) can put out enough noise to mess up an X10 setup across the street (mine).

As suggested by others, try a different brand, and see if that helps. You might also want to try manually  (either from the software or from a PalmPad) triggering the lights in the sequence they would be done with the time (B2-On, B3-On, B2-Off, B3-Off), and see if that works. If not, then I would suspect the bulb in B3 first.
If you reverse the order (B3-On, B2-On, B3-Off, B2-Off), does it work? EVERY time?
If you see the opposite problem (B3 goes off, but not B2), then it might be both bulbs that are noisy.

I would try replacing both CFLs with incandescent bulbs, for testing. If everything works with the CFLs out of the picture, then it is likely that one or both of them is/are the source(s) of the problem.

Good luck.

[HA Dave]

Does anyone here know why Dan always goes to the version first? That isn't always the correct answer. In fact, I haven't seen very many cases lately where it WAS the correct answer. problem (B3 goes off, but not B2), then it might be both bulbs that are noisy.

A HELPFUL from me!

[Knightrider]

I think Dan's frustrated that in his testing of the newer versions,  they didn't work as well as the old ones.  Don't know why he's had such poor luck, but there might be some .xml issues that don't port well into the newer versions on the timer data.

For the record, it's 3.236 on all three machines here with the 3.239 drivers, and all has worked OK since day one of that version.

[Dan Lawrence]

Where do the 3.239 drivers come from?

[Knightrider]

Where do the 3.239 drivers come from?

good question!

Tuicemen sent me the link and I think it was on the FTP page.  I'll dig for it a bit.

[systemdm]

Knightrider, let me get this one.

X10 USB Wireless Remote Drivers:    http://www.x10.com/support/support_soft1.htm

[dave w]

Knightrider, let me get this one.

X10 USB Wireless Remote Drivers:    http://www.x10.com/support/support_soft1.htm

Hark! Do we hear a voice from X10?

[Noam]

For the record, it's 3.236 on all three machines here with the 3.239 drivers, and all has worked OK since day one of that version.

I would like to add that I also haven't had any software-related issues that I know of, and I was using 3.236 from the time it came out until I upgraded to 3.271. I currently have it running on Windows 7 Pro 64-bit, with the 3.239 drivers (unless 3.271 updated them). I have been using the SmartMacros plugin since it was first released to the beta testers.

While I have seen a FEW other people report that they were able to fix issues by by reverting back to an older version, that is certainly not the majority. There is no real way to tell if those problems were really caused by the new version, or by a possibly corrupted file, or by some other software incompatibility on their PCs. To automatically blame EVERY issue on software is silly, and it is distracting to those of us who are actually trying to help the user fix the problem.

[systemdm]

Hark! Do we hear a voice from X10?

Not yet...Just a member trying to help.