Sven Lohrmann

Yes some warning pops up, but I would like to turn this off. It happened a few times that I forgot to remove the specific build from the queue, so...

I agree that it would be great to measure the real power consumption and use those values to calculate the estimated cost. But the issue is that I don't have...

> It's up to you: If you agree, I can impement and test it and than I will create a pull-request. The issue with this is the same as before...

I took a look at the documentation of the Tasmota firmware, but it's to insufficient to implement this without having the real device. If it helps I would implement it...

If you just use the `EnergyReset` command to request the power meter reading the simplest solution is to use REST API.

To be honest I'm not going to implement this. The goal of this plugin is not to provide a print history. It provides a preview of the print cost and...

Can you be more specific? I don't know what you mean.

I've never came across this issue and I'm also using Slic3r with the auto upload via the API. This plugin relies on the data (filament length and est. print time)...

The MetadataPreprocessor just reads the metadata comment generated when/after slicing the model, therefore the data is available almost instantly. But it might not be easy to setup for everyone. If...

Yes, but because the calculation happens in the frontend right now it has to be moved to the backend. Then it can be made accessible via an API endpoint.