v1.3.4 (stable)

This is a maintenance update of OctoRant, with fixes for recently reported bugs.

Bugfixes

• #75 : Add a fix for thumbnails generated by Cura that are slightly different from those generated by PrusaSlicer. Thanks @BobSleeuw for the report!

v1.3.3 (stable)

This is a maintenance update of OctoRant, with fixes for recently reported bugs.

Bugfixes

• #68 : The previous fix did not prove to work correctly, this new version should fix the bug once and for all, as the thread in charge of sending messages to Discord is now started at the same time as OctoPrint is. Don't hesitate to create a new issue if this doesn't work.

v1.3.2 (stable)

This is a maintenance update of OctoRant, with fixes for recently reported bugs.

Bugfixes

• #65 & #66 : fixes few bugs on the GCode thumbnail part. OctoRant now handles better files that may contain more than one thumbnail, and also shouldn't crash on any OctoPrint instances that use Python 3.7 or 3.8.
• #68 : fix a crash of the background thread responsible to send the actual messages to the Discord webhook. If an error occurred in this thread, it would crash but never restart correctly. Any error now will terminate the thread, that will be launched again if necessary.

Many thanks to @mavermc, @VidFerris and @LukasBlk for their feedback!

v1.3.1 (stable)

This is a maintenance update of OctoRant, with fixes for bugs created by the release of v1.3.0

Bugfixes

• #61 & #63 : Not releasing a new version for literally 2.5 years made me miss some basic things like making sure the version number is correct everywhere. This bug created an update loop and may have confused you a bit. Sorry for this.
• #62 : Declared the DiscordMessage thread as daemonic to prevent OctoRant from blocking the restart of OctoPrint.

Many thanks to @object-Object and @foosel for reporting these issues!

v1.3.0 (stable)

This long awaited (atleast by the dozen of you still using this plugin) release delivers a lot of new features.

🎇 New features

New media types

• #50 : OctoRant now offers to upload the timelapse with the "Timelapse: Rendering done" message. Be aware that the upload limit depends on the server you send it to (8MB by default, but can be greater on a boosted server)
• #47 : Given the gcode file contains a PrusaSlicer-generated thumbnail, OctoRant now offers to upload it on all events related to prints. The code is really simple for now and handles just the easy cases. If for some reason your thumbnails are not sent feel free to open an issue.

New progress notification algorithm

The code around progress notifications during a print has been completely rewritten. OctoRant now offers 3 different ways to track progress of a print:

• Percentage of completion: Be notified every X% during the print. This is the new name of the option that existed in previous versions under the "Notify every XX%"
• Timed interval: For long prints were percentage change too slowly, you can enable a timed notification every X seconds, from as low as every second.
• Height: (in Beta) Be notified for each Xmm. A quick & dirty algorithm was set to discard unrelated movements (like hovering above the plate to do Z-homing at the center), but false positives are still possible.

Considering those three options could generate a massive amount of messages, a fourth option is available:

• Throttle notification: When enabled, a minimum of X seconds between progress notifications will be respected.

Related issues/PR: #52, #11, #56

🦗Bugfixes

• #41, #42, & #46: fixed thanks to the revamp of the progress notifications
• #58: new events related to SD Card transfer were created to manage them separately to the printing events

⚠ Deprecated feature: Script execution

The "Script" feature, that would allow you to execute an arbitrary script before an after sending a message to Discord (for example, to turn on a light before grabbing the snapshot), is now deprecated and will be removed in a further release of the plugin.

This is mostly due by the fact that OctoPrint offers a much more powerful option with the Event Manager, and also because I was never comfortable offering a way to execute external code from the plugin. I'd rather let OctoPrint handle this itself. In order to use the Event Manager with OctoRant, two new events are available : plugin_octorant_before_notify and plugin_octorant_after_notify. An {event} variable is available to know which event was triggered by OctoRant.

🚧 Other

Settings migration

• Handled settings migration to the new format so all your settings will be kept.
• New events related to timelapses are not enabled by default.
• Other default settings are the same.

Code-related

• Did a massive overhaul of the project organization to better manage further maintenance.

End notes

I did my best to avoid any regressions and to prevent new bugs, but as there are as many usages as there are users, I may not have anticipated all of them. Feel free to open new issues if you need to.

Again, many thanks for everyone that took the time to report the bugs or feature requests.

1.2.3 (stable)

This is a maintenance version of Octorant, with few modifications.

Bugfix

• #34 & #38 : Now the plugin will warn the user when it has an invalid variable in the message content. Due to the fact that the available variables can change from version to version, the plugin can't know in advance what are the really available variables. Therefore the error is detected only when the message is sent to the Discord server. If an error is detected, a warning will be added to help the user detect the wrong variable, and list all the available ones.

Improvements

• #39 : The plugin is now using any Pillow version >= 5 available on the system. This may avoid installing duplicate versions of Pillow.
• 3e76d5b : the plugin is now compatible with Python 3 and therefore all Octoprint versions >= 1.4.0

1.2.2 (stable)

This new version contains a bugfix for a long overdue bug, and also a new small feature (time spent and time remaining variables for messages)

Bugfix

• #22 : The plugin now completely excludes the 100% value, no matter what threshold is set. This will accommodate most usages of this plugin. Values over 100% will be considered though, because I noticed sometimes OctoPrint didn't update the percentage calculation accordingly (like when a print is restarted but the gcode file was modified since the first run).
• A division by 0 was not detected (when the threshold for the progress event was set to 0%) and could make the plugin unstable, and was therefore fixed.

Improvements

• #32 : The plugins now offers 4 new variables usable for the progress event:
  • {spent} is the number of seconds since the print started.
  • {spent_formatted} is the same number, but formatted in a human-readable value (HH:MM:SS)
  • {remaining} is the number of seconds remaining until the print ends, per OctoPrint's estimation (that can be wildly inaccurate at the start of the print)
  • {remaining_formatted} is the same number, but formatted in a human-readable value (HH:MM:SS)

1.2.1 (stable)

v1.2.1 is a bugfix release to handle a few bugs reported

Bugfixes:

#29 - OctoRant now uses a alpha'd color for secondary background in the settings page, to easier accommodate new themes.
#19 - Added long overdue logs and exception handling when requests fails to get the snapshot from the webcam server.

#Other:

• readme.md now mentions @cameroncros DiscordRemote plugin for people looking for a two-way interaction between OctoPrint and Discord.
• added some documentation about the scripts feature

1.2.0 (stable)

Improvements

• #14 - The plugin can now execute scripts files before and after sending a message to Discord. Great if you want to light some LED ramp or doing anything else.

1.1.0 (stable)

Improvements

• #8 - The plugin now takes in account the transformations settings (Flip horizontally, vertically, or Rotate 90° ccw) to send a snapshot in the right orientation. Thanks to @waumand, @Jan2220 and @nangad for suggesting this, and @cristianefe for the temporary workaround. Hopefully this will not be needed anymore :)

Other

• Really quick cleanup of the code

---

I'd like to thank everyone for their feedback and suggestions. It has been the first time for me to really publish something publicly and it has been a really rewarding experience.

If you encounter any issue for updating or installing this version, feel free to report an issue, and I'll try to do my best.