Local V4L2 Camera / Logitech Brio 100 webcam #2678

Open
opened 2026-02-28 01:17:22 -05:00 by deekerman · 5 comments
Owner

Originally created by @ilkkamr26 on GitHub (Feb 9, 2026).

Hi!
I'm running Motioneye on a Raspberry Pi 500. The operating system is Ubuntu 25.10.
My webcam is Logitech Brio 100. The webcam works in Zoom and Telegram.

The problem is that I can't add the camera in Motioneye.
The dialog box shows only (no cameras).

The command 'ffplay /dev/video0' works on my machine.

$ v4l2-ctl --list-devices
pispbe (platform:1000880000.pisp_be):
/dev/video20
/dev/video21
/dev/video22
/dev/video23
/dev/video24
/dev/video25
/dev/video26
/dev/video27
/dev/video28
/dev/video29
/dev/video30
/dev/video31
/dev/video32
/dev/video33
/dev/video34
/dev/video35
/dev/media0
/dev/media1

rpi-hevc-dec (platform:rpi-hevc-dec):
/dev/video19
/dev/media2

Brio 100 (usb-xhci-hcd.0-1):
/dev/video0
/dev/video1
/dev/media3

Originally created by @ilkkamr26 on GitHub (Feb 9, 2026). Hi! I'm running Motioneye on a Raspberry Pi 500. The operating system is Ubuntu 25.10. My webcam is Logitech Brio 100. The webcam works in Zoom and Telegram. The problem is that I can't add the camera in Motioneye. The dialog box shows only (no cameras). The command 'ffplay /dev/video0' works on my machine. $ v4l2-ctl --list-devices pispbe (platform:1000880000.pisp_be): /dev/video20 /dev/video21 /dev/video22 /dev/video23 /dev/video24 /dev/video25 /dev/video26 /dev/video27 /dev/video28 /dev/video29 /dev/video30 /dev/video31 /dev/video32 /dev/video33 /dev/video34 /dev/video35 /dev/media0 /dev/media1 rpi-hevc-dec (platform:rpi-hevc-dec): /dev/video19 /dev/media2 Brio 100 (usb-xhci-hcd.0-1): /dev/video0 /dev/video1 /dev/media3
Author
Owner

@ilkkamr26 commented on GitHub (Feb 11, 2026):

Hi!

"To get the full functionality please connect the camera, log-observe and mount-observe interfaces using the snap connect command."

What are the slots I should use with my webcam?

Basic Syntax: sudo snap connect : :

$ snap connections motioneye
Interface Plug Slot Notes
camera motioneye:camera - -
log-observe motioneye:log-observe - -
mount-observe motioneye:mount-observe - -
network motioneye:network :network -
network-bind motioneye:network-bind :network-bind -
opengl motioneye:opengl :opengl -
removable-media motioneye:removable-media - -

@ilkkamr26 commented on GitHub (Feb 11, 2026): Hi! "To get the full functionality please connect the camera, log-observe and mount-observe interfaces using the snap connect command." What are the slots I should use with my webcam? Basic Syntax: sudo snap connect <snap-name>:<plug-name> <snap-name>:<slot-name> $ snap connections motioneye Interface Plug Slot Notes camera motioneye:camera - - log-observe motioneye:log-observe - - mount-observe motioneye:mount-observe - - network motioneye:network :network - network-bind motioneye:network-bind :network-bind - opengl motioneye:opengl :opengl - removable-media motioneye:removable-media - -
Author
Owner

@ilkkamr26 commented on GitHub (Feb 11, 2026):

Hi!

I got the webcam working by using following command:

sudo snap connect motioneye:camera

@ilkkamr26 commented on GitHub (Feb 11, 2026): Hi! I got the webcam working by using following command: sudo snap connect motioneye:camera
Author
Owner

@MichaIng commented on GitHub (Feb 11, 2026):

