MichaIng

How does your service look like? The logs show some issue with motion trying to connect/get the stream from the camera but there are also two concurrent motionEye processes. ```sh...

The 64-bit RPi OS does not ship the OMX driver anymore and it does not work with KMS so generally makes sense that it is the same issue as with...

@hrfried Thanks, valuable information. I think we'll go with something like this: https://github.com/motioneye-project/motioneye/pull/2765 A Raspberry Pi 5 with a camera module 3 just arrived here, so I am now able...

> it's interesting that raspberry pi are selling devices which seem to exclusively rely on this library (without any mention of that on the packaging) but don't seem to have...

> moved from something that did v4l compatibility The old stack did not support V4L2, but required those closed source (obscure) `raspivid`/`raspistill` blobs, or do I misunderstand what you mean?...

> My understanding is that `/dev/video0` is a standard v4l device. Ah yes, you are right. I somehow thought that e.g. `v4l2-ctl` is not able to control the camera modules...

> I would strongly discourage this, at least until the MMAL interface is obscure or broken somehow. More compatibility is always better. But as far as I can see, it...

The preferred options for Gmail, which also match their docs is, after this PR, port 465 with TLS. It makes sense that port 465 with TLS did not work before...

So far so good. As said, port 465 is for TLS while port 587 is for "connect without TLS and then switch to TLS for data transfer via STARTTLS protocol",...

Can you show the service logs? ```sh journalctl -u motioneye ``` or if no error is visible there, for errors in browser console? I know it is an issue if...