Send Motion-user mailing list submissions to
[email protected]
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
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Motion-user digest..."
Today's Topics:
1. One camera keeps dropping (David Powell)
2. Re: One camera keeps dropping (tosiara)
3. Re: Video view position with lower resolution (tosiara)
4. Re: One camera keeps dropping (David Powell)
----------------------------------------------------------------------
Message: 1
Date: Mon, 21 Jan 2019 09:05:39 -0500
From: David Powell <[email protected]>
To: Motion discussion list <[email protected]>
Subject: [Motion-user] One camera keeps dropping
Message-ID: <[email protected]>
Content-Type: text/plain; charset="utf-8"; Format="flowed"
I have several IP cameras connected to Motion on my RasPi.? They all
work fine most of the time.? But one camera, an old Panasonic, gets
disconnected from Motion approximately once or twice a day. After it
gets disconnected, it won't detect movement, and viewing it on the
streaming port yields only a gray image with the /text_left/ and
/text_right/ values showing, and a */CONNECTION TO CAMERA LOST/* message
in the upper left. The log has many, many of these lines:
*[2:nc9:shop] [ERR] [NET] [Jan 21 07:35:38] netcam_read_first_header:
Error sending 'connect' request: Broken pipe**
**[2:nc9:shop] [ERR] [NET] Above message repeats 5000 times*
The only way I have found to re-establish the connection is to kill and
restart motion. Doing so completely fixes the problem for anywhere from
an hour to a couple of days, then it drops again.
None of my other cameras do this.? One clue is that this particular
camera sees very little motion, whereas the others get triggered a
hundred times or more every day.
How do I begin to find this problem?
David
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
Message: 2
Date: Mon, 21 Jan 2019 16:22:17 +0200
From: tosiara <[email protected]>
To: Motion discussion list <[email protected]>
Subject: Re: [Motion-user] One camera keeps dropping
Message-ID:
<CACHTdwS3W3vAEvx_T+DtzYBC0YE+6H9yROOzd=mf3o25s5t...@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Which motion version?
On Mon, Jan 21, 2019 at 4:06 PM David Powell <[email protected]> wrote:
>
> I have several IP cameras connected to Motion on my RasPi. They all work
> fine most of the time. But one camera, an old Panasonic, gets disconnected
> from Motion approximately once or twice a day. After it gets disconnected,
> it won't detect movement, and viewing it on the streaming port yields only a
> gray image with the text_left and text_right values showing, and a CONNECTION
> TO CAMERA LOST message in the upper left. The log has many, many of these
> lines:
>
> [2:nc9:shop] [ERR] [NET] [Jan 21 07:35:38] netcam_read_first_header: Error
> sending 'connect' request: Broken pipe
> [2:nc9:shop] [ERR] [NET] Above message repeats 5000 times
>
> The only way I have found to re-establish the connection is to kill and
> restart motion. Doing so completely fixes the problem for anywhere from an
> hour to a couple of days, then it drops again.
>
> None of my other cameras do this. One clue is that this particular camera
> sees very little motion, whereas the others get triggered a hundred times or
> more every day.
>
> How do I begin to find this problem?
>
> David
>
> _______________________________________________
> Motion-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/motion-user
> https://motion-project.github.io/
>
> Unsubscribe: https://lists.sourceforge.net/lists/options/motion-user
------------------------------
Message: 3
Date: Mon, 21 Jan 2019 16:26:42 +0200
From: tosiara <[email protected]>
To: Gotcha IT <[email protected]>, Motion discussion list
<[email protected]>
Subject: Re: [Motion-user] Video view position with lower resolution
Message-ID:
<CACHTdwRqZk8X=bf23kzbgzy_r+ins8gj22u0ydgzpoe2p7r...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Motion does not select which part of the sensor to grab, it asks camera to
provide 1024x600 and you will see whatever camera gives
Also, there is no way to crop picture by motion, but you can setup a
middleware, like ffmpeg, that will grab picture from camera, resize/crop
and feed it to motion (if it is really worth)
On Mon, Jan 21, 2019 at 2:15 AM Gotcha IT <[email protected]> wrote:
> Hi Guys,
>
> New subscriber here.
> I use MotionEyeOS on several Raspberry Pi Zero W's as security cameras.
> With cameras connected to a 4G service, I need to use my bandwidth wisely,
> especially as the cameras are not the only devices using the 4G service.
> To reduce bandwidth I use a lower resolution (with only 1 frame per
> second) than the camera supports (a 120 degree FoV MMAL camera). Because
> I'm more interested in a wide than high view I prefer a resolution like
> 1024x600 over 1024x768.
> However, if I specify 1024x600, Motion grabs the top part of the camera
> view (CCD), not the middle part. Is this configurable? If not I would
> prefer it to default to the middle, but ideally I'd like to configure this
> as in my case I need the bottom part more than I need the top. The top
> part of the camera view is generally ceiling, which is of no interest.
>
> With MotionEyeOS I can provide Motion options for the video device, but I
> couldn't find anything related to this.
> Does anyone know if this is configurable and if yes, how?
>
> If not, perhaps this could be included as a feature request?
>
> Kind Regards,
>
> *Olger Diekstra*
> *IT Manager*
>
> [email protected]
> (07) 5564 6666
> www.gotcha.net.au
> <https://www.facebook.com/gotchakids>
> <https://www.instagram.com/gotchakidsau/>
> <http://www.gotcha.net.au/>
> This communication may contain confidential or copyright information of
> Gotcha! Pty Ltd (ABN 66 113 417 860). If you are not an intended recipient,
> you must not keep, forward, copy, use, save or rely on this communication,
> and any such action is unauthorised and prohibited. If you have received
> this communication in error, please reply to this email to notify the
> sender of its incorrect delivery, and then delete both it and your reply.
>
> _______________________________________________
> Motion-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/motion-user
> https://motion-project.github.io/
>
> Unsubscribe: https://lists.sourceforge.net/lists/options/motion-user
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
Message: 4
Date: Mon, 21 Jan 2019 09:46:59 -0500
From: David Powell <[email protected]>
To: Motion discussion list <[email protected]>,
tosiara <[email protected]>
Subject: Re: [Motion-user] One camera keeps dropping
Message-ID: <[email protected]>
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Sorry.? I've been with this group long enough to know better than to
leave that tidbit out!? It's *4.1.1+git20181002-062a328*.
David
On 1/21/19 9:22 AM, tosiara wrote:
> Which motion version?
>
> On Mon, Jan 21, 2019 at 4:06 PM David Powell <[email protected]> wrote:
>> I have several IP cameras connected to Motion on my RasPi. They all work
>> fine most of the time. But one camera, an old Panasonic, gets disconnected
>> from Motion approximately once or twice a day. After it gets disconnected,
>> it won't detect movement, and viewing it on the streaming port yields only a
>> gray image with the text_left and text_right values showing, and a
>> CONNECTION TO CAMERA LOST message in the upper left. The log has many, many
>> of these lines:
>>
>> [2:nc9:shop] [ERR] [NET] [Jan 21 07:35:38] netcam_read_first_header: Error
>> sending 'connect' request: Broken pipe
>> [2:nc9:shop] [ERR] [NET] Above message repeats 5000 times
>>
>> The only way I have found to re-establish the connection is to kill and
>> restart motion. Doing so completely fixes the problem for anywhere from an
>> hour to a couple of days, then it drops again.
>>
>> None of my other cameras do this. One clue is that this particular camera
>> sees very little motion, whereas the others get triggered a hundred times or
>> more every day.
>>
>> How do I begin to find this problem?
>>
>> David
>>
>> _______________________________________________
>> Motion-user mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/motion-user
>> https://motion-project.github.io/
>>
>> Unsubscribe: https://lists.sourceforge.net/lists/options/motion-user
>
> _______________________________________________
> Motion-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/motion-user
> https://motion-project.github.io/
>
> Unsubscribe: https://lists.sourceforge.net/lists/options/motion-user
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
------------------------------
Subject: Digest Footer
_______________________________________________
Motion-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/motion-user
------------------------------
End of Motion-user Digest, Vol 151, Issue 33
********************************************
