I have had this happen on two different installations of Octoprint 1.7.3 with the latest version of this plugin.
I have proven it occurs by rebuilding the config.yaml and running the bed leveling procedure immediately after a reboot (which is done to bring back the custom controls).
This happens every single time, on two independent installations of Octoprint.
I have had this happen on two different installations of Octoprint 1.7.3 with the latest version of this plugin.
I have proven it occurs by rebuilding the config.yaml and running the bed leveling procedure immediately after a reboot (which is done to bring back the custom controls).
This happens every single time, on two independent installations of Octoprint.