Print

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

[fje]

Hi,

I'm totally new (since a couple of months) to the X10 world, but enthusiastic with the Home automation.

First thing to say is I live in Spain and maybe some of the specifications, support, etc. are different in Europe to other sites in the world.

My first experience with AHP was that even I was able to directly fully control shutter switches, if I tried to control them using timer, it was not possible to open (fully or dimming) them. If I asked to close (OFF) in a timely manner them, it worked, if I tried to open (fully or partially) them, it didn't.

And the same experience when I tried to do it thru a macro. The "macro'ed" shutter itself worked, doing it using timer, similar problem. I was using AHP version 3.226 that I got with the CM15Pro RF (european version of TM751/CM15A ?).

I sent an email to BMB Europe, they very soon answered me telling there was a bug in the AHP software that was sending an incorrect dimming code to the shutter switch, suggested a workaround and commited to tell me when a new update of AHP with the correction would be available.

Less than 3 weeks later on (just yesterday), they have sent to me a new version (3.232) with the correction included, I tested it and it works perfectly. I don't know if any other bug has been corrected or new functions added.

I should say that my experience is GREAT SUPPORT !    

Another issue I still have is a strange delay when using timers. If you set a timer to on/off any appliance, the order is executed with a 24 secs delay after the planned time. If I set a timer to execute a macro, the macro is executed with a delay of 57 secs. after the planned time of execution. There is no explanation for it yet.

Rgds.

[steven r]

...Another issue I still have is a strange delay when using timers. If you set a timer to on/off any appliance, the order is executed with a 24 secs delay after the planned time. If I set a timer to execute a macro, the macro is executed with a delay of 57 secs. after the planned time of execution. There is no explanation for it yet....

AHP does not sync to the second! Seconds are ignored when downloading to AHP. Minutes are synced after file is downloaded to the CM15A.
e.g. It the time is 1:00:XX, regardless of the value of seconds the time is synced as 1:00:00. Try starting your download at say 42 on 45 seconds and see how things change.

[fje]

Steven, thanks. This could explain the delays, but does it imply that if I ask for executing the orders "from the PC" and not "from the interface" there wouldn't be delays?

I'll try to do some aditional tests, but it could take some time, because I'll be aout of home some time from now.....

Rgds.

[dash]

Version 3.233 now available in Europe. Anyone know what is changed?

[Dan Lawrence]

Not really, 99% of the posters here reside in the United States or Canada.

[fje]

Dash and Dan:

Not all of the subscriber are in the US and/or Canada... Some of us are in the other part of the "big lake" and are ready to share information with you....

I'm attaching the change log of the last versions that I got from somewhere. A small gift from the 1% of this side.... Hope it will be usefull.

May I ask now a question from my side? Which are the modules that accept the "BRIGHT/DIM ABSOLUTE command" ? Is LW12/LM12 one of them? Could it be a way to switch directly 100% ON (OFF) a light without passing thru the 0-to-100 dimming process? Which would be the way to do it using AHP?

Regards.

***********************************
v233:

-   Timer: Modules using extended codes now honor the "Repeat" flag's
functionality.

-   Macro: Modules using the BRIGHT/DIM ABSOLUTE command can now be
repeated.



v232:

- PLC or radio messages are sent accordingly


v231:
- Module: ULME, fixed "On" command problem.
- Module: LD11, the first "On" command will set the level to 100%.
- Module: LW11, the first "On" command will set the level to 100%.
- Module: LW12, the first "On" command will set the level to 100%.
- Module: SW10, was misconfigured as a module that remembers it's previous
state.

v230:
- Module: Editing a module from one type to another now works correctly.
- Module: SW10, sends extended codes instead of bright/dim commands.
- Module: SW10, "On" timer fix.
- Module: AM12 now responds to RF commands.
- Macro: Transmission of multiple "Send Address" & "All Lights On/Off" now
allowed.
- Macro: First command in a macro always executes without pre delay.
- Macro: When extended codes are received the GUI now responds to the input.
- Macro: Modules with memory settings now use extended codes instead of "On"
commands.
- Macro: RF signals sending either ON or OFF commands now honor the macro
trigger state.
- Macro: Conditional macros are forced to be run from the interface by
disabling the "Run from PC" option".
- Macro: When a macro is triggered by the timer, there was no start/end
animation.
- Activity Monitor: When extended codes are received the data byte is now
displayed correctly.
- Activity Monitor: Certain extended code modules were reporting the wrong
house & unit code; fixed.
- GUI: International characters now allowed.
- GUI: Fixed tool tip bug in timer editor.
- GUI: EU daylight savings time fix.
- Internals: The scoreboard remembers the previous state of known modules
who remember their state.

v229:
- Module: Fixed problem with LD11, it now remembers its previous state.
- Module: LD11 NEC (no extended code) module added.
- Module: TM751 was sending PLC's instead of RFC's when a module that shares
the same address uses PLC's.
- GUI: TM751 would not allow entering a new address if the text was
highlighted.
- GUI: Fixed BMB hyperlink tool tip text.
- GUI: Fixed problem with cities not being reset to default when "Show US &
Canada Only" checkbox is selected.
- GUI: SAX1 module removed from BMB build.
- GUI: DAX10 module removed from BMB build.
- Internals: The scoreboard remembers the previous state of the LD11.
***************************************

[-Bill- (of wgjohns.com)]

fje,

Thank you very much for the update! 

It's nice to know that X10 still has programmers working on something!

Hopefully they will eventually release an update with some fixes for those of us on this side of the pond.   

Thanks again!