2 hours ago, Bushibot said:

So I'm reading the old dvb method is no longer valid and a custom kernel is needed. This seems kind of nuts though.

I'm unclear if this outdated or stil lvalid. I don't see the kernel helper in apps though.

google doc

I think it must be outdated mate as its working fine on my setup.

I did install the dvb drivers though as recommended.

This should theoretically install the required kernel drivers needed to run a webcam.  

Glad the win11 vm worked as it shows that it is happily working with the system.

Have you ever run it of a raspberri pi to ensure that it works happily with octoprint native?

Its the last thing I can think of mate without remotely jumping in and trying to help.

And knowing that you dont know me from a bar of soap, i dont know what else to do to help you.

No-one else is commenting either which is a bit of a concern, but I had radio silence on my post as well.

Linux is my daily driver and I know some cameras suck in native usage which is what the docker image will do.

Running in win11 vm, unraid basiclly passes the whole port over to the operating system running in the vm so it all up to windows to make it work from that perspective.

In the docker image, it is not done that way.

What model of camera is it?

6 hours ago, djcs said:

I think it must be outdated mate as its working fine on my setup.

I did install the dvb drivers though as recommended.

This should theoretically install the required kernel drivers needed to run a webcam.  

Glad the win11 vm worked as it shows that it is happily working with the system.

Have you ever run it of a raspberri pi to ensure that it works happily with octoprint native?

Its the last thing I can think of mate without remotely jumping in and trying to help.

And knowing that you dont know me from a bar of soap, i dont know what else to do to help you.

No-one else is commenting either which is a bit of a concern, but I had radio silence on my post as well.

Linux is my daily driver and I know some cameras suck in native usage which is what the docker image will do.

Running in win11 vm, unraid basiclly passes the whole port over to the operating system running in the vm so it all up to windows to make it work from that perspective.

In the docker image, it is not done that way.

What model of camera is it?

I just got mint running last night in van to rest too.

it did work when I was running on the pi directly.

The log error in the octo container says videoIN fail, I something is not connecting. Feels like a driver issue. I did reboot again. Also testing with a different camera (old ms life cam).

 

I’m gonna try a different route I guess.

 

Thanks for the suggestions, appreciate it. 

2 hours ago, Bushibot said:

I just got mint running last night in van to rest too.

it did work when I was running on the pi directly.

The log error in the octo container says videoIN fail, I something is not connecting. Feels like a driver issue. I did reboot again. Also testing with a different camera (old ms life cam).

 

I’m gonna try a different route I guess.

 

Thanks for the suggestions, appreciate it. 

I just love that unraid allows us to play like this.

I know this might sound obvious, but only cause I have seen a few setups reading through this, but have you tried /dev/video1 ?

Just now, djcs said:

I just love that unraid allows us to play like this.

I know this might sound obvious, but only cause I have seen a few setups reading through this, but have you tried /dev/video1 ?

Scrap that, I rereading what you have posted and can see you have.
Too much going on in life rn and forgot i had already asked

2 hours ago, Bushibot said:

I just got mint running last night in van to rest too.

it did work when I was running on the pi directly.

The log error in the octo container says videoIN fail, I something is not connecting. Feels like a driver issue. I did reboot again. Also testing with a different camera (old ms life cam).

 

I’m gonna try a different route I guess.

 

Thanks for the suggestions, appreciate it. 

Have you tried manually opening the streams in an incognito/private window?
You are on the right track me thinks.

Copy n paste what the main url is MEANt to be rather than what is showing in the config.

So I instaled mint and then used octo deploy. Now I'm having the reverse issue of getting the printer to show up, but the camera works fine, though a full VM seems over kill.

But I think this limted the issue to the docker container or unraid config somewhere.

Is there a way to see the camera feed from unraid maybe?

41 minutes ago, Bushibot said:

So I instaled mint and then used octo deploy. Now I'm having the reverse issue of getting the printer to show up, but the camera works fine, though a full VM seems over kill.

But I think this limted the issue to the docker container or unraid config somewhere.

Is there a way to see the camera feed from unraid maybe?

