I finally got SpoolmanSync running on my Synology NAS. All is running on DSM 7.3.x in Docker Containers, managed by Portainer. Home Assistant was already installed, so i created new stacks for spoolman, spoolmansync and added https://github.com/greghesp/ha-bambulab integration with custom_components on the system.
SpoolmanSync stack is very small, only a few lines, but working:
version: "3"
services:
spoolmansync:
image: docker.io/gibz104/spoolmansync:latest
container_name: spoolmansync
ports:
- 3000:3000
environment:
TZ: Europe/Berlin
PUID: 1026
PGID: 100
volumes:
- /volume1/docker/spoolmansync:/data:rw
#- app-data:/data
Issue is now, all dockers are running 24/7, but printer is turned off during night. When i switch the printer on in the morning, the selected filament in spoolmansync that still is active gets deducted again with the last amount of used filament.
is there an option to fix this? I read after printing the Filament should be ejected from SpoolmanSync, but without AMS i think there should be a better solution to fix this. Is it possible to reset the value after sync?
I finally got SpoolmanSync running on my Synology NAS. All is running on DSM 7.3.x in Docker Containers, managed by Portainer. Home Assistant was already installed, so i created new stacks for spoolman, spoolmansync and added https://github.com/greghesp/ha-bambulab integration with custom_components on the system.
SpoolmanSync stack is very small, only a few lines, but working:
Issue is now, all dockers are running 24/7, but printer is turned off during night. When i switch the printer on in the morning, the selected filament in spoolmansync that still is active gets deducted again with the last amount of used filament.
is there an option to fix this? I read after printing the Filament should be ejected from SpoolmanSync, but without AMS i think there should be a better solution to fix this. Is it possible to reset the value after sync?