Print

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

[roger1818]

I thought it would be good to make a list
of known software bugs in AHP 3.175 and get
X10 to comment on the status of each of
them.  Lets leave the thorough description
of the bugs to other threads and only
provide a summary here:

Bug #1:  Module stops responding when
disconnected from the computer for an
extended period.
Status Last Reported:  Actively under
investigation but exact cause unknown

Bug #2:  Software won’t start for some
users of XP SP2 (works fine for me though).
Status Last Reported:  Will be fixed in
next release

Bug #3:  Dim command in macros (sometimes?)
causes ghost (all units on?) command (see
Macros Forum).
Status Last Reported: None

Bug #4: A macro containing the RF command
for All_Lights_On or All_Units_Off
transmits only the simple On or Off RF
command for unit 1.
Status Last Reported: None

Can anyone thing of any other software bugs?

Could someone from X10 please give us an
update on the status of these bugs
(especially Nos. 3 & 4)?  Thanks

[andyd]

Nice idea but I think it may be counter
productive.  We have been giving X10
feedback on problems for months.  I'd like
to see what THEY have assimilated and what
they are doing about it.

Also I don't think that us users can
determine if many problems are caused by AHP
software, or CM15a firmware, or CM15a
hardware.

Andy

[roger1818]

AndyD.

Correct me if I am wrong, but I was under
the impression that the CM15a F/W is
updated (if necessary) when the AHP S/W is
updated.  If this is the case, from the
user's perspective it doesn't really matter
if it is a S/W or F/W issue.

I agree that what seems like a H/W issue
could actually be a S/W issue and vice
versa (heck, sometimes H/W bugs can be
fixed in S/W or F/W, but that is a
different story), but you can usually guess
if it is a H/W or S/W issue (RF range and
clock drifting are likely H/W and the Ghost
commands are likely either S/W or F/W).

In a perfect world X10 would publicly
confess their all of their sins (oops, I
mean bugs) and would repent by publishing
their release notes listing all of the
features added and bugs fixed by each
release.  Although this is common in
engineering circles, the general public
often isn't as forgiving (you can guarantee
someone with no life will dig through the
release notes and complain that v1.01 had a
certain bug that he would never have
otherwise known about).  Personally I would
like to see what benefits I will get and
make an intelligent decision if I should
risk upgrading.

Given the choice I would rather remind them
of the bugs that are important to me and
ask them for a status update than wait
quietly for pigs to sprout wings. ;-)

[X10 Pro]

Roger H: Can you send the AHX file you use to
see Bug 3 to ahpsupport@x10.com. Bug 4 should
be pretty easy to work into an update soon.
Bug 2 is has been difficult to pin down, but
I think we may have it fixed in the next
update. Bug 1 is of course the big one (and
it's really several different things
happening), and the one we're still working
on. The status on that one is the same: we're
working on it intently, but don't have
anything yet.

[Noam]

X10 -
Have you guys actually been able to
produce "Bug #1" in your labs yet? It would
be nice to know what "working on it" really
meant. Have you been able to reproduce the
problem, and are looking for the cause? Have
you found the cause and are trying to
figureou out how to fix it? Have you figured
out how to fix it, but just want to be sure
that it is is REALLY fixed before releasing
the fix? Some sort of status update might
make those with the problem feel like there
is progress being made.

[X10 Pro]

Noam: "Bug #1" is really several different
things that users have experienced. We have
been able to reproduce the various different
failures here and, depending on which failure
it is, are either looking for the cause, or
working on a solution.

[david s]

Advanced Marco facility does not work.
Unable to use Tools / Preferences to enable
Advanced Macros.

[bryana_fl]

I have the same problem with the preferences
menu.

X10... Any ideas?

[donald mcmow]

The option to use ADVANCED MACROS might not
be available any longer. You should have a
button on the lower part of your screen
that says "USE CONDITIONS" - Press it and
you will have your smart macro
functionality. Things change between the
website and the software and they don't get
updated.

[X10 Pro]

That the Smart Macros preference is missing
is a bug. This will be fixed in the next release.

[Charles Sullivan]

These are probably not very critical in the
greater scheme of things, but you can add the
following:

Bug #5: AHP sends power line commands to the
TM751 transceiver (which the transceiver
isn't designed to receive) and the status
light on the icon falsely indicates the On/
Off status of the relay.  AHP should be
sending RF commands automatically.

Bug #6: Dawn and Dusk downloaded timers are
one day off when the actual transmission
times are compared with the Daily table in
ahpeeprom_w.txt.  E.g., the Dawn transmission
today occurred at the time shown in the table
for yesterday.  (Dawn and Dusk times don't
change all that rapidly at this time of year,
so it's usually necessary to monitor the
transmissions for a few days before the
pattern becomes evident.)

Bug #7:
The Dawn/Dusk table in Hardware Configuration
continues to show overlapping date ranges.

Bug #8:
The code in ahpeeprom_w.txt indicates a 365
day year during leap years (like 2004).

The above were observed with AHP 3.175
running under Win XP Pro SP1.  Downloaded
timers scheduled to execute only on one
specific day of the week work correctly, so
the CM15A clock/calendar appears to be set
properly.

[X10 Pro]

Charles: Thanks for the list.  We had a
couple of these, but didn't get them into
this release. I'll make sure they are in the
next one.

Roger H: Bug #4 is fixed now, I believe.

[steve l.]

I'm randomly (once or twice a day)
seeing, "Transmit P16 ON" in my activity
log.  I don't even have a module in the
software on that housecode.

Also when running a macro triggered off of
M13 ON, the activity log reports that it is
also running the corresponding M13 OFF
triggered macro, but it isn't actually
running, because the light it does turn off
when it REALLY runs doesn't turn off when
the "ghost" Macro data is displayed
immediately after the M13 ON macro data.

[Charles Sullivan]

Add one more to my list, this one a little
more serious:
Bug #9: If under Win XP Pro SP1 the Windows
"Date and Time Properties" > Timezone box for
"Automatically adjust clock for daylight
saving changes" is unchecked, then downloaded
Dawn and Dusk timers are executed exactly 1
hour later than the (approximately correct)
times tabulated in ahpeeprom_w.txt.  This
even though Daylight time is not in effect
this time of year.

[Charles Sullivan]

Bug #10: AHP ignores the seconds when setting
the CM11A clock, so the clock may differ from
system time by up to 59 seconds.  Downloaded
timed macros will therefore execute late by
that time discrepancy.  As far as I can tell,
this bug was introduced in AHP 3.175, and it
persists in 3.177.

This is just one more PITA stumbling block
which interferes with proper testing of AHP.