Is your feature request related to a problem? Please describe.
I see you have webhook post to Discord feature.
I'd really love if you could support sending a customizable webhook to other URL's.
I haven't tested other webhook url's then Discord though so might work..
But would like to be able to customize whats in the payload of the webhook.
Describe the solution you'd like
For example I'd like to specify multiple webhook URL's per printer.
This can be used to integrate the print statuses into for example an issue tracking system, or other generic systems.
Personally I use Jira and having such a feature is a great way for me to automatically log what I have printed and when, and get it into different tickets in my system based on the filenames. I could even automate the status of my tickets based on a inncomming webhook.
The webhook should trigger by events - the events you already got is great, maybe even add a completion % event, so can fire out screenshots/updates mid-print..
The webhook should include information such as:
Printer name
File name
Event type triggered (started/stopped/paused etc)
TheDetective status (monitoring or not)
Time spent
Time remaining estimate
Total time estimate
Progress %
Active temperatures (hot-end/bed)
Timestamps
Picture (?)
adamzolyak
commented
1 year ago
Is your feature request related to a problem? Please describe.
I see you have webhook post to Discord feature. I'd really love if you could support sending a customizable webhook to other URL's.
I haven't tested other webhook url's then Discord though so might work.. But would like to be able to customize whats in the payload of the webhook.
Describe the solution you'd like
For example I'd like to specify multiple webhook URL's per printer. This can be used to integrate the print statuses into for example an issue tracking system, or other generic systems. Personally I use Jira and having such a feature is a great way for me to automatically log what I have printed and when, and get it into different tickets in my system based on the filenames. I could even automate the status of my tickets based on a inncomming webhook.
The webhook should trigger by events - the events you already got is great, maybe even add a completion % event, so can fire out screenshots/updates mid-print..
The webhook should include information such as: Printer name File name Event type triggered (started/stopped/paused etc) TheDetective status (monitoring or not) Time spent Time remaining estimate Total time estimate Progress % Active temperatures (hot-end/bed) Timestamps Picture (?)