Which image for a PI Zero 2? Recent updates?

[My D]

Read this article and everything seemed straightforward... and then I got into the nitty gritty.

https://github.com/motioneye-project/motioneyeos/releases hasn't been updated in five years.

Releases doesn't list the board listed and linked in the article above. Which image should I use from https://github.com/motioneye-project/motioneyeos/releases to load on to a R Pi Zero 2?

If anyone has experience with the case linked from the top article, I have questions about the camera mount. Can't find a picture of it ANYWHERE or an install guide.

This is what I bought.

[StarbaseSSD]

For a working image of motionEyeOS for RPi02W:

https://github.com/motioneye-project/motioneyeos/issues/2875

My personal suggestion is RPiOS Lite Buster (10), and motionEye 0.42.1, instructions here:
https://github.com/motioneye-project/motioneye/wiki/Install-On-Raspbian

or 

RPiOS Bookworm and motionEye 0.43.1b4, here:

https://github.com/motioneye-project/motioneye#installation

Can't help with the case you link to.

[My D]

Tried the first one because the other two look like they take a lot more fiddling, and I get an infinite boot/crash loop that gets to "configuring wired network: no device" and "rebooting: caused by network."

Appreciate the help.

[StarbaseSSD]

Did you include a wpa_supplicant.conf file with your wifi network information, or a set of files to set it up as an access point?
a wpa_supplicant.conf file should follow the format:
- - - - -
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1
country=US

network={
    ssid="your ssid"
    psk=your password

}

- - - - -

Also, do NOT use RPiImager, only use Win32DiskImager, Balena Etcher, or dd. RPiImager corrupts 3 partition images like motionEyeOS.
I also am attaching a set of files to set up the access point stand alone function.

[My D]

Appreciate this. Where does the wpa_supplicant.conf go? Root of the install?

[StarbaseSSD]

Right after you image, it goes in the boot partition, the one where you can read the filenames, before you eject it or before first boot.

[My D]

I"m trying to post a new topic about a camera visible via libcamera but grey screen in MotionEye, but every time I post it's instantly deleted.

What's happening?

[StarbaseSSD]

Interesting. I just had my reply deleted too.

[StarbaseSSD]

Hey I tried posting a new conversation in the group about how the IMX219 camera I'm using works in libcamera but shows a grey screen in MotionEye, and it was instantly deleted. A follow up post in this thread was also instantly gone.

I can't see any way to contact the group leader about this. Any idea why this would happen?

Appreciate all your help.

- - - - -

IMX219: I do not know which version of it you are using, and although it's been out since 2016, your make and model nay be post 2020, which would not have been supported in the kernel used in motionEyeOS. 
If the camera works in the latest RPiOS libcamera, I would suggest using the RPiOS Lite, and the instructions here:

https://github.com/motioneye-project/motioneye#installation

As to your other issues, you need to talk with google. The most common issues are words chosen, or links included.

On Wednesday, May 28, 2025 at 12:58:15 PM UTC-4 StarbaseSSD wrote:

[M D]

Thanks. magically, my post is back.

I'm already using Lite. Looks like I may be screwed for using this camera.

[StarbaseSSD]

If you give more info, like manufacturer, model, version #, etc, if it's in RPiOS Lite, I might be able to point you in the right direction. 
The original link doesn't include the camera and the "IMX219" just describes the Sony camera chip itself, not what is driving it. 

[M D]

Linux Dash 6.12.25+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.12.25-1+rpt1 (2025-04-30) aarch64 GNU/Linux

It's an ArduCam 8MP IMX219.

Hope this info is useful:

libcamera-hello

[24:42:25.416310409] [3933]  INFO Camera camera_manager.cpp:326 libcamera v0.5.0+59-d83ff0a4

[24:42:25.543489043] [3937]  WARN RPiSdn sdn.cpp:40 Using legacy SDN tuning - please consider moving SDN inside rpi.denoise

[24:42:25.553553312] [3937]  INFO RPI vc4.cpp:447 Registered camera /base/soc/i2c0mux/i2c(at-sign)1/imx219(at-sign)10 to Unicam device /dev/media3 and ISP device /dev/media0

[24:42:25.553704769] [3937]  INFO RPI pipeline_base.cpp:1121 Using configuration file '/usr/share/libcamera/pipeline/rpi/vc4/rpi_apps.yaml'

Preview window unavailable

Mode selection for 1640:1232:12:P

    SRGGB10_CSI2P,640x480/0 - Score: 4504.81

    SRGGB10_CSI2P,1640x1232/0 - Score: 1000

    SRGGB10_CSI2P,1920x1080/0 - Score: 1541.48

    SRGGB10_CSI2P,3280x2464/0 - Score: 1718

    SRGGB8,640x480/0 - Score: 5504.81

    SRGGB8,1640x1232/0 - Score: 2000

    SRGGB8,1920x1080/0 - Score: 2541.48

    SRGGB8,3280x2464/0 - Score: 2718