Did you stop the docker before trying to connect the vm to the printer?

Also have you allocated the serial usb to the vm, it needs to be "attached" to the vm for it to work, unlike a docker.

2 hours ago, djcs said:

Have you tried manually opening the streams in an incognito/private window?
You are on the right track me thinks.

Copy n paste what the main url is MEANt to be rather than what is showing in the config.

Yeah doesn’t work. As far as I can tell unraid is not passing a stream through /dev/video*. So their is nothing for the octocontainer to parse.

25 minutes ago, djcs said:

Did you stop the docker before trying to connect the vm to the printer?

Also have you allocated the serial usb to the vm, it needs to be "attached" to the vm for it to work, unlike a docker.

It’s not clear to me how to add the serial printer port to the VM. The printer doesn’t show up as a USB device, of course. With the doctor, there’s a way to pass the device. I don’t see an option for that in the VM set up except USB or PCI.

48 minutes ago, Bushibot said:

It’s not clear to me how to add the serial printer port to the VM. The printer doesn’t show up as a USB device, of course. With the doctor, there’s a way to pass the device. I don’t see an option for that in the VM set up except USB or PCI.

Right soooo, turns out a had accidently unplugged the printer from the PC when moving cameras around. No serial in VM solved.

 

So VM looks like it will work though YEEESH, huge resource waste compared to the docker.

But zero luck with docker octoprint vidoe. I ran through every possible permutation of device and /dev/video* again just to make sure I hadn't missed some combo. Also tried same with MS life cam.

 

I might try with some other container for vid over usb, I mean somebody has to have this working as general practice, octoprint being a little nich compared to video security etc.

Mint VM runniing OCTO_deploy script, webcam up, printer up.

 

This seems be some sort of function braking error from the octoprint docker log: but my dockerfu is not good enough to dig deeper and unraid is just as obtuse to me.

MJPG Streamer Version.: 2.0
 i: Using V4L2 device.: (null)
 i: Desired Resolution: 720 x 1280
 i: Frames Per Second.: -1
 i: Format............: YUYV
 i: JPEG Quality......: 80
 i: TV-Norm...........: DEFAULT
 i: init_VideoIn failed

Hi together 

I have the problem that I can't get a webcam (IP cam stream) integrated in the Octoprint docker.

Do I have to change something in the docker variables ? 

The stream runs normally in any browser, only in Octoprint it is not displayed. 
Lockale address
http://192.168.178.10:1984/stream.html?src=TapoC210&mode=webrtc

 

I bind the stream in go2rtc docker and want to forward it from dord to Octoprint. 

But it just does not work ? 
What can I do ? 

 

 

 

Has anybody figure out how to update the docker container and NOT lose all your plugins?  Im running such an old version of Octoprint but if I try to update, all my plugins are missing.

I think the problem is because the Actual plugins are not installed in the /octoprint folder, Only the settings for the plugins are.  And the Actual plugins are installed somewhere on the image that gets overwritten when you update the docker.  This is why if you re-install the plugins you had, they come back already configured (Because the settings are in the octoprint folder, but not the actual plugins)

To fix this we need to add a line mapping the folder of the plugins to our Appdata folder.  But I dont know what folder that is

Edited December 2, 20232 yr by 007craft

I'm having issues getting octoprint to connect to my printer. Unraid picks it up as a ch340 and presents it as /dev/ttyUSB0 and with an id in the by-id folder. I've tried the normal pass through option and also running the docker in privileged mode but it won't connect. I've tried different USB cables and also plugged the printer into my laptop and it definitely works that way.

Does anyone have any suggestions?

I'm coming back to this, anyone with a new install able to get video to work via dvb or some other method? Anyone know another way to add video support to unraid directly? Or have a wifi cam that plays nice with octoprint directly?

I have tried a pretty long list of things to get octoprint to work via container with the a usb camera on the unraid box with no joy.

has anyone gotten docker wyze bridge to work as the webcam here?

 

i've tried following guides, but they seem to be a bit outdated now that wyze docker bridge needs and api key and ID. it seems when i open up wyze docker bridge it asks for a username and password, and i think thats why octoprint cant see it as there is no way to pass in the passwords. please help! i've been struggling for a few days with this

