Print

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

[kevin1]

I have a DM10a motion sensor and RR01 RF transceiver (and Robodog, all circa ~2001).  I am getting odd behavior with this thing.  I had it set up so the motion sensor would send A8 when motion was detected.  Then in my PC software (using HomeGenie), I would use that to trigger lights or send me a text only when I had the system armed.  This seemed to be working fine last week when I set it up.  Yesterday during football games however, the motion sensor started toggling my primary X10 A1 lamp every time it detected motion (right after I closed the blinds I think).  I disconnected the PC from my CM11a and the the A1 light still kept toggling.  So does DM10a toggle everything on same house code?  Robodog was unplugged too, so this was either the DM10, RR01 or CM11a.

So, I thought I should maybe change the motion sensor to a different house code, M.  But now the transceiver won't pick it up.  I need to leave the transceiver on A to pick up my remotes.  Then I had a deja-vu... I had tried this a couple weeks ago and couldn't get it to work.  Seems like everything has to be on A for the DM10a and RR01 (and Robodog as well) to work. 

Any way to make all these components a little dumber so they only do what they are told (DM10a send A8, RR01 send or receive all house codes, CM11a let PC do the controls)?

I am trying to get some stuff working by the time we go on vacation to simulate someone at home... but this X10 stff is frustrating.  I can only get the outlets in one room to work together; actually I can't even get an old X10 dimmer light switch to work reliably on other side of room!  I am familiar with the two phase issue and do not have a coupler... but thought I could work around that for my vacation (just move light to another room).   

I am about ready to dive into the Z-Wave world rather than investing in couplers, noise filters and amps though. :-(

[Brian H]

There seems to be a bug in the DM10A firmware.
When the Address is set to A8 the Dusk Dawn Sensor should be on A9.
My test DM10A is sending an A1 not A9.
I tried A7 and the Dusk Dawn is A8 as expected.
I tried A9 and the Dusk Dawn is A10 as expected.
Try a different address for the DM10. A8 seems to do A1 for Dusk Dawn not A9 as expected.

Monitor Dump from my 1132CU with Smarthome Essentials.

Address A8
Motion Sensor:
R: A8 - 11:18:09 AM 9/22/2014
R: AOn - 11:18:10 AM 9/22/2014
Dusk Dawn Sensor:
R: A1 - 11:18:18 AM 9/22/2014
R: AOn - 11:18:19 AM 9/22/2014
R: A1 - 11:18:24 AM 9/22/2014
R: AOff - 11:18:25 AM 9/22/2014
Address A7
Motion Sensor:
R: A7 - 11:18:49 AM 9/22/2014
R: AOn - 11:18:49 AM 9/22/2014
Dusk Dawn Sensor:
R: A8 - 11:18:57 AM 9/22/2014
R: AOn - 11:18:58 AM 9/22/2014
R: A8 - 11:19:03 AM 9/22/2014
R: AOff - 11:19:04 AM 9/22/2014
Address A9
Motion Sensor:
R: A9 - 11:19:20 AM 9/22/2014
R: AOn - 11:19:20 AM 9/22/2014
Dusk Dawn Sensor:
R: A10 - 11:19:29 AM 9/22/2014
R: AOn - 11:19:29 AM 9/22/2014
R: A10 - 11:19:37 AM 9/22/2014
R: AOff - 11:19:38 AM 9/22/2014

[Brian H]

Few added points.
The DM10 has a Dusk Dawn Sensor that sends an X10 On when Dusk is detected and an Off when Dawn is detected. Can't be disabled easily.
Normally addressed on the next Unit Code higher than the Motion Sensor Unit Code.
The DM10A seems to do A1 for Dusk Dawn Sensor when the Motion Address is A8.
So when you closed the drapes. It saw darkness and sent an A1 On.

Remember what ever Motion Address {Except A8 in the DM10A's case} you use. The next highest Unit Code is for the Dusk Dawn Sensor. As you choose the address you want to use. If you have the Motion Sensor on A16. Most will loop back and have the Dusk Dawn Sensor on A1.

I did not test the other House Codes but I feel Unit Code 8 with a DM10 may get a Unit Code 1 Dusk Dawn Sensor address. On the House Code set on the dial.

[kevin1]

Thank you so much, it would have taken a while for me to figure that out!  I'll try that out tonight and see if I can get back on track.