Camera image is not visible. Visiting http://octopi.local/webcam/stream returns a server error. The device is connected. I verified this by running libcamera-hello --list-cameras from the CLI.
Any troubleshooting tips would be appreciated. Thanks!
The 'server error' message from camera-streamer is an upstream issue that we're waiting on being resolved. Not quite sure what's causing it or what needs to change just yet. It seemed to be related to not opening the stream within a certain time of the Pi booting, but not sure.
Usually, if you restart the service on the command line (sudo camera-streamer-control restart on the new stack) it comes back online.
Until it is patched upstream, there is no other resolution. This is also why the new stack is not the default yet - although I appreciate it's your only option for the V3 camera.
@ Charlie_Powell Just as a FYI, I have experienced the same error (Server Error) when browsing to http://octopi.local/webcam/stream (including all variants - :8080, using IP address, etc.) and I am using a "no-name" camera module that used to work on the old camera stack. When I run the libcamera-hello --list-cameras from the CLI I get the following:
pi@octopi:~ $ sudo camera-streamer-control restart
[sudo] password for pi:
Running restart for camera-streamer-libcamera.service...
... done.
Running restart for camera-streamer-usb-default.path...
... done.
and it didn't seem to do anything! I refreshed the GUI in the browser, then checking the OctoPrint Command & Control tab, I still get a spinning wheel as indicated in the image.
I tried adding the camera=auto into the /boot/config.txt file but that didn't seem to make a difference for me. Thanks for the info. I'll give almost anything a crack to get this working. Cheers.
I had a similar issue that got far worst after adding my second and third camera.
The "Server errors" would appear, and the error is somewhat random. e.g. If I have three cameras installed or four with a RaspiCam the errant server would move to a different stream or to more than one stream each time I rebooted the Pi4 I am using.
I temporarily got around it by lowering the streaming resolution as much as possible, e.g. 320x240 @ 15 FPS. All streams became viewable with no "server error" after doing that.
Then I worked backward increasing the resolution one stream at a time until the error re-appeared, and backed down again.
There seems to be some delay when switching streams from the client side.