MichaIng
commented
5 months ago Since you are using motionEyeOS, and a fork of it, please check back with @jawsper, since this is a OS-side issue. With plain motionEye on RPi OS (legacy/Bullseye), it does work when disabling KMS and enabling the legacy camera stack via start_x=1.
When using Raspberry Pi OS Bookworm, the legacy camera stack has been removed completely, and the only way to allow motion receiving an RPi camera module stream then is via libcamerify wrapper. See some issues around this here: https://github.com/motioneye-project/motioneye/issues?q=is%3Aopen+is%3Aissue+libcamerify
I am using a raspberry pi Zero 2 W, with a pi cam rev 1.3. When i first started experimenting with it, it was having the same issue, either used to show a black screen with a no camera logo on it or a camera not detected gray screen. Idk how but it somehow got solved after 3-4 days automatically (after working around 8-9 hours on it) and i stopped looking into it for everything was working perfectly. I had kept it isolated for around 10 days while i was creating the power source for my camera and when i again turned it on it just refused to show the image saying the exact problem that was before.
More specifications- 1)Somehow it is saying that supported=1 and detected=1 2)The bcm2835-v4l2 module is installed 3)I am using jawspers version for compatibility - https://github.com/jawsper/motioneyeos/releases/tag/20220119-dev 4)I tried using the first power supply as well, telling if it helps. 5)I have been adding and inputting all commands to it through ssh as i do not have a compatible mouse or keyboard 6)Tried reuploading the image about 25 times, tried downloading 2 more images of the same os and experimenting with them as well, same prolem Would be extremely hellp if any1 can help