I'd like to get some advice / thoughts here.

 

1) It seems like it might be easier to NOT program the 2420 to a certain set of lightswitches, but to use the ISY to associate it, so I won't have to keep pressing and holding the programming button to make changes. Is there any problem with using the ISY this way? will there be a greater lag from when I walk in the room if the ISY is handling the light?

 

2) what is the best way to handle getting the light off? using the timer in the motion sensor or using the ISY? My understanding is that this motion sensor only send one ON command, so how do we make a program that handles the off? if we just wait 5 minutes from the on, then someone will could still be in the room. Does this mean that it is better to directly associate the light with the motion sensor?

 

3) I've noticed that when you do associate the sensor with a light switch, and you allow it the timer to run out and send an off command.. then if you move very quickly, the motion sensor turns the light back on (as it should) but the ISY doesn't get the correct staus update. This only seems to happen when you move within a few seconds of the off command. Anyone else have this problem?

1 - If you plan on making a lot of link changes with your motion sensor in the future, it certainly might make sense to simply use ISY programs to trigger events based on motion instead of putting your Motion Sensor in scenes. There are 2 limitations to keep in mind, however:

- if your ISY goes down for any reason, your programs do not run

- there is an additional delay with using ISY programs vs. direct device-to-device links

 

2 - The motion sensor does have an ON/OFF mode. So, you could sense motion based on the ON command and do whatever action you'd like (turn lights on), then watch for the OFF command. When the OFF command is received, you know there has been no motion for x number of minutes (whatever timeout you have configured on the Motion Sensor). I agree that the ON only mode is rather limited, in my opinion.

 

3 - I haven't seen this yet, but my motion sensors have been in low-traffic areas (closets, etc.)

someguy,

 

I have been using a motion sensor in our kitchen for about 2 weeks.

 

1. I liked the instant On when linked but I wasn't happy with the Off. Our kitchen is too busy at times. So I am using the ISY to switch the lights on and off. There is a slight delay. If the ISY goes down we still have our usual switches in place.

 

2. I watch for the MS Off command and add some seconds to it. When our kitchen is typically busy (breakfast and dinner) I don't turn the lights off, but I dim them. This reduces annoyance due to the lag. I use a non-load switch in the kitchen to override the motion sensor programs. I also key on a lamp in our family room to maintain a dim state when we are watching TV. I use three different On levels/rates that depend on the time of day (and night) and the status of the lamp. You can't do that when directly linked.

 

3. I have only seen a command missed when I try, I haven't experienced it in daily use. There is ~2-4 seconds when sending a command that the MS is busy. Perhaps relocating the sensor would solve that issue. Do you have an Access point on your PLM?

 

Rand