News

Firmware 1.30.29.20: "multi-point turning" restored after being removed

Mammotion restored a previously-removed feature in this release, relevant if you're deciding whether to wait for a fix rather than roll back.

Models
LUBA (generation unknown)
First reported
17 Aug 2026
Last updated
24 Oct 2026
Affects
Robot body — not the app
Rolling back from
1.30.29.20
LUBA (generation unknown)First reported 17 Aug 2026Details
Models
LUBA (generation unknown)
First reported
17 Aug 2026
Last updated
24 Oct 2026
Affects
Robot body — not the app
Rolling back from
1.30.29.20

What to do next

  1. Safety first

    Before you try anything below, read the safety rules from your mower’s manual.

    Check recent release notes and forum threads before weighing a rollback for a feature that disappeared. 1.30.29.20 restored multi-point turning that an earlier update had removed, and the same thing happened again in 2.3.30.39 on newer hardware.

    More about this step

    Applies when: a feature you used to have stopped working after an update.

    Worked if: you know whether waiting for a release is the realistic route, which for body firmware it is, because no self-service rollback path exists.

    Didn't work? Next: step 2 — Understand what an automated turn does before relying on it. It...

    Method: the firmware thread cited here, plus this site's 2.3.30.39 page

  2. Understand what an automated turn does before relying on it. It moves the mower into space its sensors do not cover, and that gap has an injury report recorded behind it: attributed, and with no link asserted to any update.

    Stop and get help if

    if an automated turn happens anywhere a child or a pet could reach, keep them out of the area until the turn completes.

    More about this step

    Applies when: the restored feature is multi-point turning, or you are deciding where to allow it.

    Worked if: you know the safety context for the feature being restored, before using it near anything alive.

    Didn't work? Next: step 3 — Tell us which LUBA generation you are on. The source thread says...

    Method: this site's own safety report page (a Swedish report naming no manufacturer or model)

  3. Tell us which LUBA generation you are on. The source thread says only "Luba", and 1.30.29.20 appears on none of Mammotion's own release-notes pages, so both the model attribution and the version string are still unconfirmed.

    More about this step

    Applies when: you can confirm which generation this version applies to.

    Worked if: the attribution this page flags as uncertain gets settled.

    Method: this page's own two uncertainty callouts

Robot body — not the app. See our app vs. firmware vs. RTK guide if you're not sure which one you're dealing with.

This page isn't a rollback guide; it documents a report worth knowing about before you decide to roll back at all.

What happened

Firmware 1.30.29.20 restored a feature called "multi-point turning" that had previously been removed in an earlier update1, direct evidence that Mammotion sometimes removes a feature in one release and brings it back without fanfare in a later one.

Mammotion's own statement, August 5, 2026. The removal was confirmed publicly by Mammotion's community account, in its own words: the feature went while the company was "optimizing and upgrading the algorithms across our entire product lineup", with the stated target of restoring "an improved version in an upcoming firmware update", and with owner concerns about lawn wear from zero-turn maneuvers explicitly acknowledged2. What the statement does not say is worth as much as what it does: it gives no reason beyond the algorithm overhaul, and it does not mention the injury report linked below. No link between the two is asserted here, in either direction. Its closing line is the closest it comes to a cause: Mammotion says it will "continue to balance technological advancement, operational efficiency, and product and user safety". A Mammotion staff account added in the replies on August 12 that a new, improved version would be released soon and would further improve how the robot turns3. The 136 replies under it are overwhelmingly about the removal itself: owners describing a mower they can no longer run without marking their lawns, and asking for a fix or a revert rather than for the feature to stay as it was.

Why this matters if you're considering a rollback

If you're missing a feature that used to work and are weighing whether to roll back firmware to get it back, it's worth checking recent release notes and forum threads first: there's a real, documented precedent for Mammotion restoring removed functionality in a subsequent update rather than you needing to revert.

Update, September 15, 2026: the same pattern has now happened again on newer hardware: owners report multi-point turning working again in firmware 2.3.30.39 on LUBA 3 and LUBA mini 2, alongside a mixed set of new reports. See Firmware 2.3.30.39: multi-point turning fixed on LUBA 3 AWD and LUBA mini 2 AWD.

Safety context: An automated turn moves the mower into space its sensors do not cover, and that gap has now been reported with an injury behind it: a Swedish news report from July describes a mower with no rear sensors that kept mowing while it reversed over a 15-month-old. It names no manufacturer or model, and nothing connects it to the firmware on this page. It is recorded, with its limits stated, at Reported injuries during multi-point turns. We assert no link between it and any update.

Model attribution is uncertain. The source thread's title only says "Luba," without specifying which generation (LUBA 1, LUBA 2, or LUBA 3). We're flagging that ambiguity rather than guessing. If you can confirm which model this applies to, let us know.
Not confirmed against official release notes. We checked Mammotion's own support knowledge base for LUBA 1, LUBA 2, LUBA 2 AWD X, and LUBA 3 (as of September 5, 2026) and version 1.30.29.20 does not appear on any of them. The closest published entry is 1.30.29.8, dated July 31, 2026, on both the LUBA 2 and LUBA 2 AWD X release-notes pages, close enough in numbering that 1.30.29.20 may simply be a later point release Mammotion hasn't documented yet, or the version string in the source thread may not be exact. We're stating that uncertainty rather than guessing which is true.

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