Benjamin Salchow

The easiest way would be to merge my fix into the master branch of this repository, then the automatic update of octoprint would work. But I guess this plug-in is...

See my pull request from march: https://github.com/malnvenshorn/OctoPrint-CostEstimation/pull/28

see my pull request: https://github.com/malnvenshorn/OctoPrint-CostEstimation/pull/28

well i made a pull request therefore a while ago - but it wasn't merged yet: https://github.com/malnvenshorn/OctoPrint-CostEstimation/pull/28 I run this plug-in with python 3 for months.

There is still a little issue with python3: ``` Traceback (most recent call last): File "/home/octopi/OctoPrint/venv/lib/python3.7/site-packages/OctoPrint-1.4.0-py3.7.egg/octoprint/plugin/__init__.py", line 224, in call_plugin result = getattr(plugin, method)(*args, **kwargs) File "/home/octopi/OctoPrint/venv/lib/python3.7/site-packages/octoprint_filamentmanager/__init__.py", line 225, in...

Last check-in fixes commented error by using `range` instead of `xrange`.

@NovaViper Hello, you can use my branch by installing it with the URL: https://github.com/benjamin-salchow/OctoPrint-FilamentManager/archive/master.zip This contains all changes in this pull request. Just install it from this zip and later...

Hello @NovaViper - the Python 3 Checker plug-in is useless. This plugin just takes a look in the official registry at Octoprint of the plugin. That's the reason why my...

Could it be that the firmware is not gzipped? By using the gzipped version it worked like a charm, but it's currently not supported by TasmoAdmin. https://github.com/reloxx13/TasmoAdmin/issues/403

Same on my side - using the latest docker container. It doesn't matter if I use the browser upload self build images or the original images from the tasmota release...