As with every other "filament manager" plugin, this leaves those of us with several printers between which we swap rolls of filament out in the cold. If I read this correctly, this only manages spools on a single printer. I have ~80+ different rolls of filament (just the currently open ones) that I use interchangeably between 4 different printers (with plans for two more).
Please don't suggest that I export and import .csv files every time I swap a roll in or out. What a hassle.
Why cannot it be that a single database be used, on the computer that is running the browser(s) for the OctoPrint instance? Specify a path to where the database would be stored on the local computer (not the Pi) and have all OctoPrint instances access that one database if desired. Then, it could even be stored in a Dropbox or GoogleDrive [::gag::] folder which could be accessed from any computer authorized to access that folder. Yes, you'd have to have Busy/Locked/Unlocked flags on the file so that the database could not be changed while another instance was accessing it for a write, but that's just standard programming procedure.
Why can this not be done? I've begged the authors of other filament management systems to do it, and no one ever does.
As with every other "filament manager" plugin, this leaves those of us with several printers between which we swap rolls of filament out in the cold. If I read this correctly, this only manages spools on a single printer. I have ~80+ different rolls of filament (just the currently open ones) that I use interchangeably between 4 different printers (with plans for two more).
Please don't suggest that I export and import .csv files every time I swap a roll in or out. What a hassle.
Why cannot it be that a single database be used, on the computer that is running the browser(s) for the OctoPrint instance? Specify a path to where the database would be stored on the local computer (not the Pi) and have all OctoPrint instances access that one database if desired. Then, it could even be stored in a Dropbox or GoogleDrive [::gag::] folder which could be accessed from any computer authorized to access that folder. Yes, you'd have to have Busy/Locked/Unlocked flags on the file so that the database could not be changed while another instance was accessing it for a write, but that's just standard programming procedure.
Why can this not be done? I've begged the authors of other filament management systems to do it, and no one ever does.