Print

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

[gfriedman]

So I installed the MS13 motion detector which seems to be working fine (except for my cats triggering the thing now and then).   I wanted the motion detector to turn on a light connected to an SR227 super socket at night.  Motion detector on C10  SR227 on C11.   Macro set to trigger C10 ON and then turn on SR227 only between 1AM and 6AM.   Set it up then notice the light on the SR227 turning on most of the time the motion detector is triggered  regardless of the macro.   I know the macro is working properly since there are other modules in the macro that work properly.

So first I try moving the SR227 to a different unit codes C12, C13, etc.   ... same issue.   Then take the leap and put SR227 on different house code G2.   Same problem!   I have about 12 other X10 modules that work fine.   This one seems bizarre to me.    If I look in the AHP activity monitor I can see the motion detector firing off properly on C10.

When other modules are turned on or off they dont impact this SR227 - only the motion detector.

I`m stumped.  Any ideas?  Or is this socket possessed?

Gene

[Brian H]

The MS13A has a Dusk Dawn Sensor that is on the next highest address.
So your C10 Motion Sensor has a Dusk Dawn of C11.
When you had the SR227 on C11 it is very possible it was also being controlled by the dusk dawn event.
An AHP expert will have to add information for the macros actions. With the SR227 not an an adjacent address.

[gfriedman]

Thanks, but the hawkeye is inside the house in a hallway.   If I walk in front of it I can see the red LED trigger and then a second later hear the loud click of the SR227 - even with both on different house codes.

While reading around I saw a post by Tuicemen talking about corrupted macros and macros triggering from the waste bin.   Thats the only thing that makes any kind of sense so I will try and clean up any old macros that might be lurking around and see if that fixes it.  Will report back by tomorrow.

G

[Tuicemen]

There are many users that have issues with motion sensors.
The +1 unit and the dusk dawn is just one.
Combine that with strong sun light from a nearby window and you'll have a hard time nailing it down.
There are some things I try to remember when setting up the motion sensors with macros.
Avoid triggering stuff on the same house code as the sensor
Avoid triggering stuff on house code A
The reason for both is the same.
When the batteries start getting week the first thing that happens is the sensors address starts to wander,
eventually ending up at A1.
The fact that your sensor is indoors has no effect on it thinking it is dusk and sending the +1 unit code.
Cloudy days will make the sensor think it is dusk
 

[dave w]

Thanks, but the hawkeye is inside the house in a hallway.   If I walk in front of it I can see the red LED trigger and then a second later hear the loud click of the SR227 - even with both on different house codes.

Isn't that what you want? The point is IF the Hawkeye is addressed as C10, then you want NOTHING in the house addressed as C11 otherwise it will be controlled by the C11 light-dark output from the Hawkeye.
The Dawn-Dusk feature can not be programmed off in the Hawkeye. (it can be stopped through a simple hack, if you need to use the C11 HCUC.

[gfriedman]

Thanks guys.   Yes, I do see the dusk/dawn being triggered on C11 in the Activity monitor when the kitchen light goes on/off.   Thanks for bringing that to my attention - couldn't figure out where that was coming from.   So I put a phantom MS13A module in AHP on C11 next to the real one on C10 so I have a placeholder for that code.

I also purged all the deleted macros that were sitting in the trash bin.   So far - so good.   I think that they might have been firing off the SR227 inadvertently.

Hopefully the demons have been exorcised.   But on to another problem for a new thread......

[gfriedman]

OK, here is an update with the culprit found.

The problem was the local control within the SR227 kicking in.    I had a strobe light plugged into the SR227 and it seems the sensing current was just borderline enough to trigger the strobe lightly on once and when that happened the local control of the SR227 kicks in fully.

Which explains why looking at the Activity Log was useless to solve this.   Times like this I wish I had 2-way modules.

Now to hunt down the post that shows how to disable SR227 local control....

[Brian H]

Adding a small 4 watt incandescent night light bulb to the switched outlet. Should also calm down the local trigger.

[dave w]

Which explains why looking at the Activity Log was useless to solve this.   Times like this I wish I had 2-way modules.
Now to hunt down the post that shows how to disable SR227 local control....

The 4 or 7 watt nightlight is a great solution, I think I have at least a dozen 7W nightlights to stop newer Appliance Modules from kicking back on where the controlled appliance has some sort of internal switch which falsly triggers the module (i.e the hot plate on the coffee maker and the humidistat in the dehumidifier, etc.). Brian H is one of the Smarthome.com Insteon experts on the forum and can confirm but I believe Smarthome is still selling a Insteon/X10 addressable outlet wher local control can be disabled. http://www.smarthome.com/2473SWH/OutletLinc-Relay-INSTEON-Remote-Control-On-Off-Outlet-Non-Dimming-White/p.aspx

[Brian H]

Yes the Outletlinc is still available.
It ships with Local Control turned Off but you can enable it if you care to.
The sensing current is still there. The module just ignores the signal. So real light loads like small LED bulbs may still glow dimly.
Full Users Manual is available from the link on the sales page, dave w provided.

[gfriedman]

Great!   Thanks for the info...  will have a look.