Bambu lab filament manager in handy app

[mgguinne]

Hi I noticed that there is now filament management built into the bambu lab handy app. I wonder if this could be exposed on the API so that we can have the data fed into a spool management software like spoolman etc.

[neoKushan]

Now that this has appeared in Bambu studio, I have wondered about this myself. It'd be really handy to pull the current filament details into HA as I'm always having people ask what filaments I have or that need using up. Would be a good way of setting up reminders that I'm running low on common filaments and stuff like that.

[neoKushan]

I have just created a PR that adds this functionality: #2028

[Timmes123]

Hi all – in case it helps anyone here: I built a separate HACS integration for exactly this, Bambu Filaments (https://github.com/Timmes123/ha-bambu-filaments). It mirrors the cloud Filament Manager library into Home Assistant (one device per spool with remaining weight, official color names, a dashboard card, create/edit/delete actions) and, when ha-bambulab is installed, uses its AMS slot sensors to do the things the Bambu apps only do while open: register a freshly loaded RFID spool, keep remaining weights current, book empty spools, and deduct print usage from third-party spools.

It is deliberately a separate integration rather than a PR here, since it needs its own cloud login and touches the library read/write – it complements ha-bambulab and does not replace anything. If the maintainers would like to list it as a companion project, I'd be glad, and I'm open to feedback on how the two should interact.

Disclaimer: it uses the unofficial cloud API, so it may break whenever Bambu changes things.

[neoKushan]

This is a good idea! I have to admit, I'm frustrated my PR here has languished since June with zero response from the ha-bambulab maintainers and this seems like a reasonable solution if they're not interested in the filament management functionality being part of the addon. I'd prefer it was all in one integration so we're not having to manage the same credentials in two separate instances, but this works and means I don't have to keep rebasing my PR.

[Timmes123]

Thanks! I'd genuinely like it to live in one place too, and I hope your PR still gets a look. The thing is, mine has grown well beyond a read-only inventory sensor – creating and editing spools from HA, a card, auto-registering freshly loaded RFID spools, remaining-weight sync and runout handling via the AMS sensors, usage booking for non-RFID spools. That's a lot of cloud write access plus its own options; as a PR here it would be huge, and the maintainers would have to want to own that. That's why I decided to build it as a separate integration.

On the credentials: the extra login is a one-time thing, then roughly every 90 days when Bambu's token expires, and it keeps re-authentication clear per integration. Sharing the token would tie me to ha-bambulab's internals and wouldn't help LAN-mode users at all, so I'd rather keep that separate.