My Robot Doc

Known issue

LUBA 2 AWD X: obstacle avoidance too sensitive in channels, blocks passable routes

Two independent owners report the mower refusing a "channel" path between mapped zones as blocked, one on ground it crosses without trouble during an ordinary mow, the other at a step of about 4 cm. A changelog a forum member pasted for a LUBA 2 update names better obstacle handling in channels, but Mammotion's own LUBA 2 AWD X release logs for April to May 2025 do not.

Status Open

Models
LUBA 2 AWD X 3000X (reported on this variant; may affect other LUBA 2 AWD X sizes sharing the same firmware, unconfirmed)
First reported
13 May 2025
Last updated
24 Oct 2026
Affects
Robot body — not the app
LUBA 2 AWD X 3000X (reported on this variant; may affect other LUBA 2 AWD X sizes sharing the same firmware, unconfirmed)First reported 13 May 2025Details
Models
LUBA 2 AWD X 3000X (reported on this variant; may affect other LUBA 2 AWD X sizes sharing the same firmware, unconfirmed)
First reported
13 May 2025
Last updated
24 Oct 2026
Affects
Robot body — not the app

What to do next

  1. Safety first

    Before you try anything below, read the safety rules from your mower’s manual.

    Update to the newest firmware the app offers. A forum member's copy of a changelog lists a channel fix in 1.13.4.4405, but that is a LUBA 2 release, and no LUBA 2 AWD X release log from April to May 2025 names it.

    More about this step

    Applies when: it refuses a mapped channel between zones while the same ground causes no problem during an ordinary mow.

    Worked if: the mower may cross the channel; no source confirms that for the AWD X.

    Didn't work? Next: step 2 — When it stops short of the channel, issue manual send-to-dock...

    Method: a forum member's paste of a LUBA 2 changelog, and Mammotion's own LUBA 2 AWD X release logs, which do not name it

  2. When it stops short of the channel, issue manual send-to-dock attempts. One owner needed several before it continued on its own.

    More about this step

    Applies when: you have not updated yet, or the update is not available to you.

    Worked if: the mower resumes and finishes the job on an older build.

    Didn't work? Next: step 3 — If you still see this after updating, or on another LUBA 2 AWD X...

    Method: the first owner's report on this page

  3. If you still see this after updating, or on another LUBA 2 AWD X size, tell us. That would show whether any firmware fixes it for the AWD X.

    More about this step

    Applies when: it persists after updating, or your variant is not the 3000X the reports cover.

    Worked if: owner reports settle what the changelogs do not.

    Method: this page's own closing request

Robot body — not the app. See our app vs. firmware vs. RTK guide if you're not sure which one you're dealing with.

On this page
  1. What to do next
  2. What happened
  3. Is there a fix?
  4. What this isn't
  5. Sources
No fix is confirmed for the LUBA 2 AWD X. The only changelog line about channels is a forum member's copy of a LUBA 2 release note3, and Mammotion's own AWD X logs from April to May 2025 do not mention it4567.

What happened

Two LUBA 2 owners described the same message in one forum thread on 13 May 2025: the mower treated a "channel," the mapped path connecting two mowing zones, as blocked. For the first owner, on a LUBA 2 AWD X 3000X, the same ground was no obstacle at all during an ordinary mow. The second said they had met the message before and traced it to a step.

One owner's mower stopped about 2 meters (6½ feet) short of the channel every time a task finished in the second zone, reporting that returning to charge in the current zone had failed. It took several manual "send to dock" attempts before it carried on by itself1. Deleting the channels and drawing a new one, as another member suggested, did not fix it either2.

The same owner's mower reported the channel as "blocked" near a bush that owner had trimmed, and stopped before a small incline in it, yet drove over that same incline without trouble while mowing2.

The second owner's mower refused a step about 4 cm high, although a LUBA 2 is said to manage 5 cm. In that owner's view the camera read the step as an obstacle it could not pass, and obstacle detection in channels is "definitely a problem and too sensitive"2.

A third member suggested switching obstacle avoidance to "Off." The first owner had already tried it: the setting applies to the mowing task itself, and the channel behaved as before. The second owner added that it is no fix anyway, because the mower would then cut down anything lying on the lawn2.

Is there a fix?

About six weeks after these reports, a forum member posted a changelog for a LUBA 2 update from 1.11.511.631 to 1.13.4.4405. Among other changes it lists "improved sensitivity mode for avoiding obstacles in channels"3, which matches the symptom both owners described.

That post is headed for the LUBA 2, the 2024 model, while the first owner's mower is a LUBA 2 AWD X 3000X. Mammotion's own release logs for the AWD X list 1.12.943.119 (21 April 2025)4, 1.13.2.4410 (9 May)5, 1.13.3.4413 (19 May)6 and 1.13.4.4413 (23 May)7. None of them mentions channels or obstacle sensitivity, and the 1.13.4.4405 note itself exists on this page only as the forum member's copy. So whether any firmware fixes this on the AWD X is not confirmed.

What this isn't

This is about the mapped channel between zones only, not obstacle handling during a mow. The broader "gets stuck against obstacles / fails to return to dock" pattern on recent LUBA 2 AWD X firmware is a different problem, with its own page.

If you see this on a LUBA 2 AWD X, tell us your firmware version and size (3000X/3000HX/5000X/5000HX/10000X/10000HX), and whether a firmware or app update changed it: let us know.

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.

Reddit