Notification via Pushover or other service

[jamesarm97]

The one thing I am missing from using my new DuetWifi is job notifications on my phone. I used the Pushover plugin on octoprint and think it would be nice to add such a feature on the Duet since it has networking / wifi. The pushover API is pretty simple, just a post of some JSON parameters (I say simple but I do not know what is required on the Duet side). Maybe have it triggered with a macro file or M code. Each setup would need a configuration for the token and key (passed as a parameter or setup in the config file?) then the message. If it is a macro file then it can be called at the end of a print or even from within a trigger like a filament out so you can get the message if you are not right there by the printer. Here is the API: https://pushover.net/api#messages

[sdemmery]

I'm about to purchase a duetwifi and for me pushover integration is something I will miss a lot as I move away from octopi. I use pushover a lot sends notifications to all my iDevices when job status changes. Anyone got any sort of work around?

[T3P3Tony]

I will ask Christian if this is something we could add to the DWC side relatively simply.

[Jackal]

Hi guys, I have created a version of Duet Web Control integrated with Pushover.
I didn't check how Octopi implements this, so my implementation is very basic.
I use the M117 G-code with a specified prefix (keyword) to send messages to Pushover

Under Settings > User Interface you will see a Pushover panel.
Put your Token and User Key in there for the Pushover API
The Keyword field will filter messages starting with that string and send to Pushover

After saving the settings, you can try to send M117 through the console to test it out.
e.g. M117 Push:Hello World
will send "Hello World" to your devices (if you have set Push: as the keyword)

Please let me know if this works for you
Download: https://github.com/SleepyPrince/DuetWebControl/tree/pushover

edit: changed url to Github

[iDevelo]

@Jackal:

Hi guys, I have created a version of Duet Web Control integrated with Pushover.
I didn't check how Octopi implements this, so my implementation is very basic.
I use the M117 G-code with a specified prefix (keyword) to send messages to Pushover

Under Settings > User Interface you will see a Pushover panel.
Put your Token and User Key in there for the Pushover API
The Keyword field will filter messages starting with that string and send to Pushover

After saving the settings, you can try to send M117 through the console to test it out.
e.g. M117 Push:Hello World
will send "Hello World" to your devices (if you have set Push: as the keyword)

Please let me know if this works for you
Download: https://www.dropbox.com/s/szvsdn0pv9ki09t/DuetWebControl-1.14a%2Bpush.bin?dl=0

Is this on GitHub? With a pull request?

[Jackal]

I have put it on Github now, but I believe it needs further refinement before doing a pull request (I am not a skilled programmer)
https://github.com/SleepyPrince/DuetWebControl/tree/pushover

Please leave a comment or any suggestions after you have tried it out

[T3P3Tony]

That's great work Jackal, hopefully Christian will have a look at it and include it in a future version

[kraegar]

Personally, rather than support for a single notification service, I'd rather see an API for pulling data from DWC. So we could poll the data its already displaying without generating more gcode for the duet itself to worry about. (Temps, file progress, etc)

Then it'd be trivial to use a PI or similar to do stuff with that data - push notifications, light up LEDs, turn on/off a webcam, whatever by reacting to data pulled from the API.

