Help

Need more infos. Please open an issue and attach a support package.

@MartinNYHC Done!

@MartinNYHC Thank you for your help and support. Installation was successful. Have a nice day

Still doesnt work. But I got it working via "manual" mode. Here it just worked. Pulled the image and fired up the container. 🤪 Still thanks for your help and this great programm!

My understanding is that if you have print plate confirmation checked, the print will not start till you set the plate as cleared on the printer page. Also, on the printer card, check if you have plate check enabled. It uses an image detection algo to check if there is something still on the build plate. I've found it to have too many false positives, so I just disabled it and am relying on plate clear confirmation. Check the screenshot to see the plate check toggle I am referring to. [image: 1778132512952-aef4adaa-bba1-4f5f-b2e1-81c9c8882c29-image.jpeg]

Yeah, I saw on the page for Spoolbuddy that 2Gb is the minimum. I found another mini-PC in my collection that can manage the installation. So, it's all good. Maybe nice to put it on the Bambuddy pages as well. Wonderful product by the way! It works like a charm. Thanks for sharing this!

Bug: https://github.com/maziggy/bambuddy/issues/1119

Is it just me, but I dont have integrations when going to "Settings > Integrations >"?

Bambuddy can emulate a Bambu Lab printer on your network and even relay prints remotely. Here's how the Virtual Printer and Proxy Mode work. Virtual Printer The Virtual Printer makes Bambuddy appear as a real Bambu Lab printer in your slicer (Bambu Studio or OrcaSlicer). When you send a print to the virtual printer, Bambuddy can: Archive mode — Save the file to your archive without printing Review mode — Stage the file for review before printing Queue mode — Add to the print queue automatically Proxy mode — Relay the print to an actual printer (even remotely) Setup Go to Settings > Virtual Printer in Bambuddy Enable the virtual printer Choose your emulated printer model (X1C, P1S, A1, H2D, etc.) The virtual printer will appear in your slicer via SSDP discovery (same LAN) or add it manually by IP Proxy Mode — Print From Anywhere Proxy Mode is the game-changer. It acts as a secure relay between your slicer and your actual printer: End-to-end TLS encryption — FTP, file transfer, and camera are transparently proxied No cloud dependency — Direct connection through your own Bambuddy server Uses printer's access code — No additional credentials needed Full-speed printing — Transparent TCP proxy, minimal overhead Recommended: Use a VPN For remote printing, combine Proxy Mode with Tailscale or WireGuard for full data encryption. This gives you secure access to your printer from anywhere. Use Cases Remote print farms Printing from work to your home printer Traveling makers who want to start prints remotely Detailed setup guide: https://wiki.bambuddy.cool/features/virtual-printer/

Bambuddy supports a wide range of notification providers. Here's how to set them up. Supported Providers Provider Type Setup Difficulty Telegram Bot message Easy Discord Webhook Easy WhatsApp Via CallMeBot Medium Email SMTP Medium Pushover Push notification Easy ntfy Push notification Easy Home Assistant Persistent notification Easy Custom Webhook HTTP POST Advanced What You Get Notified About Print started / completed / failed / cancelled First layer complete (with camera snapshot) Bed cooled down (configurable threshold) HMS errors (AMS jams, nozzle issues, etc.) Build plate detection alerts Queue events (waiting, skipped, failed) Missing spool assignment warnings Configuration Go to Settings > Notifications in Bambuddy Enable your preferred provider(s) Enter the required credentials (bot token, webhook URL, etc.) Test the connection with the Test button Configure quiet hours if you don't want notifications at night Customizable Templates You can customize the notification message format, including: Per-filament usage details Print finish photo URL Filament usage and progress for failed/cancelled prints Daily Digest Enable the daily digest to receive a summary of all print activity instead of individual notifications. For detailed setup instructions per provider, check the Documentation.

