Return to Question

I have installed the UV4L suite of software onto RPi3 with Jessie. I am using a USB cam (Logitech C170) rather than RPi cam. I have been struggling to get this working reliably.

Initially I could not get anything working at port 8080. Finally I worked out (as it is not clear from the online instructions) that USB webcams trigger a streaming server at port 8090 NOT at port 8080.

I rebuilt my Pi three times in order to test different approaches to getting this software working. With the most recent approach I avoided installing the auto start script..as I was suspecting some other background process was causing issues. Now when I manually start things I get the below:

pi@PI3_TWO:~ $ uv4l --enable-server --device-path 001:004 --config-file /etc/uv4l/uv4l-uvc.conf
<notice> [core] Trying to load driver 'uvc' from built-in drivers first...
<warning> [core] Driver 'uvc' not found
<notice> [core] Trying to load driver 'uvc' from external plug-in's instead...
<notice> [driver] Device found at specified path
<notice> [driver] Video functionality 'Webcam C170' recognized at 001:004
<notice> [core] Device detected!
<warning> [core] Cannot create /dev/video0 because file already exists
<notice> [core] Registering device node /dev/video1

Why would it be not initially finding the uvc driver, and what is external plugins? Why is there already a video0 file...and is this a problem? The streaming server now does not display...yet there is no error about it not starting. How can I debug this?

I have installed the UV4L suite of software onto RPi3 with Jessie. I am using a USB cam (Logitech C170) rather than RPi cam. I have been struggling to get this working reliably.

Initially I could not get anything working at port 8080. Finally I worked out (as it is not clear from the online instructions) that USB webcams trigger a streaming server at port 8090 NOT at port 8080.

I rebuilt my Pi three times in order to test different approaches to getting this software working. With the most recent approach I avoided installing the auto start script..as I was suspecting some other background process was causing issues. When I manually start things after a reboot I get the issues below:

pi@PI3_TWO:~ $ uv4l --enable-server --device-path 001:004 --config-file /etc/uv4l/uv4l-uvc.conf
<notice> [core] Trying to load driver 'uvc' from built-in drivers first...
<warning> [core] Driver 'uvc' not found
<notice> [core] Trying to load driver 'uvc' from external plug-in's instead...
<notice> [driver] Device found at specified path
<notice> [driver] Video functionality 'Webcam C170' recognized at 001:004
<notice> [core] Device detected!
<warning> [core] Cannot create /dev/video0 because file already exists
<notice> [core] Registering device node /dev/video1

Why would it be not initially finding the uvc driver, and what is external plugins? Why is there already a video0 file...and is this a problem?

But more importantly, The streaming server displays, and I have it configured for https. It displays the MJPEG stream fine. But the display will not work with the WebRTC or conerencing options. I just see a black screen. I want to get this working. I have enabled the major WebRTC options in the config, but it still doesnt work. How can I debug / get the camera working with the WebRTC and conference options?

I have installed the UV4L suite of software onto RPi3 with Jessie. I am using a USB cam (Logitech C170) rather than RPi cam. I have been struggling to get this working reliably.

Initially I could not get anything working at port 8080. Finally I worked out (as it is not clear from the online instructions) that USB webcams trigger a streaming server at port 8090 NOT at port 8080.

I rebuilt my Pi and installed again and things seem to be working a bit better. I have https configured and the streaming server works OK (although it always requires a second page refresh to show the video). However I dont get a picture when using the WebRTC capability...either in the local conference or when using Jitsi. Ideally I want both of these to work so i can use the Pi as a doorbell that will either call my Pi inside or initiate a call to the server when I am out.

Are there any special settings I need in the config for webRTC to work that I have perhaps missed?

I have installed the UV4L suite of software onto RPi3 with Jessie. I am using a USB cam (Logitech C170) rather than RPi cam. I have been struggling to get this working reliably.

Initially I could not get anything working at port 8080. Finally I worked out (as it is not clear from the online instructions) that USB webcams trigger a streaming server at port 8090 NOT at port 8080.

I rebuilt my Pi three times in order to test different approaches to getting this software working. With the most recent approach I avoided installing the auto start script..as I was suspecting some other background process was causing issues. Now when I manually start things I get the below:

pi@PI3_TWO:~ $ uv4l --enable-server --device-path 001:004 --config-file /etc/uv4l/uv4l-uvc.conf
<notice> [core] Trying to load driver 'uvc' from built-in drivers first...
<warning> [core] Driver 'uvc' not found
<notice> [core] Trying to load driver 'uvc' from external plug-in's instead...
<notice> [driver] Device found at specified path
<notice> [driver] Video functionality 'Webcam C170' recognized at 001:004
<notice> [core] Device detected!
<warning> [core] Cannot create /dev/video0 because file already exists
<notice> [core] Registering device node /dev/video1

Why would it be not initially finding the uvc driver, and what is external plugins? Why is there already a video0 file...and is this a problem? The streaming server now does not display...yet there is no error about it not starting. How can I debug this?

I have installed the UV4L suite of software onto RPi3 with Jessie. I am using a USB cam (Logitech C170) rather than RPi cam. Configuration of UV4L seems to require an in-depth understanding of Linux and video, which I unfortunately dont have.

On bootup the streaming server at http://IP Addr:8080 displays fine but none of the camera streams on that site show an image. If I run "dd if=/dev/video0 of=snapshot.jpeg bs=11M count=1" I get "failed to open ‘/dev/video0’: Operation not permitted". If I change the device to video1 or video2 it runs successfully, but the resulting jpegs seem corrupt, as they will not display in a browser.

  I killed all of the u4vl processes (sudo was required), as I expect things were starting with the wrong defaults. After doing that I cant restart the server: no matter how I try to start Uv4l I get "[core] No device detected".

Update

Its not entirely clear from the online instructions, but USB webcams trigger a streaming server at port 8090 NOT at port 8080. (Strangely it still runs a server at 8080 even though I dont have a pi camera). The problem I have now is the streaming service at 8090 only works once I run "sudo service uv4l_raspicam restart" after any reboot. It is also confusing that when I run "uv4l -t –list-drivers" it returns an empty list and "uv4l –driver-help" returns "[core] No device detected"...even when my USB camera is successfully streaming.

Update

I came back to this to do some more debugging and now I find that "sudo service uv4l_raspicam restart" does not even work to get the USB cam streaming service started.

How can I debug the UV4L driver and streaming server or otherwise get it reliably working with a USB camera?

I have installed the UV4L suite of software onto RPi3 with Jessie. I am using a USB cam (Logitech C170) rather than RPi cam. I have been struggling to get this working reliably.

Initially I could not get anything working at port 8080. Finally I worked out (as it is not clear from the online instructions) that USB webcams trigger a streaming server at port 8090 NOT at port 8080. 

I rebuilt my Pi and installed again and things seem to be working a bit better. I have https configured and the streaming server works OK (although it always requires a second page refresh to show the video). However I dont get a picture when using the WebRTC capability...either in the local conference or when using Jitsi. Ideally I want both of these to work so i can use the Pi as a doorbell that will either call my Pi inside or initiate a call to the server when I am out.

Are there any special settings I need in the config for webRTC to work that I have perhaps missed?