I have several, and they're all running in DevMode/LAN Mode. I drive them using this project:

https://bambuddy.cool/

LAN mode works well with home assistant and some HACS Bambu integration. Takes some setup but then you get real time camera feed and all the nice sensors for temp, humidity, including any AMS you have. I connected mine to Bambu server for the app just to see what it does, and my home assistant setup still works over LAN. Great printers and for now offline modes work well.

Is it possible to back out the firmware updates and setup that came along with this change to get self sufficient, or is that not necessary? I recall hearing that a firmware update made the printer (P1S in my case) phone home even potentially when in LAN mode. This is an area where I just kind of gave up and let it happen, though I kind of regret it now.

I know I'm worried when they're going to start mandating client-side scanning of 3D prints.

https://www.eff.org/deeplinks/2026/06/we-can-still-stop-cali...

This part gives me hope, but I have not been able to find the certificate:

Option B: cloud mode without Developer Mode

Starting with v2.0.0 the plugin can also drive a cloud-paired printer with verification left ON — no Developer Mode. This keeps the cloud features (cloud print dispatch, print history, MakerWorld) but is meant for advanced users, because it requires private slicer credentials that this project does not distribute.

Two things are needed:

1. Bambu's slicer credentials, which you provide yourself. Put slicer_cert.pem, slicer_key.pem and slicer_crl.pem in the plugin's config directory (or point at them with slicer_cert_pem / slicer_key_pem / slicer_crl_pem in obn.conf). The plugin uses the key to sign MQTT print commands and to install its app certificate on the printer. These are private credentials. This project does not ship them and gives no instructions on obtaining them — you have to find or extract them yourself, and you alone are responsible for ensuring your use complies with the applicable terms and law.

2. Two settings in obn.conf. Set block_cloud = 0 (the default 1 blocks cloud printing outright) and client_name = BambuStudio (the honest default client name is rejected by the cloud print API with HTTP 403).

With that in place you get signed MQTT commands, on-printer app-certificate install, cloud print dispatch, print history and MakerWorld — without touching Developer Mode.

What the default cloud_print = cloud_only actually uploads. Even in this mode the model itself normally stays on your network: for a print with a cloud record the plugin sends the .3mf straight to the printer over LAN FTPS, and only the record goes to Bambu — a project entry, a task entry (mode=lan_file) and a small config .3mf that print history uses for its thumbnails. That record is exactly what buys you the cloud extras: print history in Studio and Handy, and the ability to rate models on MakerWorld. The full model is uploaded to Bambu's servers only when Studio dispatches a pure cloud print (start_print), e.g. for a printer that is not reachable on your LAN.

You can limit even that: set cloud_print = try_lan_first or lan_only to print over the LAN without writing a cloud record at all, and cloud_hide_history = 1 to hide the cloud print history in Studio.

If you run neither Developer Mode nor valid credentials, the printer rejects every print / project_file command and shows on its screen:

MQTT Command verification failed err_code: 84033543

Is it faster to send prints than using the cloud Bambu service?

Oh shit, I didn’t realize that had been cracked. Nice, I’m gonna switch ASAP.

I bought a P2S, and then literally a few days later, the X2D came out. Thanks Microcenter, and your excellent customer service and return policy. The X2D is everything the P2S is, but with another nozzle.