Build 2.3.30.26 spotted in the wild — Mammotion hasn't published notes for it. Reminder: back up your maps before updating.
MammoStatsMammoStats

Is LUBA 2 AWD firmware 1.15.21.1 safe? — Too early to say

Only 6 owners have reported on this build so far — not enough for a score. What we do know: 4 of the 6 reports describe problems.

1.15.21.1OFFICIAL
LUBA 2 AWD · Released 27 May 2026 · rollout: Current
Too early to say
Mixed

2 normal and 4 glitchy across 6 reports. Most cited: getting stuck (2). A score appears at 10 weighted reports; this build has 6.

What owners report on this build

  • Getting stuck or pausing for no reason — 2 owners

Reported by one owner each

  • Won't dock or charge — 1 owner
  • Mapping errors (missed patches, wrong edges) — 1 owner
  • Tank turning (spins in place, tears the turf) — 1 owner
  • Tears or digs up the lawn — 1 owner

What owners say this build fixed

    Reported by one owner each

    • Phantom obstacles (stops for things that aren't there) — 1 owner

    The 6 reports, in full

    I have two Luba 2 AWD 3000s installed at two different properties. Both have been running for about a month and both are updated to the latest firmware (v1.15.21.1). Overall I’m very happy with them, but both occasionally pause during mowing for no obvious reason.

    A week or moreyard details not provided

    Ever since I updated, my Luba 2 has become practically useless. While mowing, especially near the boundary edges, it constantly gets itself stuck. It starts digging holes into the ground, attempts bizarre erratic turns, and keeps doing tank turns even though I have the tank turn setting explicitly turned off! Before this update, everything was fine, but the new firmware completely broke the navigation.

    A week or moreyard details not provided

    I also have Luba 2 AWD and this update actually fixed a lot of issues for me with camera sensitivity.

    A week or moreyard details not provided

    On my side, with my Luba 2 AWD 3000, I noted since the 1.15.21.1 release it's not possible to rename any area as no windows appears to enter the new name.

    yard details not provided

    Habe heute das Update durchgeführt. Ich bin der Meinung dass Remote nun wieder ohne Probleme funktioniert. Habe heute rund 900 qmtr aus der Ferne gemäht und konnte mich mehrfach direkt verbinden. Ich bin aktuell zufrieden.

    Did the update today. I'm of the opinion that Remote now works without problems again. Mowed around 900 sqm remotely today and was able to connect directly several times. I'm satisfied at the moment.

    Just updatedyard details not provided

    Habe auch das Update gemacht, läuft nun auch wieder mit HA ganz gut

    Did the update too, it's running quite well again with HA [Home Assistant] now.

    Just updatedyard details not provided

    That's everything we have — and the reports are mixed. We'd rather show you 6 real reports than a made-up percentage; if you're on this build, yours is the report that moves it.

    1 report on this build turned out to be something else.

    1 the phone app

    These don't affect the score.

    Running 1.15.21.1?
    30 seconds, no account. Back up your maps first if you haven't.
    Log yours

    Do I need to update the app too? →How does 1.15.21.1 behave on other models? →