Did they? Your screenshot cuts off the rest of the release.
Isn’t this what the community was asking for? Full control with no connection or control from the cloud?
Oh and it’s interesting to note there is now a “Bambu Local Server” option (Pulled from the Prusa playbook?).
The Bambu Connect wiki page still says (beta) and there’s still no Linux version (I don’t have a computer with macOS or Windows unfortunately); I’m confused why this firmware update was released when it seems like Connect is still under development, is there a rush? 
No lol. We already had full control with no connectivity to the cloud.
They pushed out no control unless you completely disconnect from the cloud
Except there is now a monkey wrench in Bambu’s targeting. It’s called the Centauri Carbon. Half the price of a P1S, reviews have all been positive. The MMS is coming out later this year.
The other area this will screw things for Bambu is people like me who are looking at adding more printers this year and making recommendations to friends asking “which printer should I buy?”
I wouldn’t exclude Qidi Plus 4 from the possible options, at least for the time being.
LOL no. The “developer mode” was basically a “last resort” type of solution, but it’s absolutely incomplete - there’s no “handy” so one has to use all the other 3rd party tools full time in that mode… Which is stupid, because any dev team worth their salt could make it so that local commands stay local without the need for the cloud and with all the safety features… but noooo apparently hiring experts and listening to advanced members of community is “saving face” XD
Also that “bambu local server”… Requirements: “Windows 10 or later” and “64-bit cpu with x86 instruction set”… For HTTP server? LMAO.
I know what I’m explicitly not recommending.
Yeah isn’t it nice? After having done my “homework” before buying to ensure things will run fine with my operating system 
, like we keep being told, this happens. If I were to update (accidentally or otherwise), this rug pull prevents me from using the software I had working perfectly fine prior to the 30 day return window closed.
So I guess the “do your research before buying” line morphs into “you agreed to the terms” and “you should have known the risks” at that point. Or some other blame the victim phrase.
I won’t hold my breath for a working Linux version any time soon.
Well, windows 7 is no longer a supported OS and neither is 8, what version of windows did you think would end up as the minimum required version?
There aren’t any other versions left below 10 anymore
I’m sure Johnny will clarify shortly, but I am going to speculate that the issue is that it’s only for Windows (No Linux? For a server application?) and only x86 CPUs (no ARM). So basically it looks like amateur hour again.
And of course “Linux Docker support is currently in development to enable multi-platform support”. (Seriously, we’d need to run this thing in a Docker container?)
Normally Linux is THE go-to for server applications. Using Windows for a server these days… well let’s just say many IT pros will laugh if you admit to it. Especially for something like this, which should be a lightweight use case. It should probably run on a Raspberry Pi and so on. But not with those requirements.
It should support native Linux, and not just x86. But as we already know, a “small” company with many millions of dollars in revenue (or something) cannot yet afford the expensive technology professionals required for correctly implemented security… or this. 
@Lou explained nicely. Also, windows 10 isn’t server os, it’s desktop one.
I would for beginners based on the price to get in . The Carbon is $400 cheaper and a few of the more advanced specs in the Qidi printer won’t mean much to beginners. The print size may or may not come into play.
For people with experience, I agree with you.
And not sure what a server OS has to do with running the client, even then 2022 is the only mainstream supported version of windows server, there are some older versions with paid extended support options, either way not really relevant for running bambu connect as thats aimed at consumer machines, in which case windows 10 is the minimum supported version of the OS for pretty much anything these days
What makes you think connect is a server application exactly?
Its built for running on the same machines that would run the slicer, its just there to act as a go-between for 3rd party slicers and software, the protocol hooks for bambu connect won’t even work in a server environment to begin with without a fair amount of extra work, its designed to run on the end user machine
We’re talking about the “Local Server” component. But thanks for your input.
As a once potential customer, EVERYTHING I am hearing on BOTH sides of the argument have led me to look at any printer EXCEPT Bambu. My concern is that while existing owners have the option of not upgrading, what is shipping on NEW printers. My primary reason for looking at Bambu was the number of community users that stated it was very easy to get set up and just PRINT. Now I am seeing those same users complain about various issues creting difficulties. Now I am leqning towards Creality or Anycubic. The beta test has been a disaster and rather than roll it back and do further inhouse testing and development, the company seems to be saying take it or don’t so i chose NOT to take the risk and will spend my hard earned money ELSEWHERE.
Your reading comprehension needs some work… Here, let me help you:
I said:
See? For reference, this part is about:
Clearly NOT about Connect.
Lou’s post mentions 2 items that clarify it’s not about connect: “server application” and “linux docker support” which if you had looked at just at connect you’d see that there’s no mention of docker anywhere regarding connect and if you looked at local server you’d know it’s clearly about it.
Hopefully that clarifies it 
No it doesn’t because regardless of what you’re going to be running, if it runs on windows then 10 is literally the oldest supported version of windows
Windows doesn’t deal with arm for the most part and x86-x64 is the defacto standard for most devices at this point, yes you could make the argument for mac transitioning over to ARM based hardware but at present their market share is not really large enough to matter
So yeah i’m not sure why you would expect them to be building for ARM or really even building with linux in mind, the windows 10 version will run on server 2022 without any issues, hell you could even throw it in a hyper-v environment if you really really wanted to
Lemme be blunt here - locking a “local server” to Windows 10 is laughable. People who would run a “local server” very likely already have actual local servers running Linux. Your defense of this Windows-only, x86-only requirement ignores the reality of how server-grade systems work. It’s not just a bad choice; it’s a rookie move that screams amateur hour.
How certain are you about that?
Personally I wouldn’t make such a statement so confidently…
