X10 Community Forum

🔌General Home Automation => Automating Your House => Troubleshooting Automation Problems => Topic started by: craig-o on December 01, 2006, 01:57:44 PM

Title: House Code A & M
Post by: craig-o on December 01, 2006, 01:57:44 PM
I'm relatively new to X-10 and have been reading quite a bit here and on other forums.  I ran across this posting http://forums.accessx10.com/showthread.php?s=&threadid=253 and was struck by number 10 - "Don't use house code A or M".  The post didn't provide any explanation so I thought I'd ask why it would say to stay away from code A and M? 

Thanks!
Title: Re: House Code A & M
Post by: Puck on December 01, 2006, 02:18:01 PM
House Code A:  When batteries start to die on motion sensors, the motion sensor will reset itself to House Code A, Unit Code 1. So actually, A1 & A2 should be avoided for modules that could accidentally be turned on / off because of this. As well, because this is the default setting for all new stuff, another module may still have the same address (maybe even a neighbour).

House Code M: Most unreliable because the 4 bits are all Zeros. Also, if the House Code selector switch were to fail (in the open state) the default house code becomes M. So for this same reason, Unit Code 13 can experience the same problem.

So if you have a module on M13... well your just asking for trouble.   ;) ;D :D
(Especially if you have an AHP Macro triggering it on[/b][/color] A1.  :P)
Title: Re: House Code A & M
Post by: Brian H on December 01, 2006, 04:21:29 PM
OH Yes. M13. The code I use when I have modules apart for testing and no wheels are connected. ::)
Title: Re: House Code A & M
Post by: Dan Lawrence on December 01, 2006, 10:55:10 PM
Quote from: craig-o on December 01, 2006, 01:57:44 PM
I'm relatively new to X-10 and have been reading quite a bit here and on other forums.  I ran across this posting http://forums.accessx10.com/showthread.php?s=&threadid=253 and was struck by number 10 - "Don't use house code A or M".  The post didn't provide any explanation so I thought I'd ask why it would say to stay away from code A and M? 

Thanks!

I don't use housecode M, but I have Housecode A in use since the earliest X10 days. The Living Room, Bathroom and Bedroom lights are all on A withhout a single problem ever.

Whoever posted on accessx10.com about never using housecode A for anything does not know what he's talking about, at least about A.
Title: Re: House Code A & M
Post by: TakeTheActive on December 02, 2006, 03:12:34 AM
Quote from: Puck on December 01, 2006, 02:18:01 PM

House Code A:  When batteries start to die on motion sensors, the motion sensor will reset itself to House Code A, Unit Code 1. So actually, A1 & A2 should be avoided for modules that could accidentally be turned on / off because of this. As well, because this is the default setting for all new stuff, another module may still have the same address (maybe even a neighbour).

House Code M: Most unreliable because the 4 bits are all Zeros. Also, if the House Code selector switch were to fail (in the open state) the default house code becomes M. So for this same reason, Unit Code 13 can experience the same problem.

So if you have a module on M13... well your just asking for trouble.   ;) ;D :D(Especially if you have an AHP Macro triggering it on[/b][/color] A1.  :P)

Excellent, complete, nicely-formatted ;) answer, IMHO...
Title: Re: House Code A & M
Post by: TakeTheActive on December 02, 2006, 03:15:14 AM
Quote from: Brian H on December 01, 2006, 04:21:29 PM

OH Yes. M13. The code I use when I have modules apart for testing and no wheels are connected. ::)

Is there another ECHO ECHO ECHO ECHO ECHO ECHO ECHO ...in here? ;)
Title: Re: House Code A & M
Post by: TakeTheActive on December 02, 2006, 03:27:41 AM
Quote from: Dan Lawrence on December 01, 2006, 10:55:10 PM

I don't use housecode M, but I have Housecode A in use since the earliest X10 days. The Living Room, Bathroom and Bedroom lights are all on A withhout a single problem ever.
Whoever posted on accessx10.com about never using housecode A for anything does not know what he's talking about, at least about A.


How can you possibly make this statement *AFTER* reading Puck's EXCELLENT reply? ??? :-[
Title: Re: House Code A & M
Post by: craig-o on December 02, 2006, 09:47:17 AM
Thanks to all who have responded.  I am a little confused by one thing though.

Quote
House Code A:  When batteries start to die on motion sensors, the motion sensor will reset itself to House Code A, Unit Code 1. So actually, A1 & A2 should be avoided for modules that could accidentally be turned on / off because of this. As well, because this is the default setting for all new stuff, another module may still have the same address (maybe even a neighbour).

I get almost everything here except why A2 is added.  I understand the reseting to default settings when batteries fail issue, but unless I'm just not reading something right here, I can't see how A2 comes into the mix.

Thanks again all!!
Title: Re: House Code A & M
Post by: KDR on December 02, 2006, 10:22:16 AM
Motion sensors respond 2 ways. Motion and dusk/dawn. A default rest puts it at A1 for motion. The dusk/dawn is always the motion code plus 1 so default motion is A1 and dusk/dawn would be A2. (its automatic)

Hope that helps
Title: Re: House Code A & M
Post by: Brian H on December 02, 2006, 11:54:37 AM
I also use A with no problems. I also like not having to reprogram remotes from the dead battery A as that is the default.
That said if I had motion sensors A would most likely not be my code of choice. Every set up is different so one perons problem is not another's.
Title: Re: House Code A & M
Post by: vhoang on December 02, 2006, 03:33:02 PM
Quote from: Brian H on December 02, 2006, 11:54:37 AM
I also use A with no problems. I also like not having to reprogram remotes from the dead battery A as that is the default.
That said if I had motion sensors A would most likely not be my code of choice. Every set up is different so one perons problem is not another's.

I use A1 for the same reason.  I don't respond to A1-AOff.  I let a timer countdown turn it off.  Non critical stuff considering the possible side effects mentioned above.