Mammotion - Home Assistant Integration v0.6.6 🚀

This release brings new features and improvements to the Mammotion integration for Home Assistant. 🌿🤖

What's New 🎉

5fe5782 - Michael Arthur: release: 0.6.6 - 91b7e16 - Michael Arthur: feat: map backup services, in-job setting changes and transport switch fixes - 8983f62 - Michael Arthur: release: 0.6.5

New features

Map backup and restore through the Mammotion cloud: there are six new services.
- backup_map makes a new backup, or overwrites an existing one if you pass its backup ID. It returns the backup ID.
- restore_map replaces the mower's current map with a backup. The mower restarts once the restore finishes.
- get_map_backups lists the backups on the account the integration is signed in with.
- get_map_backup_progress shows how far a backup or restore has got.
- cancel_map_backup cancels a backup or restore that is still running.
- delete_map_backup deletes a backup from the cloud.
- Backup, restore, cancel and delete are admin-only.
- Clear errors are shown when there's no working cloud login or the cloud refuses a request (for example, when the mower is busy).
modify_running_job service: changes settings on the job that's already running without restarting it (Luba 2 and newer). It covers blade height, speed, obstacle detection, path spacing, route mode, no-go zone laps, rain tactics, auto change direction and progress. Areas and route geometry are kept as they are, so a change can't re-plan the job.
set_blade_height service: sends a blade height (15–100 mm) straight to the cutter motor.
Changing the Progress number during a job now updates the running job. Its maximum is now 99%, to match the cloud's limit.

Fixes

The Bluetooth and Cloud switches now stay available when both are off. Before, turning both off left no way to turn either one back on.
Turning scheduled updates back on now works properly. Before, the switch could keep showing off and the BLE link never reconnected.
Cloud (Aliyun) setup failures are now handled. They used to hit the generic catch-all with no reason shown. Now setup falls back to BLE-only mode if BLE is available, and otherwise gives a clear "not ready" error so Home Assistant retries.
Running-job settings are now read correctly from the device. Border mode, no-go zone laps and progress are decoded properly, so an in-job edit doesn't reset them.

For detailed instructions, please refer to the README.

If you encounter any issues or have suggestions, please:

A big thank you to all contributors and users of this integration. Your feedback and support help make this project better!

Full Changelog: v0.6.5...v0.6.6