Help with motion/lighting rule

[killervette]

I have a motion sensor sitting at the top of the basement stairs. I also have an insteon toggle switch for the hall light to go downstairs. With my current rule, the light will come on when the motion detector is On. Thats fine.

 

The problem is when i come back up stairs and want the light off. I pass the motion sensor, its on, i then toggle the switch off. The light turns off and then comes back on because of the motion being on. Is there any rules I can use to fix this?

[ergodic]

If by "rule" you mean ISY program, then disabling you 'on' program for some period of time after you press the OFF button should do it.

 

IOW assuming your motion programs are these:

 

M1:

If 'motion1' is switched on

or 'motion1' is switched fast on

then

set 'S1' on

 

M2:

If 'motion1' is switched off

or 'motion1' is switched fast off

then

set 'S1' off

 

Now I think what you want to do is add a program like this:

 

D1:

If 'S1' is switched off

or 'S1' is switched fast off

then

disable program 'M1'

wait 10 seconds

enable program 'M1'

 

You cannot do what you desire with scenes, you'll have to use programs. With motion sensors and the ISY I've found that's almost always to the best.

 

If there's a power failure in the 10 second window then your ISY comes back up with D1 disabled. That's fixable either with a startup program or by adding a usually-redundant 'enable program 'D1'' line to the M1 script.

[killervette]

thank you so much. seems to be working.

[drfunmetal]

Question

If I program the 2420 to have a 4 minute "On" time, does that mean that the 2420 does not recognize movement again for 4 minutes or does is reset to see motion after 1 minute as it does from the factory with the "on" time set at 1? Thanks for any reply.

[Sub-Routine]

The Timeout is the amount of time of no motion before the Off is sent. Only after an Off is sent will an On be sent again. The Timeout is not x minutes from the first motion, it is x minutes since the last motion.

 

Rand

[backinthelab]

Rand,

 

I have the opposite situation with motion in the kitchen. Currently, the motion sensor is linked to the "Kitchen Island" switch. I want the sensor's "Off" command disabled if someone manually hits the "Island" or "Main" switch, then to resume functionality once those switches are turned off. Can you verify this programming?

 

 

M1:

If

Control "Motion 1" is switched On

or Control "Motion 1" is switched Fast On

 

Then

Set "Kitchen Island" On

 

 

M2:

If

Control "Motion 1" is switched Off

or Control "Motion 1" is switched Fast Off

 

Then

Set "Kitchen Island" Off

 

 

Disable Motion:

If

Control "Kitchen Island" is switched On

or Control "Kitchen Island" is switched Fast On

Control "Kitchen Main" is switched On

or Control "Kitchen Main" is switched Fast On

 

Then

Disable program "M2"

 

Else

Enable program "M2"

 

 

I currently have a scene named "Kitchen Motion" that has Motion 1 managing Kitchen Island. Do I need to delete this?

 

Any help would be greatly appreciated. I've been racking my brain with this and thought I had it working.

 

Thanks!

[ergodic]

I think you may be having problems if you've scene-linked your motion sensor and are also at the same time trying to use ISY programs to control it as you've described.

 

What you have seems reasonable. But use the motion sensor to trigger the programs and take it out of any Insteon scenes as they just end up (logically) fighting with each other.

 

The only advantage of scene-linking is that it is almost instantaneous, vs the small lag you get with ISY programs.

 

I use something similar, but I also jumper-disable the MS "Off" and use ISY program "Wait"s to handle the off delay. This is more flexible - for one thing you can cancel a program from other programs. It also is easier to change since you don't have to put the MS in linking mode every time you want to alter the setting.

 

My general rule is I don't even bother trying to scene-link motion sensors. Even if it works the way I want at the start, I soonor or later seem to end up with some enhancement or another I want that requires the flexibility of programs.

 

The other thing you may want someplace in your program list is to re-enable the disabled program if things get 'out of sync', which they inevitably do. I use dimmer fast on/fast offs (which people rarely use) to signal program enable/disables. And I also have one program that runs at 3AM and is also linked to the ISY startup and a KPL button that resets everything to a known state.

[backinthelab]

I had thought that the scene would conflict, thanks for verifying this! Conversely, could I keep the scene in place of the M1 & M2 programs? If so, would this program work:

 

Disable Motion:

If

Control "Kitchen Island" is switched On

or Control "Kitchen Island" is switched Fast On

or Control "Kitchen Main" is switched On

or Control "Kitchen Main" is switched Fast On

 

Then

Set "Motion 1" Off

 

Else

Set "Motion 1" On

 

What would be the pros/cons of this method?

 

I'll probably just delete the scene and let the ISY take full control, just wanted to see if I could keep the scene and somehow just disable it with a program.

 

Thanks for the help so far!

[ergodic]

The motion sensor is a status-only device so far as I know. I don't believe you can programmatically control the state of an Insteon motion sensor because I don't think - (I could be wrong) - the sensor itself evn has that capability. Motion sensors do show up in the "Insteon" action list but I'm not sure the reason or what affect changing the state has - I've never tried it. Perhaps Michael can shed some light on this.

[Michel Kohanim]

Hi backinthelab,

 

ergodic is 100% correct: Motion Sensors are responder only and, on top of that, they are battery operated which means that they do NOT hear anything while they are in sleep mode.

 

With kind regards,

Michel

[intellihome]

I have a motion sensor sitting at the top of the basement stairs. I also have an insteon toggle switch for the hall light to go downstairs. With my current rule, the light will come on when the motion detector is On. Thats fine.

 

The problem is when i come back up stairs and want the light off. I pass the motion sensor, its on, i then toggle the switch off. The light turns off and then comes back on because of the motion being on. Is there any rules I can use to fix this?

 

Killervette, I have a similar setup (basement lights). My switch is inconveniently located behind the door. So I put a MS at the top of the stairs. However I disabled the OFF command (jumper 4). Flipping the toggleLinc on the way out is fine with me. It's actually preferable because I don't want the lights shutting off while I'm down there.

 

A great feature in the MS is that even though I disabled the OFF command, the MS still counts down from 60 seconds from the last movement. During this count down it will not send an ON command. Therefore when I flip the ToggleLinc off, the lights go out and will not turn back on while moving past the MS.

 

When the 60 seconds elapses, the MS is ready for another trigger ON.