[GH-ISSUE #427] [Bug]: API filament query does not return filaments created in UI (only API-created filament is returned) #265

New issue

Closed

opened 2026-05-07 00:08:15 +02:00 by BreizhHardware · 1 comment

BreizhHardware commented

2026-05-07 00:08:15 +02:00

Owner

Originally created by @kleinerflo on GitHub (Feb 18, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/427

Originally assigned to: @maziggy on GitHub.

Bug Description

When querying the API endpoint for filaments, the response does not include filaments that were created via the Bambuddy UI.

Additionally, even after creating a filament via the API, it does not appear under “Filaments” in the UI. However, the API query returns only the filament that was created through the API itself.

This suggests that the UI filament storage and the API filament storage might not be synchronized or might use different data sources.

Expected Behavior

The API should return all filaments stored in the system, including those created via the UI.
Filaments created via the API should appear in the UI filament list.

Steps to Reproduce

Create one or more filaments in the Bambuddy UI under Filaments.
Call the API endpoint to retrieve all filaments.
Observe the response.
Create a filament via the API.
Call the API endpoint again.
Check the UI filament list.

Printer Model

P2S

Bambuddy Version

0.2.0

Printer Firmware Version

01.01.01.00

Installation Method

Docker

Operating System

Linux (Ubuntu/Debian)

Relevant Logs / Support Package

Screenshots

Additional Context

No response

Checklist

I have searched existing issues to ensure this bug hasn't already been reported
I am using the latest version of Bambuddy
My printer is set to LAN Only mode

Originally created by @kleinerflo on GitHub (Feb 18, 2026). Original GitHub issue: https://github.com/maziggy/bambuddy/issues/427 Originally assigned to: @maziggy on GitHub. ### Bug Description When querying the API endpoint for filaments, the response does not include filaments that were created via the Bambuddy UI. Additionally, even after creating a filament via the API, it does not appear under “Filaments” in the UI. However, the API query returns only the filament that was created through the API itself. This suggests that the UI filament storage and the API filament storage might not be synchronized or might use different data sources. ### Expected Behavior - The API should return all filaments stored in the system, including those created via the UI. - Filaments created via the API should appear in the UI filament list. ### Steps to Reproduce 1. Create one or more filaments in the Bambuddy UI under Filaments. 2. Call the API endpoint to retrieve all filaments. 3. Observe the response. 4. Create a filament via the API. 5. Call the API endpoint again. 6. Check the UI filament list. ### Printer Model P2S ### Bambuddy Version 0.2.0 ### Printer Firmware Version 01.01.01.00 ### Installation Method Docker ### Operating System Linux (Ubuntu/Debian) ### Relevant Logs / Support Package ```shell ``` ### Screenshots <img width="1071" height="641" alt="Image" src="https://github.com/user-attachments/assets/a84a0c56-f36f-41b8-b0e8-6b2544f9e600" /> <img width="2273" height="653" alt="Image" src="https://github.com/user-attachments/assets/add1d758-737c-4a35-abc1-920f287b0f35" /> ### Additional Context _No response_ ### Checklist - [x] I have searched existing issues to ensure this bug hasn't already been reported - [x] I am using the latest version of Bambuddy - [x] My printer is set to LAN Only mode

BreizhHardware

2026-05-07 00:08:15 +02:00

closed this issue
added the
bug
label

BreizhHardware commented

2026-05-07 00:08:15 +02:00

Author

Owner

@maziggy commented on GitHub (Feb 18, 2026):

Thanks for reporting this! You're right — the /api/v1/filaments/ endpoint and the "Filament" page in the UI are two completely separate data stores, which is confusing.

UI "Filament" page → spool inventory (your physical spools) → API: /api/v1/inventory/spools/
/api/v1/filaments/ → material type catalog (filament definitions with cost, temperature, density data)

We've renamed the endpoint to /api/v1/filament-catalog/ to make this distinction clear. If you're looking to query your spool inventory via the API, use /api/v1/inventory/spools/ instead.

Available in branch 0.2.1b.

If you find Bambuddy useful, please consider giving it a ⭐ on GitHub — it helps others discover the project!

@maziggy commented on GitHub (Feb 18, 2026): Thanks for reporting this! You're right — the /api/v1/filaments/ endpoint and the "Filament" page in the UI are two completely separate data stores, which is confusing. - UI "Filament" page → spool inventory (your physical spools) → API: /api/v1/inventory/spools/ - /api/v1/filaments/ → material type catalog (filament definitions with cost, temperature, density data) We've renamed the endpoint to /api/v1/filament-catalog/ to make this distinction clear. If you're looking to query your spool inventory via the API, use /api/v1/inventory/spools/ instead. Available in branch 0.2.1b. ----- If you find Bambuddy useful, please consider giving it a ⭐ on [GitHub](https://github.com/bambuman/bambuddy) — it helps others discover the project!