Known issue

Mowing progress climbs while the mower sits still, and part of the lawn is marked done but never cut

Owners on several models report the app's percentage or route shrinking while the mower is parked, stuck or paused, so the task ends with strips uncut. What they saw, what they tried, and how to check the lawn after a task that looked finished.

Status Open

Models: Cross-model (reported on several models)
First reported: 12 Jul 2026
Last updated: 24 Oct 2026
Affects: Robot body — not the app

Cross-model (reported on several models)First reported 12 Jul 2026Details

Models: Cross-model (reported on several models)
First reported: 12 Jul 2026
Last updated: 24 Oct 2026
Affects: Robot body — not the app

What to do next

After a task that finished early or too fast, walk the lawn and look for uncut strips. Check especially around the spot where the mower stopped. Owners report the app marking those areas done when the mower never covered them, and one says the app seems to redraw the mowed line afterwards, so the app map is not proof.

More about this step

Applies when: the percentage jumped, the task ended sooner than usual, or the mower sat in one place during the task.

Worked if: you know what was actually cut, and can start a second task for what was not.

Didn't work? Next: step 2 — Switch the mower off with its power button until it really shuts...

Method: owners in the cited threads
Switch the mower off with its power button until it really shuts down. Switch the RTK station off too, wait a while and start both again. A full reboot of the mower and the RTK fixed it for one owner who thought it was a data-link problem. It did not for another.

More about this step

Applies when: the progress is moving but the mower is not, particularly after a firmware update.

Worked if: the mower follows the route it is showing.

Didn't work? Next: step 3 — If it happens at the same place every time, look at your map...

Method: two owners' accounts
If it happens at the same place every time, look at your map there. One owner found a closed virtual fence zone had made an area the mower could not reach count as finished, and fixed it by re-creating the zone with the fenced area left out of the boundary. Another backed up the maps to the cloud, deleted everything and mapped again, and says it then worked.

Stop and get help if
back up the maps to the cloud first: starting again means mapping every area again.

More about this step

Applies when: the same spot causes the stall, or the stall began after you edited a zone.

Worked if: the task no longer counts an unreachable area as done.

Didn't work? Next: step 4 — Tell us your model, the firmware version, and whether it stalled...

Method: two owners' accounts
Tell us your model, the firmware version, and whether it stalled in the same place each time.

More about this step

Applies when: it happens to you.

Worked if: the pattern across models gets clearer.

Method: this page's own closing request

Cause not confirmed. The reports are on different models and different firmware, and the fixes below worked for some owners and not for others. Mammotion has not given a cause in these threads.

What owners see

A YUKA mini 600 owner says that when the mower gets stuck, sometimes the percentage mowed increases while it is not moving. The owner's mower once paused in a corner already mowed, and on resuming skipped half the yard because it believed it was further along than it was¹. In August the same owner wrote that the mower had stopped and paused again, and the percentage climbed without it moving².

A LUBA 2 owner saw the mower leave the dock and stop, while progress and time remaining ticked down in the app until it reached 100% and went home to the dock it was still sitting beside³. Another owner says that on standing, segments of the planned route disappear from the map and the percentage creeps up⁵.

A different owner posted that the mower thinks it is moving while it sits still, then reports it is blocked on flat ground⁷. In the same thread another owner says the mower sat there, erased the lines on the map, and told them it was done⁹. A LUBA 3 owner went further: the app does not simply show where the mower has mowed, but appears to redraw the line after the fact¹⁰.

What owners tried

A full reboot of the mower and the RTK. It fixed it for one owner, who thought the cause was the RTK data link⁶. A LUBA 2 owner tried a reboot and then rebooted the RTK too, without success⁴.
Re-creating a zone. A closed virtual fence zone had created a mowable area the mower could not enter, so the task marked it complete. Re-creating the zone and leaving the fenced area out of the boundary fixed it⁸.
Deleting all maps and starting again. One owner did this after backing the maps up, and the task then ran. They note it meant mapping everything again⁴.
A no-stop zone at the spot. A Mammotion staff account suggested a no-stop zone at the spot where the mower keeps stopping. It added that the climbing-progress report had been escalated to the relevant team¹¹.

If the task finished early or too fast, walk the lawn before assuming it was cut. Tell us what stalled it and where.

Independently reported 10 times by different owners. Manufacturer has acknowledged this. This records that the issue was independently reported — it isn't an estimate of how common the issue is among all owners.

Sources

Did this work, or not?

Telling us what happened helps the next owner with the same fault.

Tell us what happened

Fixed it? Share with other owners.

Post directly to Reddit or use link in text, email, Facebook, etc.