Print

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

[bebop]

After updating to 3.177 I have multiple
problems now where everything was quite
stable with 3.175. Getting a custom city
setting that never existed before with
totally messed up long/lat settings. Had to
uncheck US/Canada to find ANY cities other
than custom. My macros don't seem to run any
more although I can trigger things manually.
I'm getting incorrect codes sent to modules
like "A1 Front Porch" "A Off". Can't expect
modules to turn off with number included in
the off command. This command was supposed
to be sent at 10:30PM once but now it's
being sent every minute since there is
apparently no acknowledgement from the
module. I have several commands just being
sent repeatly with no result because the
module numbers are not being sent. Far as I
can tell this is a disaster here and I'll
probably need to go back to 3.175! For
taking as long as this update did to come
out and for having been tested in 3.176 this
shouldn't be happening!

[bebop]

Forgot to enter my email addy for replies!

[Charles Sullivan]

I don't know about your other problems, but
X10 commands are send in two (or more)
chunks: First the housecode-unit address (or
addresses) of the modules to be controlled,
e.g., "A1 Front Porch", then the housecode-
function, e.g., "A Off".  So what I think
you're describing is perfectly normal.

Unless you have 2-way modules like the LM14A
there is no acknowledgement from the module -
the standard X10 lamp and appliance modules
are receive-only.

[bebop]

Thanks Charles for the clarification. Then
at least that part is functioning normally.
Still had those problems with the "custom"
city info which I never entered! I was able
to get back my St. Paul, MN settings by
playing around with the hardware
configuration settings for a while.
Macros...well that's gonna take some sorting
out although part of my problems may have
been caused by weak batteries in one of my
motion sensors. I use the dusk/dawn sensor
to trigger a few macros and that takes some
sorting when things go wrong. After a couple
hours of re-programming things are finally
getting back to some order, although I still
have no idea why my logitude/latitude
settings flipped out.

[roger1818]

From what I can tell, everyone who upgrades
to 3.177 has to reset the
longitude/latitude settings (a bug in the
upgrade I guess).  To add to the confusion,
the "Custom" location that it changes to is
at the end of the list.  To see the other
locations you have to scroll up (you don't
actually need to uncheck US/Canada).

[X10 Pro]

We're fixing the geographic location problem
today.