Jump to content

Using 2842 on-only


DMA29

Recommended Posts

Posted

Hello,

 

[New to ISY and Insteon. Reading and learning. Thanks for all you've shared so-far.]

 

My question regards motion detectors. I am using several 2842 detectors to trigger outdoor lights. I want to use 'on-only' so that any motion in front of a detector will reset the WAIT timer for the lights.

 

However, when I set jumper 4 to 'on-only' there's never a change back to OFF. I monitor the SENSOR status and it stays ON forever. I tried settting it back to OFF under program control but it doesn't seem to stick.

 

What do I need to do in ISY99 programming to make use of the 2842 'on-only' mode?

 

Thanks in advance for your help.

Dwayne A

Posted

Normally Motion Sensor options are set through the ISY using Jumper 5 which enables programmatic setting of options. If Jumper 5 is in place the other jumpers have no affect (except for the sensitivity jumper). Click the Set Options button to display and change the motion sensor options if Jumper 5 is in place. Need to be on 3.3.2 if a relatively new Motion Sensor.

 

If not using Jumper 5 it is necessary to power cycle (remove the battery) for other jumper changes to take effect.

 

IMPORTANT - in On Only mode no Off commands are issued by the Motion Sensor so the Sensor will show On after the first motion is sensed.

 

Each motion sensed refreshes the motion timeout interval unless using Occupancy (Sensing) mode.

 

EDIT: in case it was not clear the On Only mode has no affect on establishing a new timeout interval when motion is sensed.

Posted

Occupancy Mode or Sensing Mode as it is labeled on the ISY Set Options causes the Motion Sensor to send a Motion On message every time motion is sensed. If not in Occupancy Mode the Motion Sensor waits until the timeout interval has expired before sending the next Motion On message.

Posted

Using the Admin Console click the Motion Sensor - Sensor node. In the right pane click Set Options. The popup instructions will direct the Motion Sensor be put into linking mode by pressing the Motion Sensor Set button until the Red LED blinks continuously. When the Set Options popup displays check Sensing Mode: and probably Night Only: check boxes if the motion sensor should work at all times.

Posted

Hey great, thank you.

 

What I've done in ISY to use this is:

If

$VerState is 1

And (

Control 'Mx_Drive.Sensor' is switched On

Or Control 'Mx_Ver.Sensor' is switched On

Or Control 'KP_VerLite.LD' is switched On

)

Then

Set 'KP_VerLite.LD' On

Wait 45 seconds

Set 'KP_VerLite.LD' Off

Else

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

 

It seems to work the way I intended in that motion on any sensor will reset the timer. I have noted though that I cannot monitor the motion sensors in the devices pane. Instead I've created little diagnostic programs to see that the sensors are actually functioning and communicating.

If

Control 'Mx_Drive.Sensor' is switched On

Then

$MxDrive = 9

Wait 5 seconds

$MxDrive = 0

Else

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

 

Am I doing something in a way that will cause grief later on?

 

Thanks again for your help.

Dwayne A

Posted
Am I doing something in a way that will cause grief later on?

Whether it causes grief to you is based solely on whether the program does what you intend. Unfortunately, your stated intentions are limited to:

 

motion on any sensor will reset the timer

 

I believe your program will do this, but only if "$VerState is 1". Unfortunately, I cannot see where you describe the conditions which control this variable. Is it possible that ther will be times ($VerState is not 1) when motion does not reset the timer? Is this what you want?

 

Having said all that, consider the possibility that you are in a wait state, and the program triggers and evaluates false, because the variable is not "1". The wait will halt, and the light will remain on indefinitely (until the next program trigger evaluation is true). I will leave it to you decide whether this constitutes grief.

 

There are lots of motion sensor examples in the forum and in the wiki. This can get complicated quickly. Do you want to be able to manually disable the motion sensor? If you turn the light on manually, do you want it to stay on indefinitely? Do you want it to work only during periods of darkness?

 

Time spent thinking about the details of what you want it to do is time well spent, in my mind.

Posted

Okay good, you've confirmed what I was thoguht I knew.

 

My main quesition was about using If Control 'Mx_Ver.Sensor' is switched On to read the motion detector operating in sensor mode. Your response tells me this test is okay.

 

My next question was about using the devices pane to monitor a motion detector operating in sensor mode. Your lack of a response to that question tells me it cannot be done. Fine. My diagnostic code also seems to work.

 

Control of $VerState is what takes care of the remainder of the issues you identified and is not discussed in this post. Again fine.

 

You all have a good night.

Dwayne A

Posted
My main quesition was about using If Control 'Mx_Ver.Sensor' is switched On to read the motion detector operating in sensor mode.

I don't believe the proposed ISY program cares what mode the sensor is in. It will respond to "on" commands, whenever they are recieved. The sensor mode only affects the frequency at which the sensor will send "on" commands. Each "on" command will trigger an evaluation, at which point this will result in a "true" or "false" condition and associated response (then or else).

 

My next question was about using the devices pane to monitor a motion detector operating in sensor mode. Your lack of a response to that question tells me it cannot be done.

From the admin panel, the status of a motion sensor device is based on last command recieved. If a motion sensor is configured to send only "on" commands, the admin-displayed status will be "on" continuously. Motion sensors cannot be queried, I don't believe.

Posted

As a battery powered device. The Motion Sensor goes into a power saving mode and will not respond to a query.

The status display in the administrative pane is the last known state.

If I have a Switchlinc showing On and I use an X10 command to turn it Off. The consoles still shows On as it didn't process the X10 Off.

Guest
This topic is now closed to further replies.

  • Recently Browsing

    • No registered users viewing this page.
  • Forum Statistics

    • Total Topics
      37.2k
    • Total Posts
      372.4k
×
×
  • Create New...