If you own a P1P or a P1S, you may have seen that a new firmware, version 1.06.00.00, was released at the beginning of this week. The new firmware brings some welcome changes, but it has a twist!
Before we look into that twist, let’s check the changelog:
- Non-LAN binding via PIN code on the Studio side (in conjunction with Bambu Studio v01.09 and up)
- Improved manual flow calibration parameters management
- Third-party filament support
- Added filament verification for “Reducing purging through retracting filament” function
- Added heatbed abnormal protection
- Added carbon rods & lead screws maintenance notice
- Improved color display for gradient and dual-color filaments
- Added option to opt in/out of User Experience Improvement Program in Settings > Devices
- Added secondary confirmation when stopping a print as safety to protect the user from accidentally canceling a print.
- Optimized Total Print Time Calculation, add abnormal pausing time into the stat.
- Auto filament type verification when printing with 3MF files from an SD card
- Improved the Custom Device Name function to auto-save the custom name when logging out. The name will also synchronize across devices.
- Fixed the button no response glitch when formatting the SD card
- Fixed intermittent black screen after power-loss recovery
- Optimized firmware update printer status check for safer update
- Optimized status verification when downloading a language package to avoid process conflict
- Fixed the issue of devices being unable to send print jobs after not restarting for an extended period.
- Prevent conflicts with Bambu Cloud service & potential damage to printer hardware by prohibiting crucial printer controls (initiating printing, heating the nozzle, and heating the heatbed) through the local MQTT Broker while the printer is logged into Bambu Cloud service.
Most of these are just regular improvements to great printers. Yet, if you carefully read the highlighted part of the last change, you might spot something that breaks a feature you may have relied upon. More specifically, if you own an XTouch or BigTreeTech Panda Touch display or use Home Assistant to control your printer, updating to 1.06.00.00 will prevent them from initiating a print, heating the nozzle, and heating the heatbed. That doesn’t mean those are rendered useless, but it cripples what they can do.
Yet, this might be temporary, as it seems that BigTreeTech will soon release a “cloud mode” firmware update beta. A user who claims to have read it on the Facebook official group has reported this on Bambu Lab’s forum. We cannot confirm or deny this as we are not in this group.
It seems XTouch is also nearing a “cloud mode” and a firmware is already available. You can find out more in their Discord‘s #cloud-release channel.
Also, we don’t know why this restriction only applies to the P1 series. The A1 and X1 series don’t seem to have this limitation. If you are curious, here is Bambu Lab’s explanation for implementing this limitation:
Before this firmware update, the printer’s local MQTT Broker can process control commands under cloud mode. This meant that two asynchronous channels were controlling the printer simultaneously. The commands from these two channels would execute in an overlapping manner without any order assurance, which is considered conflicting.
To ensure the stable operation of the printer and avoid malfunctions caused by control channel conflicts, we will disable certain printer control functions via the local MQTT Broker under cloud mode. These functions have higher security requirements, and we want only one channel to be able to use these functions at any given time. The restricted controls include:
- Initiating print
- Heating the nozzle
- Heating the heatbed
Please note that this restriction will affect the use of software and hardware such as Home Assistant and BiQu Panda Touch. Suppose you still need to use such software and hardware to control the restricted functions. In that case, we recommend enabling the printer’s LAN Only mode to continue using the restricted control functions with the Local MQTT Broker.
As always, the full changelog can be found on Bambu Lab’s wiki page: https://wiki.bambulab.com/en/p1/manual/p1p-firmware-release-history