Print

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

[Burdy]

After installing 3.177 on my Win98SE
machine I had the problem with AHP not
starting as others have mentioned, but was
able to do a fresh install on an XP SP2
system.

I'm seeing what appears to be a bug in how
the dusk time is being applied to timers.
According to the hardware config. dusk/dawn
table, for my timezone on today's date
(using the 4 day granularity) dusk should
be at 17:07, which sounds about right.  But
when 'on at dusk' is selected in the timer
designer, it shows the Dusk 'on time' as
12:13 AM (greyed out and checked). Way too
early...

Coincidentally, this happens to be what the
hardware config dusk/dawn table entry shows
for the 1/29 date range for the very FIRST
entry in the 'world'
cities,  'Aachen/Merzbruck'.   It looks
like the chosen city dusk/dawn entry isn't
actually being applied to the timer design
window (unless you live in
Aachen/Merzbruck).

[X10 Pro]

This is definitely a problem. We're looking
at it now, and I expect an update to fix it
later today.

[brann jeter]

Same problem here. XP SP2. Location got
screwed up after the "upgrade."  Finally
managed to set the correct location (Screen
wasn't drawing. All the cities to chose from
were blank.)

Now, all my DUSK timers are setting
themselves to 11:27AM or some time that's
obviously NOT dusk in Dallas, TX.

Didn't have this problem in any of the
other "upgrades" that I had to troubleshoot.

What shall I do now?

Thanks,

Brann

[noshali]

Same issue with dusk and dawn setting.
Also, some modules are receiving the on
command but donot acknowledge the off
command and vice versa.
also, the dimmer slider is not working in
the software. when clicked on on it says
1005 but the sliders does not move like it
used to yesterday and before.