Print

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

[jpwilk]

Just got AHP and CM15 interface. Installed software and connected the CM15.
Just learning how to use AHP so I maybe doing something wrong.
I get odd results with "store in interface".
I set up an appliance module and want to time it on and off.
With "store in interface" unchecked the timer works OK from AHP at the exact time I have it set to.
If I check "store in interface" and change the "on" time but don't download to interface, the timer never works from AHP. No events are recorded.
If I check "store in interface", change the time and "Download timers and macros" from the Tools menu the the timer works but with anything from a 20s-60s delay.
The AHP version is 3.236.
What am I missing here?

[Dan Lawrence]

It's 3.236.  It's a BUGGY relase and should be avoided.  Go to http://software.x10.com/pub/applications/activehome/ and get ahp_updt_204.exe.  Install that over what you have now.  When 3.204 is installed, try uploading what you created and make sure it loads properly.

Once you have everything uploaded to the CM15A, use the upgrade link in AHP to upgrade to 3.228, the last good version of AHP.  BTW, 3.228 is not in the X10 Software Depository.   Apparently X10 sales does not know 2.236 is a buggy release.      

[MANOWAR©]

I bought smart macros the other day and they emailed me the plug-ins but they are version .236. How do I get the old versions. I've emailed them twice and they send me to the same download link.

[Dan Lawrence]

Go to http://software.x10.com/pub/applications/activehome/ and get ahp_updt_204.exe. Install that over what you have now.  It should not affect any plug-ins.

Once you have 3.204, installed you can use the the upgrade link in AHP to upgrade to 2.228, the last GOOD version of AHP.

[jpwilk]

It's 3.236.  It's a BUGGY relase and should be avoided.  Go to http://software.x10.com/pub/applications/activehome/ and get ahp_updt_204.exe.  Install that over what you have now.  When 3.204 is installed, try uploading what you created and make sure it loads properly.

Once you have everything uploaded to the CM15A, use the upgrade link in AHP to upgrade to 3.228, the last good version of AHP.  BTW, 3.228 is not in the X10 Software Depository.   Apparently X10 sales does not know 2.236 is a buggy release.      

Thanks for that download link. I had used the "online chat" at X10 to inquire where I could get the "downgrade" and they were telling me it wasn't possible.
Anyhow, I followed your directions so I now have 3.228.
Unfortunately, nothing changed. Still have the same things happening. It looks like that the time to execute the timer with changes downloaded to the interface is a little faster (within 30s) but otherwise it's still the same.
I tested using 3 modules in various outlets throughout the house all set to the same codes (tested different codes but all modules the same) with one module in the socket next to the interface.

One thing I learned though - make sure that the actual module matches what you tell AHP it is. I realized that I had an actual appliance module plugged in but told AHP that it was a lamp module. I could turn the module on/off through AHP and using wireless remotes but couldn't turn it on through a timer even though AHP showed it had turned on.

[Dan Lawrence]

It's 3.236.  It's a BUGGY relase and should be avoided.  Go to http://software.x10.com/pub/applications/activehome/ and get ahp_updt_204.exe.  Install that over what you have now.  When 3.204 is installed, try uploading what you created and make sure it loads properly.

Once you have everything uploaded to the CM15A, use the upgrade link in AHP to upgrade to 3.228, the last good version of AHP.  BTW, 3.228 is not in the X10 Software Depository.   Apparently X10 sales does not know 2.236 is a buggy release.      

Thanks for that download link. I had used the "online chat" at X10 to inquire where I could get the "downgrade" and they were telling me it wasn't possible.
Anyhow, I followed your directions so I now have 3.228.
Unfortunately, nothing changed. Still have the same things happening. It looks like that the time to execute the timer with changes downloaded to the interface is a little faster (within 30s) but otherwise it's still the same.
I tested using 3 modules in various outlets throughout the house all set to the same codes (tested different codes but all modules the same) with one module in the socket next to the interface.

One thing I learned though - make sure that the actual module matches what you tell AHP it is. I realized that I had an actual appliance module plugged in but told AHP that it was a lamp module. I could turn the module on/off through AHP and using wireless remotes but couldn't turn it on through a timer even though AHP showed it had turned on.

