Christian Würthner
Christian Würthner
Do this: ``` rm -rf /usr/data/octoapp rm -rf /usr/data/octoapp-env cd /root/ git clone https://github.com/crysxd/OctoApp-Plugin/ octoapp git checkout k1-install-fix ./install.sh ```
Sorry, missed one command: ``` rm -rf /usr/data/octoapp rm -rf /usr/data/octoapp-env cd /root/ git clone https://github.com/crysxd/OctoApp-Plugin/ octoapp cd octoapp git checkout k1-install-fix ./install.sh ```
Thanks for checking, Gina! Totally agree - not a super urgent issue and more in the "annoying" category.
@yosephws I host a fork with this changes on the GitLab package registry. Feel free to copy this: https://gitlab.com/realoctoapp/octoapp/-/commit/0170752edc12a5c41d23e08808e53eb17865c025
OctoApp dev here 👋 I think what happens is that PTG really doesn't like the layer commands I insert since the 2.1 update. Initially, I inserted `OCTOAPP_LAYER_CHANGE LAYER=1234` and this...
@clarkiej If you had a chance to test the new plugin and verify everything is back in order...please let me know :)
@clarkiej My bad....new update 2.1.4
@clarkiej Can you download the file with the 8h estimation from OctoPrint and post it here?
I pushed update 2.1.5 and removed all `G` from the commands :D - `M118 E1 OCTOAPP_LAYER LAYER=n` - `M118 E1 OCTOAPP_DISABLE_LAYER_MAXIC`
@eyal0 Enjoy your vacation, we will work around the bug :) I'm pretty sure my 2.1.5 changes without a `G` will work fine!