Print

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

[bielser]

I just upgraded a few of my wall switches with the newer soft start versions.  I still have a few of the older switches in my system.  I am running ActiveHome Pro software (Ver 3.311) on my ActiveHome Pro CM15A interface.  All of my switches are X10Pro.  After creating new modules with corresponding timers in ActiveHome Pro and downloading them into the CM15A, the new switches will turn the lights on and off but they won't dim to the proper level. 

All of the old switches will still dim from the associated timers but it looks like the new soft start switches will not.  No two switches have the same address.  All lights have incandescent bulbs.  New modules were created in ActiveHome Pro choosing the correct X10Pro switch.  What am I missing in setting up the new switches? 

Thanks in advance. 

[Noam]

AHP version 3.311 is pretty old (4/4/2011). The latest version is 3.318 (10/3/2011).
However, 3.311 should still support SoftStart modules properly.
The "check for updates" function doesn't work, you need to download the update from here:
http://www.x10.com/support/support_soft1.htm

Once you install the newer version, check the definitions of all your modules. re-define your older (non soft start) modules using the "old lamps - no soft start" category.

Check your Activity Monitor. When it is addressing the new (SoftStart) modules, is it using an Extended Code, or is it using a dim% level?

Unless the new ones are actually X10 *PRO* modules, use the ones from the "lamps" category for those.
You might want to try that anyway, even if they ARE the PRO versions.

[bielser]

I updated AHP, redefined all of my modules and now I will see how everything runs tonight. 

I will report my findings later tonight or in the morning. 

Thank you for your quick reply. 

[Noam]

I updated AHP, redefined all of my modules and now I will see how everything runs tonight. 

I will report my findings later tonight or in the morning. 

Thank you for your quick reply. 

Can you manually (from the AHP interface) control all the lights, and dim them properly now? If not, then I doubt the timers will work any better.

[bielser]

Yes, I can turn the lights on and off as well as dim them manually with the AHP interface. 

[bielser]

I just started to play with my lights again.  I don't know if I can explain what I have done but here goes ...

I turned on one of my lights manually with the AHP interface.  It was very dim - probably at the minimum setting.  I ramped the slider switch icon on my AHP screen down and up to get it to full power.  I then turned the light off with the AHP interface.  I then turned the light back on with the AHP interface to make sure it came on to full power.  It came on to full power so I moved the slider switch icon down to 50%.  The light dimmed.  I then turned the light off with the interface.  I then turned the light back on and it came on to the last power setting.  Note that my AHP control screen did not reflect any dim level.  Whenever I turn on a light from the control screen it shows 100%. 

Do I just need to set each light to my preferred dim level with the AHP control screen and then make my timers turn on without any dim command?  It appears the lights will turn on to their last dim setting. 

Let me know if I am way off on this. 

Thanks.   

[Noam]

This is a bug, that I reported to the developers back on 4.14.2011, in version 3.310.
It still hasn't been fixed.
You can see the entire user-reported AHP bug list here:
http://forums.x10.com/index.php?topic=22373.0
This bug is listed as:

* Turning on a SoftStart module that was dimmed before being turned off results in an Extended Dim command to the previous dim state, instead of the full 100%. In AHP, the slider momentarily goes to the previous dim state, but then goes to 100%.

The workaround would be for the timers and/or macros to be set to turn on the light at the specific brightness level you want (100%, 75%, etc), instead of just turning "on." Since this problem appears to only affect SoftStart modules, you should be able to get them to come on at the desired brightness level that way. Check the Activity Monitor to see what is actually happening when the commands are sent to the lights.

Keep in mind, this is a user-reported, and user-maintained list. The developers may be working on other bugs that are not on this list, but they are aware of this list. A few of us "Admin" users are in direct contact with the developers from time to time (bypassing the HelpDesk), so we try to make sure they are aware of problems that are reported here.

If you find bugs in AHP, check the bug list first. If the bug you found isn't listed there, then ask about it. It may be a new (or previously un-reported) bug, or it may be on the list, just not described exactly the way you are seeing it. It also might not be a bug at all, but rather be in there by design (we call those "features").

[bielser]

I guess I am confused what to do here. 

Should I keep my timers set the way they are now where I have certain soft start switches come on at 50%?  And if so, should I go through and turn all my lights on to full power once and then turn them off from that state?  I don't know if the "re-set" activity is necessary.  The last time they were turned off was from a dimmed setting that was attained via the AHP interface and not the actual switch.

