BamBuddy – self-hosted Bambu Lab printer management as a Home Assistant App

Hi everyone,

I’d like to share a project I’ve been working on: BamBuddy as a Home Assistant App (formerly called add-on).

BamBuddy by maziggy is a self-hosted command center for Bambu Lab printers – from a single A1 to a whole print farm: live monitoring, camera, print archive, a virtual printer you can send jobs to from Bambu Studio or OrcaSlicer, Spoolman integration, notifications and much more. Your printers. No cloud. Your rules.

My repository packages BamBuddy so it installs and updates like any other Home Assistant app – no Docker knowledge needed.

What you get

  • One-click install with prebuilt images for amd64 and aarch64 – nothing is built on your device, so it also runs on a Raspberry Pi.
  • Two channels: BamBuddy (stable, recommended) and BamBuddy (Daily) with the latest upstream daily build.
  • Automatic updates: new BamBuddy releases are picked up automatically. Each one is tested on both architectures before it is published, then it shows up in Home Assistant as a normal update, release notes included.
  • Your data stays put: the print archive, settings and logs live in the app’s configuration folder (addon_configs). They survive updates and even an uninstall (unless you choose to delete that folder), and they are part of your Home Assistant backups.
  • Printer discovery and the virtual printer work out of the box.

Options

Option What it does
trusted_frame_origins Lets you embed BamBuddy in a Webpage card or panel
enable_share / enable_media Makes /share and /media available as storage in BamBuddy
use_system_trust_store + certfile Trusts your own CA, e.g. for a self-hosted Spoolman behind HTTPS
debug Verbose logging

Installation

Add repository to Home Assistant

Or manually: Settings → Apps → App Store → ⋮ → Repositories and add https://github.com/Spegeli/homeassistant-app-bambuddy. Then install BamBuddy and open the web UI.

You need Home Assistant OS (apps require the Supervisor; they are not available on Container or Core installations).

Good to know

  • No Ingress: BamBuddy opens in its own browser tab (port 8000). Its web interface needs a fixed address, which Ingress doesn’t provide.
  • Virtual printer ports: the virtual printer uses several ports on the host, including 8883, which clashes with the Mosquitto MQTT broker. The app’s Documentation tab lists all ports.

Links

This is not an official release by the BamBuddy developer – all credit for BamBuddy itself goes to maziggy. I maintain the Home Assistant packaging. For problems with the app itself (installation, updates, options), please open an issue in my repository. Bugs and feature requests for BamBuddy belong in the BamBuddy project.

Feedback is very welcome!

1 Like