Print

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

[miguel222]

I tested a basic setup with an Eagle-Eye, Lamp Module (LM465), and RF remote all on A1.  Everything worked, dimming, on, off, etc.  Soft-on/off is a bit confusing however.

Things went bad when I switched the LM465 to A2 and created an A1-ON macro and and A1-OFF macro. (Triggered by the Egale Eye still on A1)

The A1-ON macro brightens the light by 10%.

The A1-OFF macro turns the light all the way off.

As soon as I did this, the LM465 began to misbehave.  If any ON is sent to the LM465, it comes on for a second (soft or hard), but then turns off about a second later.  It then repeats this ad nauseum.  Sending several OFFS eventually stops the loop, but another ON from the macro or the RF remote starts the loop again.

I've tried "bright 100% to on" and the 2-way lamp module hack, to no avail.

[miguel222]

I should add that during this cycling, AHP does *not* show the macros being triggered.

[Brian H]

The Eagle Eye has a Dusk Dawn sensor in it. When it get dark it send an On command and an Off when it gets light.

The Dusk Dawn feature is on the motion sensors address +1 Unit code.

So in your setup. Motion is on A1 and Dusk Dawn is on A2.

If the LM465 is set to A2 and the controlled light is physically shining on the motion sensor Dusk Dawn detector. It will turn Off the module when it see the light. Then the light goes off and the sensor send an On. Then the whole cycle starts again. 
As a test, if you can block the Motion Sensor; with maybe a piece of cardboard. See if the cycling stops.

Try moving the LM465s address to A3 and modifying the macro to send an A3 instead of A2.

Some users as they gain experience with X10 and macros. Have found that using a different House Code for Macro triggers works better. Also some will split House Codes by functions. Like Motion Sensors using their own House Code from other modules.

[miguel222]

The Eagle Eye has a Dusk Dawn sensor in it. When it get dark it send an On command and an Off when it gets light.

The Dusk Dawn feature is on the motion sensors address +1 Unit code.

So in your setup. Motion is on A1 and Dusk Dawn is on A2.

If the LM465 is set to A2 and the controlled light is physically shining on the motion sensor Dusk Dawn detector. It will turn Off the module when it see the light. Then the light goes off and the sensor send an On. Then the whole cycle starts again. 

As a test, if you can block the Motion Sensor; with maybe a piece of cardboard. See if the cycling stops.

Try moving the LM465s address to A3 and modifying the macro to send an A3 instead of A2.

Some users as they gain experience with X10 and macros. Have found that using a different House Code for Macro triggers works better. Also some will split House Codes by functions. Like Motion Sensors using their own House Code from other modules.

Sure enough, that was the issue.  Thanks.