det.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
Mastodon Server des Unterhaltungsfernsehen Ehrenfeld zum dezentralen Diskurs.

Administered by:

Server stats:

2.1K
active users

#bambulabs

0 posts0 participants0 posts today

I may have added slightly too much oil on the Y axis steel guide rods on my #bambulabs #p1p. Like there’s still some “puddling” of excess oil on the top of the rods - I may gently wipe any of that off when I get home tonight.

While we are all mad at #bambu for being evil, here is a quality of life improvement for anyone stuck with one of their units. Hopefully it improves your day. (Also, it makes it much easier to get along without their spyware.)

The printers' MQTT broker only accepts a couple of connections. 4 I think. This is an issue if you (for example) use a slicer(1), home assistant(2), xtouch (3), octoprint (4-5), nodered(6+), etc.. And once you use them up, you have to basically turn everything off for a while (up to 12 hours! in my experience) before you can start connecting again.

Using this, any number of clients that use pure MQTT (or handle failures appropriately) can be multiplexed to the printer over a single connection. xTouch, OctoPrint, everything.

gist.github.com/disconn3ct/7257eb31fa278ae9f4ca0b3b0892cb7b

@3dprinting #3dprinting #bambulab #bambulabs #mqtt #homeautomation #smarthome #mqtt

 Mosquitto relay for Bambu Labs printers . GitHub Gist: instantly share code, notes, and snippets.
GistMosquitto relay for Bambu Labs printers Mosquitto relay for Bambu Labs printers . GitHub Gist: instantly share code, notes, and snippets.

It seems Bambu Labs is making a change that creates a hard dependency on their cloud service to use their printers, even if you're running in LAN mode. This is disappointing, as I'd really like to get an X1C for their print quality, flexibility, and ease of use. I don't want to use their cloud, tho.

I've created a basic framework for a local-only Authorization Control System that would provide equal security without using the cloud.

duksta.org/post/2025/01/19/a-p

Ramblings of an Elder Nerd · A proposal for local-only Authorization Control for Bambu PrintersA CC0 licensed proposal for Bambu Labs or anyone else to use to provide a secure binding between an embedded device with an on device UI and a local management application for access to privileged APIs
Continued thread

It seems to me that if Bambu Lab is concerned and upset by malicious or excessive queries to their cloud infrastructure then they should decrease its necessity.

1. Enhance the user experience around LAN and direct connectivity between slicer software and the printer.
2. Allow for third-party clouds.

Every (IoT) vendor seems to struggle with this. At least for Bambu Lab, they have an actual reason for their cloud infrastructure and model repository. But, forcing more features through it when that's apparently "bad" is like doubling down and shooting themselves in their other foot.

Vendor, "You must use our cloud"
Vendor, "Oh no it's so dangerous and expensive to maintain our cloud service"

Continued thread

Here's the official response from Bambu Labs (via OrcaSlicer): They will not be supporting any direct access. Only their app.

I wonder about forced returns since the product is substantially different than advertised...

Prusa has got to be absolutely shitting themselves with joy over this.

github.com/SoftFever/OrcaSlicer/issues/8063

#3dprinting @3dprinting #bambu #bambulabs #orcaslicer #prusa #enshittification

Is there an existing issue for this feature request? I have searched the existing issues Is your feature request related to a problem? Bambu is going to release a "security" firmware update that wi...
GitHubFW 1.08.03.00 from Bambu WILL BREAK ORCASLICER for X, P and A series · Issue #8063 · SoftFever/OrcaSlicerBy WimVDK
Continued thread

This thread has some helpful context and links to a Reddit post.

fosstodon.org/@vordenken/11384

I'm pausing my usage of my printer and will hold off on the firmware update.

I still don't see anything clear on if this change requires Internet connectivity or if the authentication and authorization can be performed locally on device/LAN without Internet connectivity.

I overall agree that this is a bad direction.

I think that adding security around printer controls is good. But, I don't understand why it was done in a way that blocks third-party tools. This screams "security through obscurity" and DRM. Both are more security theater than actual security. There has to be a better AAA option that also supports third-party software.

Fosstodonvordenken 👨🏼‍💻 (@vordenken@fosstodon.org)If you own a BambuLab 3D-printer, you should read the reddit post and act! We need to stop this as a community! Why you should care about Bambu Labs removing third-party printer access, and what you can do about it https://reddit.com/r/BambuLab/comments/1i3gq1t/why_you_should_care_about_bambu_labs_removing/ #3dprinting #BambuLab #OpenSource

Can someone please explain to me why requiring authentication and authorization to control Bambu Labs printers is a bad thing? We see SCADA and other industrial devices getting wrecked all of the time for trusting all input and commands.

Is it because the authorization is performed by the Bambu Labs cloud and not on the device?

Are they forbidding or blocking custom firmware that can maintain third-party software support?