Does anyone have this working with a printer that has klipper installed? Ready to rip my hair out over trying to get this to work.

Tried all the things mentioned here with /dev/serial/by-id etc and all I get is this in the logs:
 

Quote

2024-05-31 14:13:28,101 - octoprint.util.comm - INFO - Changing monitoring state from "Offline" to "Opening serial connection"
2024-05-31 14:13:28,102 - octoprint.util.comm - INFO - Connecting to port /dev/serial/by-id/usb-Klipper_stm32g0b1xx_2B0031000250415339373620-if00, baudrate 250000
2024-05-31 14:13:28,169 - octoprint.util.comm - INFO - Changing monitoring state from "Opening serial connection" to "Connecting"
2024-05-31 14:13:28,172 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2024-05-31 14:13:28,463 - octoprint.server - INFO - Autorefresh of serial port list stopped
2024-05-31 14:14:12,180 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0

I have octoklipper plugin installed to and it's not changing anything. No idea what to do..

 

 

 

edit: abandonded this and running a VM now with linux server / kiauh to install mainsail klipper. way easier.

Edited June 17, 20242 yr by coltography

@spants would you envision updating the docker image to include the new camera stack?
https://octoprint.org/blog/2023/05/24/a-new-camera-stack-for-octopi/
https://plugins.octoprint.org/plugins/camerastreamer_control/

It would be fantastic to have RTC support for the buttery smooth streaming.

 

Thanks in advance!

On 6/20/2024 at 9:01 AM, secretstorage said:

@spants would you envision updating the docker image to include the new camera stack?
https://octoprint.org/blog/2023/05/24/a-new-camera-stack-for-octopi/
https://plugins.octoprint.org/plugins/camerastreamer_control/

It would be fantastic to have RTC support for the buttery smooth streaming.

 

Thanks in advance!

Hi!

My office is in bits at the moment due to a m,ove, so I dont have access to my printers. It may be a month or so.....

Hey everyone,

 

I finally got this working (with USB Camera)

 

Note* I did have to install the DVB drivers (a reboot might have been needed)

I could not get it the usb camera to show as dev/video0 (this is why I had tried it)

The webcam device, to find the right path you have to go with lsusb (terminal on unraid) which will return bus/dev/ mine was 001/002.

for me this gave me the full details in terminal as well 

 

udevadm info    --name=/dev/bus/usb/001/002

 

 

 

As for the Classic Webcam settings are as such:

 

Stream URL:

http://[IP]:5003/webcam/?action=stream (as the docker settings tell you)

 

Snapshot URL:

http://[IP]:5004/?action=snapshot (as the docker settings tell you)

 

Is there a trick to getting the timelapse feature to work?  Do I need to have a specific plugin for ffmpeg to work there?

On 7/29/2024 at 5:46 PM, Zervonn said:

Is there a trick to getting the timelapse feature to work?  Do I need to have a specific plugin for ffmpeg to work there?

Do you have DVB Drivers installed and configured per this post?

Even after that, I had to restart the service and my server a second or third time for ffmpeg to passthrough.  I'm unsure why, unless I was mistyping the path, but it does work for me now.  If you have the driver service and plugin installed, after the restarts you should be able to populate this field with

/usr/bin/ffmeg

I've been trying to get obico to work with this Docker for a while. When I still had Octoprint running on the RP, it worked without any problems. Unfortunately, the RP no longer worked and I wanted to get the whole thing to work in Unraid with Docker. Unfortunately, that doesn't really work. Apparently the Janus gateway that Obico needs is missing. Can this be integrated into Docker? Or does anyone have a solution to the problem?

Hi All,

 

Has anyone found a way to run multiple camera?
I am yet to try it but I was going to try doubling down on the container variables, webcam2 , snapshot2, webcam device2 ,etc.
 

Let me know, I'd like to run a nozzle cam. 

Is this still an active thread and still being supported?

or is there a better option?

Hey Ascent,
I still get the emails etc and try and help when I can, last couple of questions have been beyond me though...

DJ