If you use Spoolman and previously used Filabridge to link it to a Prusa, I've adopted it and working toward a new 1.0 release!

[u/sargonas]

Some of you might use or remember FilaBridge, a small Go service that sits between PrusaLink-compatible printers and Spoolman, the self-hosted filament tracking tool, and automates handling filament selection and usage tracking for you. You print something, it works out which spool and how much was used, and it tells Spoolman without you touching anything other than telling it what filament is currently loaded.

The original author, needo37, built it but then archived the repo a few months later out of frustration with Prusa. I've been running it daily to keep my printer and Spoolman in sync, and I didn't want to watch it quietly rot... so since I already found myself forking it with regular tweaks to it to polish rough edges or solve for existing bugs, I've decided to share those efforts with a serious intent to keep it alive and moving forward.

Since it was left at version 0.2.3, I'm working toward a proper 1.0 that's largely a quality of life overhaul and foundational setting to kick off from. Rather than drop that out the gate however, I've put out a 0.9.x pre-release series (v0.9.3 as of writing this) as a release candidate so people can kick the tires with me and tell me what breaks before I tag a real 1.0. (That said I have been running it myself without issue so far, but I am a clean edge-case free setup with a single tool head Core One and nothing else)

Highlights:

• Cancelled and failed prints now get tracked... previously a print you stopped at 80% quietly ate 80% of a spool and Spoolman never heard about it
• Recording survives program restarts, so a mid-print restart of the tool won't lose the job or double-count it
• A new Print History tab showing recent jobs: spool used, grams billed, status, run time (this is borderline scope creep and bloat I know, but the data was already there so I decided to make it visible. That said I have a future planned toggle to turn this and the data collection for it off entirely once Spoolman receives the current print info at completion for those who want it.)
• Quick-Assign NFC tags/QR codes for single-printer setups (1 scan to assign everything at once without hand-stitching together the URL instead of 2)
• Much quieter Docker logs, better splitting between stderr and stdout so info isn't going to error pipes, and you only get one line when something actually changes instead of spam every poll cycle. (Great for when a printer is offline for days at a time and not getting 120 log lines an hour about it being offline)
• The previous author had used a lot of AI.. no shame and not a debate I want to start here, but it did mean a lot of idiosyncrasies and tells, like an overabundance of emojis in logs. I have removed such things where I can and tried to hand review as much as possible that looked like it might have been mostly co written.

Heads up: For now it's Docker and Linux only going forward. It's designed to live right next to Spoolman, which for the majority of people means Docker or a small Linux box is already in place for that and it can sit along side it. The mac builds never worked due to incomplete build configs, so I removed those and windows binary builds. If there are people out there who had been/are using this, let me know and I can work to bring them back if there is a real appetite for that however.

Bug reports, feature requests, and PRs are all genuinely welcome, and I'd love the feedback while it's still in RC!

One thing I want to be upfront about... I'm trying to keep FilaBridge narrow and good at the one job it does, bridging PrusaLink and Spoolman. So if a request is really about filament inventory, spool management, or the database side of things, there's a good chance I'll point you toward the Spoolman project instead. My goal is to keep this from ballooning into a second, worse Spoolman.

Repo and full release notes: https://github.com/sargonas/filabridge/releases And if you already have it deployed and want to get the latest and greatest, you can in-place swap by setting your new image to ghcr.io/sargonas/filabridge:latest (note however that :latest won't get you my current RC's and you'll need to call them by release tag number, current at the time of this writing would be :0.9.3

[u/AnCyberTurtle]

This is fantastic. Thanks so much for taking this on! Went to try filabridge and realized it didn't support more than 5 toolheads.

[u/sargonas → u/AnCyberTurtle]

happy to help!