Solution: Printer not saving a custom filament profile to an AMS Slot

Problem: In Bambu Studio or Bambu handy, setting a custom filament profile to a slot in the AMS suddenly doesn’t work. When a custom profile is saved, the AMS displays the profile in the correct slot but then after 5-10 seconds, the profile is removed and the “?” appears again.

Solution: This seems to be an issue with the printer syncing with the cloud service. To fix, follow the steps below. This was performed on my P1S but its probably similar for other printers:

  1. Turn on the printer and navigate to where your account is listed. Just leave it at this screen.
  2. Open the Bambu Handy app and go to Devices and tap the hamburger menu (three horizontal bars) at the top right.
  3. Tap Delete Device and confirm deletion.
  4. Confirm on the printer that the account has been removed. Go back a screen in the menu then enter the account option again. You should see a 6 character pin code.
  5. Open Bambu Studio on your computer and select the Device tab. The printer should no longer be there. If it is, sign out and log back in to confirm the printer is gone. (Note: Do not use Bambu Handy to add the printer. It didn’t work for me. You need to use the cloud generated pin code)
  6. With the printer gone, add the printer again by clicking the “+” icon towards the top right of Bambu Studio.
  7. A new window will pop-up asking for the pin code. Enter the pin code and click Confirm
  8. Your printer should now be visible again. Try and map a custom filament profile to an AMS slot again and it should work.

If there are any differences with other printers, please note them below. Thanks.

8 Likes

This doesn’t seem to work on the P1S.

I created a custom filament profile in orca slicer, which showed up In the [prepare pane in both Studio an Orca Slicer. I think I printed using the the profile from Orca, and got the unknown filament in AMS confirm dialog.

The next day, Orca had lost contact with the printer.

I used this post an re-established the printer connection to both slicers, but I still can’t select the custom profile for an AMS slot on the device page.

I now notice that it also doesn’t show up as an option for the external spool either.

Hi there, unfortunately your complete guide doesn’t work for X1 users due to the inability to login with a PIN. I’ve tried re-adding my X1C both with the QR code and by letting Studio detect it on my network and neither seemed to resolve the issue with custom filament profiles “sticking” when assigned to the AMS via Handy, Studio, or directly on the printer display. Appreciate you working to find solutions.

1 Like

Having the same problem on X1E.
Fix doesn’t work.
Really frustrating.

I know this is an old post but I recently had this issue. I turned off the printer and walked away for about an hour. I plugged it back in and it started working again.

I had a slightly different isssue, but similar. I deleted the new filament profile and added it back a few minutes later and that worked also. I agree this is a cloud sync issue and sometimes just a simple reboot works.

This issue was exactly what I was experiencing and the described steps for rebinding the printer after deletion worked perfectly for me. Thanks!

I had the issue where I could not update my X1C with a custom filament.
X1C showed the error message “Failed to obtain cloud custom material information”
Rebinding the printer to my account worked.
Instead of the PIN, I had to use the mobile Handy app to bind the printer (using the QR code).
On the X1C, I was able to see the added custom filament listed.

1 Like

I just had this issue, was unable to find a PIN code to readd the printer and adding with the QR code gave the same problem. However I was able to add the printer back using network Access Code/Serial Number option and then it saved the filament profile info again so thanks for putting me on the right track.

Thank you for sharing this. It fixed the issue on my X1C. I used the QR code to bind the printer.

Been struggling with this for months, to finally come accross this and rebinding fixed it for me.

God, I’m tired of figuring out what I’m doing wrong. I already thought I was too dumb (haha, after a couple of custom homemade printers, I couldn’t figure out AMS from Bambulab), but no. In my opinion, it’s a gross mistake by Bambulab. Although I think they’re not particularly interested in fixing errors related to third-party filament brands.

Anyway, the solution helped me to set custom filament to AMS. It didn’t cause any problems. All the while, I used Orca instead of Bambu Studio, and the problem was still resolved (it’s not necessary to use Bambulab Studio app for the fix to work).

Any update on this? I have a ton of non-bambu filament and this is making it impossible to use it. As much as I LOVE my P1S, I will NOT be okay with them making it a Bambu only product/device.

Glo’s solution worked for me on my X1C

I am newly (July 2025) having this same issue on my P1S. Can’t change filament in my AMS2 Pro to anything except Bambu rolls auto detected with RFID. I can go set it in the handy or studio app but then within about 10 seconds it reverts to an unknown filament type with a ?.

Latest firmware, app and studio versions. I’ve also factory reset, reinstalled the app and even changed and rebound the printer to an entirely new account. Also have confirmed the Studio app is only running on a single PC and not had Bambu Studio and Bambu Handy running at the same time.

Same problem, this is frustating!

Recently had this problem in July 2025. Opened a support case with Bambu and they provided a workaround of enable-lan-mode.

They also shared the root cause for me:
[Root Cause and Current Situation]
Our cloud service provider began a security upgrade in a phased manner on July 24th. During the upgrade process, we received feedback from a small number of users stating that the commands to control the printer were not functioning correctly. We promptly contacted the provider and rolled back the upgrade. The system returned to normal operation after 8 p.m. on July 30th.

[Follow-up Measures]
Please rest assured that this issue will not affect your future usage. Additionally, we will strengthen our management of the supplier to prevent such incidents from happening again.

I’d suggest trying LAN mode and opening a support case.

I fixed it by simply closing and opning Bambu Studio, and it seems that work well.