v0.1.0

What's New

This release triples the number of ways Mover Status can reach you: alongside Discord and Telegram, the script now supports Pushover, Apprise (CLI or API), and native Unraid notifications. It also handles Mover Tuning's startup phase far more gracefully.

📲 Pushover

Set USE_PUSHOVER=true with your app token and user key. Includes its own progress and completion message templates and a configurable title.

📣 Apprise

Set USE_APPRISE=true and choose APPRISE_MODE="cli" (local apprise binary) or "api" (Apprise API server). APPRISE_TARGETS accepts any number of Apprise URLs, each delivered and retried independently. In API mode the target URL travels in the JSON body rather than the command line, so credentials stay out of the process list.

🟩 Native Unraid notifications

Set USE_UNRAID=true to post through Unraid's own notify binary, so updates show up in the web GUI notification list and as browser toasts. If Unraid's Apprise agent is configured, it will forward these too.

All channels can run side by side, and each has its own *_MOVING_MESSAGE / *_COMPLETION_MESSAGE template.

🚀 Improvements

• Mover Tuning startup is handled properly. When the mover starts but Mover Tuning is still scanning the cache, the script now sends a "preparing" notification instead of reporting bogus progress, and it ignores mover.ini data left over from a previous run.
• Delivery failures no longer break a run. Failed Pushover and Apprise notifications are retried on the next poll, pending progress updates are coalesced to the newest percentage, and healthy channels are not re-notified while another one is retrying.

📖 Documentation

The README now covers setup for all five notification channels, including the Unraid Community Applications packages used for testing Apprise, an example Apprise API Docker deployment, and notes on keeping notification credentials out of the process list.

🙏 Thanks

A big thank you to @btc08gh, who authored every feature in this release (#27, #28, #29) and in doing so closed feature requests that had been sitting open for years — Apprise support (#5, from 2024), Pushover support (#6), and Unraid web GUI notifications (#10). Much appreciated!

⬆️ Upgrading

Existing configurations keep working unchanged — the new channels default to false. To pick them up, copy the updated script from main into your User Script and re-apply your settings.

Full changelog: 0.0.11...0.1.0

0.0.11

Fixed

• EXCLUDE_PATH exclusions now apply correctly in both mover_ini and du_polling modes (#17)

Changed

• Standardized Renovate policy
• Added agent context files (CLAUDE.md, AGENTS.md, GEMINI.md)

0.0.10

What's Changed

• fix: correct ETA calculation for late-join scenarios by @engels74 in #16

Full Changelog: 0.0.9...0.0.10

0.0.9

Changelog:

• Refactor: dynamic mover process detection and script improvements: a0c57db
• Add mover.ini support, crash recovery, and enhanced progress tracking: 1d4f832
• fix: resolve false-positive staleness warnings and duplicate notifications: 9de349a

Full Changelog: 0.0.8...0.0.9

0.0.8

Changelog:

• fix: allow discordapp.com in webhook URL validation: d0fdc33

Full Changelog: 0.0.7...0.0.8

0.0.7

Changelog:

• Made the version check into a function. It now checks for a new version at every new loop, instead of only at launch. Fixes #4.

Full Changelog: 0.0.6...0.0.7

0.0.6

Changelog:

• Slight update to script's copyright notice, to include GitHub repository link. Fixes #3.

Full Changelog: 0.0.5...0.0.6

0.0.5

Changelog

Main Changes

• Telegram Support: Added support for sending notifications to Telegram.
• Persistent Loop Execution: The script now runs in a continuous loop instead of exiting after one run. This change makes it incompatible with cron scheduling in the User Scripts plugin. Refer to the README for more details.
• Percentage-Based Notifications: Implemented notifications based on progress percentages using the NOTIFICATION_INCREMENT variable instead of time intervals.
• Improved Calculation Accuracy: Enhanced the accuracy of the progress and remaining time calculations.
• Updated README: Revised the README.md with new installation instructions and additional details.
• License Change: Changed the license from GPLv3 to AGPLv3 and added a copyright notice in the script as required by the license.

Other things

• Dry Run Option: Introduced a DRY_RUN mode for testing webhook configurations without monitoring.
• Debug Logging: Added an ENABLE_DEBUG option for detailed debug logs, including the full webhook payload for troubleshooting.
• Increased Logging: Enhanced logging throughout the script for better monitoring and troubleshooting.
• Improved Error Handling: Added more robust error handling to cover various edge cases and failures.

Full Changelog: 0.0.4...0.0.5

0.0.4

Changelog:

• Added a small amount of error handling. The script will check if the Discord Webhook is set properly, and if the webhook responds with a HTTP 200 (OK), else it'll log the error.
• Edited the way the variables are set, so it should be easier to figure out
• Made the EXCLUSION_PATH_XX empty by default

Full Changelog: 0.0.3...0.0.4

0.0.3

Changelog:

Now you can change the message it posts:

• Added MOVING_MESSAGE and COMPLETION_MESSAGE variables

Full Changelog: 0.0.2...0.0.3