[24:42:25.571136393] [3933]  INFO Camera camera.cpp:1205 configuring streams: (0) 1640x1232-YUV420 (1) 1640x1232-SBGGR10_CSI2P

[24:42:25.571928785] [3937]  INFO RPI vc4.cpp:622 Sensor: /base/soc/i2c0mux/i2c@1/imx219@10 - Selected sensor format: 1640x1232-SBGGR10_1X10 - Selected unicam format: 1640x1232-pBAA

[StarbaseSSD]

Try 640x480x10fps in Settings, Video Device. Reboot

If that works, up it to 800x600x10fps and reboot.

keep increasing until it doesn't work. 

[M D]

Do I need to reboot each time, or can I just restart Motioneye?

640x480 @10fps was no change--still grey screen.

Found another diagnostic tool that gave me this.

v4l2-ctl --list-devices

unicam (platform:3f801000.csi):

/dev/video1

/dev/media2

bcm2835-codec-decode (platform:bcm2835-codec):

/dev/video10

/dev/video11

/dev/video12

/dev/video18

/dev/video31

bcm2835-isp (platform:bcm2835-isp):

/dev/video13

/dev/video14

/dev/video15

/dev/video16

/dev/video20

/dev/video21

/dev/video22

/dev/video23

/dev/media0

/dev/media1

[M D]

And after a reboot of the Pi, still grey screen.

[StarbaseSSD]

What choice are you making for:

Add Camera:

Camera Type: V4L2 or mmal?

Camera: (what /dev)?

[M D]

v4L2 is the only one that finds the camera. 

/dev/media2

[M D]

And under v24l the selection is "unicam" by default. I could choose other options, but in trying those it had the same result previously.

[StarbaseSSD]

I would try /dev/video10 (what my PiZero webcam uses). at 640x480x10FPS. 

If that doesn't work, I don't know. I would go with motionEye 0.43.1b4, it seems to work. 

[M D]

I removed the pi camera and re-added it and it picked up /dev/video10 this time. Still grey image.

[M D]

I was pretty sure I was running the recommended version 0.43.1.b4, and I am:

sudo python3 -m pip install --pre motioneye --break-system-packages

Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple

Requirement already satisfied: motioneye in /usr/local/lib/python3.11/dist-packages (0.43.1b4)

Requirement already satisfied: tornado>=6.5.0 in /usr/local/lib/python3.11/dist-packages (from motioneye) (6.5.1)

Requirement already satisfied: jinja2 in /usr/local/lib/python3.11/dist-packages (from motioneye) (3.1.6)

Requirement already satisfied: pillow in /usr/local/lib/python3.11/dist-packages (from motioneye) (11.2.1)

Requirement already satisfied: pycurl in /usr/local/lib/python3.11/dist-packages (from motioneye) (7.45.6)

Requirement already satisfied: babel in /usr/local/lib/python3.11/dist-packages (from motioneye) (2.17.0)

Requirement already satisfied: boto3 in /usr/local/lib/python3.11/dist-packages (from motioneye) (1.38.25)

Requirement already satisfied: botocore<1.39.0,>=1.38.25 in /usr/local/lib/python3.11/dist-packages (from boto3->motioneye) (1.38.25)

Requirement already satisfied: jmespath<2.0.0,>=0.7.1 in /usr/local/lib/python3.11/dist-packages (from boto3->motioneye) (1.0.1)

Requirement already satisfied: s3transfer<0.14.0,>=0.13.0 in /usr/local/lib/python3.11/dist-packages (from boto3->motioneye) (0.13.0)

Requirement already satisfied: MarkupSafe>=2.0 in /usr/local/lib/python3.11/dist-packages (from jinja2->motioneye) (3.0.2)

Requirement already satisfied: python-dateutil<3.0.0,>=2.1 in /usr/local/lib/python3.11/dist-packages (from botocore<1.39.0,>=1.38.25->boto3->motioneye) (2.9.0.post0)

Requirement already satisfied: urllib3!=2.2.0,<3,>=1.25.4 in /usr/lib/python3/dist-packages (from botocore<1.39.0,>=1.38.25->boto3->motioneye) (1.26.12)

Requirement already satisfied: six>=1.5 in /usr/lib/python3/dist-packages (from python-dateutil<3.0.0,>=2.1->botocore<1.39.0,>=1.38.25->boto3->motioneye) (1.16.0)

[StarbaseSSD]

I don't know when you switched to the motionEye from motionEyeOS, but it can and does make a difference. I was trying to help with motionEyeOS on a {iZero2W as you said the motionEye install looked likie a lot more 'fiddling'. For motionEye 0.43.1b4 you need to shift over to their support site (different devs)

https://github.com/motioneye-project/motioneye/issues 

and file an issue.