Best way to install motion on RPI Bullseye 64bit ?

[KarlBaumann]

Hi!

I noticed there is no PI version available in the latest releases. What would be the best way to install motion on RPI 4 with a RPI camera?

[Mr-Dave]

Building from source is your only option. I personally prefer to use the create a deb file.

https://motion-project.github.io/motion_build.html

[KarlBaumann]

Thanks for the reply @Mr-Dave!

I tried to build it, but there are some errors
bullseye_motion_4.5.0+dirty20221030-28de590-buildlog-any.txt

[Mr-Dave]

This is strange. It seems that somehow mmal was put onto the computer and it then reports that it isn't compatible with the infrastructure.

1. Can you confirm that you are starting with a "vanilla" base OS and didn't do anything unusual with respect to trying to install 32b packages.
2. Can you confirm that when you run the following commands it returns something? pkg-config --libs mmal

I'll try to do some research on this too...

[KarlBaumann]

pi@lv-pi:~ $ pkg-config --libs mmal
-lmmal -lmmal_core -lmmal_util -lmmal_vc_client -lbcm_host -lvcsm -lvcos

Should be pretty clean. Overlay-FS is enabled. Legacy Cam support is disabled.
If you want, I can give you ssh access.

Ahh, and I also did a full-upgrade.

[Mr-Dave]

A revision to the builddeb script has been pushed that should resolve this issue.

[KarlBaumann]

still does not seem to work :(
bullseye_motion_4.5.0+dirty20221030-28de590-buildlog-aarch64.txt

[Mr-Dave]

Can you make sure you have the new builddeb.sh script? The new one reports on the screen a PKGARCH:

such as

Using Username: AdhocBuild, User Email: [email protected], Git Branch: master, Install Pkgs: N, Arch: armv7l, PKGARCH: armhf

[KarlBaumann]

I have the one from the master branch

pi@lv-pi:~ $ ./builddeb.sh

Usage:    builddeb.sh name email <optional branch>
Name:     Name to use for deb package must not include spaces
Email:    Email address to use for deb package
Branch:   The git branch name of Motion to build (If none specified, uses master)
Install:  Install required packages
Arch:     Architecture


Using Username: AdhocBuild, User Email: [email protected], Git Branch: master, Install Pkgs: N, Arch: aarch64, PKGARCH: arm64

All packages installed
Cloning into 'motion'...
remote: Enumerating objects: 8010, done.
remote: Counting objects: 100% (582/582), done.
remote: Compressing objects: 100% (271/271), done.
remote: Total 8010 (delta 395), reused 465 (delta 306), pack-reused 7428
Receiving objects: 100% (8010/8010), 7.58 MiB | 3.08 MiB/s, done.
Resolving deltas: 100% (5984/5984), done.
Already on 'master'
Your branch is up to date with 'origin/master'.
Cloning into 'motion-packaging'...
remote: Enumerating objects: 177, done.
remote: Counting objects: 100% (64/64), done.
remote: Compressing objects: 100% (46/46), done.
remote: Total 177 (delta 31), reused 45 (delta 18), pack-reused 113
Receiving objects: 100% (177/177), 119.50 KiB | 1.49 MiB/s, done.
Resolving deltas: 100% (63/63), done.
Version: 4.5.0+dirty20221030-28de590
Building package....
Build Error.  Check build log
saved in /home/pi
pi@lv-pi:~ $

[Mr-Dave]

That is still the old one. You need to update it with the current version via a get pull or wget. Note the following line in the repo version.

[KarlBaumann]

I get it using wget every time: wget https://raw.githubusercontent.com/Motion-Project/motion-packaging/master/builddeb.sh

[KarlBaumann]

I think there was some horizontal scrolling necessary to see this :)

[Mr-Dave]

This is a raspbian distro right? i.e. what is the output of lsb_release -a

[KarlBaumann]

pi@lv-pi:~ $ lsb_release -a
No LSB modules are available.
Distributor ID:	Debian
Description:	Debian GNU/Linux 11 (bullseye)
Release:	11
Codename:	bullseye

