-
Notifications
You must be signed in to change notification settings - Fork 371
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stream from Raspberry Cam stopped working #798
Comments
This should already be fixed in the nightly builds after I put in #790. If you could test either the Release Candidate or nightly builds that would be wonderful. With the Raspberry Pi cameras, they also still work with the v4l2/uvc mode, so using usb or auto mode should allow the stream to continue working. |
Unluckily I have spotted this in my production environment, thought it might be quite specific and instead of checking issues spent a while to debug and fix it on my own, I might deploy an RC the other day, though and check my h/w setup. BTW thanks for OctoPi, it's great! Upd: I actually took PR you have mentioned and edited the script directly - it works as expected with regex. Hopefully release is somewhere behind the corner. |
Hey, just saw this now - is there anything else left to fix? |
update your instance |
Closing if no reply form OP |
The issue: stream from Raspi Cam v1.3 became unavailable after a casual boot up.
There was an issue with /root/bin/webcamd script because of the output of
vcgencmd get_camera
has been changed from expectedsupported=1 detected=1
tosupported=1 detected=1, libcamera interfaces=0
Solution:
Replace /root/bin/webcamd:219-:220 with
raspi_cam=$(vcgencmd get_camera | sed 's/,.*//' | tr -d \\n) if [ "$raspi_cam" == "supported=1 detected=1" ]; then
It uses sed and tr to trim all the obsolete information, as I assume supported and detected are still fully enough to run the stream. Unluckily I was not patient enough to continue searching for the source code of /root/bin/webcamd for opening a pull request, nevertheless I am fine to do so if someone knows where it is stored.
The text was updated successfully, but these errors were encountered: