Please login or register.

Login with username, password and session length

Author Topic: ActiveHome and MS14a issues  (Read 3991 times)

loren

  • Newbie
  • Helpful Post Rating: 0
  • Posts: 3
ActiveHome and MS14a issues
« on: February 09, 2006, 10:03:36 PM »

I have a socket rocket set to A1. It is
working fine with Activehome. I have a ms14a
eagle eye motion sensor, that sends a signal
to activehome telling it to turn on
everything set to A1.

I turn on the motion sensor, and see that
activehome is receiving the signal when it
detects motion.

When it detects motion activehome switches my
socketrocket to the 'on' position in the
software, but the actual light doesn't turn on.

If i click on a different section of
activehome, and click back real the switch is
in the 'off'position.

It appears the software is just changing the
little graphic on, and not the actual light.

Any suggestions?

Thanks

Logged

Charles Sullivan

  • Hero Member
  • *****
  • Helpful Post Rating: 94
  • Posts: 1565
    • HEYU - X10 Automation for Linux, Unix, and Mac OSX
Re: ActiveHome and MS14a issues
« Reply #1 on: February 09, 2006, 10:44:22 PM »

Loren:
Click Tools > Hardware configuration
and make sure the box for transceiving
housecode A is checked.
Logged
Yesterday it worked.
Today it doesn't work.
X10 on Windows is like that.

HEYU - X10 Automation for Linux, Unix, and Mac OS X     http://www.heyu.org

loren

  • Newbie
  • Helpful Post Rating: 0
  • Posts: 3
Re: ActiveHome and MS14a issues
« Reply #2 on: February 10, 2006, 12:44:07 AM »

Thanks for help...that solved the problem.

I'm sure it's something easy to figure out,
although I'm stuck again. The sensor
succesfully turns on the light, and after the
set amount of time, it turns it off. The only
problem is that the light I have set to A2
turns on when the light triggered by the
sensor (A1) turns off.

Any ideas?
Logged

Brian H

  • Community Organizer
  • Hero Member
  • ***
  • Helpful Post Rating: 305
  • Posts: 13260
Re: ActiveHome and MS14a issues
« Reply #3 on: February 10, 2006, 06:58:54 AM »

Loren; That is the way the MS14a motion
sensor works. It has a dusk dawn sensor
along with the motion sensor. It sends an on
at dusk and an off at dawn on the address
one higher than the motion address. So if
you have motion on A1 you get dusk dawn on
A2. My guess here is the light on A1 shines
on the motion sensor. So it goes off and the
A2 goes on. Maybe easiest to not use A2 and
readdress the A2 module to a different
address.
Your first problem is commonly known one as
only X10 knows why the AHP software defaults
to none. Older versions didn't!
Logged

roger1818

  • Hero Member
  • *****
  • Helpful Post Rating: 28
  • Posts: 1072
  • Roger H.
Re: ActiveHome and MS14a issues
« Reply #4 on: February 13, 2006, 10:10:16 AM »

Loren:  Brian is correct about the light sensor probably being triggered by the light at A1.  There are a couple other solutions if you are wanting to keep the other light at A2 so that you aren’t wasting buttons on your remotes:

1. Change the address of the motion sensor to a different house code (lets assume house code M) and then create macros on M1 ON and OFF to turn A1 on and off accordingly.  If you get a second motion sensor that you want to turn a different light on and off, make sure you put it on M3 (not M2).  Don’t forget to mark both A and M to be transceived.

2. If you don’t need the light sensor, there is an article at: http://www.idobartana.com/hakb/modifying_hawkey_sensor.htm#Disabling dusk/dawn sensor on how to disable it.  Alternately, the ActiveEye can be programmed to disable the dusk/dawn notification.
« Last Edit: October 24, 2009, 01:03:53 AM by -Bill- (of wgjohns.com) »
Logged
 

X10.com | About X10 | X10 Security Systems | Cameras| Package Deals
© Copyright 2014-2016 X10.com All rights reserved.