[KarlBaumann]

this one

[Mr-Dave]

Ok....not Raspbian....The script needs to be changed. Essentially putting into the debian section the condition that was added to the raspian section. (e.g. This line )

[KarlBaumann]

yeah, that looks better! tnx

pi@lv-pi:~ $ sudo gdebi bullseye_motion_4.5.0+dirty20221030-28de590-1_arm64.deb
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Reading state information... Done

Video camera capture program supporting motion detection
 Motion is a program that monitors the video signal from
 one or more cameras and is able to detect if a significant
 part of the picture has changed. Or in other words, it can
 detect motion.
 .
 The output from motion can be image files, videos or execution
 of user provided scripts.
 .
 Also, Motion has its own web server to provide output via a browser.
Do you want to install the software package? [y/N]:y
/usr/bin/gdebi:113: FutureWarning: Possible nested set at position 1
  c = findall("[[(](\S+)/\S+[])]", msg)[0].lower()
Selecting previously unselected package motion.
(Reading database ... 50762 files and directories currently installed.)
Preparing to unpack bullseye_motion_4.5.0+dirty20221030-28de590-1_arm64.deb ...
Unpacking motion (4.5.0+dirty20221030-28de590-1) ...
Setting up motion (4.5.0+dirty20221030-28de590-1) ...
Adding group `motion' (GID 114) ...
Done.
Adding system user `motion' (UID 110) ...
Adding new user `motion' (UID 110) with group `motion' ...
Not creating home directory `/var/lib/motion'.
Adding user `motion' to group `video' ...
Adding user motion to group video
Done.
Created symlink /etc/systemd/system/multi-user.target.wants/motion.service → /lib/systemd/system/motion.service.
Processing triggers for man-db (2.9.4-2) ...
pi@lv-pi:~ $

[KarlBaumann]

Sorry for the noob question, but from the docs I understand that it should be running with

pi@lv-pi:~ $ libcamerify motion
-bash: libcamerify: command not found

Where do I get that libcamerify ?

[Mr-Dave]

Not sure anyone has tried that on a arm64 distro so unsure if it will work.

From a previous discussion here it is indicated that is in the libcamera-tools package. (Again, not sure if it will work or whether that package even exists outside of Raspbian 32bit.)

[KarlBaumann]

it almost works