A collection of frequently reported issues and their solutions. Printer Shows as Offline Cause: Network connectivity or Developer Mode not enabled. Fix: Verify Developer Mode is enabled on the printer Confirm the printer and Bambuddy are on the same network/VLAN Check the IP address in Settings > Printers Restart the printer if it was recently updated Camera Not Showing Preview Cause: Camera stream not accessible or blocked. Fix: Make sure the camera is enabled in your printer's settings Check that port 6000 (RTSP) is not blocked by a firewall For X1C/P1S: camera works over LAN only with Developer Mode Try refreshing the browser or clearing cache Print Won't Start from Queue/Archive Cause: Filament mismatch, printer busy, or file transfer issue. Fix: Check that the printer has the required filaments loaded Make sure the printer isn't already printing or in error state Check the queue status — it might be in "Queue Only" mode Verify the 3MF file isn't corrupted (try downloading and opening in slicer) Large File Upload Fails Cause: Timeout or proxy configuration. Fix: If using a reverse proxy, increase client_max_body_size and timeouts For direct access, check available disk space Try a wired connection instead of WiFi AMS Mapping Shows Wrong Colors Cause: AMS slot configuration out of sync. Fix: Go to the Printers page and click on the AMS slots to refresh Try the RFID re-read button for affected slots Ensure spools are properly assigned in the Spool Inventory Docker on Windows: Network Issues Cause: Docker Desktop doesn't support host networking. Fix: Enter your printer's IP address manually in Bambuddy settings Don't rely on auto-discovery (SSDP) — it won't work through Docker Desktop's NAT Still stuck? Create a new topic in the Help category with: Your Bambuddy version Printer model A Support Package

Bambuddy requires Developer Mode to communicate directly with your printer over the local network, bypassing Bambu Cloud. Why Developer Mode? By default, Bambu Lab printers route everything through Bambu Cloud. Developer Mode enables local MQTT/FTP access, which Bambuddy uses for: Real-time status monitoring Sending print jobs directly Camera streaming Printer control (pause, resume, stop) How to Enable It On your printer's touchscreen, go to Settings Navigate to Network or General (varies by model) Find Developer Mode or LAN Only Mode Enable it Note the Access Code displayed — you'll need this in Bambuddy Also Required: Store Sent Files on External Storage In Bambu Studio or OrcaSlicer: Go to your printer settings Enable "Store sent files on external storage" This ensures 3MF files are saved to the printer's SD card, which Bambuddy archives automatically. Important Notes Developer Mode works alongside Cloud connectivity — you don't lose cloud features The Access Code changes if you reset it on the printer Your printer and Bambuddy server must be on the same local network Once enabled, add your printer in Bambuddy: Settings > Printers > Add Printer — enter the IP address and access code.

If you want to access Bambuddy over HTTPS or via a domain name, you'll need a reverse proxy. Here's a working Nginx configuration. Nginx Configuration server { listen 80; server_name bambuddy.yourdomain.com; return 301 https://$host$request_uri; } server { listen 443 ssl; server_name bambuddy.yourdomain.com; ssl_certificate /etc/letsencrypt/live/bambuddy.yourdomain.com/fullchain.pem; ssl_certificate_key /etc/letsencrypt/live/bambuddy.yourdomain.com/privkey.pem; client_max_body_size 500M; proxy_read_timeout 300; proxy_connect_timeout 300; proxy_send_timeout 300; location / { proxy_pass http://127.0.0.1:5000; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; } } Important Notes WebSocket support is required — The Upgrade and Connection headers are essential for real-time printer status updates and camera streaming. Increase client_max_body_size — 3MF files can be large. 500M is a safe value for print farms. Increase timeouts — Some operations (firmware updates, large uploads) take time. SSL Certificate with Let's Encrypt sudo apt install certbot python3-certbot-nginx sudo certbot --nginx -d bambuddy.yourdomain.com For more details, check the Documentation.

This guide walks you through installing Bambuddy using Docker — the recommended method. Prerequisites Docker and Docker Compose installed on your system A Bambu Lab printer with Developer Mode enabled "Store sent files on external storage" enabled in Bambu Studio or OrcaSlicer Printer and server on the same local network Installation Option A: Pre-built Image (Fastest) mkdir bambuddy && cd bambuddy curl -O https://raw.githubusercontent.com/maziggy/bambuddy/main/docker-compose.yml docker compose up -d That's it! Open http://your-server-ip:5000 in your browser. Option B: Build from Source git clone https://github.com/maziggy/bambuddy.git cd bambuddy docker compose up -d --build Multi-Architecture Support Bambuddy runs on both AMD64 and ARM64 (Raspberry Pi 4/5). Docker will automatically pull the correct image. macOS / Windows (Docker Desktop) Docker Desktop doesn't support host networking. You'll need to enter your printer's IP address manually in Bambuddy settings instead of relying on auto-discovery. Updating docker compose pull docker compose up -d Daily Beta Builds Want to try the latest features? Use the daily build tag: image: ghcr.io/maziggy/bambuddy:daily Note: Daily builds are never tagged as latest — you need to explicitly opt in. First Steps After Install Open Bambuddy in your browser Go to Settings > Printers and add your printer's IP and access code Your printer should appear on the dashboard within seconds Start a print from your slicer — it will be automatically archived! Having trouble? Check the Documentation or ask in the Help category.