Print

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

[dave w]

Decline to state - Tom
Yes the X10 product has hardware problems,
the smarthome product does not...as long as
it is not connected to the software. But the
Smarthome product does not live up to the
Smarthome marketing claims. If one has a
problem in a macro, but can not troubleshoot
the problem because the software can't
follow the activity, that is a problem as
frustrating as X10's problems. Same with the
sequence comment. Sequences do not
issue "old fashion" DIM commands...but SMPs
% DIM command doesn't work either, so again
the software does not / can not perform as
Smarthome has claimed. If one uses SMP for
rudimentary timing functions, it works fine.
Sorta like AHP.

[Decline to state]

Dave-

I'm just pointing out that you have an
unusual installation.  Most people send a
few seconds of x10 commands at a time at
most.  What percentage of their customers do
you suppose send out 30 seconds of dims at a
stretch?  Who wants to wait that long to
control anything else?  The controller will
do it, you just can't spy on the controller
with the SMP software while that particular
macro is running w/o clicking on an OK.

I haven't played with the % Dim feature
using a generic X10.com lamp controller, but
I know % dim works great with my newer
devices that accept the modern extended
commands.

As bad as it is to find ANY bug, I think it
is important to put it in context.  HARDWARE
bugs are the worst, because no amount of
software will 'fix' them--the best you can
do, if anything at all, is add bulky
software patches.  Core feature SOFTWARE
bugs are bad, because they interfere with
basic, normal operations.  Obscure SOFTWARE
bugs are annoying, but hardly a deal-breaker.

With my AHP interface, I ran into all kinds
of problems in all three categories.  With
my SH interface, I found obscure bugs when
they were pointed out.  That hardly makes
the two equally bad.

Tom