mirror of
https://github.com/maziggy/bambuddy.git
synced 2026-05-09 05:35:30 +02:00
[GH-ISSUE #489] [Bug]: Unable to connect Camera Stream (H2C, V1.05.00) #311
Labels
No labels
A1
automated
automated
bug
bug
Closed due to inactivity
contrib
dependencies
dependencies
duplicate
enhancement
feedback
hold
invalid
Notes
P1S
pull-request
security
security
ThumbsUp
user-report
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/bambuddy#311
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @speedy764 on GitHub (Feb 22, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/489
Originally assigned to: @maziggy on GitHub.
Bug Description
Good day. I need your help.
Running on Bambuddy V0.2.0. and firmware 1.05.00 of the H2C.
Since I was unable to set up the virtual printer in Bridge Mode (Docker - WSL, PC:A) in BBL Studio, I installed a VM (HyperV) with Ubuntu 24 on my other computer and set up a new installation with Docker in Host Mode (PC:B). This works fine. I see the virtual printer (proxy-mode). But the connection to the camera stream does not work. When I run both installations in parallel, I have a camera image in the Docker (Bridge, PC:A) but not in the Docker (Host, PC:B).
Expected Behavior
bambuddy-support-20260222-141335.zip
Steps to Reproduce
Open Camera view from the printer page.
Windows (see screenshot) opens, but run in a loop to reconnect
Printer Model
H2C
Bambuddy Version
0.2.0
Printer Firmware Version
1.05.00
Installation Method
Docker
Operating System
Linux (Ubuntu/Debian)
Relevant Logs / Support Package
Screenshots
Additional Context
No response
Checklist
@maziggy commented on GitHub (Feb 22, 2026):
Show me a picture of your printer's LAN Only settings menu.
@speedy764 commented on GitHub (Feb 24, 2026):
@speedy764 commented on GitHub (Feb 26, 2026):
Sorry seems that I closed the issue when I uploaded the picture, ...
@maziggy commented on GitHub (Feb 27, 2026):
Please use branch 0.2.1 and send me a new support package.
@speedy764 commented on GitHub (Feb 28, 2026):
I have updated both installions to 0.2.1. The problem is still the same. I am able to connect to camera on the Docker (WSL-Bridge) but not on Docker (HyperV / Ubuntu 24 / Host mode). I have added the support file.
Camera_bambuddy-support-20260228-100901.zip
@maziggy commented on GitHub (Feb 28, 2026):
Looks like Bambu Lab changed the internal model code for the H2C from O1C to O1C2. Added new model ID and camera stream should now work with branch 0.2.2b1.
I see a lot of networking errors in your logs. This is, because you don't run the Docker network in mode host, but bridge. Please note, that Bambuddy is requiring host mode!!!
"network_mode_hint": "bridge"
@speedy764 commented on GitHub (Feb 28, 2026):
No. the Docker is running in network mode host:
Here is my compose.yml
compose (Linux).yml
@maziggy commented on GitHub (Feb 28, 2026):
Nice picture :)
I don't know Docker WSL and HyperV. Perhaps it is handled different internally. Don't know. Sorry.
Back to the main issue: is the caanera working now?
@speedy764 commented on GitHub (Feb 28, 2026):
Camaera is working running in Network_mode:bridge but not on the client with network_mode:host.
On docker in (Bridge-mode) the camera stream seams to be initiate via Starting RTSP camera stream for 192.168.178.143 (stream_id=1-2bffb38d, model=H2C, fps=15)
on Docker in (host-mode) the camera stream is initated via api/v1/printesr/1/camera/stream?fps=15&t......
Not sure could that be the issue....
@maziggy commented on GitHub (Feb 28, 2026):
Looking at your support package, setup is actually running in bridge mode — the network_mode_hint confirms this:
"network_mode_hint": "bridge"
Why? network_mode: host on Docker Desktop for Windows doesn't work the same as on native Linux. Docker Desktop runs containers inside a WSL2 / Hyper-V Linux VM, so host networking gives the container access to the VM's network stack — not your actual Windows host network. Effectively, it's still bridge mode.
This is a Docker Desktop limitation, not a Bambuddy issue. True network_mode: host is only supported on native Linux Docker.
The two different messages you noticed aren't different behavior — they're just different layers of the same flow:
The browser hits the API endpoint, which then triggers the RTSP/ffmpeg stream internally. Both your setups go through the exact same code path.
@speedy764 commented on GitHub (Feb 28, 2026):
Thanks.Maybe I confused youTo clarify, Installation 1: Camera does not workI run a native Ununtu Installation as VM hosted on HyperV. IPAddress from my LAN. Docker runs in this Linux VM. Bambuddy runs in Host mode.Installation 2: Camera worksThis run on Docker in WSL.(Windows)Bambuddy runs in bridge mode with Port configuration.I dont know why do you see my Installation 1 in bridge mode...Let me go back to prevously creste Checkpoint and Start again and install docker again..Gesendet von Outlook für AndroidVon: MartinNYHC @.>Gesendet: Samstag, Februar 28, 2026 2:04:40 PMAn: maziggy/bambuddy @.>Cc: speedy764 @.>; State change @.>Betreff: Re: [maziggy/bambuddy] [Bug]: Unable to connect Camera Stream (H2C,
V1.05.00) (Issue #489)maziggy left a comment (maziggy/bambuddy#489)Looking at your support package, setup is actually running in bridge mode — the network_mode_hint confirms this:"network_mode_hint": "bridge"Why? network_mode: host on Docker Desktop for Windows doesn't work the same as on native Linux. Docker Desktop runs containers inside a WSL2 / Hyper-V Linux VM, so host networking gives the container access to the VM's network stack — not your actual Windows host network. Effectively, it's still bridge mode.This is a Docker Desktop limitation, not a Bambuddy issue. True network_mode: host is only supported on native Linux Docker.The two different messages you noticed aren't different behavior — they're just different layers of the same flow:api/v1/printers/1/camera/stream?fps=15&t=... → the browser request (what you see in the network tab)Starting RTSP camera stream for 192.168.178.143 → the backend log (what you see in docker logs)The browser hits the API endpoint, which then triggers the RTSP/ffmpeg stream internally. Both your setups go through the exact same code path.—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you modified the open/close state.
@speedy764 commented on GitHub (Mar 4, 2026):
Hi Martin, soory for late response, I didn't get the time earlier to build a new Ubuntu VM. Camera is working as designed in 02.2.b1 (Host mode). THX