Print

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

[RNick]

I cannot get an SR227 to turn on lights as selected but the same unit will turn the light off at the selected time.  I can plug an LM465 into the uncontrolled outlet of the SR227 and the light works just fine.  I have tried 3 different SR227S including one brand new, with the same results, including various locations in my house.  Wherever I use an LM465, the light works fine, but with the SM227, the light will not go on.  I have even tried plugging my CM15A into the uncontrolled outlet of the SR with the same results.  Any thoughts?

[Brian H]

What revision of AHP are you using?
The module is defined as a SR227 in AHP?

[RNick]

I have version 3.228 of AHP running.

[RNick]

And yes, the module is identified as SR227 in my AHP version.

[Noam]

It might be a noise issue.
However, 3.228 is quite an old version.
I recommend upgrading to the latest version 3.306, and trying again.
You can download it here: http://software.x10.com/pub/applications/activehomepro/sw31a_setup_ahp.exe

Keep in mind, however, that lamp modules (and wall switches) that are older than about 2008 may not have "SoftStart" functionality. These will need to be defined within AHP using the "Old Lamps - no SoftStart" category, instead of the "Lamps" category in order to function properly.
The quick test is to turn the lamp on, either using AHP or a remote. If it slowly "ramps up" to full brightness, then it is SoftStart. If it comes on to full brightness instantly, then it is NOT SoftStart.

[dave w]

I cannot get an SR227 to turn on lights as selected but the same unit will turn the light off at the selected time.  I can plug an LM465 into the uncontrolled outlet of the SR227 and the light works just fine.  I have tried 3 different SR227S including one brand new, with the same results, including various locations in my house.  Wherever I use an LM465, the light works fine, but with the SM227, the light will not go on.  I have even tried plugging my CM15A into the uncontrolled outlet of the SR with the same results.  Any thoughts?

When the LM465 worked ON and OFF in the unswitched outlet of the SR277 were you following the same times as the SR277 was supposed to turn ON?
Will the SR277 control ON and OFF manually from AHP? Palm Pad remote?
With CM15A in the unswitched outlet. SR277, did you try to control it manually with AHP and Palm Pad? Did it act the same (i.e. OFF functions but ON does not).
Did the SR277 ever work, or is this a new install?
Do you have a TM751 transceiver you can test with?

If I understand you; the SR277 will not work if a controller such as CM15A is plugged into unswitched outlet. It will turn OFF but will not turn ON, two other (new?) SR277 act exactly the same way when wired in same box. If this statement is not correct, you correct the errors, because what you are describing does not fall into any of the typical X10 problem scenarios that I am familiar with.

[RNick]

Thanks for all your help.  The problem was solved by downloading the lastest version of AHP and using the new SR227 that I bought.  This is a great forum for those of us who just want to "plug and play'

[RNick]

To NOAM, thanks for the tip on "Old Lamps - No Soft Start".  That was my basic problem and I now have fixed all modules that I have in the house.  I wonder how many others have no idea that this simple fix is there.

[Dan Lawrence]

Simple is correct.   I converted 15 .ahx files in less than a hour!!

[Noam]

It would have been nice if starting with version 3.302 (when they introduced SoftStart support) they had included a wizard that would come up when you start the program. It could explain the difference between SoftStart and non-SoftStart behavior, and ask you which of your (currently defined) modules were SoftStart, and which weren't.
Having a testing application would be nice too, for those who aren't sure about some of their modules. It could set the lights to flash, one at a time. You would set it to flash, and go watch it. If it dimmed up and down, it was SoftStart. If it came on immediately, it was not. You would then tell the program which it did, and the program would adjust the module definition accordingly.
Wishful thinking, I guess...