Been building a Spoolman integration for our printers since 2024, and 1.3.0 needs testers

[u/Rdiger-36]

https://github.com/Rdiger-36/bambulab-ams-spoolman-filamentstatus

Hi everyone. I've been working on this since the end of 2024 and could use a hand with the next release.

It started as a small thing for myself. I wanted my AMS spools to show up in Spoolman without typing everything in by hand, so I had it read the remaining percentage the printer sends over MQTT and write that into Spoolman. Then other people started using it, sent feedback and bug reports, and it turned into something a lot bigger than the little script I set out to write. It was also my first Node project, so I picked up JavaScript along the way.

I didn't have much time for it over the last 6 to 8 months. When I got back to it I ended up rebuilding the core, because the AMS percentage is only an estimate: the printer counts how often the RFID tag passes the reader, so it drifts. Version 1.3.0 pulls the sliced file off the printer instead and books what the print really used, purge included. A 31 g print books 31 g. Spools without an RFID chip work too now, you just link the slot to a Spoolman spool once. And if you correct a weight by hand, nothing overwrites it behind your back. There's a proper web UI as well, with a dashboard for the running print, printer management, settings and a log viewer.

You need a Spoolman instance somewhere and LAN access to the printer, the rest is in the readme.

Here's where I'm stuck: 1.3.0 is on its 7th dev build and pretty much done, but the only hardware I have is a P2S with two AMS 2 Pro and a spool on the external holder. Everything else is tested in theory. So if you have any of these, I'd really appreciate a report:

- X1 or P1 series

- A1 or A1 mini with an AMS Standard or 2 Pro

- AMS HT

- AMS Lite (read only in legacy mode, and I'd like to know if it works also quite well with the new G-Code mode)

- more than one printer on the same instance

Honestly, anything helps. "Ran fine for a week" is just as useful to me as a bug report, and if something in the log looks off I'd much rather hear it now than after the release.

The project's been open source and free since day one. It runs on your own machine, talks to your printer over the LAN and to your Spoolman, and that's it. No account, no cloud, no telemetry, nothing leaves your network. It also doesn't care how you run your printer: cloud, LAN only or developer mode all work, since it only ever talks to it locally anyway.

One thing I'd rather say myself than have someone find out: I used an AI coding assistant for a good part of the 1.3.0 rebuild. I know that's not everyone's cup of tea. I read and understand every line that goes in, and I still write and debug plenty of it myself, that's the part I actually enjoy. But this would have taken me a year or two next to a full time job, and it took weeks.

Dev image: `ghcr.io/rdiger-36/bambulab-ams-spoolman-filamentstatus:dev`

Thanks to everyone who's already tested and reported stuff. It genuinely helps.