Your issue may already be reported! Please search on the issue tracker before creating one.
Describe the solution you'd like
A recent suggestion in the AnkerMake Discord pointed out that there is no "historical" information on the printer such as total print hours, total filament length, number of prints, etc.
With the MQTT connection, we could gather this information when it is broadcast and update a small internal database (Redis? SQLite? Mongo:Alpine?) with the details from the print that could then be calculated and presented on screen. We could even store print history this way so you could look back at previous jobs (at least by name, how long it printed and the recorded speed?).
Describe alternatives you've considered
None
Additional context
Add any other context or screenshots about the feature request here.
Your issue may already be reported! Please search on the issue tracker before creating one.
Describe the solution you'd like A recent suggestion in the AnkerMake Discord pointed out that there is no "historical" information on the printer such as total print hours, total filament length, number of prints, etc.
With the MQTT connection, we could gather this information when it is broadcast and update a small internal database (Redis? SQLite? Mongo:Alpine?) with the details from the print that could then be calculated and presented on screen. We could even store print history this way so you could look back at previous jobs (at least by name, how long it printed and the recorded speed?).
Describe alternatives you've considered None
Additional context Add any other context or screenshots about the feature request here.