Print

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

[Burdy]

There are two separate problems in this
scenario:

I created a smart macro with the
conditional 'The time is between Dusk and
11:15pm'.  I tried triggering it at 4:30pm.
It executed, and it should not have (dusk
according to the hardware config table for
my location is 5:12pm). I've reported
problems with the logic being broken in
the "Time is Between" conditionals which use
dusk and dawn before; it looks like they are
still not working correctly.

The second problem is that the condition
block shows dusk time (greyed out) as
8:12pm.  This is wrong for my location.

Regardless of the incorrect dusk time that
was set in the condition block, the logic
still isn't working correctly.

[X10 Pro]

We'll take a look.

[Burdy]

Logic problems aside, I just noticed that my
Win98SE machine *is* putting the correct
dusk and dawn times into the 'Time is
between...' macro condition block, however
my XP machine is not -- its dusk/dawn times
are 3 hours off.  The dusk time should be
5:12pm; the macro condition block shows
8:12pm if dusk is set in the conditonal on
the XP SP2 machine.

The discrepancy between the dusk/dawn times
in the conditon blocks remains even if the
same identical timer source file is loaded
into each machine.

Both machines are using AHP 3.178, both
windows local time settings are EST GMT-
5:00; and both use the same location city in
the hardware interface configuration.

[rob]

>> I've reported  problems with the logic
being broken in  the "Time is Between"
conditionals which use  dusk and dawn
before;

Burdy -- As have I... Twice.

[X10 Pro]

We found a couple different problems in
looking at this stuff today, including the
display of the Dusk/Dawn time, and in the
"between" logic. They'll be fixed in the next
update.