Hello,
can’t get motioneye work with a camera module 3 on a Raspberry Pi 3.
Much information about installation around, some of it quite old.
So…anyone has a guide how to get it running with the latest dietpi version?
So?..
Anything new with trixie & motioneye (new or old camera)?
maybe better to ask this question on Motioneye GitHub.
I got it to run with motion (on RPi 3 and a camera module 3), but not motioneye. Idk if this would be enough for you?
Stop the motioneye service and then run motion with libcamerify:
libcamerify motion
Now you can watch the stream at port 8080 (default motion config)
According to this, it should also work with motioneye
https://github.com/motioneye-project/motioneye/issues/2900#issuecomment-1870273642
/usr/bin/libcamerify /home/python-venv/bin/meyectl startserver -c /etc/motioneye/motioneye.conf
but it fails on my RPi 3. I will have another look tomorrow.
I got it to work!
Activate the cam in dietpi-cpnfig.
Then we need libcamera-tools it comes withlibcamerify.
If you want to test if your camera is recognized, you can also install libcamera-apps
apt install libcamera-tools libcamera-apps
rpicam-hello --list-cameras
This should output the connected cams.
Then we need to change the service file for motioneye:
nano /etc/systemd/system/motioneye.service
You just need to add the this /usr/bin/libcamerify to the ExecStart= before anything else, like:
ExecStart=/usr/bin/libcamerify /usr/local/bin/meyectl startserver -c /etc/motioneye/motioneye.conf
Save the file, and restart the service:
systemctl daemon-reload
systemctl restart motioneye
1 Like
Can somebody else test this for verification?
Maybe we should implement this, since the legacy stack does not work anymore on trixie? @MichaIng
I aim to implement this right into motionEye, as part of the motioneye_init command: Cannot add ov5647 CSI camera - unable to open video device · Issue #3183 · motioneye-project/motioneye · GitHub
But what I want to test is whether wrapping the whole motionEye process into libcamerify can cause issues with other attached cameras, and whether instead wrapping it around the particular motion processes is a better approach. There is an open PR which does it that way: Implement libcamerify support for motion binary by strips · Pull Request #2765 · motioneye-project/motioneye · GitHub
1 Like
It works with Camera Module 3 Wide, thank you.
I did have to add camera_auto_detect=0 and dtoverlay=imx708 to the config.txt file, and then run apt install libcamera-tools libcamera-apps so that rpicam-hello --list-cameras would report a working camera.
Oddly enough, vcgencmd get_camera returns:
supported=1 detected=0 libcamera interfaces=1, but it still works.
Greetings from Germany (translated with Google Translate)
I am using a pi zero and I bought a Camera module 3 NOIR.
Will it be able to run motion eye?
Maybe something to ask the Motion Project on their Github repository