Feature requests, bug fixes, and dev-mode bambu support!
Added
Spool home locations (#38)
When a spool comes off a toolhead it can now go back to the drybox or shelf it came from, instead of to one shared default location.
Turn on "Return each spool to the location it came from" under the auto-assign setting in Advanced Settings. FilaBridge notes where a spool was as it goes onto a toolhead, along with any storage location you scan or assign it into, then sends it back there when it comes off. There is nothing to configure per spool, it is all detected in the background.
Spools FilaBridge has not seen come from anywhere yet still fall back to the default location, so nothing changes for existing setups. Off by default.
Thanks to @eVoxOne for the suggestion.
Bambu Lab support, developer preview
FilaBridge can now track prints on Bambu Lab printers over your local network, with no Bambu Cloud account involved. Live state and progress come over MQTT, the per-filament gram counts come from the sliced .3mf pulled off the printer over FTPS, and both feed the same Spoolman usage recording that PrusaLink printers already use.
This is early, and hidden behind a developer flag. Set FILABRIDGE_DEVELOPER_MODE=true to get the printer type selector when adding a printer. Without it, Bambu printers cannot be added at all, so nothing changes for anyone who does not opt in.
Known gaps, so please do not point this at inventory you care about yet:
- AMS slot mapping is positional. FilaBridge currently assumes slicer filament 1 is AMS slot 1, filament 2 is slot 2, and so on. If your slicer's filament order does not match your AMS slot order, usage gets deducted from the wrong spool with no warning. Proper AMS mapping is on its way.
- Multi-plate .3mf files are not properly supported yet. FilaBridge always reads the first plate's numbers, so a multi-plate project printed from the SD card can record the wrong plate's usage. Also on its way.
- Low-filament warnings and auto-pause do not work for Bambu printers yet. Those are still PrusaLink only.
- Flaky initial printer status. A Bambu printer will read offline on the dashboard for up to one poll interval after startup, until the first monitor cycle caches its state
Feedback from anyone with a Bambu printer is very welcome, that is exactly why this is going out early.
Fixed
FilaBridge no longer knocks printers off wifi (#35)
PrusaLink serves HTTP from a wifi coprocessor with a very small socket pool, and exhausting it takes the printer off the network entirely, rather than just failing a request. FilaBridge was building a new HTTP client per request, each with its own connection pool, so sockets piled up over a long print until the printer dropped off wifi.
FilaBridge now keeps one pooled connection per printer, caps itself at 3 concurrent sockets, holds idle connections open across poll cycles, and caches printer status for 90 seconds so the dashboard and websocket broadcasts read the cache instead of hitting the printer. Changing a printer's address or key rebuilds its client, and removing a printer closes its connection.
Spoolman location handling (#32)
- Locations are read from Spoolman's locations setting instead of its spool list, so locations that currently hold no spools show up.
- Unassigning a spool moves it to your configured default location even when that location is empty, instead of clearing the location.
- Toolhead locations reliably generate NFC and QR tags, so a spool can be loaded to a toolhead by scanning.
- New per-printer "clear loaded" button drops stale toolhead mappings without touching Spoolman, for the stuck "already loaded" case.
Printer API key display
Printer cards reported "API Key: Not configured" even when a key was set. They now read the flag the backend actually sends.
Internal
- Removed dead location code left over from the earlier Spoolman location migration, including the create and delete location handlers and routes, an unreachable delete link, the orphaned archive method, and unused NFC payload fields.
- New regression tests covering location handling, connection pooling and reuse, spool home locations, and the Bambu slice_info parser and state machine.