I've been running BamBuddy to manage my Bambu Lab P1S locally — no cloud, no Bambu account required. It's a great self-hosted alternative but until now there was no proper way to run it as a Home Assistant add-on.
So I built one.
What it does:
Wraps the official BamBuddy Docker image as a native HA Supervisor add-on
Persistent storage — your data survives updates
Configurable bind address (useful if you run Mosquitto on the same machine and have a port 8883 conflict)
Embeddable in the HA sidebar via a Webpage dashboard
Installation — one step:
Add this repository to your app store:
Then install BamBuddy from the store like any other app.
HTTPS + sidebar embedding:
If you access HA via HTTPS and use Cloudflare Tunnel, BamBuddy will be blocked from embedding in an iframe by default due to CSP headers. The README includes step-by-step instructions to fix this with a Cloudflare Transform Rule — it takes about 2 minutes.
I looked in your Repo... 1. Navigate to **Settings → Add-ons → Add-on Store** in Home Assistant.
no longer exists. Add-ons have been renamed to Apps some months ago now.
Using the term Add-on with new software can cause some confusion because people have been trying to find add-on in the HA UI, and it is no longer there. Confusion = more issues for you to deal with.
Please consider a wording revision.
I am guessing you had an AI write this all for you and you didn't check for accuracy...
If only I would've found this thread a little earlier...
I managed to do the same but I struggeled a lot with it.
Mine also misses the persistent storage.
the add-on itself runs fine on a Raspberry Pi 5 — I build for aarch64 alongside amd64.
The only limitation on ARM64 is the Slicer API sidecar (the optional BamBuddy feature that lets you slice files server-side without a desktop slicer). Bambu Lab doesn't publish an ARM64 AppImage, so that specific feature won't work on a Pi. Everything else — printer management, virtual printer, archives, queue, dashboard — works normally.
In terms of resources, BamBuddy is a Python/FastAPI app and is fairly lightweight. A Pi 5 with 4GB+ RAM should handle it comfortably alongside a standard HA installation, though it depends on how many other add-ons you're running.
If you hit any issues specific to the Pi 5, feel free to open an issue on the GitHub repo!
Update: I've added a second app to the same repository — Bambu Studio API.
This is a fork of griffinmartin's ha-app-bambu-studio-api, with one key addition: automatic version tracking. A daily GitHub Actions workflow checks for new Bambu Studio releases and opens a PR with the updated Dockerfile, config.yaml, and CHANGELOG.md — so keeping the sidecar's Bambu Studio version current no longer requires a manual bump. Just merge the PR and HA offers the update as usual.
What it does:
Runs the official Bambu Studio slicer headless, wrapped in a REST API
Lets BamBuddy (or anything speaking the same API) dispatch server-side slicing jobs — no desktop slicer install needed
Automatic upstream version tracking (see above)
Note: amd64 only — Bambu Lab doesn't publish an ARM64 AppImage for Bambu Studio.
I tried this bambuddy app from nakedhead as from Spegeli
Both addons (ha os) dont start up… My friend also tried both, with same result.
Anhyone else experiencing problems???
It’s hard to say without more information. Could you please open an issue and fill in all the requested details?
That will help me investigate and try to help you.
Ok installed everything, set up a virtual printer, added the certificate, but as soon as i try to add/connect the virtual printer in bambu studio i get a connect -1 error.
However i found out that (im also running mosquitto broker on same machine as bambuddy), as soon as i disable broker, trying to connect to virtual printer works immediately
So i guess port issue on 8883 ? Now what?
good catch on the diagnosis — that confirms it’s a port conflict on 8883.
The fix is to move Mosquitto’s SSL/TLS listener off 8883, since BamBuddy’s virtual printer needs that port and it can’t be changed (it’s hardcoded in Bambu Studio).
Here’s what to try:
In your Mosquitto configuration, change the “Normal MQTT with SSL” listener port from 8883 to something else (e.g. 8885) and restart the broker.
Check your Mosquitto logs — in most cases your other integrations and devices connect on plain MQTT port 1883, not the SSL one, so they likely won’t be affected at all.
Any client that was using 8883 (SSL) will need its port updated to 8885 (or the number you selected in step 1).
If changing the Mosquitto port breaks something you can’t easily reconfigure, the alternative is to give BamBuddy a dedicated IP alias so both services can use 8883 on different IPs — but that’s harder to set up on HA OS, so try the Mosquitto port change first.
