General Discussion

If you run BamBuddy in a container on the same machine as Home Assistant add-on and the Mosquitto broker add-on on the same HAOS box, and Bambu Studio can't connect to your Virtual Printer (connection error, TLS handshake fails) while the BamBuddy log shows MQTT port 8883 is already in use — this is a port collision on the host, not a BamBuddy bug. Why Bambu Studio hardcodes MQTT/TLS on port 8883 for LAN printers, so BamBuddy's Virtual Printer MQTT server needs host port 8883 (and the HA add-on runs with network_mode: host). The Mosquitto add-on also maps host 8883→8883 by default (its TLS listener). Mosquitto wins the bind, so Bambu Studio connects to Mosquitto's cert instead of the Virtual Printer CA cert → TLS verification fails. Fix (HA UI only — the SSH add-on's SUPERVISOR_TOKEN is read-only on the supervisor API, so this can't be scripted) Settings → Add-ons → Mosquitto → Network. Remap the TLS listener host port 8883 → 8885 (leave 1883/1884/8884 as-is). Restart the Mosquitto add-on, then the BamBuddy add-on. Verify BamBuddy log: Simple MQTT server listening on port 8883. openssl s_client -connect <HA-IP>:8883 returns a cert with CN=<your-VP-serial> issued by Virtual Printer CA, Verify return code: 0 (ok). Gotcha a Mosquitto add-on update can reset its network config to defaults and reclaim 8883, breaking the Virtual Printer again. If it recurs, just re-apply the 8883→8885 remap.

Thank you. Works perfectly just wasn't obvious to me.

Please open an issue.

OK, so that's not an open-source option. Proprietary interface only available through purchase of the the Official Bambuddy Appliance. Disappointingly expected. Thanks

I am also having some issues with the virtual printer on a Windows install. I keep getting 508 errors in my terminal. I plan to uninstall Bambu Studio (beta) and reinstall it to see if that helps. Edit: I am able to print in lan mode and see the printer in lan mode through bambuddy.

Ok, I think this was a firmware issue, my A1 mini was freaking out until I updated it to the most recent version. I had things set up properly in Bambuddy, but adding the A1 mini's virtual printer to Bambu Studio or OrcaSlicer resulted in an 'Incorrect Password' error. After updating the firmware and refreshing the access code everything is working correctly!

I think i need to look into it more detailed. Please open an issue for it.

Ahh, you are not talking about custom but standard profiles. They cannot be deleted, this is a BL cloud limitation.

This is available in the next daily image.

https://github.com/maziggy/bambuddy/issues New issue

I only need to restore my print and usage history

All issue related details must go to the issue and not here in the forum!

Need more infos. Looks like a problem with your installation. Please open an issue for it. Thanks.

Please open an issue on Github. Need to look into it more detailed.

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.

Assuming your user info is good, check your permissions on the bambuddy folder in file station. I grappled with this for a bit before checking permissions and it fixed it for me.

@teknoziz What kind of NAS do you have? Maybe I can help—I'm running it on a NAS as well.

That doesn't work. Use the integrated tailscale.

Mhhh...I see multiple projects which are actively maintained. Anyway....of course it's your choice

If your slicer can reach your physical printer directly, VP mode proxy is not the right one for you. You either need to use one of the other VP modes or make sure that the slicer cannot reach the physical printer directly.