My only thought on the non-bambu would be to support octoprint - that way it would support that whole stack, but thats probably because i have octoprint on my other printer.
SL666
Posts
-
Plans to support non-bambu printers? -
Weird Network Issues?Update - The camera stream doesn't hang, if there isn't a print going on (watching the stream, turning the light on & off etc seems fine)
edit -
further testing and logwatching - the hangs are happening when the fault detection fires -
bambuddy | 2026-05-14 14:53:54,969 INFO [backend.app.api.routes.camera] [a6fa2778] Using RTSP protocol for X1C bambuddy | 2026-05-14 14:53:54,969 INFO [backend.app.api.routes.camera] [a6fa2778] Camera viewer attached to printer-1 (subscribers=1) bambuddy | 2026-05-14 14:53:58,010 WARNING [backend.app.api.routes.camera] [34034de4] RTSP read timeout for 10.0.20.9 (stream_id=1-fanout) bambuddy | 2026-05-14 14:53:58,542 INFO [backend.app.services.camera] [-] Capturing camera frame bytes from 10.0.20.9 using RTSP (model: X1C) bambuddy | 2026-05-14 14:54:00,011 WARNING [backend.app.api.routes.camera] [34034de4] ffmpeg didn't terminate gracefully, killing (stream_id=1-fanout) bambuddy | 2026-05-14 14:54:00,022 INFO [backend.app.api.routes.camera] [34034de4] RTSP reconnecting (1/30) for 10.0.20.9 (stream_id=1-fanout) bambuddy | 2026-05-14 14:54:00,425 INFO [backend.app.services.camera] [-] Successfully captured camera frame bytes: 64224 bytes bambuddy | 2026-05-14 14:54:12,203 INFO [backend.app.services.camera] [-] Capturing camera frame bytes from 10.0.20.9 using RTSP (model: X1C) bambuddy | 2026-05-14 14:54:14,097 INFO [backend.app.services.camera] [-] Successfully captured camera frame bytes: 67890 bytes bambuddy | 2026-05-14 14:54:27,217 INFO [backend.app.services.camera] [-] Capturing camera frame bytes from 10.0.20.9 using RTSP (model: X1C) bambuddy | 2026-05-14 14:54:29,155 INFO [backend.app.services.camera] [-] Successfully captured camera frame bytes: 72468 bytes bambuddy | 2026-05-14 14:54:40,402 INFO [backend.app.api.routes.camera] [a6fa2778] Camera viewer detached from printer-1 (subscribers=0) bambuddy | 2026-05-14 14:54:40,419 INFO [backend.app.api.routes.camera] [34034de4] Camera stream cancelled (stream_id=1-fanout) bambuddy | 2026-05-14 14:54:40,507 INFO [backend.app.api.routes.camera] [658b9606] Using RTSP protocol for X1C bambuddy | 2026-05-14 14:54:40,507 INFO [backend.app.api.routes.camera] [658b9606] Camera viewer attached to printer-1 (subscribers=1) bambuddy | 2026-05-14 14:54:40,508 INFO [backend.app.api.routes.camera] [658b9606] Starting RTSP camera stream for 10.0.20.9 (stream_id=1-fanout, model=X1C, fps=15) bambuddy | 2026-05-14 14:54:42,284 INFO [backend.app.services.camera] [-] Capturing camera frame bytes from 10.0.20.9 using RTSP (model: X1C) bambuddy | 2026-05-14 14:54:42,420 WARNING [backend.app.api.routes.camera] [34034de4] ffmpeg didn't terminate gracefully, killing (stream_id=1-fanout) bambuddy | 2026-05-14 14:54:44,210 INFO [backend.app.services.camera] [-] Successfully captured camera frame bytes: 70629 bytes bambuddy | 2026-05-14 14:54:56,006 INFO [backend.app.services.camera] [-] Capturing camera frame bytes from 10.0.20.9 using RTSP (model: X1C) bambuddy | 2026-05-14 14:54:57,903 INFO [backend.app.services.camera] [-] Successfully captured camera frame bytes: 71444 bytes bambuddy | 2026-05-14 14:55:09,694 INFO [backend.app.services.camera] [-] Capturing camera frame bytes from 10.0.20.9 using RTSP (model: X1C) bambuddy | 2026-05-14 14:55:09,714 INFO [backend.app.api.routes.camera] [658b9606] Camera viewer detached from printer-1 (subscribers=0) bambuddy | 2026-05-14 14:55:09,718 INFO [backend.app.api.routes.camera] [109457ee] Using RTSP protocol for X1C bambuddy | 2026-05-14 14:55:09,718 INFO [backend.app.api.routes.camera] [109457ee] Camera viewer attached to printer-1 (subscribers=1) bambuddy | 2026-05-14 14:55:11,656 INFO [backend.app.services.camera] [-] Successfully captured camera frame bytes: 63267 bytes bambuddy | 2026-05-14 14:55:19,817 INFO [backend.app.api.routes.camera] [109457ee] Camera viewer detached from printer-1 (subscribers=0) bambuddy | 2026-05-14 14:55:19,817 INFO [backend.app.api.routes.camera] [658b9606] Camera stream cancelled (stream_id=1-fanout) bambuddy | 2026-05-14 14:55:19,917 INFO [backend.app.api.routes.camera] [68fb9162] Using RTSP protocol for X1C bambuddy | 2026-05-14 14:55:19,918 INFO [backend.app.api.routes.camera] [68fb9162] Camera viewer attached to printer-1 (subscribers=1) bambuddy | 2026-05-14 14:55:19,918 INFO [backend.app.api.routes.camera] [68fb9162] Starting RTSP camera stream for 10.0.20.9 (stream_id=1-fanout, model=X1C, fps=15) bambuddy | 2026-05-14 14:55:20,300 INFO [backend.app.api.routes.camera] [397bf934] Shut down camera fan-out broadcaster for printer 1 bambuddy | 2026-05-14 14:55:20,300 INFO [backend.app.api.routes.camera] [397bf934] Stopped 0 camera stream(s) for printer 1 bambuddy | INFO: 172.31.0.8:34472 - "POST /api/v1/printers/1/camera/stop HTTP/1.1" 200 OK bambuddy | 2026-05-14 14:55:23,439 INFO [backend.app.services.camera] [-] Capturing camera frame bytes from 10.0.20.9 using RTSP (model: X1C) bambuddy | 2026-05-14 14:55:25,350 INFO [backend.app.services.camera] [-] Successfully captured camera frame bytes: 37452 bytes bambuddy | 2026-05-14 14:55:29,170 INFO [backend.app.api.routes.camera] [68fb9162] Camera viewer detached from printer-1 (subscribers=0) bambuddy | 2026-05-14 14:55:29,178 INFO [backend.app.api.routes.camera] [03c4106c] Using RTSP protocol for X1C bambuddy | 2026-05-14 14:55:29,179 INFO [backend.app.api.routes.camera] [03c4106c] Camera viewer attached to printer-1 (subscribers=1) bambuddy | 2026-05-14 14:55:36,252 INFO [backend.app.api.routes.camera] [773b5487] Using RTSP protocol for X1C bambuddy | 2026-05-14 14:55:36,252 INFO [backend.app.api.routes.camera] [773b5487] Camera viewer attached to printer-1 (subscribers=2) bambuddy | 2026-05-14 14:55:36,260 INFO [backend.app.api.routes.camera] [773b5487] Camera viewer detached from printer-1 (subscribers=1) bambuddy | INFO: 172.31.0.8:50416 - "PUT /api/v1/settings/ HTTP/1.1" 200 OK bambuddy | 2026-05-14 14:55:43,296 INFO [backend.app.api.routes.camera] [773b5487] Camera viewer detached from printer-1 (subscribers=0) bambuddy | 2026-05-14 14:55:43,306 INFO [backend.app.api.routes.camera] [d40345cf] Using RTSP protocol for X1C bambuddy | 2026-05-14 14:55:43,306 INFO [backend.app.api.routes.camera] [d40345cf] Camera viewer attached to printer-1 (subscribers=1) bambuddy | 2026-05-14 14:55:47,684 INFO [backend.app.api.routes.camera] [d40345cf] Camera viewer detached from printer-1 (subscribers=0) bambuddy | 2026-05-14 14:55:47,693 INFO [backend.app.api.routes.camera] [68fb9162] Camera stream cancelled (stream_id=1-fanout) bambuddy | 2026-05-14 14:55:47,789 INFO [backend.app.api.routes.camera] [c5bbe1b1] Using RTSP protocol for X1C bambuddy | 2026-05-14 14:55:47,789 INFO [backend.app.api.routes.camera] [c5bbe1b1] Camera viewer attached to printer-1 (subscribers=1) bambuddy | 2026-05-14 14:55:47,790 INFO [backend.app.api.routes.camera] [c5bbe1b1] Starting RTSP camera stream for 10.0.20.9 (stream_id=1-fanout, model=X1C, fps=15) bambuddy | 2026-05-14 14:55:49,695 WARNING [backend.app.api.routes.camera] [68fb9162] ffmpeg didn't terminate gracefully, killing (stream_id=1-fanout)Turning off AI failure detection - the camera stream functions normally.
-
Weird Network Issues?Hi There,
Pretty new to Bambuddy (but not new to Bambu/3D printing/docker), having a couple of strange issues - hoping they can be easily solved.
BB v0.2.4 (with HASS & Fail detection working)
Spoolman Version 0.23.1 (usage tracking works)
X1C (Lan only mode)
Bambu Studio 2.6.1.53Trying to send a print from BS via - slice - print plate I get this error.

Searching for it - doesn't really give me much information - I have printed directly since this has been set up, but lately i've had to export the sliced gcode and upload into BB and print from there - which does work without issue.
The other is that if I open the camera view of the printer, it will freeze after a few seconds, pressing the refresh button does re-connect and show another few seconds, same behaviour as when it times out and re-connects on its own.
Not sure if I'm using things wrongly etc or ? no errors sticking out in the docker logs.
Cheers Steve.