My Robot Doc

Known issue

LUBA mini 2 AWD 1500/1500H (LiDAR): LiDAR fails to initialize on firmware 2.3.27.16

New units on firmware 2.3.27.16 couldn't start mapping because LiDAR wouldn't initialize. Mammotion confirmed it in-thread as a known, firmware-caused batch problem, resolved for three reporting owners by a follow-up update within days.

From owners' reports in German, not from Mammotion's own pages.

Status Manufacturer-acknowledged

Models
LUBA mini 2 AWD 1500/1500H (LiDAR)
First reported
27 Jun 2026
Last updated
07 Sep 2026
Affects
Robot body — not the app
LUBA mini 2 AWD 1500/1500H (LiDAR)First reported 27 Jun 2026Details
Models
LUBA mini 2 AWD 1500/1500H (LiDAR)
First reported
27 Jun 2026
Last updated
07 Sep 2026
Affects
Robot body — not the app

What to do next

  1. Check for a firmware update and install it. Make sure the companion app is current too, because some updates only trigger from the latest app rather than from the version-history screen.

    More about this step

    Applies when: a new unit on 2.3.27.16 cannot start mapping because LiDAR will not initialize.

    Worked if: LiDAR initializes and mapping starts normally.

    Didn't work? Next: step 2 — Ask Mammotion support directly if no update is offered: one...

    Method: three of the four reporting owners confirmed the follow-up update fixed it

  2. Ask Mammotion support directly if no update is offered: one owner was told they were already current while newer builds existed, and had to wait for Mammotion to push it.

    Stop and get help if

    do not treat it as a hardware fault: Mammotion confirmed in-thread that this was a batch problem caused by the current firmware, and every case in the thread was firmware.

    More about this step

    Applies when: the app reports you are current but the fault persists.

    Worked if: the update arrives rather than the reader waiting on an app that says they are up to date.

    Didn't work? Next: step 3 — If you see the icon cycling green-to-orange rather than a clean...

    Method: the owners' experiences in the thread

  3. If you see the icon cycling green-to-orange rather than a clean resolution, tell us what eventually worked. The thread ends without that case being closed.

    More about this step

    Applies when: the fault comes and goes after a reboot rather than clearing.

    Worked if: the one unsettled outcome on this page gets an ending.

    Method: this page's own callout

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. Mammotion's response
  4. Resolution
  5. Sources
This page documents a known issue, not a rollback target: Mammotion acknowledged it directly in the thread below rather than owners needing to work around it via a version change.

What happened

On new LUBA mini 2 AWD 1500/1500H units running firmware 2.3.27.16, LiDAR would not initialize, blocking mapping entirely. The app's own retry-then-restart advice didn't help1. Four owners hit it in the same thread.

Mammotion's response

Mammotion support replied in-thread, apologizing and confirming the issue as "a known, temporary batch problem caused by the current firmware", explicitly stating it was not a hardware defect and that technical staff were working on it as top priority1. The reply was in German; the original is in the thread. A second support reply, two days later, had no fix yet and offered 24 replacement blades as compensation once resolved.

Resolution

A follow-up firmware update arrived roughly two days after the first report. Three of the four reporting owners confirmed it resolved the problem for them: LiDAR initialized, mapping and mowing completed normally1. The thread never names the resolving firmware's version string, so that number is unconfirmed; treat "any firmware after 2.3.27.16" as the safest bar rather than a specific build.

The rollout was uneven: one owner stuck on an older build (2.3.25.19) initially couldn't trigger the update at all (the app reported they already had the current version even though newer builds were listed), and had to wait for Mammotion to push it before it downloaded automatically overnight. Some firmware updates also require the latest companion app version to actually trigger, not just being available in the version-history screen, per another owner in the thread.

The same initial fault showed up for a fourth owner, whose LiDAR briefly showed green after a reboot before reverting to the orange warning icon. The thread ends without that owner confirming a full fix. If you're seeing intermittent green/orange cycling rather than a clean resolution, let us know what eventually worked.
If you're hitting this: confirm you're on 2.3.27.16, check for a pending firmware update (and make sure your companion app is also current), and if no update is offered yet, contact Mammotion support directly rather than assuming a hardware fault: every case in this thread turned out to be firmware, not hardware. See what to have ready before you contact support.

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