X10 Community Forum
🖥️ActiveHome Pro => ActiveHome Pro General => Software Problems & Bugs => Topic started by: Burdy on December 08, 2004, 12:38:00 PM
-
(Disregard if these comments are no longer
useful, I'm using 3.173 that was released
before being suspended yesterday):
Macro delay operations seems to work much
better now, as do consecutive flag
operations. I'm noticing however that
whenever I 'Download timers and Macros' to
the interface using my current timer file,
that flag 1 always appears to be set, and
flag 2 (if previously on) gets cleared
immediately. As far as I can determine no
macros have triggered which could have set
the flags (I purged 'delayed' events before
downloading, activity monitor has no
entries, and I check the status immediately
after downloading to the interface).
Also, this behavior doesn't happen with all
timer files (the samples file doesn't do it).
Are there characteristics of certain timer
or macro configurations that could cause the
flags 1 & 2 to be initialzed this way after
a download? I know about the 15 & 16
behavior.
-
We'll take a look at this today. Setting
flags is not part of the download process,
but they changes could be something we're
doing in the interface configuration that
happens afterward.
-
As far as I can tell with the macros I've
written to experiment with this, it looks
like bit 1 is getting set, and bits 2-14 are
all cleared when the timer download is
performed.
-
I always wondered how flag 1 was always
getting set on me. I was using it to set a
condition for day shift have since started
to use 3
I just tried downloading and checked the
flag status after. It is repeatable so much
for relying on flag status as a condition!
hopefully this bug gets fixed soon!
-
I checked flag status immediately after a
download with 3.173 and none of the flags
were set.
I've got close to 25 Macros
(including "Else" macros), 6 timers and
daily dawn/dusk resolution (78% memory
left). I'm not using any daytime/nighttime
conditions, only one dusk (+offset) based
timer and a few macros have time ranges as
conditions.
I've seen flag bits 15/16 affected by
daytime/nighttime conditions in a test I
ran as reported by Burdy but flag bit 1
never seems to get set on a download. One
of my motion controlled lights should not
turn on if flag bit 1 gets set and I
haven't had an issue with it yet.
I do tend to "Purge Delayed Macro Events"
and "Clear Interface Memory before
downloads. I wonder what the difference in
our setups could be that's causing our
different observed behavior.
Burdy, Thanks for ths issue reports. Your
post on flag bits 15/16 was a great catch!
Mike
-
Mike, it has to be something in the timer
config. I have at least one config
(samples.ahx) that doesn't set flag 1 or
clear 2-14 as well. The timer file that
shows this behavior has 23 smart and not-
smart macros, 88 timers, date ranges up the
kazoo, dusk & dawn, but still has 71% memory
available. However, things seem to work
(within known limitations) if I make sure
the flags are initialzed properly after a
download.