notifications upon start/pause/finish of print

Torin

@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.

mct82

@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.

slack-var-config

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?

Torin

@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.

https://gitlab.com/Toriniasty/reprap_notify/-/releases/v6

mct82

@Torin Thanks for the quick update!

I documented a little of my setup to help with troubleshooting, maybe something has changed on Slack's end?

Here is my webhook setup:

And here is the next action in the workflow:

This is the result posted to the channel:

Is there a way to post to a channel from a webhook w/o using the workflow tool? Maybe that's something I missed....

Torin

Actually just tested it quickly. It works literally as you did. Just copy paste slack webhook url, put it in config and it should just appear.

text is not needed, as it is send via attachments in slack:
https://api.slack.com/reference/messaging/attachments

mct82

@Torin Well it works perfectly when set up properly

So to change the content of the attachment, I just need to update these sections and recompile?

func sendNotification(status rrStatusType, fileinfo rrFileinfoType) {
	messageTitle := `Your friendly 3d printer status`
	messageText := fmt.Sprintf(`Status: %v, print file name: %v, print time: %v`, returnStatus(status.Status), fileinfo.FileName, niceTime(fileinfo.PrintDuration))

	if status.TimesLeft.File != 0 && status.Status == `P` {
		messageText = fmt.Sprintf(`, print time left: %v`, niceTime(int(status.TimesLeft.File)))
	}

and


	if viper.GetBool(`notifications.slack.enabled`) &&
		viper.Get(`notifications.slack.webhookurl`) != `` &&
		contains(returnStatus(status.Status), viper.GetStringSlice(`notifications.slack.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)
	}

Thank you for putting this together!

mct82

@Torin said in notifications upon start/pause/finish of print:

Also added re-notify feature.

The re-notify feature does not appear to be working under windows. I receive the first notification for any new status, but no subsequent updates after status changes. I see a reference to time.Now().Unix() in the main.go source, could this be part of the issue?

Torin

@mct82 Basically yeah, you would also need to update struct for json payload.
In regards to windows, time.Now().Unix() should without any problem on windows. That's something I would need to check later during the week. but feel free to look around, add some timers maybe and logging

mct82

@Torin I'm not a programmer and I have never used the Go language, so I don't think you want me mucking up your code. I just don't have time to learn a new language right now, so I will have to wait for someone who knows what they're doing to do it properly.

I will mention that if I were to modify this tool in any way, it would be to pull the message content out so it can be edited w/o re-compiling. Perhaps read in a message template for each status (print, pause, finish), or a single template with multiple sections. It would be really powerful to be able to grab additional fields from the OM to include in (or conditionally modify) push notifications.

Torin

@mct82 Hey, so I got a bit of spare time today and I've looked into it. Renotifications didn't work because I forgot to add two more if's.

I've created new release here: https://gitlab.com/Toriniasty/reprap_notify/-/releases/v7

TheBasedDoge

Hi, this is working great for me, but is there a way to make it poll for 2 duet boards? I have two printers I would like to use it on.

Festivejelly

This is fantastic. Just what I was looking for.

I tried running this on windows from command line, but theres no feedback... so im not even sure its running?

I do have a spare raspberry pi lying around so which release would I use for that?

Torin

@thebaseddoge Simply start two programs with from two different directories with two different config files

@festivejelly There's no feedback unless there's a problem If you want to run on rpi you need an arm build.

Festivejelly

@torin So do I run from command line? or do I just double click the exe? When I do either I dont see the process running in the list. Ill give the arm build a try instead on my rpi

Torin

@festivejelly You can run it both ways, either from command line or double click. If it doesn't quit and windows stay open it should just work.

Nxt-1

@torin I don't know if you planned on maintaining this app, but it sure would be nice if it received an update.
I did some testing and got a contineous stream of JSON parse errors. After checking the sources it seems the program uses the GET /rr_status way of talking to the Duet. However, according to this page on the Duet Github, it is deprecated now.

Should you decide to maintain it, I could make time to help out testing.

-Nxt

madeinta1wan

@nxt-1 getting the similar errors via windows

"2022/06/21 14:23:53 Error while downloading rr_status: Too many errors, resetting counters and stoping track operation. Will hide consequent errors..."

Any chance there's a fix for this @Torin ?

Thanks,

Nate

Torin

@madeinta1wan This is due to API changes introduces in RRv3. There's a chance but it requires few hours of work which I currently do not have, however I will try to squeeze that in somehow. The code is opensource so if someone would make an PR I will happily merge it.

chrishamm

@madeinta1wan @madeinta1wan rr_status is still supported in standalone mode AFAIK. We will add a support layer for rr_ requests to SBC mode in v3.5 but I'm afraid it won't support rr_status. If possible, I'd strongly recommend upgrading to rr_model which returns portions of the object model.

Torin

So I finally found some time and resurfaced my duet enabled printer so I have started updating the app.... So hopefully soon there will be something to show

@chrishamm How do I currently identify finished print? Previously it was in rr_status marked as 'I'(capital I), now I can see see only in rr_model?key=state status: idle, pause, printing.