mirror of
https://github.com/motioneye-project/motioneye.git
synced 2026-03-02 22:57:06 -05:00
RTSP and V4L2 cameras Grey screen issues #2517
Labels
No labels
Android app
Arch Linux
CI/CD
CSS
FreeBSD
HTML/HTTP
Home Assistant addon
JavaScript
Python
Raspberry Pi
Stale No Activity 60 Days
bug
code format
dependencies
dev branch
docker
documentation
duplicate
enhancement
feature
help wanted
i18n/l10n
invalid
legacy motionEye
meta
motion
motionEyeOS
notourproblem
python update
question
question
security
troubleshooting
wontfix
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/motioneye#2517
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ejwjohn on GitHub (Apr 24, 2024).
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.
@MichaIng commented on GitHub (Apr 24, 2024):
Please paste the motionEye server logs:
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?
@ejwjohn commented on GitHub (Apr 24, 2024):
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
@ejwjohn commented on GitHub (Apr 25, 2024):
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?
@ejwjohn commented on GitHub (Apr 26, 2024):
One final comment is issue 2972 the same as my report here???