-
-
Notifications
You must be signed in to change notification settings - Fork 228
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Control PSU from OctoDash #201
Comments
Yes if the printer is offline OctoDash can't send anything, because everything will go through OctoPrint which will throw the 409 error. But thats a good idea and fits really well into the custom actions. Also kill would make kind of more sense then. So that feature probably is coming soon :) Could you link the plugin so I can have a look? |
Here’s the plugin: https://github.com/kantlivelong/OctoPrint-PSUControl |
It does have an API so the plugin can be integrated quite easily :) |
Small update; enabling the save connection settings and the auto connect on server startup in conjunction with this plugin enables auto connection after powering on the psu: https://github.com/markwal/OctoPrint-PortLister |
I've almost finished the sleeping screen, which also attempts to connect to the Printer (just needs some testing and some minor tweaks). And because I don't use the WebInterface, but rely on the API it hopefully should work just fine. Maybe if this doesn't work out I'll have a look at the plugin |
As I mentioned in #200 I would love the ability to control the PSU-control plugin through the OctoDash screen.
Without knowing any of the details: I'm using the app OctoPod which can control the plugin so there is some sort of API.
It's also possible to set up PSU-control to respond to Gcode commands, (defaults to M80/M81), so this could probably be added to the custom controls? Though without having tried it yet it looks like the power on Gcode command would not be usable since OctoDash throws a 409 error continuously when the printer is offline?
The text was updated successfully, but these errors were encountered: