Bambu Studio completely forgets LAN only printer between sessions

[RoubenRehman]

Bambu Studio Version

2.4.0.70

Where is the application from?

Bambu Lab Official website

OS version

Windows 11 and NixOS

Additional system information

No response

Printer

Bambu Lab P2S

Printer Firmware Version

01.00.05.00

How to reproduce

1. P2S in Lan Only Mode with developer mode enabled
2. Open Bambu Studio
3. Go to the "Device" tab
4. Click "Connect with access code"
5. Enter Printer IP and access code => Printer connects and can be used
6. Close Bambu Studio
7. Open Bambu Studio

Now, there is no device under the "Device" tab and the whole procedure has to be done again.

Actual results

I can connect to the printer, but the connection is not remembered after closing Bambu Studio. Upon launching it again, the printer has to be bound again from the start by entering its IP and access code.

Expected results

When re-opening Bambu Studio on the same machine after the printer was bound before, Bambu Studio should remember the printer - rebinding it every time should not be necessary.

Project file & Debug log uploads

I've tested this on a desktop PC and a Laptop on Win 11, NixOS (native), and NixOS (flatpack). The issue persists everywhere.

Checklist of files to include

• Log file
• Project file

[RoubenRehman]

I was able to partially circumvent this issue, but the behaviour is - in my opinion - still suboptimal.

My local network is situated so that my PCs access smart devices like the printer through a router. While the printer thus remains accessible via its local IP, this prevents auto-discovery because the router does not reverse-broadcast those packets to its clients.

By moving the printer to the same LAN the PCs use, BambuStudio now auto-discovers it in the device tab and I can click connect. The access token is saved and does not need to be entered again.

I am aware that the initial networking setup could be kept by using services like Avahi reflector, but in my opinion it would be far easier if BambuStudio would just save the local IP together with the access token. That way, it wouldn't rely on auto-discovery for machines that were already bound manually.

[ziogref]

I am also facing this issue, but only on my Linux machines.
I have the printer in Lan only mode.
On my Windows machine, the application remembers the printer and its a 1 click connect.
On my Linux Mint Desktop and my Kubuntu laptop (Both use Ubuntu as a base) using a mix of the latest appimage and flatpak it will forgot the printer on exit, requiring me to enter the IP address and randomly generated access code each time I open the app.

[RoubenRehman]

@ziogref are all of your machines on the same network with the printer without any NATs, routers, etc. in between? I think BambuStudio never actually remembers the printer, it auto-discovers it because the printer is announcing its presence on the network. Either those announcements never make it to your Linux machines, or something is up with your networking stacks. I'll check if my NixOS installation works now and report back. Did you install the network plugin and are sure that BambuStudio has network access on your machines?

[RoubenRehman]

@ziogref after switching to my NixOS installation, I can confirm that the issue persists on Linux for me too. I'm currently using the flatpack version - 2.4.0.70. This is most likely an mDNS issue, I'll look into this further.

[ziogref]

@ziogref are all of your machines on the same network with the printer without any NATs, routers, etc. in between? I think BambuStudio never actually remembers the printer, it auto-discovers it because the printer is announcing its presence on the network. Either those announcements never make it to your Linux machines, or something is up with your networking stacks. I'll check if my NixOS installation works now and report back. Did you install the network plugin and are sure that BambuStudio has network access on your machines?

No. I use Ubiquiti, they are on separate VLANs (but currently no blocks between the networks).
My desktop dual boots Windows 11 and Linux Mint. Windows has no issues, Linux mint does.

As for the network itself I think the path is Bambu -> Wifi AP -> UCG Fiber router (which doubles as a switch) -> PC (Ethernet)

I basically have narrowed it down to the Linux Images having something missing or wrong.

[RoubenRehman]

I found this old discussion stating:

Bambu appear to have implemented Multicast SSDP instead of mDNS, Which is a shame as Avahi does not support this.

I suspected the issue to be mDNS not being properly processed by Linux, so I've installed Avahi but ´avahi-browse -a` yielded no results. Apparently, Bambu doesn't use mDNS though but Multicast SSDP instead. I'm unsure however whether the logic that listens to these packages should be part of BambuStudio or a system daemon. In my brief search so far I've not found any such daemons.

[fahaaaxiki]

Hello，could you provide your log files to help us solve this issue？
The steps to obtain the logs are as follows：
https://wiki.bambulab.com/en/x1/troubleshooting/bambu-studio-log

[DiegoDAF]

Hello，could you provide your log files to help us solve this issue？ The steps to obtain the logs are as follows： https://wiki.bambulab.com/en/x1/troubleshooting/bambu-studio-log

I have the same problem in Linux Mint, with the AppImage.
This is my log file: debug_Mon_Jan_26_11_17_05_1297289.log
May it help.

Some extra notes from Claude:

Environment:

• OS: Linux Mint 22.2 (Ubuntu Noble based)
• Bambu Studio: 02.04.00.70 (AppImage)
• Printer: P2S
• Mode: LAN Only + Developer Mode

Behavior:

• Printer connects successfully via IP + Access Code
• Connection works fine during the session
• After closing and reopening Bambu Studio, printer is forgotten
• Must re-enter IP and Access Code every time

Log evidence:

• Connection establishes correctly: set_selected_machine: select new lan machine, dev_id =22E*********496
• NO logs showing save/persist of LAN printer configuration
• Config file ~/.config/BambuStudio/BambuStudio.conf shows empty user_access_code section
• No IP stored anywhere in config directory after connection

Workaround:
Currently re-entering IP and Access Code on each session.

[h0m35t4r]

I believe this is now working in the latest 2.5 minor release. I opened Bambu Studio today and was happy to find that my LAN only mode A1 mini was already connected.

Looking through the commits since the 2.4 release, it appears this is the commit that has fixed this issue 79c14b5

[RoubenRehman]

I can confirm that this seem partly fixed to me too. I've updated my flatpack version on NixOS, which yielded Bambu Studio 2.5.0.64 - not quite the most recent build. After connecting to my printer once using Bind with Access Code and entering its local IP and code, it so far has remained connected in between restarts.

However, I still had to manually bind the printer, unlike the Windows Version, which shows the printer automatically as available on the network.

[ziogref]

This is fixed for me as well. I use the flatpak