Unable to Run webcamd2 for a Second usb Camera in Octopi 0.17.0

Salty-Doug · January 16, 2020, 8:29am

Camera model
Camera 1: Logitech C525, USB HD c
Camera 2: UNIQUESKY_CAR_CAMERA (USB endoscope)

What is the problem?
I see one camera on the primary feed on port 8080 but I don't see the second camera feed on port 8081. I am viewing octopi.local with firefox on my Mac os 10.16.5. Octopi is on a Raspberry Pi 3 B+.
What did you already try to solve it?
I installed the Octopi 0.17.0 image onto a mini SD card and configured the network. It boots and runs my printer.
I have installed the MultiCam plugin.
I followed these instructions to setup the two camera daemons.
I also viewed Chris Riley's video after the above instructions did not work.
I followed these instructions to make the scripts. to start the webcam2 daemon. That did not work either.
I followed a suggestion from OutsourcedGuru and added the webcamd2.service file in /etc/systemd/system. After creating that file, the webcam2 service tried to start but has an error.

I can see the webcamd service running but the webcam2 service is dead. See below:
webcamd2.service.txt.zip (838 Bytes)

pi@octopi:~ $ 
[sudo] password for pi: 
● webcamd2.service - the OctoPi webcam daemon with the user specified config
   Loaded: loaded (/etc/systemd/system/webcamd2.service; disabled; vendor preset
   Active: inactive (dead)

Logs (/var/log/webcamd.log, syslog, dmesg, ... no logs, no support)
I do not see the webcamd.log:

pi@octopi:~ $ cd /var/log/
pi@octopi:/var/log $ ls
alternatives.log  fontconfig.log                syslog
apt               haproxy.log                   syslog.1
auth.log          haproxy.log.1                 syslog.2.gz
bootstrap.log     haproxy.log.2.gz              syslog.3.gz
btmp              kern.log                      user.log
daemon.log        lastlog                       uvcdynctrl-udev.log
debug             messages                      wtmp
dpkg.log          private
faillog           regenerate_ssh_host_keys.log

pi@octopi:~ $ cat /var/log/haproxy.log
Jan 16 00:02:17 octopi haproxy[577]: [WARNING] 015/000217 (577) : Setting tune.ssl.default-dh-param to 1024 by default, if your workload permits it you should set it to at least 2048. Please set a value >= 1024 to make this warning disappear.

Additional information about your setup (OctoPrint version, OctoPi version, ...)
OctoPrint version : 1.3.12
OctoPi version : 0.17.0
Rasberry Pi 3B+
Mac Os 10.14.5 Mojave
Firefox for Mac Browser.

Does anyone have an idea why the second webcam daemon is not running?
How can I enable logging for the webcam daemon?

Thanks in advance.

PrintedWeezl · January 16, 2020, 8:58am

Please upload all scripts you created - maybe there is a simple typo (zip them for the upload).

Also post the output of v4l2-ctl --list-devices

Salty-Doug · January 16, 2020, 6:20pm

pi@octopi:~/scripts $ v4l2-ctl --list-devices
bcm2835-codec-decode (platform:bcm2835-codec):
/dev/video10
/dev/video11
/dev/video12

UNIQUESKY_CAR_CAMERA: Integrate (usb-3f980000.usb-1.3):
/dev/video0
/dev/video1

HD Webcam C525 (usb-3f980000.usb-1.5):
/dev/video2
/dev/video3

This zip file contains both script files:
Archive.zip (1.9 KB)

Thanks in advance.

PrintedWeezl · January 16, 2020, 9:52pm

try to replace

camera_usb_options="-r 640x480 -f 20-d /dev/video0"

with

camera_usb_options="-r 640x480 -f 20 -d /dev/video2"

Salty-Doug · January 17, 2020, 6:00am

Hi,
Good catch!
I changed video0 to video1 to agree with my other configuration files which didn't work then video2 which didn't work either. The second camera is recognized by the Raspberry pi OS now since the illumination led's are powered up now but I still don't see a picture on port 8081 and the webcamd2 daemon is not running.

Best.
Salty Doug

ULTIMAKER · January 17, 2020, 10:12am

Hi Salty Doug, I have the same problem as you! If I disconnect the first (webcamd) the second webcam can be started. And if you lookup the status from your second webcam (webcamd2) what ist the result from:
service webcamd2 status
● webcamd2.service - the OctoPi webcam daemon with the user specified config Loaded: loaded (/etc/systemd/system/webcamd2.service; enabled; vendor preset: enabled) Active: active (running) since Thu 2020-01-16 14:42:55 CET; 1h 5min ago Process: 375 ExecStart=/root/bin/webcamd2 (code=exited, status=0/SUCCESS) Main PID: 461 (mjpg_streamer) Tasks: 3 (limit: 2077) Memory: 1.9M CGroup: /system.slice/webcamd2.service └─461 ./mjpg_streamer -o output_http.so -w ./www-octopi -n -i input_uvc.so -d /dev/VideoLogitech -r 640x480 -f 10 Jan 16 14:42:55 octopi mjpg_streamer[461]: MJPG-streamer [461]: www-folder-path......: ./www-octopi/ Jan 16 14:42:55 octopi mjpg_streamer[461]: MJPG-streamer [461]: HTTP TCP port........: 8080 Jan 16 14:42:55 octopi mjpg_streamer[461]: MJPG-streamer [461]: HTTP Listen Address..: (null) Jan 16 14:42:55 octopi mjpg_streamer[461]: MJPG-streamer [461]: username:password....: disabled Jan 16 14:42:55 octopi mjpg_streamer[461]: MJPG-streamer [461]: commands.............: disabled Jan 16 14:42:55 octopi mjpg_streamer[461]: MJPG-streamer [461]: starting input plugin input_uvc.so Jan 16 14:42:55 octopi mjpg_streamer[461]: MJPG-streamer [461]: starting output plugin: output_http.so (ID: 00) Jan 16 14:42:55 octopi webcamd2[375]: Done bring up all configured video device Jan 16 14:42:55 octopi webcamd2[375]: Goodbye... Jan 16 14:42:55 octopi systemd[1]: Started the OctoPi webcam daemon with the user specified config.
In my case the displayed port is wrong. (webcamd2 configured for port 8081) But port 8080 is in the status, I think this is our problem.

I have configured port 8081 in /bin/root/webcamd2 and in the service webcamd2 as Chris has done.

Carsten

Salty-Doug · January 17, 2020, 6:56pm

Here is what I have this morning:

pi@octopi:/ $ systemctl status webcam2.service
Unit webcam2.service could not be found.

Salty-Doug · January 17, 2020, 7:22pm

I see I did a typo. Here it is again:

pi@octopi:/ $ systemctl status webcamd2.service
● webcamd2.service - the OctoPi webcam daemon with the user specified config
   Loaded: loaded (/etc/systemd/system/webcamd2.service; disabled; vendor preset: enabled)
   Active: failed (Result: start-limit-hit) since Fri 2020-01-17 11:06:19 PST; 14min ago
  Process: 2563 ExecStart=/root/bin/webcamd2 (code=exited, status=0/SUCCESS)

Jan 17 11:06:19 octopi systemd[1]: webcamd2.service: Service RestartSec=100ms expired, scheduling restart.
Jan 17 11:06:19 octopi systemd[1]: webcamd2.service: Scheduled restart job, restart counter is at 5.
Jan 17 11:06:19 octopi systemd[1]: Stopped the OctoPi webcam daemon with the user specified config.
Jan 17 11:06:19 octopi systemd[1]: webcamd2.service: Start request repeated too quickly.
Jan 17 11:06:19 octopi systemd[1]: webcamd2.service: Failed with result 'start-limit-hit'.
Jan 17 11:06:19 octopi systemd[1]: Failed to start the OctoPi webcam daemon with the user specified config.

OutsourcedGuru · January 17, 2020, 7:28pm

In a case like this where you have a game of "musical chairs" when multiple webcams, for example, like to change places then udev rules are your friend. In my case, I have a Smoothieware board and a PyBoard plugged into the same Pi and depending upon the weather, they like to change device slots after a bootup.

Create two rules:

sudo touch /etc/udev/rules.d/99-usb-serial.rules
sudo nano /etc/udev/rules.d/99-usb-serial.rules

Contents of 99-usb-serial.rules (editing for your own idVendor and idProduct values as well as the name of the device you want created):

SUBSYSTEM=="tty", ATTRS{idVendor}=="1d50", ATTRS{idProduct}=="6015", SYMLINK+="smoothieboard"
SUBSYSTEM=="tty", ATTRS{idVendor}=="f055", ATTRS{idProduct}=="9800", SYMLINK+="pyboard"

What you get:

ls -l /dev
  lrwxrwxrwx  1 root root           7 Jan 17 09:39 pyboard -> ttyACM0
  lrwxrwxrwx  1 root root           7 Jan 17 09:39 smoothieboard -> ttyACM1

So you could then have /dev/coolcam and /dev/othercam, for example, and then refer to these from the other configuration files you talked about earlier.

Salty-Doug · January 17, 2020, 7:31pm

Here is my MultiCam configuration:

Salty-Doug · January 17, 2020, 7:34pm

Thanks Outsourced Guru.
I'll add this rules file and let you know what the results are.

ULTIMAKER · January 17, 2020, 7:37pm

and what happended if you unplug the cam for webcamd and cold.boot the pi with the second cam?
service webcamd2 status
can you post the result?
Is webcamd2 now running, but on the false port 8080? - Carsten

Salty-Doug · January 17, 2020, 8:07pm

The webcamd2 service is Dead:
pi@octopi:~ $ systemctl status webcamd2.service
● webcamd2.service - the OctoPi webcam daemon with the user specified config
Loaded: loaded (/etc/systemd/system/webcamd2.service; disabled; vendor preset
Active: inactive (dead)
The webcamd service is running and the second camera feed is working in the browser.

ULTIMAKER · January 17, 2020, 8:12pm

and if you
service webcamd2 start

Salty-Doug · January 17, 2020, 8:17pm

pi@octopi:~ $ ls -l /dev
total 0
crw-r--r-- 1 root root     10, 235 Jan 17 12:02 autofs
drwxr-xr-x 2 root root         580 Jan 17 12:02 block
crw------- 1 root root     10, 234 Jan 17 12:02 btrfs-control
drwxr-xr-x 3 root root          60 Dec 31  1969 bus
crw------- 1 root root     10,  63 Jan 17 12:02 cachefiles
drwxr-xr-x 2 root root        2920 Jan 17 12:02 char
crw------- 1 root root      5,   1 Jan 17 12:08 console
crw------- 1 root root     10,  62 Jan 17 12:02 cpu_dma_latency
crw------- 1 root root     10, 203 Jan 17 12:02 cuse
drwxr-xr-x 7 root root         140 Jan 17 12:02 disk
crw-rw---- 1 root video    29,   0 Jan 17 12:02 fb0
lrwxrwxrwx 1 root root          13 Feb 14  2019 fd -> /proc/self/fd
crw-rw-rw- 1 root root      1,   7 Jan 17 12:02 full
crw-rw-rw- 1 root root     10, 229 Jan 17 12:02 fuse
crw-rw---- 1 root gpio    254,   0 Jan 17 12:02 gpiochip0
crw-rw---- 1 root gpio    254,   1 Jan 17 12:02 gpiochip1
crw-rw---- 1 root gpio    254,   2 Jan 17 12:02 gpiochip2
crw-rw---- 1 root gpio    247,   0 Jan 17 12:02 gpiomem
crw------- 1 root root     10, 183 Jan 17 12:02 hwrng
lrwxrwxrwx 1 root root          12 Feb 14  2019 initctl -> /run/initctl
drwxr-xr-x 4 root root         140 Jan 17 12:02 input
crw-r--r-- 1 root root      1,  11 Jan 17 12:02 kmsg
lrwxrwxrwx 1 root root          28 Feb 14  2019 log -> /run/systemd/journal/dev-log
brw-rw---- 1 root disk      7,   0 Jan 17 12:02 loop0
brw-rw---- 1 root disk      7,   1 Jan 17 12:02 loop1
brw-rw---- 1 root disk      7,   2 Jan 17 12:02 loop2
brw-rw---- 1 root disk      7,   3 Jan 17 12:02 loop3
brw-rw---- 1 root disk      7,   4 Jan 17 12:02 loop4
brw-rw---- 1 root disk      7,   5 Jan 17 12:02 loop5
brw-rw---- 1 root disk      7,   6 Jan 17 12:02 loop6
brw-rw---- 1 root disk      7,   7 Jan 17 12:02 loop7
crw-rw---- 1 root disk     10, 237 Jan 17 12:02 loop-control
drwxr-xr-x 2 root root          60 Jan 17 12:02 mapper
crw-rw---- 1 root video   241,   0 Jan 17 12:02 media0
crw-rw---- 1 root video   241,   1 Jan 17 12:02 media1
crw-rw---- 1 root video   241,   2 Jan 17 12:02 media2
crw-r----- 1 root kmem      1,   1 Jan 17 12:02 mem
crw------- 1 root root     10,  59 Jan 17 12:02 memory_bandwidth
brw-rw---- 1 root disk    179,   0 Jan 17 12:02 mmcblk0
brw-rw---- 1 root disk    179,   1 Jan 17 12:02 mmcblk0p1
brw-rw---- 1 root disk    179,   2 Jan 17 12:02 mmcblk0p2
drwxrwxrwt 2 root root          40 Dec 31  1969 mqueue
drwxr-xr-x 2 root root          60 Jan 17 12:02 net
crw------- 1 root root     10,  61 Jan 17 12:02 network_latency
crw------- 1 root root     10,  60 Jan 17 12:02 network_throughput
crw-rw-rw- 1 root root      1,   3 Jan 17 12:02 null
crw------- 1 root root    108,   0 Jan 17 12:02 ppp
crw-rw-rw- 1 root tty       5,   2 Jan 17 12:10 ptmx
drwxr-xr-x 2 root root           0 Feb 14  2019 pts
brw-rw---- 1 root disk      1,   0 Jan 17 12:02 ram0
brw-rw---- 1 root disk      1,   1 Jan 17 12:02 ram1
brw-rw---- 1 root disk      1,  10 Jan 17 12:02 ram10
brw-rw---- 1 root disk      1,  11 Jan 17 12:02 ram11
brw-rw---- 1 root disk      1,  12 Jan 17 12:02 ram12
brw-rw---- 1 root disk      1,  13 Jan 17 12:02 ram13
brw-rw---- 1 root disk      1,  14 Jan 17 12:02 ram14
brw-rw---- 1 root disk      1,  15 Jan 17 12:02 ram15
brw-rw---- 1 root disk      1,   2 Jan 17 12:02 ram2
brw-rw---- 1 root disk      1,   3 Jan 17 12:02 ram3
brw-rw---- 1 root disk      1,   4 Jan 17 12:02 ram4
brw-rw---- 1 root disk      1,   5 Jan 17 12:02 ram5
brw-rw---- 1 root disk      1,   6 Jan 17 12:02 ram6
brw-rw---- 1 root disk      1,   7 Jan 17 12:02 ram7
brw-rw---- 1 root disk      1,   8 Jan 17 12:02 ram8
brw-rw---- 1 root disk      1,   9 Jan 17 12:02 ram9
crw-rw-rw- 1 root root      1,   8 Jan 17 12:02 random
drwxr-xr-x 2 root root          60 Dec 31  1969 raw
crw-rw-r-- 1 root netdev   10,  57 Jan 17 12:02 rfkill
lrwxrwxrwx 1 root root           7 Jan 17 12:02 serial1 -> ttyAMA0
drwxrwxrwt 2 root root          40 Feb 14  2019 shm
drwxr-xr-x 4 root root         240 Jan 17 12:02 snd
lrwxrwxrwx 1 root root          15 Feb 14  2019 stderr -> /proc/self/fd/2
lrwxrwxrwx 1 root root          15 Feb 14  2019 stdin -> /proc/self/fd/0
lrwxrwxrwx 1 root root          15 Feb 14  2019 stdout -> /proc/self/fd/1
crw-rw-rw- 1 root tty       5,   0 Jan 17 12:02 tty
crw--w---- 1 root tty       4,   0 Jan 17 12:02 tty0
crw--w---- 1 root tty       4,   1 Jan 17 12:02 tty1
crw--w---- 1 root tty       4,  10 Jan 17 12:02 tty10
crw--w---- 1 root tty       4,  11 Jan 17 12:02 tty11
crw--w---- 1 root tty       4,  12 Jan 17 12:02 tty12
crw--w---- 1 root tty       4,  13 Jan 17 12:02 tty13
crw--w---- 1 root tty       4,  14 Jan 17 12:02 tty14
crw--w---- 1 root tty       4,  15 Jan 17 12:02 tty15
crw--w---- 1 root tty       4,  16 Jan 17 12:02 tty16
crw--w---- 1 root tty       4,  17 Jan 17 12:02 tty17
crw--w---- 1 root tty       4,  18 Jan 17 12:02 tty18
crw--w---- 1 root tty       4,  19 Jan 17 12:02 tty19
crw--w---- 1 root tty       4,   2 Jan 17 12:02 tty2
crw--w---- 1 root tty       4,  20 Jan 17 12:02 tty20
crw--w---- 1 root tty       4,  21 Jan 17 12:02 tty21
crw--w---- 1 root tty       4,  22 Jan 17 12:02 tty22
crw--w---- 1 root tty       4,  23 Jan 17 12:02 tty23
crw--w---- 1 root tty       4,  24 Jan 17 12:02 tty24
crw--w---- 1 root tty       4,  25 Jan 17 12:02 tty25
crw--w---- 1 root tty       4,  26 Jan 17 12:02 tty26
crw--w---- 1 root tty       4,  27 Jan 17 12:02 tty27
crw--w---- 1 root tty       4,  28 Jan 17 12:02 tty28
crw--w---- 1 root tty       4,  29 Jan 17 12:02 tty29
crw--w---- 1 root tty       4,   3 Jan 17 12:02 tty3
crw--w---- 1 root tty       4,  30 Jan 17 12:02 tty30
crw--w---- 1 root tty       4,  31 Jan 17 12:02 tty31
crw--w---- 1 root tty       4,  32 Jan 17 12:02 tty32
crw--w---- 1 root tty       4,  33 Jan 17 12:02 tty33
crw--w---- 1 root tty       4,  34 Jan 17 12:02 tty34
crw--w---- 1 root tty       4,  35 Jan 17 12:02 tty35
crw--w---- 1 root tty       4,  36 Jan 17 12:02 tty36
crw--w---- 1 root tty       4,  37 Jan 17 12:02 tty37
crw--w---- 1 root tty       4,  38 Jan 17 12:02 tty38
crw--w---- 1 root tty       4,  39 Jan 17 12:02 tty39
crw--w---- 1 root tty       4,   4 Jan 17 12:02 tty4
crw--w---- 1 root tty       4,  40 Jan 17 12:02 tty40
crw--w---- 1 root tty       4,  41 Jan 17 12:02 tty41
crw--w---- 1 root tty       4,  42 Jan 17 12:02 tty42
crw--w---- 1 root tty       4,  43 Jan 17 12:02 tty43
crw--w---- 1 root tty       4,  44 Jan 17 12:02 tty44
crw--w---- 1 root tty       4,  45 Jan 17 12:02 tty45
crw--w---- 1 root tty       4,  46 Jan 17 12:02 tty46
crw--w---- 1 root tty       4,  47 Jan 17 12:02 tty47
crw--w---- 1 root tty       4,  48 Jan 17 12:02 tty48
crw--w---- 1 root tty       4,  49 Jan 17 12:02 tty49
crw--w---- 1 root tty       4,   5 Jan 17 12:02 tty5
crw--w---- 1 root tty       4,  50 Jan 17 12:02 tty50
crw--w---- 1 root tty       4,  51 Jan 17 12:02 tty51
crw--w---- 1 root tty       4,  52 Jan 17 12:02 tty52
crw--w---- 1 root tty       4,  53 Jan 17 12:02 tty53
crw--w---- 1 root tty       4,  54 Jan 17 12:02 tty54
crw--w---- 1 root tty       4,  55 Jan 17 12:02 tty55
crw--w---- 1 root tty       4,  56 Jan 17 12:02 tty56
crw--w---- 1 root tty       4,  57 Jan 17 12:02 tty57
crw--w---- 1 root tty       4,  58 Jan 17 12:02 tty58
crw--w---- 1 root tty       4,  59 Jan 17 12:02 tty59
crw--w---- 1 root tty       4,   6 Jan 17 12:02 tty6
crw--w---- 1 root tty       4,  60 Jan 17 12:02 tty60
crw--w---- 1 root tty       4,  61 Jan 17 12:02 tty61
crw--w---- 1 root tty       4,  62 Jan 17 12:02 tty62
crw--w---- 1 root tty       4,  63 Jan 17 12:02 tty63
crw--w---- 1 root tty       4,   7 Jan 17 12:02 tty7
crw--w---- 1 root tty       4,   8 Jan 17 12:02 tty8
crw--w---- 1 root tty       4,   9 Jan 17 12:02 tty9
crw-rw---- 1 root dialout 204,  64 Jan 17 12:02 ttyAMA0
crw------- 1 root root      5,   3 Jan 17 12:02 ttyprintk
crw------- 1 root root     10, 239 Jan 17 12:02 uhid
crw------- 1 root root     10, 223 Jan 17 12:02 uinput
crw-rw-rw- 1 root root      1,   9 Jan 17 12:02 urandom
drwxr-xr-x 4 root root          80 Jan 17 12:02 v4l
crw-rw---- 1 root video   243,   0 Jan 17 12:02 vchiq
crw-rw---- 1 root video   248,   0 Jan 17 12:02 vcio
crw------- 1 root root    249,   0 Jan 17 12:02 vc-mem
crw-rw---- 1 root tty       7,   0 Jan 17 12:02 vcs
crw-rw---- 1 root tty       7,   1 Jan 17 12:02 vcs1
crw-rw---- 1 root tty       7,   2 Jan 17 12:02 vcs2
crw-rw---- 1 root tty       7,   3 Jan 17 12:02 vcs3
crw-rw---- 1 root tty       7,   4 Jan 17 12:02 vcs4
crw-rw---- 1 root tty       7,   5 Jan 17 12:02 vcs5
crw-rw---- 1 root tty       7,   6 Jan 17 12:02 vcs6
crw-rw---- 1 root tty       7, 128 Jan 17 12:02 vcsa
crw-rw---- 1 root tty       7, 129 Jan 17 12:02 vcsa1
crw-rw---- 1 root tty       7, 130 Jan 17 12:02 vcsa2
crw-rw---- 1 root tty       7, 131 Jan 17 12:02 vcsa3
crw-rw---- 1 root tty       7, 132 Jan 17 12:02 vcsa4
crw-rw---- 1 root tty       7, 133 Jan 17 12:02 vcsa5
crw-rw---- 1 root tty       7, 134 Jan 17 12:02 vcsa6
crw-rw---- 1 root video   244,   0 Jan 17 12:02 vcsm
crw-rw-rw- 1 root root     10,  58 Jan 17 12:02 vcsm-cma
crw-rw---- 1 root tty       7,  64 Jan 17 12:02 vcsu
crw-rw---- 1 root tty       7,  65 Jan 17 12:02 vcsu1
crw-rw---- 1 root tty       7,  66 Jan 17 12:02 vcsu2
crw-rw---- 1 root tty       7,  67 Jan 17 12:02 vcsu3
crw-rw---- 1 root tty       7,  68 Jan 17 12:02 vcsu4
crw-rw---- 1 root tty       7,  69 Jan 17 12:02 vcsu5
crw-rw---- 1 root tty       7,  70 Jan 17 12:02 vcsu6
crw------- 1 root root     10, 137 Jan 17 12:02 vhci
crw-rw---- 1 root video    81,   0 Jan 17 12:02 video0
crw-rw---- 1 root video    81,   1 Jan 17 12:02 video1
crw-rw---- 1 root video    81,   4 Jan 17 12:02 video10
crw-rw---- 1 root video    81,   5 Jan 17 12:02 video11
crw-rw---- 1 root video    81,   6 Jan 17 12:02 video12
crw-rw---- 1 root video    81,   2 Jan 17 12:02 video2
crw-rw---- 1 root video    81,   3 Jan 17 12:02 video3
crw------- 1 root root     10, 130 Jan 17 12:02 watchdog
crw------- 1 root root    251,   0 Jan 17 12:02 watchdog0
crw-rw-rw- 1 root root      1,   5 Jan 17 12:02 zero

Do I need to edit one of the other daemon/script files to recognize the devices from my rules file, below?

SUBSYSTEM=="video", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="0826", ATTRS{se$
SUBSYSTEM=="video", ATTRS{idVendor}=="1bcf", ATTRS{idProduct}=="0b09", SYMLINK+$

Salty-Doug · January 17, 2020, 8:19pm

SUBSYSTEM=="video", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="0826", ATTRS{serial}=="5755BBA0", SYMLINK+="logitech"
SUBSYSTEM=="video", ATTRS{idVendor}=="1bcf", ATTRS{idProduct}=="0b09", SYMLINK+="borescope"

ULTIMAKER · January 17, 2020, 8:21pm

HERE (Chris on Youtube) you can see how to create the symlinks, and how to find the correct data for it.

Salty-Doug · January 17, 2020, 9:29pm

Thanks Carsten. Chris' videos are very detailed.

Salty-Doug · January 17, 2020, 11:09pm

I am still unable to view the second camera. I can see the first camera, video0, but not the second camera, video2.

I have created the 99-usb.rules file and completed it per Chris Riley's latest Jan 3, 2020 video Here.
I also edited the webcamd2 and webcamd2.service files per his video but I used port 8082 for the second camera.
When I reboot the RPi, webcamd2 service will not start:

pi@octopi:~ $ sudo service webcamd2 status
● webcamd2.service - the OctoPi webcam daemon with the user specified config
   Loaded: loaded (/etc/systemd/system/webcamd2.service; enabled; vendor preset:
   Active: failed (Result: start-limit-hit) since Fri 2020-01-17 14:26:40 PST; 5
  Process: 633 ExecStart=/root/bin/webcamd2 (code=exited, status=0/SUCCESS)

Jan 17 14:26:40 octopi systemd[1]: webcamd2.service: Service RestartSec=100ms ex
Jan 17 14:26:40 octopi systemd[1]: webcamd2.service: Scheduled restart job, rest
Jan 17 14:26:40 octopi systemd[1]: Stopped the OctoPi webcam daemon with the use
Jan 17 14:26:40 octopi systemd[1]: webcamd2.service: Start request repeated too 
Jan 17 14:26:40 octopi systemd[1]: webcamd2.service: Failed with result 'start-l
Jan 17 14:26:40 octopi systemd[1]: Failed to start the OctoPi webcam daemon with

If I manually stop and restart it I don't see any errors but I don't see any video on port 8082. Also the daemon starts with the wrong device, video0 not video2.

Please let me know if you have any more suggestions.

Thanks.
Salty Doug

ULTIMAKER · January 18, 2020, 10:52am

have you created the symlinks?
use the symlink in /root/bin/webcamd and webcamd2
here my:
camera_usb_options="-d /dev/VideoLogitech -r 1280x720 -f 10"
What if you use only the webcamd2-webcam?(Other unplugged)