Yep.  Modules have to be created exactly in AHP, Lamp Modules and Appliance Modules are different in operation, Lamp Modules can be dimmed, Appliance Modules  cannot be dimmed and Socket Rockets can't be dimmed either.  Both, BTW are great for CFLs.  For example, my Breakfast Room (where we eat, cooking is done in the Kitchen) has a swag light. When I changed the bulb for a CFL, I also had to redefine what module F-1 was in AHP.

[mquintas]

Just got AHP and CM15 interface. Installed software and connected the CM15.
Just learning how to use AHP so I maybe doing something wrong.
I get odd results with "store in interface".
I set up an appliance module and want to time it on and off.
With "store in interface" unchecked the timer works OK from AHP at the exact time I have it set to.
If I check "store in interface" and change the "on" time but don't download to interface, the timer never works from AHP. No events are recorded.
If I check "store in interface", change the time and "Download timers and macros" from the Tools menu the the timer works but with anything from a 20s-60s delay.
The AHP version is 3.236.
What am I missing here?

Same timer delay issue here,
If I check "store in interface", Download timers and macros to CM15 interface, the timer works but with anything from a 20s-60s delay.
With "store in interface" unchecked running from PC, all timers works OK at the exact time I have it set to.
My AHP version: 3.228
Any suggestions?
mquintas

[Dan Lawrence]

Do us a favor and post the contents of one of the timers so we can see what you are trying to do.  If you don't upload to the CM15A, the timers will not run, turning modules on and off through AHP defeats the whole reason for having X10 - automatic turning on and off of lights/appliances.

[mquintas]

Do us a favor and post the contents of one of the timers so we can see what you are trying to do.  If you don't upload to the CM15A, the timers will not run, turning modules on and off through AHP defeats the whole reason for having X10 - automatic turning on and off of lights/appliances.

Thank you for your response,
As an example I created this timer:

Timer for Appliance1 (AM486)
Turn ON TIME=14:48  OFF TIME=14:53
I have check "Store in Interface" and "Repeat" options then i have upload the timer to CM15A interface.
Results:
Real Time ON of the appliance=14:48:55 (55 seconds of delay)
Real Time OFF of the appliance=14:54:54 (114 seconds of delay)

I have attached 2 pictures, one of the AHP timer designer and other of the Macro Monitor.
It is noted that the interface CM15A makes 2 attempts to turn ON and 3 to turn OFF the appliance, but with several seconds of delay compared with the scheduled time of the timer.

mquintas

[Dan Lawrence]

Thanks.

One thing to remember:  AHP and the CM15A do not work on the exact minute. If you have a timer that turns On at 7:35AM and Off at 8:15AM daily (We don't use times in 24 hour settings in the US, we use AM for morning and PM for after Noon times.)  That timer will run at some point of the 60 seconds at the time.   Since both the US and Canada use the standard hours, minutes and seconds, that's how the CM15A operates. 

[hawk1]

correct me if i'm wrong but can't you switch to a 24 hour time clock in ahp?  US Military uses 24 hour time.

[Dan Lawrence]

True enough.  However, the civilian population is raised on AM & PM, not 24 hour time, so are the majority of digital clocks.  Military time is 24 hours, but midnight is 0000, in the civilian time it's 2400.   

[mquintas]

thanks for your response,
in the example, CM15A delayed 114 seconds to turn OFF the appliance, it did at 2:54PM and the timer was set to 2:53PM
also It is noted that the interface CM15A makes 2 attempts to turn ON and 3 attemps to turn OFF the appliance, but with more than 60 seconds delay compared with the adjusted schedule.
I tested with diferent modules in various outlets of the house and with one module in the socket next to the interface. Same problem...
Could be due an electrical noise or interference?

mquintas

[Dan Lawrence]

thanks for your response,
in the example, CM15A delayed 114 seconds to turn OFF the appliance, it did at 2:54PM and the timer was set to 2:53PM
also It is noted that the interface CM15A makes 2 attempts to turn ON and 3 attemps to turn OFF the appliance, but with more than 60 seconds delay compared with the adjusted schedule.
I tested with diferent modules in various outlets of the house and with one module in the socket next to the interface. Same problem...
Could be due an electrical noise or interference?

mquintas

Could be.  Check the Forums for noise and noise.     I don't have those problems.  It could also be a corrupt .ahx file.  Suggest you try creating a new ahx file with just one module and a single timer and see what it does.

[Brian H]

The X10 modules are not two way, so the CM15A has no way of knowing the module responded. Maybe it just tries a few times for better chances of success.