Open ejwjohn opened 7 months ago
Please paste the motionEye server logs:
journalctl -u motioneye
Did you try it with only the USB camera and/or only 1 network camera, to rule out that it is a bandwidth or load issue? And does it work when you add the network camera as MJPEG camera (direct stream without passing through motion/motionEye), in case it does provide an MJPEG stream?
OK, thanks for the info about the journal command, when I did that I noted that there were a lot of failures due to the camera failed authorization.
so I did a few tests and put in a known incorrect password in the camera setup stage and Motioneye accepted it??? this would appear to be a BUG.
Now that I have resolved my password issue I was using an out-of-date version ..my mistake) I can now see the image for the RTSP cameras
However the directly connected USB camera still does not function, and when I execute the journalctl command you suggested I cannot see any entries for today's date, as I wanted to see what is happening with the USB camera. I have no experience of using the journalctl command so could you give me some pointers please I have looked at the man page but cannot see anything of use. also is there a way to export this log file where is it stored exactly?
Thanks JohnW
Hello, Ref my request for guidance on using journalctl I have found what I was looking for and managed to get the logs that impact the USB camera.
For some reason, motioneye thinks the camera I am using does not support capturing. which does not sound correct, I use this as a normal camera on my MAC and I have used it for Zoom etc. i have tried to configure it as MMAl but there system cannot find any compatible cameras?
One final comment is issue 2972 the same as my report here???
Have installed Motioneye 043.1b1. on a new image of Bullseye on Rpi 3B.
2 existing fully functioning networked cameras connected to Motioneye as RSTP using port 554 not getting camera image.
1 local USB camera connected as V4L2 same results as the RTSP cameras.
Ref the RTSP cameras tried TCP and UDP same results, also tried Sub and Main view options within the RTSP:// statement.
No Change.