LUBA mini AWD LiDAR

4 entries, recently updated first

Reference LUBA 2 AWD, LUBA 2 AWD X, LUBA mini AWD, LUBA mini AWD LiDAR, YUKA, YUKA mini & YUKA mini Vision (see scope note for what's not covered)

Mammotion fault & error code reference

Official Mammotion fault/error codes, meaning and manufacturer-recommended fix for each, cross-checked against seven current official user manuals, plus which model lines' manuals don't document fault codes at all.

Last updated 03 Nov 2026

Known issue YUKA (sub-model not stated in most reports), LUBA Mini AWD LiDAR, and LUBA 1 / LUBA 2 (cross-model corroboration)

Error 1200 (Recharge failed): reported across multiple models, at least three distinct causes

"Recharge failed (1200)" has been independently reported across the YUKA line, LUBA Mini AWD LiDAR, and LUBA 1 / LUBA 2 units, with several confirmed different causes: a faulty charging station whose light has gone dark, a dock that passes every check and still fails, and an unlevel dock. Check each before assuming a mower-side fault.

First reported 08 Jun 2024 Last updated 03 Nov 2026

Known issue LUBA 2 (including the 3000H), LUBA mini AWD LiDAR

Error 1201 'Robot is trapped' on open ground after updates: LUBA 2 and LUBA mini AWD LiDAR

Owners report the mower stopping with error 1201, "Robot is trapped", on open lawn with nothing in its way, several times a mow and in a different place each time, since the late-summer updates. What Mammotion says to check, what owners found, and the blades that can stay off when you press Continue.

First reported 04 Sep 2026 Last updated 21 Oct 2026

Guide LUBA mini AWD LiDAR (1500 / 1500H)

LUBA mini AWD LiDAR (1500/1500H): official firmware version history

Every firmware release for this model, as Mammotion lists it in its own release notes.

Firmware: 1.17.0.4312

Last updated 05 Sep 2026

Nothing here matches your symptom?

If yours isn't here, it may not have been reported enough times to confirm yet. That doesn't mean it isn't real.

Do this first: common mechanical causes
Many symptoms that look like firmware turn out to be physical — a loose cutting disc, gummed-up wheel shafts, grass buildup, an unlevel charging dock. Cheaper and faster to rule out than a rollback.
Issues we're watching
Problems confirmed by two or more independent owner reports but not yet pinned to a specific firmware or app version. If yours is there, a new report with version details is what promotes it to a full guide.

What to have ready before you contact Mammotion support

Support resolves cases fastest when the report is specific. "It broke after the update," with no version number, is very hard for anyone — including Mammotion — to act on.

Exact model and variant, including any suffix — e.g. LUBA 2 AWD 5000X vs. 5000 (the "H" suffix means a taller cutting-height range, not a different generation).
Your mower's body firmware version — usually under Device Info / About Device in the app (a longer string like 1.30.29.26). Separate from the app version.
Your companion app version — from the app's own About/Settings screen.
The exact symptom, and what the mower was doing when it started.
Whether it began right after a firmware or app update, and which one.
Any in-app error code, and roughly when it appeared.
The app's event log or diagnostic report, if your model provides one.
Photos or a short video, if the issue is physical (docking, damage, turf).

Mammotion lists its support channels by region — including a 24/7 live chat — at mammotion.com/pages/contact-us. Regional support email: support-na@ (North America), support-eu@ (Europe), support-apac@ (Asia Pacific).

Found something we don't cover yet? Send us the details — that's how the next owner finds it documented.