(If such an API already exists, I haven't found it referenced yet)

[Flyer007]

Nice work on the Push; But I agree the API would be sweet and open up a bunch of capability.

@kraegar:

Personally, rather than support for a single notification service, I'd rather see an API for pulling data from DWC. So we could poll the data its already displaying without generating more gcode for the duet itself to worry about. (Temps, file progress, etc)

Then it'd be trivial to use a PI or similar to do stuff with that data - push notifications, light up LEDs, turn on/off a webcam, whatever by reacting to data pulled from the API.

(If such an API already exists, I haven't found it referenced yet)

[chrishamm]

@Jackal:

I have put it on Github now, but I believe it needs further refinement before doing a pull request (I am not a skilled programmer)
https://github.com/SleepyPrince/DuetWebControl/tree/pushover

Please leave a comment or any suggestions after you have tried it out

Could you push your source changes to GitHub too? That way I could check how much work would be required.

[Jackal]

There are a few http requests you can send to DWC
https://github.com/chrishamm/DuetWebControl/blob/master/README.md
Probably rr_status is what you need

[T3P3Tony]

How do you see a general API working, further than the existing rr_…... Http requests?

[kraegar]

Didn't know about rr_status. It may do what I was looking for, I'll have to play with it and see what's reported.

I'd envision it polling from the DWC itself rather than relaying the requests on to the firmware, to keep the processing load lower, but perhaps that's not needed.

Typically in an API like that I'd expect any value displayed within the interface to be a pollable value in the API. So the current temps, current print layer, all your xyz axis, zprobe status, whatever. Just give each value a name for the API, and have it report those when queried for that value.

[Jackal]

@chrishamm:

@Jackal:

I have put it on Github now, but I believe it needs further refinement before doing a pull request (I am not a skilled programmer)
https://github.com/SleepyPrince/DuetWebControl/tree/pushover

Please leave a comment or any suggestions after you have tried it out

Could you push your source changes to GitHub too? That way I could check how much work would be required.

Oh, I didn't realize I only committed the compiled files. It should be fixed now.
You would probably laugh at my poor coding :hc:
I just hack things together to make it work, I believe you will have a better way to do it.

[chrishamm]

Thanks for the new commit.

Well, TBH I'm not planning on adding support for cloud-based services to DWC as I see no good reason to send data to external web services unless more people explicitly ask for this. One exception may be STL drag'n'drop which would require slicing to be done on an external server, but that's just an idea I might implement someday.

Modern browsers already provide Web Notifications and in fact I thought you were using this technique to achieve pushover notifications (also see https://www.w3.org/TR/notifications/)), so I'm wondering if there is any good reason why we cannot use this standard instead. If you want to see a demo, have a look at this page: https://davidwalsh.name/demo/notifications-api.php

[Jackal]

I believe they want push notification for unsupervised printing.

By the way, in case it is not obvious, my implementation depends on DWC using jQuery ajax to interact with Pushover.
That means you will need DWC running on a browser while printing to have push notification.

[kraegar]

the current rr_status is good. If you added in the currently printing filename, if that's possible, to type 3, it should be easily doable to implement auto-generated timelapses whenever a file is printing.

Push notifications should be doable easily with this, and lighting up LED strips, etc should also work just fine.

(I can start a new thread if that's more appropriate)

[chrishamm]

@Jackal:

That means you will need DWC running on a browser while printing to have push notification.

That's the point, you need to have one DWC instance running anyway to send push messages to that web service so I think it would be sufficient if DWC generated those messages on its own. DWC is capable of running on mobile devices as well and it could be expanded to show "native" push notifications, so I see no reason why we need to rely on a web-based service for the same purpose.

@kraegar:

the current rr_status is good. If you added in the currently printing filename, if that's possible, to type 3, it should be easily doable to implement auto-generated timelapses whenever a file is printing.

The way DWC gets the name of the file being printed is by checking the status character and if it changes to printing, it requests rr_fileinfo once which sends back the filename and some more info. If you're looking for further documentation about the status responses, check out this link: http://reprap.org/wiki/RepRap_Firmware_Status_responses

[jmg123]

How about using mqtt? there is a reference implementation based on the lwip tcp/ip stack used in the duet. Could hook it up to all manner of local or cloud based things. Those who don't mind using the cloud could use it in conjunction with IFFT to get native notifications or turn lights/things on or off. For those who don't like cloud services, they can setup their own local broker and subscribers/clients and still get the benefit.

[sdemmery]

@T3P3Tony:

That's great work Jackal, hopefully Christian will have a look at it and include it in a future version

Ive finally got my DuetWifi & new printer all built honestly Duet is just awesome if only Pushover were implemented it would be perfect for me. Appreciate the work Jackal has done but clearly that version of DWC is & has been left behind by the official release (loving FW 1.18 & DWC 1.15 BTW)

So my question any progress on implementation into the official release? Seems it should be a simple case of implementing & testing Jackal's code right? Or am I over simplifying Also appreciate it might not be top of the list, but if it were available i think many would move to use Pushover.

Thanks]
Stuart