Sorry for my confusion and the need for more clarification.   

It looks like I will regret upgrading to soft start switches. 

Again, thank you. 

[dave w]

Should I keep my timers set the way they are now where I have certain soft start switches come on at 50%?  And if so, should I go through and turn all my lights on to full power once and then turn them off from that state?  
 

That is the way I fixed my "soft start" problems. After we go to bed I have system "reset" all softstart lights.

[Noam]

I don't have any WS467's, so I can't test what happens if you turned the light off from 50%, and then try to turn it on at the switch. (I was doing my testing with the lamp module) I have a feeling it will come on at 50% (resume dim). The fix it to hold the button for 5 seconds to force the light to ramp all the way up, or all the way down (if it goes down, hold it for 5 seconds again to ramp it all the way back up). However, I think that turning the switch off manually (at the switch) from a dimmed state results in it coming back on at that dimmed state when turned back on at the switch. I can see why it would have been nice if the user could turn this feature on and off.

The bug appears to be in AHP (and the SDK, if you are using it). The software is remembering the previous dim state of the module, and sending it a command to turn back on at that state (instead of at 100% - which is what an "on" should do).

All of your timers and macros should use "absolute" brightness levels, so the lights come on at exactly the level you want. As for controlling the lights manually from the interface itself, drag the slider up to 100% to turn the light on at 100%. Using the "toggle" will bring the light on at the last known dim level.

I don't know how much of this is a function of the "Resume dim" built into the switch, and how much of it is the software. However, I know that there is a software issue involved (since I saw the SDK send an Extended Code to the specific brightness level, instead of sending one to full brightness.
Strangely enough, if you tell the SDK to send an "ON," it still sends an Extended Code to the SoftStart modules, and it does so at the last know brightness level (other than "off"). This is another bug in the list.

[bielser]

I just turned one of the lights on with the actual switch.  It looks like it went to the last dim level I set it to with the AHP interface. 

This almost makes me think I should just send an "on" command in my timer settings rather than having a 50% dim command sent to the switch.  I will know more in a couple of hours when the timer settings are executed. 

I did look at the "preferences" tab in the AHP software.  Under the Macro Options, I checked the box for "Issue 'On' in place of of 'Bright 100%'".  This was not checked before.  My fear now is that I am changing too many things at once to determine what is the real issue. 

I might just start looking for old switches without the soft start feature.   

[Dan Lawrence]

I just turned one of the lights on with the actual switch.  It looks like it went to the last dim level I set it to with the AHP interface. 

This almost makes me think I should just send an "on" command in my timer settings rather than having a 50% dim command sent to the switch.  I will know more in a couple of hours when the timer settings are executed. 

I did look at the "preferences" tab in the AHP software.  Under the Macro Options, I checked the box for "Issue 'On' in place of of 'Bright 100%'".  This was not checked before.  My fear now is that I am changing too many things at once to determine what is the real issue. 

I might just start looking for old switches without the soft start feature.   

Older switches are very hard to find.  The dealers that sell X10 products all seem to have only soft-start modules.  You might try searching for "X10 Non Soft-Start modules"  Good luck. 

[Brian H]

X10 wall switches made after 2007 have Soft Start and Preset Dim.
I think you have run into the preset dim feature. Though many will dispute it as a feature. 

http://kbase.x10.com/wiki/Newer_Wall_Switches_and_Preset_Dim

[Noam]

The "Issue ON in place of Bright 100%" probably won't help here.
It all depends on what you are trying to do.
If you WANT the light to come on at 100%, then just put that in the macro.
If you want it to come on at 50%, then put THAT in the macro.

If you want to reset the dim level when you shut off the light, briefly put it at 100% before you turn it off.
That might work.

[bielser]

The lights seemed to work tonight.  I am not sure if it is because I 'pre-set" the dim level earlier in the day or what. 

My AHP CM15A transmitted each macro timer "extended code bright/dim 50%" signals to my three new soft start switches.  All three lights came on to a dimmed level. 

I noticed that my old switches (non soft start) first get a Bright 100% signal and then get a 40% dim signal.  The soft start switches get one, extended code bright/dim signal. 

Hopefully this will all still work when I disconnect my USB cable and run the interface like I have for the past few years.  It will be nice to put this all behind me again. 

Thank you to everyone for the help and opinions.