[Request] Add support for event.waiting ? about octoprint-pushover HOT 9 CLOSED

In case it helps, I edit the Gcode manually when doing colour changes. If you use an M0 command to pause then you will get a notification and you can use M70 to send a specific message. I requested this a few months ago:
#8

from octoprint-pushover.

Hello @kroyster, You are right the command M600 isn't supported by either this plugin or OctoPrint, when I was testing it by adding M600 too the list of waiting commands, I saw it triggers a waiting event instead of a Pause event @coldfire3000 mentioned.

gcodeToEvent = {
	# pause for user input
	"M226": Events.WAITING,
	"M0": Events.WAITING,
	"M1": Events.WAITING,
	"M600": Events.WAITING,

This plugin currently only supports the pause event (M0 and the M1) however I will create an update to support the Waiting event, and maybe I will try to support the M600 command (don't pin me on this).

I will keep you posted.

@coldfire3000 Which command are you using M0 or M600 ?

from octoprint-pushover.

I use the M0 and it works great for me :)

from octoprint-pushover.

from octoprint-pushover.

I implemented the wait event in this plugin. I recommend you use the M226 instead of the M600 or the M0. The M226 will (at least on my printer Prusa i3) raise and park the hotend, retract, make sound etc.

And with the latest release it will also send a Pushover notification, remember you have to enable this through the settings.

Can you please let me know if it doesn't work.

from octoprint-pushover.

from octoprint-pushover.

I hope it works otherwise someone has to ad the M600 to the util/comm.py file, maybe I will experiment with that later this week.

from octoprint-pushover.

I updated the plugin and new settings, but M226 did not work for me, as it is not implemented (as a pause) in the Marlin firmware. M600 is the only fully automated pause command that works for me, but I could not get it to trigger the Pushover notification. I did manually add a mapping for the M600 command to trigger a waiting state in the comm.py file, and rebooted octoprint, but it didn't seem to "take". So unfortunately I'm unable to confirm if this update works. M0 pauses and triggers the Pushover alert, but doesn't retract/park my print head, so it's not useful to me for filament changes unless I can figure out how to add those commands AND return it to it's pre-pause location to resume the print. Thank you though - I'm sure someone else will find this update helpful!

from octoprint-pushover.

Correction - I just noticed that I edited the /src/ version of comm.py, but there are various other versions in oprint/lib/*, including compiled python libraries. So I'm guessing I need to edit one of the other files and/or compile it. I tinker, but I'm not a developer, so it may take me a little digging to figure it out and give it another try.

from octoprint-pushover.