Print

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

[tom j]

Say why can't you combine a Dust/Dawn timer with Security?? I gave my parents my old Activehome and set it up with a few light switches and as anybody knows that's used the older I might also say supposedly less sophisticated version that you combine these two easily why then can't you do the same with the newer version. Got another grip why can't you perfectly sequence the clock on your computer with the interface the best you can do as I understand it is within 59 seconds. Say WHAT GIVES, this thing has been out for something like three years and there still problems.

Tcj

[Dan Lawrence]

You can.

Create a new timer with a dusk on time and the security option checked.  I have one lamp with a dusk timer and security option set and it works perfectly.

[Charles Sullivan]

Got another grip why can't you perfectly sequence the clock on your computer with the interface the best you can do as I understand it is within 59 seconds. Say WHAT GIVES, this thing has been out for something like three years and there still problems.

I suspect some sort of serious firmware bug in at least the early CM15A units led X-10 to zero out the seconds when setting the clock.   The original release or two of AHP did set the clock to the second, or at least pretended it did.  The reason for the change was never explained, but in response to complaints like yours the word came down from X10Pro that it would never be changed back.

A workaround is to click on "Tools" in the menu bar, then wait until the system clock in the status bar rolls over to the next whole minute. At that instant  click the "Hardware configuration" menu item.  (In the past at least the clock was set as soon as the "Hardware configuration" item was clicked and "Cancel" after that was sufficient.)

[tom j]

Got another grip why can't you perfectly sequence the clock on your computer with the interface the best you can do as I understand it is within 59 seconds. Say WHAT GIVES, this thing has been out for something like three years and there still problems.

I suspect some sort of serious firmware bug in at least the early CM15A units led X-10 to zero out the seconds when setting the clock.   The original release or two of AHP did set the clock to the second, or at least pretended it did.  The reason for the change was never explained, but in response to complaints like yours the word came down from X10Pro that it would never be changed back.

A workaround is to click on "Tools" in the menu bar, then wait until the system clock in the status bar rolls over to the next whole minute. At that instant  click the "Hardware configuration" menu item.  (In the past at least the clock was set as soon as the "Hardware configuration" item was clicked and "Cancel" after that was sufficient.)

Quote
"but in response to complaints like yours the word came down from X10Pro that it would never be changed back"

Say Thanks guys! Charles are you saying that just because of some complaints by their customers that they decided not to address the issue? And every time I try to combine the dust/dawn with security the security gets grayed out. Thanks for the work around!

Tcj

[Charles Sullivan]

"but in response to complaints like yours the word came down from X10Pro that it would never be changed back"

Charles are you saying that just because of some complaints by their customers that they decided not to address the issue? And every time I try to combine the dust/dawn with security the security gets grayed out. Thanks for the work around!

The change to setting the clock only to the whole minute appeared in one of the early upgrades of AHP.  When the question was raised  in the forum by a few nitpicking users like myself about it being changed back, X10Pro answered and said it wouldn't be.

I  can only speculate that AHP was changed because of some CM15A firmware bug which surfaced and that changing AHP back would result in a large number of users experiencing the bug, necessitating a major CM15A recall.  It was never clear what the bug might be -- the early releases of AHP had so many bugs that you couldn't tell which were software and which were  firmware.

[tom j]

Quote From Charles
It was never clear what the bug might be -- the early releases of AHP had so many bugs that you couldn't tell which were software and which were  firmware.

Say you got that right!! and I really don't think that is nitpicking I feel any reasonable person would expect at least the same functionality that was in the much less sophisticated Active Home. And what about combining the dust/dawn and security is this a bug to?? I guess they don't intend on addressing this issue either. Thanks!

Tcj

[Charles Sullivan]

Quote From Charles
It was never clear what the bug might be -- the early releases of AHP had so many bugs that you couldn't tell which were software and which were  firmware.

Say you got that right!! and I really don't think that is nitpicking I feel any reasonable person would expect at least the same functionality that was in the much less sophisticated Active Home. And what about combining the dust/dawn and security is this a bug to?? I guess they don't intend on addressing this issue either. Thanks!

Tcj

I suspect that dawn/dusk and security not working together is another firmware bug.  If so, I expect it will never be fixed since it is so visible.  (It's possible the firmware is already fixed, but X-10 won't update AHP to use the feature until all the warranties on the "unfixed" units have expired - and they've been offering 5-year warranties.)

[tom j]

Quote From Charles
It was never clear what the bug might be -- the early releases of AHP had so many bugs that you couldn't tell which were software and which were  firmware.

Say you got that right!! and I really don't think that is nitpicking I feel any reasonable person would expect at least the same functionality that was in the much less sophisticated Active Home. And what about combining the dust/dawn and security is this a bug to?? I guess they don't intend on addressing this issue either. Thanks!

Tcj


 

I suspect that dawn/dusk and security not working together is another firmware bug.  If so, I expect it will never be fixed since it is so visible.  (It's possible the firmware is already fixed, but X-10 won't update AHP to use the feature until all the warranties on the "unfixed" units have expired - and they've been offering 5-year warranties.)

:-

Tcj

[tom j]

Say Charles you know that really takes a lot of functionality away from the product I could really use the ability of combining the two. Isn't x10 concerned about the legitimate concerns of their customers, this is just no way to do business!

Tcj

[Dan Lawrence]

The problem seems to be you can't add the Security Option to an existiing timer, which should be an option.

To invoke the Security Option, you do that before creating the timers. Once that is done and you save the timer, the Security Option is greyed out. That's the bug in AHP.

That's made clear at all in the AHP help.

My one light on the that has the Security Option has a dusk timer that turns it on and dims it to 40%. A timer turns it off at 12:55 AM daily. The Security Option adds 30 minutes to the timer on a sliding schedule that has the light going on up to 30 minutes before dusk and off up to 30 minutes from 12:55 AM. The on and off times are different every day.