Skip to content

power: in process_request replace notify_power_changed with process_power_changed #987

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

MrSmoer
Copy link

@MrSmoer MrSmoer commented Apr 3, 2025

When the powerstate was changed by third party, and a power on request is sent, moonraker is now able to start klippy properly.

My previous workflow was:
I go to the printer, check if it has power and see that it doesn't have power.
Therefore, I push the button on wireless socket thingy, which makes my printer light up and pull up Mainsail on my Laptop/Phone.
There is the popup to toggle to power on the printer, because it didn't notice that it was switched on manually (which is fine).
So I press the "power on" button in the UI, it displays the "moonraker can't connect" and stays at this screen, because it is stuck in the codepath where it just sent a notification, but doesn't try to restart klippy.
In that case the button to power on or off isn't displayed at all anymore and there is no obvious way to get out of this, other than restarting the moonraker systemd-service.

process_power_changed should call notify_power_changed as well, I don't see incompatibilities, but I am new to the codebase :)
I tested this on my printer.

Thank you very much for this awesome piece of software in the open-source 3D-printing-stack!!
MrSmör ^^

…ower_changed

When the powerstate was changed by third party, and a power on request is sent,
moonraker is now able to start klippy properly
Signed-off-by: MrSmör <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant