Erradic Behavior with 3.170

[bebop]

Updated to 3.170 the other day and although
I have never had any unusual behavior with
previous updates I am now experiencing very
erradic behavior with macros, lack of
entries in the activity monitor, timers not
firing at the correct time, conditional
macros that rely on a range of time not
being processed correctly and the list goes
on! Something is wrong with 3.170.

[X10 Pro]

bebop: can you send me the AHP data file
you're using currently?

[bebop]

Info sent.

[jdelapen]

I am running AHP 3.172 and I am
experiencing the same thing:  macros and
timers are not executing as programmed.  I
deleted my macros and write them again with
no positive results.  AHP behavior is
totally erratic.  Hope to get a fix on this
ASAP.  My house is going crazy!!!

[jdelapen]

Well, analyzing a little bit more the data
to complement my last post, I think the
problem resides in the fact that AHP 3.172
is adding the accumulated times instead of
the delay times in macros.  This is the
cause for erratic behavior.  The difference
can be found on the ahpeeprom_w.txt file,
which shows the information that has been
loaded to the interface eeprom.  If this is
the case, I believe it should be fairly
easy to come up with a fix.

[X10 Pro]

We're looking at these problems today, and
hopefully we'll have a release to address
them soon.