Closed cmeister2 closed 5 years ago
Hi @cmeister2, The RasPi temp logic is enabled by default as the vast majorty of people using the plugin are runnign RasPis. To be a bit more accomodating of other platforms given the default is True, I've tweaked the logic to detect the "not found" scenario and log a simple error vs. a overly verbose exception + stack trace.
I also noticed _bot_progress_last_req and a couple of other related variables (for a recently added feature) did not have default values and would not have been set if a print had never been executed. That having been said, even without the defaults, I wasn't able to reproduce the issue on my end. I've submitted the defaults which may clear up the issue; please pull the latest from main and let me know if it's still a problem. If you do still see the issue after pulling the latest, please share a few details about your environment: -OS/Version -Version of OctoPrint -Steps to reproduce from "service octoprint restart" onward
Thanks!
That seems to have fixed things; I now get:
:heavy_minus_sign: Print progress N/A :horse_racing:
*File* N/A
Printer: Operational, Bed: 21.3°C/0.0°C, Nozzle: 21.3°C/0.0°C
which is great. Thanks!
Hi,
I wanted to have a play with this plugin locally, so I cloned it at 4cfbd33f. I sent a 'status' request in Slack to the bot and it hit this exception:
I then turned off the Raspberry Pi temperature query and retried, with the same error: