Don't Turn Off Yet

[Deuce]

Hi, first-time-poster here...

 

I graduated from the Insteon Hub to the ISY and WOW, what a difference.  It seems like there are no limitations with regard to programming, if you know what you're doing...

 

I have a long driveway (1/3 mile) that has many lamp posts along the way.  At both ends, I have an Insteon motion sensor stashed in a little bird house in a tree.  The motion sensors have their jumpers set to have the device controlled by software.  I have built simple programs that when motion is sensed, the post lights go from dim to full-on.  After a few minutes, the program returns the lamps to their dim state.  For the most part, this works perfectly for motorists.  For pedestrians however, there is a hitch.  Walking down the driveway, the first motion kicks on and your good for the journey.  But, before the turn-off event of the program, you hit the second sensor as you turn around to return.  It then starts the same program.  But a half-minute into the return trip, down goes the lights.

 

I think that while my expectation is that the trigger of the second sensor is starting the time period for lights full-on, what is happening is that the first program's time has expired and it is calling for lights down.

 

So my question is, how do we get the two motion sensors to work together so that together, they act more as a single occupancy sensor, restarting the clock whenever motion is sensed, either side?

 

Thanks.

 

[paulbates]

Hi, welcome to the UDI Forums!

 

If I understand correctly, the idea would be to "stop" the first program, if and only if the second triggers, so it doesn't interfere with the lights?

 

If so, in the 'Then' part of the second program, add a 'Stop' statement as the first statement

• Select Program from the first Action drop down,
• Pick stop from the second drop down
• Pick the program name of the first program from the list
• Use the "Move Line Up" button to make it the first statement under 'Then'

If that doesn't do it, please post the programs here and we'll take a look

 

Paul

[stusviews]

If you have one program and an Or for both sensors, the second trigger should interrupt the Wait and restart the program/timer.

[TrojanHorse]

I agree with Stu. You also say it triggers the same program. I would think that would restart it?

Welcome to ISY. I'm still learning it after about 3 years.

 

Edit: I also agree with Paul. Depending on your program structure you may want to stop a program.

 

I've just started posting here but have been reading this forum for a while. Thanks everyone for sharing your knowledge!

 

Sent from my iPhone using Tapatalk

Edited December 13, 2016 by TrojanHorse

[larryllix]

If nearMS is switched ON

Then turn on lights, Wait 30 seconds, enable program farMSstop, Wait 20 minutes, turn off lights.

 

If farMS is switched On

Then turn on lights, Wait 30 seconds, enable program nearMSstop, Wait 20 minutes, turn off lights.

 

Program farMSstop (disabled)

If farMS is switched On

Then Wait 1 minutes, turn lights Off, disable program self

 

Program nearMSstop (disabled)

If nearMS is switched On

Then Wait 1 minutes, turn lights Off, disable program self

 

There is some logical problems like two people entering the zone from each end or people changing their minds and turning around or MS motion missed but the 20 minutes Waits should handle those just-in-case elements.

Edited December 13, 2016 by larryllix

[Deuce]

Thanks all for the suggestions.  I tried the single program approach without the desired result.  It is notable however, that if I trigger a motion sensor (and the subsequent program), then halfway through the "wait" cycle activate it again, it does not seem to start the clock again.  Here's the code:

 

If

From    Sunset 
To        11:29:00PM (same day)

     And Status 'Motion Sensors / Driveway' is On

      Or Status 'Motion Sensors / Driveway' is On 

 

Then

        Set 'Driveway / Pole Lights' On 

        Set 'Driveway / Carriage Lights' 10% 

        Set 'Porch / Porch-Front' 40% 

        Set 'Porch / Porch-Side' 40% 

        Wait  1 minute  

        Set Scene 'Dim Driveway' On 

        Wait  1 minute  

        Set 'Porch / Porch-Side' Off 

        Set 'Porch / Porch-Front' Off 

 

Else

     - No Actions - (To add one, press 'Action')

[TrojanHorse]

Looks like you need parentheses around your two statements that are intended to be OR.

I believe they are to the lower right of the program editor.

 

 

Sent from my iPhone using Tapatalk

[Deuce]

I'm not sure that I understand the parenthesis.  Should it look like this:

 

If

From    Sunset 
To        11:29:00PM (same day) 

     And Status 'Motion Sensors / Driveway' is On

      Or (

                 Status 'Motion Sensors / Driveway' is On 

           )

[TrojanHorse]

And (

Status on 1 OR

Status on 2

)

 

 

Sent from my iPhone using Tapatalk

[stusviews]

Is "Motion Sensors / Driveway" a scene with both sensors? There's n need to include the same scene twice. Also, an or statement should include multiple (different) commands, not just one.

 

More importantly, do you have the MS set to send ON commands only. If not, then the MS will turn it's links off no matter what you program.

[Deuce]

Stu,

 

 "Motion Sensors / Driveway" and "Motion Sensors / Driveway" are both motion sensors. not scenes.  Regarding motion sensors, the ON commands only checkboxes were not selected - I'll give that a shot. 

[Deuce]

Also...

 

Should the "Sensing Mode" also be checked?  If I'm understanding correctly, by leaving it unchecked, the MS will not report motion until the timeout expires, and that seems to be what is prohibiting my setup from working.

 

Lastly, to make settings on the motion sensors, I have to physically switch them in to setup mode, correct?

[stusviews]

You have two motion sensors with identical names? Not a good practice, in fact, a terrible practice.

 

Place both sensors into the same scene. Select every option (except LED to save battery life). Use the program to turn the light scene off.

[oberkc]

Deuce,

 

Sensing mode MAY help but I consider it unlikely to be the root of your problems. In addition to the parentheses, I recommend use of CONTROL rather than STATUS for your two program conditions.

 

You also have a potential problem at 11:29pm if your program is in the wait state.

 

Make sure your motion sensors are NOT in a scene controlling the lights.

 

Do you want to turn the lights off after wait timeout, or dim?

[Deuce]

Suggestions of moving to a single program and using an "or" statement within parenthesis, setting the MS's correctly, etc., etc., all collectively enabled me to get things working as I wanted.  Thanks to all for your assist!