notifications upon start/pause/finish of print
-
Good work - like how it integrates with different push notification services.
-
Cheers. I've tried it to make as simple as possible, so if there are any other services you guys would like to see and ideally if there's go module for it let me know it should be fairly easy to add.
Also if you have any problems - shout
Or just feel free to push merge request
-
Next we need a machine learning module that looks at the print via a camera and sends a notification when things go wrong. https://www.tensorflow.org
EDIT: similar to this one but detecting mess instead of forks https://play.google.com/store/apps/details?id=ninja.nanja.app.forkdetector
-
-
that. especially like that you can self host it
-
I'd be interested in telegram support
-
@torin said in notifications upon start/pause/finish of print:
Very nice! Now we need an open source one that doesn't require octoprint.
(I am trying to avoid those print servers and Duet makes it very easy)
-
@jay_s_uk If you will open releases page it should be there(v3) in about 10-15 minutes, it's building as we speak.
Brief instructions in the readme. -
Hi all. I've been using this for quite some time and it has always been very reliable. Unfortunately, the API response format has changed (I noticed this in RRF v3.2beta4). I have fixed the problem, but I don't have the time right now to make it generic and support both the old and new versions of the firmware.
@Torin I have submitted a merge request.
If anyone has this problem, you can get my fork.
-
Merged Cheers dude!
-
Bonjour,
Je rencontre un problème avec reprap notify :
"Error parsing JSON: json: cannot unmarshal array into Go struct field .fanRPM of type int"
J'ai une duet 2 wifi en 1.04, et j'utilise RRF 3.2.1.J'aimerais beaucoup pouvoir recevoir un email en fin d'impression...
Merci pour votre aide.
-
@scumdead Can you give it a go with new release?
https://gitlab.com/Toriniasty/reprap_notify/-/releases/v5Also could you please write in english, I only understood what you've said because of the error in the post. Hope it will be all good now.
Also added re-notify feature.
-
Thanks for the answer, Iβm testing this day, and tell you if it works.
Sorry for my poor english. -
This would be cool as a plugin
-
It works perfectly, thank you very much.
(Linux amd64 version) -
@LB If you're talking about renotification then it is already there
-
-
@LB said in notifications upon start/pause/finish of print:
Do I have to download something and import it or how would it work?
Ah. Okey. To be fair, I haven't seen plugins functionality and I'm not sure how it is supposed to work. Maybe one day I will have a look and see if there's any possibility.... Anyhow, to make the notifier work just download one file from release page matching your system that's running, configure it via example yaml file and start it.
-
@Torin Can you provide a little guidance on the Slack integration setup?
I have created a workflow and successfully posted to a channel, however I'm not able to determine which variable names to use to extract information from the web request. Slack doesn't provide many details for troubleshooting.
The workflow completes successfully with a single variable named "text", but this appears to be empty. Do I need to reconfigure the contents of notifications.go to eliminate the nested json (slack docs say they aren't supported for variables)?
if viper.GetBool(`notifications.slack.enabled`) && viper.Get(`notifications.slack.webhookurl`) != `` && contains(returnStatus(status.Status), viper.GetStringSlice(`notifications.pushover.when`)) { go func(messageText string, messageTitle string) { log.Printf("Sending slack message\n") message := slackRequestBody{ Attachments: []attachment{{ Title: messageTitle, Text: messageText, Color: "good", }, }, } sendSlackNotification(message) }(messageTitle, messageText) }
Also seems like "viper.GetStringSlice" should refer to notifications.slack.when, correct?
-
@mct82 Hey, that's a good spot with if condition. I found the same problem in email and telegram too ... So if you will head down to releases page there should be a new one with the fix.
In regards to Slack. I can't remember, but it should just work ootb when you change enable do true and put webhook url in. If you will still struggle let me know, I will try to see and check it during week.