X10 Community Forum
🖥️ActiveHome Pro => ActiveHome Pro General => Topic started by: x10orbust on December 05, 2007, 05:03:29 PM
-
I have the latest version of AHP (3.204) with a new CM15A. This is a recent upgrade from the serial version with AH (due to a computer upgrade that no longer has a serial port).
I have programmed all my modules (on various house codes: A, D, F) for a variety of turn-on, turn-off scenarios on different days. There are about 12 total modules. Each turn-off command work fine. However, none of the turn-on commands work at all. Commands are downloaded and work off the CM15A interface without the need for a computer.
Any ideas on what to do. X10 tech support is not very useful here.
-
Did you set up your timers with both on and off times? Also, if you kept your old .x10 files from Active Home, AHP will import them, including all timers and any macros.
-
Yes, I set up all timers with on and off times. And, I can manually turn on and off from the AHP program.
-
If you can control them by AHP, then there's no noise problem. The only thing I can suggest is to clear the CM15A, close AHP, go into Windows Explorer and delete all .ahx files that are not added the install program, they are the ones you created. Then rebuild all of them. I suspect that somewhere they got corrupted.
-
I believe that I figured out the source of the problem for the turn on commands never working from the interface, but always working from the AHP program.
From the AHP program, a turn on command of a lamp module (for example a Leviton 6831) will always issue a turn on command. The lamp modules receive this as a turn on and actually turn on.
However, when the macros are stored in the interface, a turn on command is always issued as a 'Bright 100%' command for lamp modules.
The 'Issue on in place of Bright 100%' from the AHP program preferences seems to only reference the AHP program, not the interface. Therefore, it seems to me that the problem is in the interface.
The short-term workaround for this is to set all lamp modules (dimmable or not, although mine are dimmable) as appliance modules. These appliance modules have an ON/OFF structure, without brightness logic. Although this works, there is no ability to control brightness levels (without creating a duplicate dummy module as an applicance that is first turned on before sending a dim command via the lamp module -- a very cumbersome approach).
The long-term approach seems to be for X10 to update the bios on the interface to correctly reflect the bright 100% command as a turn on. Does this make sense to anyone?
I find it hard to believe that I am the first one to experience this problem. Anyone else out there worked on this?
-
No, you are not the only experiencing works OFF, but not on. My problem, however, is a little more selective.
Using AHP ver 3.204 and CMA15 with Tools | Preferences | ActiveHome Pro | Multiple Modules can use same address enabled, I have three lamp modules all set to N3. One module controls the Christmas tree, one the Fireplace mantel lights, and one the Nativity set. They are all on the same circuit in my house. As with you, all the modules espond both On and OFF using the icon in the Room. Originally, I had a timer tied directly to the module that would turn them on at 16:00 and of at 23:45. The timer would fire, but only the Cristmas tree would come ON. The other two would not light. All would turn OFF just fine. Last night, I redid the lighting scheme using macros and a timer that triggers a phantom module addressed as M4. Same result, all N# modules turn OFF as scheduled, but only the Christmas tee turns ON.
-
there is an options to issue an "on" instead a "bright 100%". You click on tools in AHP then Preferences followed by the "Macro Options" and last you choose the option to "Issue "ON" in place of "Bright 100%"
hope this will help
YC
-
I have mine set to On in place of bright also, no problems.
See if that setup helps.
-
Great illustration EL34. A helpful has been added. :)
-
Note that the "Issue 'On' in place of 'Bright 100%'" option only applies to macros, not downloaded timers. Simple On/Off timers have to be reprogrammed and downloaded as a pair of timed macros.