Send Motion-user mailing list submissions to
motion-user@lists.sourceforge.net
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/motion-user
or, via email, send a message with subject or body 'help' to
motion-user-requ...@lists.sourceforge.net
You can reach the person managing the list at
motion-user-ow...@lists.sourceforge.net
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Motion-user digest..."
Today's Topics:
1. Re: Reliable system - capture of bugs at night (Jim at ScopeStuff)
2. Re: Reliable system - capture of bugs at night (Jim at ScopeStuff)
3. How to programmatically detect unreachable cameras (Evuraan)
----------------------------------------------------------------------
Message: 1
Date: Sun, 13 Sep 2020 19:50:59 -0500
From: Jim at ScopeStuff <j...@scopestuff.com>
To: Motion discussion list <motion-user@lists.sourceforge.net>
Subject: Re: [Motion-user] Reliable system - capture of bugs at night
Message-ID: <4.3.2.7.2.20200913185904.037a2...@mh2.hctc.net>
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
That absolutely works. The IR attracts the flying critters, which attract the
spiders. The further away from the camera the better for the IR illuminators.
That and using a very limiting motion mask works, but false hits with an
IR illuminator are going to happen.
On the Rasberry Pi, I use PIR and/or microwave/radar motion detection to
qualify the saving of motion images. Quite a bandaid, but it works.
I set up Tracking (Pan/Tilt), track_type 4, to call a shellscript. That script
saves a "trigger" file in a tempfile (ramdisk) directory. (That keeps it from
wearing out the SD card with almost continuous writes.)
A python program is checking for presence of the file that the shellscript
writes. It is also looking at the GPIO pins that the PIR and microwave
motion sensors are hooked to. If the Python program sees a PIR and/or
microwave motion hit, that triggers a time window of "action", and if it then
sees the tempfile written by the shellscript (that was called by Motion),
it copies motion images stored by Motion into another directory of motion
images qualified by PIR and/or microwave hits. Simple!
So now I get motion images that were only generated by something warm
(PIR) or something metal or fleshy (aliens and their vehicles). All of the
images of non-warm and non-alien movement are erased. The cold
blooded silicon based dry aliens can slip by without being detected.
I stumbled on this mess of a technique while learning to use motion to
aim a squirt gun at the parade of neighborhood cats that piss on my
front porch railing. With the PIR/Radar detectors qualifying the target
and Motion providing the X-Y aiming numbers, I don't waste squirts on
flying bugs, shadows and ghosts. Excluding the mailman from the
target list is a future upgrade.
I can try to document the mess if there is interest.
Another possibility is to ask the Motion Gods to add a qualification input,
from GPIO pins perhaps, for the saving of motion images. Unless the pin
has a "1" and not a "0" then a motion file won't be saved. Or the Motion
files are saved to one of two paths based on the polarity of the GPIO bit.
Or perhaps add a conversion specifier in the tracking section like
"%A = value of GPIO bit XYZ". That could add a tag to the file name so
the file could be used or discarded downstream of Motion.
While we're at it, the Motion Gods could allow a GPIO pin to be boinged
whenever motion is detected, so it can open a trap door that releases the
Kraken, so I don't have to refill the feline squirting device.
Jim, the sleep deprived.
At 05:33 PM 9/13/2020 -0500, you wrote:
>Content-Type: multipart/alternative;
> boundary="------------2061926BBE66940C9EFECEF0"
>Content-Language: en-US
>
>I have a similar problem and don't know how to fix it, but I do have an
>idea about the spiders.
>
>It seems that spiders (and bugs in general) are attracted to the IR light
>emitted by security cameras at night.? I figure (and I have not yet tried
>this) that if you turn off or disable the infrared "night vision" on the
>camera, and put another IR source several feet away, perhaps you will have
>the same "night vision" functionality but the spiders will build their
>webs in front of the IR source instead of the camera.
>
>I plan to try this when I get a chance. It won't solve all the problems
>but may help some. Has anyone else tried it?
>
>David
Jim Henson
ScopeStuff
www.scopestuff.com
512-259-9778
------------------------------
Message: 2
Date: Sun, 13 Sep 2020 20:59:13 -0500
From: Jim at ScopeStuff <j...@scopestuff.com>
To: Motion discussion list <motion-user@lists.sourceforge.net>
Subject: Re: [Motion-user] Reliable system - capture of bugs at night
Message-ID: <4.3.2.7.2.20200913203648.05a5b...@mh2.hctc.net>
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
A simpler potential solution came to mind:
Use PIR and/or microwave motion sensor(s) to turn on the IR illuminator(s).
If the IR isn't on, the insects won't be seen by the camera.
Since most IR illuminators have a daylight sensor, they wouldn't come
on unless it is dark and there is motion sensed by the PIR/microwave
triggers.
The PIR and microwave sensor outputs can't drive the IR illuminator
directly, so a relay or DC solid state relay would be needed. That could
be one power FET and a few resistors.
This is typical of the PIR motion sensors I've used:
Search eBay for "HC-SR505 Infrared PIR Motion Sensor Precise Infrared
Detector Module Arduino MCU"
This is the microwave one:
Search eBay for "Microwave Doppler Radar Motion Detector Sensor RCWL-0516
Module Board"
This is way overkill for a DC solid state relay, but simple:
Search eBay for "40A Solid State Relay SSR DC In DC Out"
The microwave "Radar" motion detector boards are omnidirectional and can
see thru walls, but make good qualifiers for PIR detector outputs. PIRs can
sometimes false on bright sunlight shadows, but gated with the microwave
sensor you get a good probability that something real is moving. But there
aren't many bright sunlight shadows at night, at least not in my neighborhood.
However, selectively turning on the IR illuminators isn't nearly as much
fun as
having Motion trigger a shell script that writes a file that another
program picks
up and then copies motion image files based on logic inputs from other sensors!
Jim
At 07:50 PM 9/13/2020 -0500, you wrote:
>That absolutely works. The IR attracts the flying critters, which attract the
>spiders. The further away from the camera the better for the IR illuminators.
>
>That and using a very limiting motion mask works, but false hits with an
>IR illuminator are going to happen.
>
>On the Rasberry Pi, I use PIR and/or microwave/radar motion detection to
>qualify the saving of motion images. Quite a bandaid, but it works.
>
>I set up Tracking (Pan/Tilt), track_type 4, to call a shellscript. That
>script
>saves a "trigger" file in a tempfile (ramdisk) directory. (That keeps it from
>wearing out the SD card with almost continuous writes.)
>
>A python program is checking for presence of the file that the shellscript
>writes. It is also looking at the GPIO pins that the PIR and microwave
>motion sensors are hooked to. If the Python program sees a PIR and/or
>microwave motion hit, that triggers a time window of "action", and if it then
>sees the tempfile written by the shellscript (that was called by Motion),
>it copies motion images stored by Motion into another directory of motion
>images qualified by PIR and/or microwave hits. Simple!
>
>So now I get motion images that were only generated by something warm
>(PIR) or something metal or fleshy (aliens and their vehicles). All of the
>images of non-warm and non-alien movement are erased. The cold
>blooded silicon based dry aliens can slip by without being detected.
>
>I stumbled on this mess of a technique while learning to use motion to
>aim a squirt gun at the parade of neighborhood cats that piss on my
>front porch railing. With the PIR/Radar detectors qualifying the target
>and Motion providing the X-Y aiming numbers, I don't waste squirts on
>flying bugs, shadows and ghosts. Excluding the mailman from the
>target list is a future upgrade.
>
>I can try to document the mess if there is interest.
>
>Another possibility is to ask the Motion Gods to add a qualification input,
>from GPIO pins perhaps, for the saving of motion images. Unless the pin
>has a "1" and not a "0" then a motion file won't be saved. Or the Motion
>files are saved to one of two paths based on the polarity of the GPIO bit.
>
>Or perhaps add a conversion specifier in the tracking section like
>"%A = value of GPIO bit XYZ". That could add a tag to the file name so
>the file could be used or discarded downstream of Motion.
>
>While we're at it, the Motion Gods could allow a GPIO pin to be boinged
>whenever motion is detected, so it can open a trap door that releases the
>Kraken, so I don't have to refill the feline squirting device.
>
>Jim, the sleep deprived.
>
>
>
>At 05:33 PM 9/13/2020 -0500, you wrote:
>>Content-Type: multipart/alternative;
>> boundary="------------2061926BBE66940C9EFECEF0"
>>Content-Language: en-US
>>
>>I have a similar problem and don't know how to fix it, but I do have an
>>idea about the spiders.
>>
>>It seems that spiders (and bugs in general) are attracted to the IR light
>>emitted by security cameras at night.? I figure (and I have not yet
>>tried this) that if you turn off or disable the infrared "night vision"
>>on the camera, and put another IR source several feet away, perhaps you
>>will have the same "night vision" functionality but the spiders will
>>build their webs in front of the IR source instead of the camera.
>>
>>I plan to try this when I get a chance. It won't solve all the problems
>>but may help some. Has anyone else tried it?
>>
>>David
>
>
>
>
>
>Jim Henson
>ScopeStuff
>www.scopestuff.com
>512-259-9778
>
>
>
>
>_______________________________________________
>Motion-user mailing list
>Motion-user@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/motion-user
>https://motion-project.github.io/
>
>Unsubscribe: https://lists.sourceforge.net/lists/options/motion-user
Jim Henson
ScopeStuff
www.scopestuff.com
512-259-9778
------------------------------
Message: 3
Date: Sun, 13 Sep 2020 19:03:45 -0700
From: Evuraan <evur...@gmail.com>
To: Motion-user@lists.sourceforge.net
Subject: [Motion-user] How to programmatically detect unreachable
cameras
Message-ID:
<ca+jjsorqgpqnhx_j902xefzeapv+tysug6pyt9f+xw0ygye...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Hello,
I've motion polling a number of IR cameras. Some of those are on WIFI
and they often go unreachable for a variety of reasons.
If I navigate to the webcontrol_port of my motion server, I'd see the
grey image saying "UNABLE TO OPEN VIDEO DEVICE SINCE <TIMESTAMP>".
I've attached a sample screenshot.
Sometimes although I can reach a camera over HTTP, motion may still
display the above notice until I restart the motion server.
Is there a way I can programmatically determine how many of my video
devices cannot be reached? Apparently motion knows the last timestamp
a camera was last seen, if you can point me in the right direction
that would be great.
If X out of my Y cameras are unavailable, I am looking to automate restarts.
Thanks in advance!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: lostCamera.png.jpg
Type: image/jpeg
Size: 8442 bytes
Desc: not available
------------------------------
------------------------------
Subject: Digest Footer
_______________________________________________
Motion-user mailing list
Motion-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/motion-user
------------------------------
End of Motion-user Digest, Vol 171, Issue 7
*******************************************
