My Robot Doc

Known issue

LUBA 2: rolling back firmware 1.15.21.1

What changed in 1.15.21.1, what it broke that used to work, and how to roll back if it's causing problems on your unit.

Status Open

Models
LUBA 2
First reported
27 May 2026
Last updated
15 Aug 2026
Affects
Vision module (on the robot) — not the app
Rolling back from
1.15.21.1
Target version
previous release (not yet confirmed, see note below)
LUBA 2First reported 27 May 2026Details
Models
LUBA 2
First reported
27 May 2026
Last updated
15 Aug 2026
Affects
Vision module (on the robot) — not the app
Rolling back from
1.15.21.1
Target version
previous release (not yet confirmed, see note below)

What to do next

  1. Note your current version first. Then check whether the live camera feed fails over SIM/4G while still working over Wi-Fi: that is the fault reported against this release.

    More about this step

    Applies when: the mower is on 1.15.21.1 and you rely on a cellular connection for remote monitoring.

    Worked if: you know whether 1.15.21.1 is actually costing you anything.

    Didn't work? Next: step 2 — Read Mammotion's own LUBA 2 release notes and confirm the exact...

    Method: the release thread: owner reports, against a changelog that mentions only improved camera resolution

  2. Read Mammotion's own LUBA 2 release notes and confirm the exact version string of the release before this one.

    Stop and get help if

    no prior build can be confirmed: the immediate predecessor's version string is unknown, and LUBA 2 numbering does not rise in a straight line, so 1.11.511.631 must not be assumed to be the one before this.

    More about this step

    Applies when: you are considering reverting at all.

    Worked if: you have a real target build rather than an assumption.

    Didn't work? Next: step 3 — Ask Mammotion support about a revert, and tell us the version...

    Method: this page's own two version warnings

  3. Ask Mammotion support about a revert, and tell us the version string if you can confirm it. The body firmware has no self-service downgrade path, which is the conclusion of this site's own rollback guides.

    More about this step

    Applies when: the fault affects you and no target build has been confirmed.

    Worked if: the case is with support, and the version string this page cannot supply is on record.

    Method: the rollback guides' own position, plus this page's open request

Vision module (on the robot) — 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 changed in this release
  3. What's been reported
  4. Rollback procedure
  5. Sources
Before you start: confirm your mower's current firmware version and note it down. If this rollback doesn't go as planned, you'll want that number to ask for help.

What changed in this release

Released May 27, 2026. Improved the live camera feed resolution.

What's been reported

The live camera feed stops working over SIM/4G on this version; it still works fine over Wi-Fi1. If your mower relies on a cellular connection for remote monitoring, this is the fault to check for before deciding whether to roll back.

Rollback procedure

There is no procedure here to follow. The release immediately prior to 1.15.21.1 is what to ask Mammotion support for, not something an owner can run: this is the mower's own body firmware, and no confirmed manual downgrade path exists. The general Android and iOS guides cover what is actually possible today, which is the phone app rather than the mower.

Exact prior build not yet confirmed. Mammotion's own knowledge base2 shows a LUBA 2 release dated May 25, 2026, just two days before 1.15.21.1, very close to it, and its exact version string is unknown. The last confirmed version number is 1.11.511.631 (April 16, 2025), but that's over a year earlier and there was very likely at least one release in between. Check the official LUBA 2 release notes directly for the May 25, 2026, entry before picking a target build: don't assume it's 1.11.511.631.
Version numbers on LUBA 2 don't increase in a simple straight line across releases (a jump like 1.11.511.631 → 1.15.21.1 → 1.30.29.8 suggests the numbering scheme itself was restructured), so confirm the exact build against the official release notes before asking support for it, rather than assuming "previous" means "lower number."

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