pi@lv-pi:~ $ libcamerify motion
[0:motion] [NTC] [ALL] conf_load: Processing thread 0 - config file /etc/motion/motion.conf
[0:motion] [NTC] [ALL] motion_startup: Logging to syslog
[0:motion] [NTC] [ALL] motion_startup: Motion 4.5.0+dirty20221030-28de590 Started
[0:motion] [NTC] [ALL] motion_startup: Using default log type (ALL)
[0:motion] [NTC] [ALL] motion_startup: Using log type (ALL) log level (NTC)
[0:motion] [NTC] [STR] webu_start_strm: Starting all camera streams on port 8081
[0:motion] [NTC] [STR] webu_strm_ntc: Started camera 0 stream on port 8081
[0:motion] [NTC] [STR] webu_start_ctrl: Starting webcontrol on port 8080
[0:motion] [NTC] [STR] webu_start_ctrl: Started webcontrol on port 8080
[0:motion] [NTC] [ENC] ffmpeg_global_init: ffmpeg libavcodec version 58.91.100 libavformat version 58.45.100
[0:motion] [NTC] [ALL] translate_init: Language: English
[0:motion] [NTC] [ALL] motion_start_thread: Camera ID: 0 is from /etc/motion/motion.conf
[0:motion] [NTC] [ALL] motion_start_thread: Camera ID: 0 Camera Name: (null) Device: /dev/video0
[0:motion] [NTC] [ALL] main: Waiting for threads to finish, pid: 28990
[1:ml1] [NTC] [ALL] motion_init: Camera 0 started: motion detection Enabled
[1:ml1] [NTC] [VID] vid_start: Opening V4L2 device
[1:ml1] [NTC] [VID] v4l2_device_open: Using videodevice /dev/video0 and input -1
[12:30:05.465586682] [28993]  INFO Camera camera_manager.cpp:293 libcamera v0.0.1+21-7c855784
[12:30:05.535886129] [28994]  WARN RPI raspberrypi.cpp:1297 Mismatch between Unicam and CamHelper for embedded data usage!
[12:30:05.537600704] [28994]  INFO RPI raspberrypi.cpp:1414 Registered camera /base/soc/i2c0mux/i2c@1/imx219@10 to Unicam device /dev/media1 and ISP device /dev/media0
[1:ml1] [ERR] [VID] v4l2_device_capability: Not a V4L2 device?
[1:ml1] [ERR] [VID] vid_start: V4L2 device failed to open
[1:ml1] [WRN] [ALL] motion_init: Could not fetch initial image from camera
[1:ml1] [WRN] [ALL] motion_init: Motion continues using width and height from config file(s)
[1:ml1] [NTC] [ALL] image_ring_resize: Resizing pre_capture buffer to 1 items
[1:ml1] [NTC] [ALL] image_ring_resize: Resizing pre_capture buffer to 4 items
[1:ml1] [WRN] [ALL] mlp_retry: Retrying until successful connection with camera
[1:ml1] [NTC] [VID] vid_start: Opening V4L2 device
[1:ml1] [NTC] [VID] v4l2_device_open: Using videodevice /dev/video0 and input -1
[1:ml1] [ERR] [VID] v4l2_device_capability: Not a V4L2 device?
[1:ml1] [ERR] [VID] vid_start: V4L2 device failed to open

[KarlBaumann]

I also tried to add overlay config to the boot/config.txt (as mentioned in #1434 (comment)) , but that did not help

camera_auto_detect=0
dtoverlay=imx477

[Mr-Dave]

You are going to be on your own with the libcamera problems and that is probably a different discussion than this one. This discussion is how to install Motion on a ARM64 distro. (FWIW, my recommendation would be to not use ARM64/Debian if you want to use a PI camera.).

[KarlBaumann]

The 64 bit version feels way more responsive and faster. I think everyone will switch to that soon.

The libcamera itself works fine. I can do stills directly. It's just that motion does not know how to use it.

pi@lv-pi:~ $ libcamera-jpeg -o test2.jpg
Preview window unavailable
[0:09:59.917291375] [1849]  INFO Camera camera_manager.cpp:293 libcamera v0.0.1+21-7c855784
[0:09:59.986064904] [1850]  WARN RPI raspberrypi.cpp:1297 Mismatch between Unicam and CamHelper for embedded data usage!
[0:09:59.987738425] [1850]  INFO RPI raspberrypi.cpp:1414 Registered camera /base/soc/i2c0mux/i2c@1/imx219@10 to Unicam device /dev/media3 and ISP device /dev/media0
[0:09:59.989150060] [1849]  INFO Camera camera.cpp:1026 configuring streams: (0) 1640x1232-YUV420
[0:09:59.989815405] [1850]  INFO RPI raspberrypi.cpp:800 Sensor: /base/soc/i2c0mux/i2c@1/imx219@10 - Selected sensor format: 1640x1232-SBGGR10_1X10 - Selected unicam format: 1640x1232-pBAA
[0:10:05.123951736] [1849]  INFO Camera camera.cpp:1026 configuring streams: (0) 3280x2464-YUV420 (1) 3280x2464-SBGGR10_CSI2P
[0:10:05.125581999] [1850]  INFO RPI raspberrypi.cpp:800 Sensor: /base/soc/i2c0mux/i2c@1/imx219@10 - Selected sensor format: 3280x2464-SBGGR10_1X10 - Selected unicam format: 3280x2464-pBAA
Still capture image received
pi@lv-pi:~ $

[Mr-Dave]

Motion works fine with v4l2 devices.....The libcamera is in the category of "nothing to fix" for Motion.