Print

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

[radeohedca]

I have an MS14A triggering a socketrocket via a Macro in the CM15A to turn on my front porch light for a couple of minutes.
When I use my Logitech IR remote to control that same light through an IR543 it will turn on but go off after a couple of minutes. It seems as though the ON command, however it's done is still subject to the Macro (couple of minutes ON then OFF).  What am I doing wrong ?  Is it possible to isolate the macro from other ON/OFF commands to the socketrocket ?

Thanks.

[Tuicemen]

The most common mistake is having the light the same address as the macro trigger.
They have to be different!
You are most likely sending the macro address not the light address with the remote.
 

[radeohedca]

When the MS14A (assigned to address H16) senses movement it initiates the Macro, the socketrocket at H4 is turned ON, there is a couple of minutes delay then the Macro sends H4 OFF.
When I use the IR remote it simply sends H4 ON and the socketrockets turns ON but then a couple of minutes later it turns OFF.

If I understand correctly you are saying that I'm probably sending an H16 command initiating the Macro (??) which is not the case.

Thanks.

[Brian H]

Anything on H1?

Is the light by chance shining on the MS14A?

The MS14A has a Dusk Dawn sensor in it. That sensor is usually motion address +1 Unit Code. With H16 as motion address the dusk dawn loops back to H1.

[Tuicemen]

Do you have another remote like a palm pad that you can use to turn on the light?
Does the same thing happen if you turn off the light with AHP?
What is the Activity monitor showing?
Do you have any macros in the AHP recycle bin?
Good point Brian! Sensor may be seeing the light as motion if to close to it

[radeohedca]

Anything on H1?

Is the light by chance shining on the MS14A?

The MS14A has a Dusk Dawn sensor in it. That sensor is usually motion address +1 Unit Code. With H16 as motion address the dusk dawn loops back to H1.

H1 is not being used in my system.
No light shining on the MS14A unless it sees motion.
I'm not using the dusk/dawn functionality for anything. Should the motion sensor still work at addr. H16 ?

[Brian H]

Yes if you have set the MS14A for the H16 address for sensing motion. An H16 On will be sent when motion is detected and if no motion is sensed for the timeout period. The H16 Off will be sent.

[Tuicemen]

No light shining on the MS14A unless it sees motion.

As a test cover up the motion sensor and see if turning on the light still causes it to shut off after a couple of minutes.
That will tell you if it is to close to the light!
 

[radeohedca]

Ahh... I see what you're getting at. I'm willing to bet that's the issue since the sensor is close to the light that it turns on.

That would also explain why the delay in the macro is set for 4 minutes but the light never seems to stay on for longer than a minute or so. (I was going to attack that as a separate issue).
The light is very close to the sensor so I guess the sensor is turning it off before the actual macro does.  Same applies if I turn the light on with an H4 ON command from any other device.... the MS14A thinks it's dawn and initiates the OFF command after a minute or so.

I guess I wasn't clued in to the dusk/dawn functionality of the sensor.  I'll try relocating the sensor and maybe fabricate a light shield/blind for it.

When Tuicemen asked "...is the light shining on it ?", I thought you were referring to the LED within the MS14A, i.e. is the LED flashing a lot (I tend to take things a little too literally).

An obvious newbie mistake.
Thanks !

[radeohedca]

Is there a way to reduce the sensitivity of an MS14A like an internal control or am I limited to putting physical blinders on it ?

[radeohedca]

Is there a way to reduce the sensitivity of an MS14A like an internal control or am I limited to putting physical blinders on it ?

Disregard... I found this: http://forums.x10.com/index.php?topic=4567.0