Print

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

[Picsman]

We have this fixed in our code here,
but we're still working on getting the update
released.

  I'm running AHP v3.201, using XPPro SP2 and having the same problem identified above.  Prior to v3.201 I did not have this problem so I'm thinking something went wrong with this latest update.

FYI:  I have cleared the interface, removed the USB cable, unplugged it, removed the batteries, put it all back together again, reset the device configuration, downloaded it all again--twice--and I get the same result.

Even plugged the interface into another 110v outlet--far from the computer or any TV set with no USB cable--and the only thing that does not work is any event that should be triggered by "dusk" or "dawn."

It also seems that not all "events" sent to or from the interface are reported in the Activity Monitor.

So, H-E-L-P, please!  Thanks. 

[X10 Pro]

Can you check your city and other settings in Hardwre Configuration? Does everything look correct there?

[Picsman]

Yes, everything looks correct:

Interface time is correct
Resolution is 2 days (plenty of available memory left)
Date range, dawn, dusk times look reasoable
Monitored house code is "F"
Transceived  code is "auto" and "F" is checked

FWIW:
I'm in "City One."
On the grounds some table might be messed up, I set the location to nearby "City Two."
No change: I get the same result.

Also, all commands from AHP are executed without a problem.
(I have a "phase coupler/repeater" installed at the distribution panel.)

Wow!  Instant response!!  Love it!!!

Thanks!!

[X10 Pro]

Can you take a look for a file called ahpeeprom_w.txt in \Documents and Settings\All Users\Active Home Professional\ on your computer and send it to me by e-mail?