So you are using a motionEye snap? I didn't know it exists. ... I see:

Note that this is the very outdated Python 2 version. I would strongly advice against using it, for security reasons alone. Also, it is unmaintained, as you can see from the repository.

If you need to run it as container, we provide official Docker images. So you can run it with something like this:

sudo mkdir /etc/motioneye /var/lib/motioneye
docker run -d --restart='unless-stopped' \
  -p '8765:8765' --name='motioneye' \
  --device='/dev/video0' --device='/dev/video1' \
  -v '/etc/localtime:/etc/localtime:ro' \
  -v '/etc/motioneye:/etc/motioneye' \
  -v '/var/lib/motioneye:/var/lib/motioneye' \
  'motioneyeproject/motioneye'

It bind-mounts the two video devices which seem to be related to your Brio cam, the default config and data dir from same paths on the host, and exposes the web UI on the default port.

@MichaIng commented on GitHub (Feb 11, 2026): So you are using a motionEye snap? I didn't know it exists. ... I see: - https://snapcraft.io/motioneye - https://github.com/ogra1/motioneye-snap Note that this is the very outdated Python 2 version. I would strongly advice against using it, for security reasons alone. Also, it is unmaintained, as you can see from the repository. If you need to run it as container, we provide official Docker images. So you can run it with something like this: ```sh sudo mkdir /etc/motioneye /var/lib/motioneye docker run -d --restart='unless-stopped' \ -p '8765:8765' --name='motioneye' \ --device='/dev/video0' --device='/dev/video1' \ -v '/etc/localtime:/etc/localtime:ro' \ -v '/etc/motioneye:/etc/motioneye' \ -v '/var/lib/motioneye:/var/lib/motioneye' \ 'motioneyeproject/motioneye' ``` It bind-mounts the two video devices which seem to be related to your Brio cam, the default config and data dir from same paths on the host, and exposes the web UI on the default port.
Author
Owner

@ilkkamr26 commented on GitHub (Feb 11, 2026):

Hi!
Thanks for your answer!
I installed MotionEye snap from Ubuntu's App Center.
Could you ask Ubuntu developers to remove the snap?

@ilkkamr26 commented on GitHub (Feb 11, 2026): Hi! Thanks for your answer! I installed MotionEye snap from Ubuntu's App Center. Could you ask Ubuntu developers to remove the snap?
Author
Owner

@MichaIng commented on GitHub (Feb 11, 2026):

This is not within out possibilities: Everyone can upload snaps, and obviously Canonical has no rules (or enforces those) whether snaps are based on outdated software, or whether they are uploaded/provided by the upstream developers.

That Oliver Grawert uploaded a lot of snaps for 3rd party software, many of them never updated: https://snapcraft.io/publisher/ogra
I don't think this is useful for anyone, but the same is true for a lot of Docker images on Docker Hub, but at least on Docker Hub, the uploader account is part of the image name. Just try to stick with official distributions where available, like for every other software.

Would be a different thing we provided snaps as well, and integrate them (+uploads) into our release schedule, then I'd try to contact him to free the name slot. But I have not much knowledge about and interest in snap.

@MichaIng commented on GitHub (Feb 11, 2026): This is not within out possibilities: Everyone can upload snaps, and obviously Canonical has no rules (or enforces those) whether snaps are based on outdated software, or whether they are uploaded/provided by the upstream developers. That Oliver Grawert uploaded a lot of snaps for 3rd party software, many of them never updated: https://snapcraft.io/publisher/ogra I don't think this is useful for anyone, but the same is true for a lot of Docker images on Docker Hub, _but at least on Docker Hub, the uploader account is part of the image name_. Just try to stick with official distributions where available, like for every other software. Would be a different thing we provided snaps as well, and integrate them (+uploads) into our release schedule, then I'd try to contact him to free the name slot. But I have not much knowledge about and interest in snap.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/motioneye#2678
No description provided.