YUKA mini 2 1000H (LiDAR)

4 entries, recently updated first

News LUBA 3, LUBA mini 2 Series & YUKA mini 2 Series

LUBA 3 / LUBA mini 2 / YUKA mini 2: the version history Mammotion's own knowledge base is missing

Mammotion's support knowledge base for this line still shows 2.3.27.23 as current, while real and official reports put it at least two releases further ahead.

First reported 13 Aug 2026 Last updated 03 Nov 2026

News YUKA mini 2 (the dashed-line owner has a YUKA mini 2 500)

YUKA mini 2: what Mammotion says about LiDAR warmth, DropMow in low light, the dashed line and the side LEDs

Four questions YUKA mini 2 owners asked on Reddit in September and October 2026, and what a Mammotion staff account answered: a warm LiDAR module while charging is normal, DropMow needs enough light, the dashed line points at the first zone, and the side LEDs stay on while docked.

First reported 22 Sep 2026 Last updated 25 Oct 2026

News LUBA 3 AWD / LUBA mini 2 AWD / YUKA mini 2 / LUBA 2 AWD (rollout pending)

Firmware 2.3.30.39: multi-point turning fixed on LUBA 3 AWD and LUBA mini 2 AWD; early owner reports are mixed

What owners are reporting after updating to 2.3.30.39: the multi-point turn fix many were waiting for, early reports of new navigation quirks, and one case that turned out to be an app setting rather than the firmware.

Firmware: 2.3.30.39

First reported 10 Sep 2026 Last updated 24 Oct 2026

Known issue YUKA mini series, YUKA, YUKA mini 2, LUBA mini AWD, LUBA 2 (base & AWD X) & LUBA 3 3000

Error 1425 (vision module fault): reported across YUKA, YUKA mini, YUKA mini 2, LUBA mini AWD, LUBA 2 (base & AWD X) & LUBA 3

"Error detected in the 3D vision module (1425)" has shipped as an official fix on four model lines and been independently owner-reported on four more, with at least five different causes. Here's what's confirmed for each, so you're not chasing the wrong fix.

First reported 15 Jul 2024 Last updated 24 Oct 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.