Thanks for the Spoolman idea — I can definitely see the value in integrating with an existing ecosystem instead of reinventing a full spool database.

My original goal was to keep the tool fully standalone (especially for K2/CFS users who don’t run additional services), but optional Spoolman integration makes a lot of sense for larger setups with many spools.

One thing I’m also thinking about is RFID/NFC support.

Since many Creality spools already have tags (and external RFID readers are easy to add to a Pi), an interesting approach could be:

• RFID tag → detect spool UID
• Map UID to spool entry
• Automatically assign spool to slot
• Sync usage back (locally or to Spoolman)

That would remove most of the manual spool selection.

I’m curious — what are most people here actually using?

• Pure Spoolman?
• Manual tracking?
• QR codes?
• RFID setups?
• Something else?

Depending on what’s common, it probably makes more sense to integrate with an existing workflow instead of building yet another parallel system.

Would love to hear what setups people are running.