Print

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

[mmeinert]

So I'm done with the xxxEye Occ sensors. They drain batteries too quickly and don't reach from the 2nd floor to the basement where my http://www.bayweb.com/wp-content/uploads/BW-WT4-2DOC.pdfBayweb thermostat with X10 receiver lives. The thermostat programming is straight forward: Just tell it the house and unit codes of the occ sensor and tell it what to do. The xxxEye Occ sensors are straightforward albeit cumbersome to assign the house and unit codes.  Not so the MS10A. I have no idea how to find the house and unit codes and don't want to immerse myself too much into the many options of X10. I have looked around and need some help to figure out how I can a) identify the factory preset house and unit codes of the MS10A occ sensors and b) How to change the codes without buying too much X10 stuff I'll never use again. If I'm presented with spending 10 hours trial and error learning curve or spending 50 buck to WYSIWYG I'd go with the 50 bucks. I don't mind coding via dipswitches and little buttons if it works, though.

[Brian H]

The MS10A is a Security Sensor and does not use a standard X10 House Code and Unit Code.
It sends an X10 Security Code message and is registered with a security console.
AHP with On Alert can process the messages and the WGL V572RF32 module can process the security messages also.
So it will not be simple.

http://kbase.x10.com/wiki/MS10A

http://www.wgldesigns.com/v572.html

The WGL V572RF32 also will need a X10 power line interface. I believe the XTB523 is the only one still available.