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. Abrupt Failure upon Apt upgrade to RPi2B (sidestep99)
2. Event_start/event_end behaviour (James Smith)
3. Re: Abrupt Failure upon Apt upgrade to RPi2B (AG)
4. Re: Abrupt Failure upon Apt upgrade to RPi2B (tosiara)
----------------------------------------------------------------------
Message: 1
Date: Sat, 13 Feb 2021 16:26:41 +0000
From: sidestep99 <[email protected]>
To: "[email protected]"
<[email protected]>
Subject: [Motion-user] Abrupt Failure upon Apt upgrade to RPi2B
Message-ID:
<fl5N_Th-GzerDZ86Y13xuCl_4ofnMy-731eRy55UMyZf016OWETuvTjpZL6IlpxXRpOqsJ_R5BkPZbTlL_jsbxKtl-M_QNWsAjYS0yRp-cU=@protonmail.com>
Content-Type: text/plain; charset="utf-8"
I don't know if anyone else is writing about this, but my most recent weekly
update/upgrade to a test Raspberry Pi with Pi camera running Motion (which was
installed from apt) has abruptly ceased to function.
A bit more background: Fully functioning, weekly updated/upgraded Raspberry Pi
with motion.conf simply taking a photo upon identifying the default amount of
motion. After my upgrade yesterday, motion no longer likes the config. I didn't
change anything in motion.conf. It all just stopped working immediately after
my weekly apt update/upgrade of this Pi.
~ tail motion.log:
v4l2_select_input: Device does not support specifying PAL/NTSC norm
followed by:
v4l2_do_set_pix_format: Error setting pixel format
Anybody have any idea what changed causing this simple setup to no longer work?
Sent with [ProtonMail](https://protonmail.com) Secure Email.
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
Message: 2
Date: Sun, 14 Feb 2021 11:24:17 +1000
From: James Smith <[email protected]>
To: [email protected]
Subject: [Motion-user] Event_start/event_end behaviour
Message-ID:
<cak21x7snso9acjuwbjxkvdaqtj2pst0_jqdvcm84tu7uhk+...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
I'm using event_start and event_end to run a python script I've written to
push captured images in a motion event to a deepstack AI server and on
detection of specific objects then cast that cameras stream to a Google
Nest Hub.
In general it's working fine, however as I have 4 cameras set up to run the
same script on motion, quite often there can be an overlap of motion
detection, especially at night with bugs galore attracted to the IR LEDs.
>From what I can tell, it appears an event_start from another camera looks
to override the event_gap setting and kills any event and the scripts it
run that may already be in progress from another.
My reason for thinking this is because the script, which I also have doing
some other tasks, like generating an animated gif from the event and then
removing the images, is not finishing all of the time when triggered from
motion, so I could only assume this happens when another event gets
triggered while this one is running.
Is this intended behaviour, or should it be spawning an entirely new
process each time and allowing the script to run to completion? Any
suggestions how I can make sure the scripts aren't interrupted?
Regards
James
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
Message: 3
Date: Sat, 13 Feb 2021 20:31:34 -0500
From: AG <[email protected]>
To: sidestep99 <[email protected]>, Motion discussion list
<[email protected]>
Subject: Re: [Motion-user] Abrupt Failure upon Apt upgrade to RPi2B
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii; format=flowed
I had a working config but after upgrading to package version 4.3.2-1 on
Bullseye, the process would exit upon start. Note, systemd took care to
run it as a service upon startup.
What got it going for me was commenting out the 'daemon on' near line 16
in motion.conf. If you have any luck with that, it might make sense to
perhaps have a bug filed with its packager.
On Sat, Feb 13, 2021 at 04:26:41PM +0000, sidestep99 via Motion-user wrote:
>I don't know if anyone else is writing about this, but my most recent weekly
>update/upgrade to a test Raspberry Pi with Pi camera running Motion (which was
>installed from apt) has abruptly ceased to function.
>
>A bit more background: Fully functioning, weekly updated/upgraded Raspberry Pi
>with motion.conf simply taking a photo upon identifying the default amount of
>motion. After my upgrade yesterday, motion no longer likes the config. I
>didn't change anything in motion.conf. It all just stopped working immediately
>after my weekly apt update/upgrade of this Pi.
>
>~ tail motion.log:
>v4l2_select_input: Device does not support specifying PAL/NTSC norm
>followed by:
>v4l2_do_set_pix_format: Error setting pixel format
>
>Anybody have any idea what changed causing this simple setup to no longer work?
>
>Sent with [ProtonMail](https://protonmail.com) Secure Email.
>_______________________________________________
>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: 4
Date: Sun, 14 Feb 2021 08:31:50 +0200
From: tosiara <[email protected]>
To: sidestep99 <[email protected]>, Motion discussion list
<[email protected]>
Subject: Re: [Motion-user] Abrupt Failure upon Apt upgrade to RPi2B
Message-ID:
<cachtdwsnmj9wrkzojrrlbcejbhmr-_zhtswtcs+s7ur1s7u...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
> v4l2_do_set_pix_format: Error setting pixel format
Which pixel format is specified in your config?
On Sat, Feb 13, 2021, 18:27 sidestep99 via Motion-user <
[email protected]> wrote:
> I don't know if anyone else is writing about this, but my most recent
> weekly update/upgrade to a test Raspberry Pi with Pi camera running Motion
> (which was installed from apt) has abruptly ceased to function.
>
> A bit more background: Fully functioning, weekly updated/upgraded
> Raspberry Pi with motion.conf simply taking a photo upon identifying the
> default amount of motion. After my upgrade yesterday, motion no longer
> likes the config. I didn't change anything in motion.conf. It all just
> stopped working immediately after my weekly apt update/upgrade of this Pi.
>
> ~ tail motion.log:
> v4l2_select_input: Device does not support specifying PAL/NTSC norm
> followed by:
> v4l2_do_set_pix_format: Error setting pixel format
>
> Anybody have any idea what changed causing this simple setup to no longer
> work?
>
>
>
>
> Sent with ProtonMail <https://protonmail.com> Secure Email.
>
> _______________________________________________
> 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 176, Issue 24
********************************************
