-
Notifications
You must be signed in to change notification settings - Fork 35
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
Support notifications for other events #1
Comments
Towards #1. Notification configuration only via config.yaml editing for now.
@foosel @dcwalmsley I created a Here's an example of what the config looks like now: emailnotifier:
_config_version: 2
mail_server: smtp.gmail.com
mail_username: [email protected]
notifications:
FileSelected:
body: '{file} selected for printing.'
enabled: true
snapshot: false
title: Selected {filename}
MovieDone:
body: Timelapse of printing {gcode} saved as {movie}.
enabled: true
snapshot: false
title: 'Timelapse rendered: {movie_basename}'
PrintDone:
body: '{file} done in {time}.'
enabled: true
snapshot: true
title: 'Print complete: {file}'
recipient_address: [email protected] Unfortunately I haven't figured out how to make a settings template interface for |
As an interim interface solution, the Yamlpatcher plugin can be used to add/edit/remove notifications. |
Here is a rough static HTML mockup of the settings interface I envision for multiple notifications. Clicking Add would add another row to the table. Select from available Event names and edit message templates. I'm not sure how to achieve this, though. Do any existing plugins offer a similar interface? I find the Jinja2/knockout/viewmodel/Javascript documentation a bit too overwhelming to work it out from scratch. |
@anoved you could take a look at the temperature profile or the terminal filter configuration pages in the OctoPrint settings, those follow a similar pattern: Interesting source code locations:
|
Thanks for the pointers. Perfect example. I will take a shot at it soon. |
Currently notifications are only sent in response to the
PrintDone
event, but there are many others.The text was updated successfully, but these errors were encountered: