Boom, done! All three changes have been made. Thanks for the great feedback! Let me know if you think of any other improvements 
1 Like
Thanks a lot for providing SpoolmanSync as a HAOS app (aka add-on).
When starting it, I noticed that the default port 3000 conflicts with the one of Uptime Kuma. May I suggest to use a different default? eg 7242 
Of course I could change the port myself in the configuration section; on the other hand when applying code snippets or sharing URLs for e.g. troubleshooting the changed port has to be considered all the time by everyone.
I just created the automations and helpers via the SpoolmaSync UI.
And it was different than before - no copy/paste anymore.
But, surprise: homeassistant got rebooted - without warning nor information 
I suggest to let the user decide when to apply the changes and when to reboot.
btw, how did you apply the changes? did you modify the yaml files?
Cheers
I can confirm your latest changes are working great!
I do have a few additional UI suggestions - though admittedly some of this might just be my OCD kicking in. (
)
#1:
In the Print QR Labels section, would it be possible to make the area that lists selectable spools manually resizable?
Right now, only three spools are visible at a time. If you’re generating labels for several spools at once, it would be helpful to expand that area to see more without scrolling.
#2:
In Spoolman, I have several multi-color filament types:
- Dual-color “Coextruded” filaments (e.g., Silk Blue and Purple)
- Longitudinal multi-color filaments that transition between multiple colors as they print
However, when they appear in SpoolmanSync, their colors default to black - presumably because multiple colors are associated with the spool/filament in Spoolman.
Would it be possible to visually display multi-color filaments in SpoolManSync in a similar way to how Spoolman handles them? For example, Spoolman appears to:
- Display coextruded filaments with colors shown horizontally
- Display longitudinal filaments with colors shown vertically
For reference:
#3:
Under the Dashboard view I wonder if it would make sense to list the word “Remaining” beside the filament remaining stat?
E.G:
- “320g Remaining”
instead of just: - “320g”
#4:
For future functionality, have you considered implementing some form of reporting?
It would be useful to see:
- An overview of which specific filaments were used over a selected time period
- How much of each filament was consumed over that period
This could help with tracking usage trends and when planning restocks.
#5:
Speaking of the above, another feature that would be very helpful is some type of low-filament notification - either through Home Assistant integration or via email.
For example, if you are down to your last active spool of a particular filament type and it drops below 25% remaining, a notification could be triggered to remind you to order more.
This you could achieve already with the HA Integration:
The examples shown in Github are covering exactly your use case.
I hear you on the Uptime Kuma conflict. That said, I’m not sure changing the default to a different port would help much in practice. Any port could conflict with someone else’s setup, and there’s no universally “safe” choice. The configurable port in the add-on Configuration tab is the intended way to handle this. Once you change it there, SpoolmanSync uses the configured port everywhere (including generated QR code URLs), so there shouldn’t be anything else you need to adjust. If I’m missing what you mean about code snippets or shared URLs needing adjustment, let me know — happy to look into it.
Fair point. The restart after configuring automations should be communicated better. Here’s what happens under the hood: SpoolmanSync reads your existing configuration.yaml, finds the SpoolmanSync section (between comment markers), replaces just that section with the updated config, and writes the file back. Your existing configuration outside the SpoolmanSync section is left untouched. The restart is needed because HA requires a full restart to load new YAML-defined entities like input_number, utility_meter, template sensors, and rest_command. automation.reload alone isn’t sufficient for those.
I’ll add a warning/confirmation before the restart so you know it’s coming and can choose to restart later on your own if you prefer.
Great suggestions, thanks for taking the time to write these up. A few thoughts:
#1 Resizable spool list in QR labels: Good idea, I’ll look into making that list expandable or taller so you can see more spools at once without scrolling.
#2 Multi-color filament display: I like this one. I’ll look into how Spoolman stores multi-color data and see if I can replicate the horizontal/vertical color display for coextruded and longitudinal filaments.
#3 “Remaining” label next to weight: Simple and makes sense for clarity. I’ll add that.
#4 Usage reporting: This is on my radar. SpoolmanSync already logs every usage deduction in the Activity Log, so the data is there. A reporting view that summarizes filament consumption by type/spool over a time period would be a natural next step.
#5 Low filament notifications: Definitely something I want to add. SpoolmanSync already knows every spool’s remaining weight from Spoolman, so threshold-based alerts are very doable.
The spoolman-homeassistant integration does offer a low-filament binary sensor, which is cool. Worth noting though that it’s a general-purpose Spoolman ↔ HA data bridge, but it doesn’t track filament usage itself. Its sensors (including the low-filament alert) only update when something else has already deducted filament from Spoolman. You’d need to pair it with SpoolmanSync (or your own custom automations) to actually feed it usage data.
I’d like to build low-filament alerts directly into SpoolmanSync since we already handle the deductions automatically. That way it’s a single integrated workflow without needing to install and configure a separate integration.