tl;dr: “Fuck You, we’re right, but here’s a crumb from the table” but in PR-speak.
There’ll be a Lan-Mode (still requiring Bambu Connect), and a Dev-Mode (which will continue MQTT, live steam and FTP).
The Writing continues to be on the wall.
tl;dr: “Fuck You, we’re right, but here’s a crumb from the table” but in PR-speak.
There’ll be a Lan-Mode (still requiring Bambu Connect), and a Dev-Mode (which will continue MQTT, live steam and FTP).
The Writing continues to be on the wall.
But don’t they currently allow local connections and also use them if the printer is running in cloud mode? I would assume if the printer can be “seen” by your machine locally, Bambu Studio would connect locally for some of its data transfer? Regardless of printer configuration (LAN only or Cloud) it still has its local ports open, which currently can be used by e.g. Home Assistant without any cloud connection. This is nice, but at the same time can be a security risk, as any local malware might also send commands. So a way to secure the local connections is definitely needed.
API keys would be nice for any type of connection, but it’s something they’d need to implement, including a way to request/revoke them from either your Bambu account (cloud again, not preferred by the open source community) or directly from the printer (might be a hassle to use with the P1S’ small screen). Instead they decided to go full-throttle by using some form of certificate authentication, possibly using per-device and per-account certs in the future, that might be generated locally and signed by their endpoints using your Bambu account.