My Robot Doc

Known issue

LUBA 2 AWD X: mower gets stuck / fails to return to dock on recent firmware

The mower gets stuck against obstacles, drives into no-go zones, and fails to return to the charging station, on the latest firmware as of late August 2026.

Status Open

Models
LUBA 2 AWD X (3000X/3000HX, 5000X/5000HX, 10000X/10000HX)
First reported
31 Aug 2026
Last updated
03 Sep 2026
Affects
Robot body — not the app
LUBA 2 AWD X (3000X/3000HX, 5000X/5000HX, 10000X/10000HX)First reported 31 Aug 2026Details
Models
LUBA 2 AWD X (3000X/3000HX, 5000X/5000HX, 10000X/10000HX)
First reported
31 Aug 2026
Last updated
03 Sep 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.

    Read your exact firmware version out of the app's device info and write it down. This page cannot name one, so yours is the number that makes it specific.

    More about this step

    Applies when: you are seeing 1200, 1030 or 1032 events, or the mower driving into a no-go zone.

    Worked if: you have the detail this page is missing, whatever you do next.

    Didn't work? Next: step 2 — Check whether the stall sits in the mower's blind spot. The...

    Method: the thread's event log (August 31, 2026), version unconfirmed

  2. Check whether the stall sits in the mower's blind spot. The bumper bar's distance from the wheel, plus single-direction LiDAR that does not cover the sides, means a side-on obstacle can be missed whatever the firmware does.

    Stop and get help if

    the mower is stuck anywhere a person or an animal could reach it: secure the machine before diagnosing anything.

    More about this step

    Applies when: it gets stuck against a tree or a low obstacle rather than failing in open ground.

    Worked if: you know whether a rollback could even address your case before spending a rollback's effort on it.

    Didn't work? Next: step 3 — Read the rollback guide for what is actually possible today....

    Method: this page's own hardware caveat

  3. Read the rollback guide for what is actually possible today. Then send us your version and whether an earlier build behaved better.

    More about this step

    Applies when: the version is confirmed and the stuck events continue.

    Worked if: you know the realistic options, and the page carries version numbers instead of a general description.

    Method: this page's own closing instruction and its open 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.

Exact firmware version not confirmed. This is described as happening "on the latest firmware," but no exact version string is stated anywhere in the source thread, documented as-is rather than guessing which release it was.
We checked Mammotion's own knowledge base2 for LUBA 2 AWD X, most recently on September 10, 2026: 1.30.29.8 (released July 31, 2026) is still the most recent published release, a full month before the source thread's report and the only official candidate for "latest firmware" at the time. We can't confirm the mower in the report was actually on that build, so we're naming it as the likely candidate, not a confirmed match.

What happened

An in-app event log (August 31, 2026) on a LUBA 2 AWD X shows repeated errors: "Failed to return to the charging station (1200)," "Robot is lifted or tilted (1030)," and "Robot is stuck in complex terrain (1032)," across multiple sessions over two days1, firmware version unknown.

The same pattern shows up repeatedly in replies: the mower driving into a no-go zone and getting physically stuck against a tree, and the same behavior "WITH a lidar sensor on the latest firmware." Part of this may be a hardware limitation rather than a software update that broke something that used to work. The bumper bar's distance from the wheel, combined with single-direction LiDAR that doesn't cover the sides, is worth ruling out before assuming a firmware rollback alone would fix it.

Why we're not giving a specific rollback target here

No exact firmware version is confirmed in the source thread, so this page can't responsibly point at a specific "roll back from X to Y." If you can confirm your exact firmware version (and, ideally, whether a specific prior version was better), that's genuinely useful. Let us know so this page can carry real version numbers instead of a general description.

If your mower is getting stuck near obstacles or missing the charging station, the general Android rollback guide covers what's actually possible today. It's worth reading before assuming a firmware change is the fix, given the hardware-limitation caveat above.

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