You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to display the current status of the printer on my Grafana dashboard and in the InfluxDB dataset I'm not seeing where it's being logged that the printer is offline or disconnected.
It looks like in the code that if the printer is not online you are just exiting the function. Is it possible to instead have it write into the state table that the printer is offline?
I've never dealt with Python or even plugins for Octoprint, but I could try and see what I can do and go from there. It could be interesting, but possibly make the change on my system (after I figure out where the files are at) then submit a PR for the changes.
The text was updated successfully, but these errors were encountered:
This has been available through the PrinterStateChange event, but using it was awkward because of how events were stored. This has been changed, and also now the state measurement is updated even if the printer is offline. These changes are part of 1.3.0, which should be available for automatic upgrades.
I'll close this for now, but if this doesn't help feel free to re-open. (And PRs are, of course, always welcome!)
I'm trying to display the current status of the printer on my Grafana dashboard and in the InfluxDB dataset I'm not seeing where it's being logged that the printer is offline or disconnected.
It looks like in the code that if the printer is not online you are just exiting the function. Is it possible to instead have it write into the state table that the printer is offline?
I've never dealt with Python or even plugins for Octoprint, but I could try and see what I can do and go from there. It could be interesting, but possibly make the change on my system (after I figure out where the files are at) then submit a PR for the changes.
The text was updated successfully, but these errors were encountered: