Issues we're watching

LUBA 1

Partial-charge ceiling with no error code, seen twice five months apart. One report followed winter hibernation (capped around 52-55%); the other followed an unspecified update (capped around 22-48%, worsening over time)¹. Same specific symptom, different apparent trigger, no confirmed cause in either. From 2024; treat as historical unless someone reports it recently.

LUBA 2

4G/cellular connectivity breaks after a firmware update, with no shared version. One mower lost all 4G after a firmware update; a further update didn't restore it, and Mammotion support diagnosed an "initialization error" in the 4G module before the unit was sent in for repair. A second owner's cellular connection stopped working entirely (with WiFi also becoming "very poor") after version 1.30.25.11 was offered, with no such problems on the version they had been running². The two reports name different versions, so no single update is confirmed as the cause.

Rear wheel motor develops axial play: the wheel stops turning correctly. The left rear wheel stops turning correctly (the mower can no longer drive straight) but still turns by hand, with noticeable side-to-side play in the motor mount; the motor casing would not open without force. A second owner hit the identical left-rear-wheel symptom and was told to send the unit in for repair after a long wait to reach support³. Neither report names a firmware version or a triggering event, so this reads as a hardware wear or defect issue rather than a firmware update that broke something that used to work.

LUBA 3

A firmware update arrived even though automatic updates were switched off. A LUBA 3 owner reports that despite setting automatic updates to off, the mower updated anyway, and asks whether Mammotion force-updates regardless⁵. The obvious explanation in the thread, that the phone app's own store setting auto-updated without them noticing, was checked and ruled out by the owner ("I checked that, still set to manual. They must have forced it."), and another owner answers that they have read of the same thing happening to others⁵. One caveat on the strength of that: the agreement in that thread is second-hand, so that thread on its own contains a single first-hand report of the setting being ignored, not two.

A second, independent first-hand report of the same outcome, September 15, 2026. In a Reddit thread about the LUBA 2 AWD X perimeter and blade-stop fault from the update, an owner who had deliberately turned updates off describes the setting being changed for them in the app. The result: "I had updates turned off deliberately to avoid this sort of issue. But they changed it in the app so I woke up to a stopped Luba and a chewed lawn."⁷ Different owner, different platform, different model line from the LUBA 3 report above, so the pattern now rests on two independent first-hand accounts rather than one. The route is still not pinned down, and we're not claiming it is: the LUBA 3 report describes the mower's own auto-update setting being ignored, while this one describes an app-side setting being changed. Close outcomes, not provably the same mechanism.

The same outcome shows up elsewhere in a different form. In a May 2025 report, the app would not let the owner continue to the mower's page without installing a firmware update, and the five-step workaround they found stopped working whenever a task was already running⁶. That is a different mechanism (the app withholding access rather than an auto-update setting being ignored), but the result is the same: a firmware update the owner did not choose. The app side of that story is documented on Mammotion Android app: version history.

Neither report names a firmware version and neither includes an error code, which is why this sits here rather than on a version-specific page. If your mower updated when you had told it not to, the version it moved to is the detail that would move this entry forward, so tell us.

YUKA mini

Constant "front wheel lifted" warnings have moved to their own page: YUKA mini front-wheel-lifted and tilt warnings.

Across models

"Robot trapped" stops on open ground have moved to their own page: error 1201 on open ground.

Home Assistant accounts shut down. Two owners who connect their mowers to Home Assistant report the account being shut down. One got "Your account activity is abnormal and has been deactivated" on a single login attempt in September, the second time after the same happened in June⁸. The other wrote in late September that their dedicated Home Assistant account had recently been banned⁹. On June 3 Mammotion wrote that owners can keep using platforms such as Home Assistant through supported methods, and that after a new firmware, then in early access, accounts would no longer be restricted for abnormal traffic patterns¹⁰. Neither owner names their firmware version. Mammotion staff accounts said more in the replies under its June post: user accounts do not support multi-device login, so to keep the main account from being logged out when using Home Assistant, use an additional account and share the device from the main one¹¹; and the company was developing plans for local communication support¹². On September 10, restoring an account for another owner, a staff account said that certain incompatible clients, such as Home Assistant, can cause this problem, and suggested switching to a different client for now¹³.

Before you blame the firmware

Two reports read as corrections rather than faults, and both are worth checking before you conclude a firmware update broke your mower.

• A grass build-up under the blade guard is the documented cause of most height-adjustment failures. An authorized Mammotion dealer's repair-shop walkthrough attributes the overwhelming majority of these cases to grass compacted under the blade guard (the disc just below the cutting blades), which the blade-lift mechanism eventually cannot overcome, so the mower reports that it can't complete the height adjustment⁴. It also explains why the report so often reaches owners as a connectivity problem. Clearing the build-up out is the fix; the full diagnosis and prevention practice are at LUBA 2/2X cutting height system failure.
• An obstacle-avoidance mode left on 'Basic' explains destructive mowing. An owner who had blamed the firmware noticed the mode was set to Basic and not Sensitive, and reports much better behaviour afterwards. See the 2.3.30.39 page.

Both share a shape: a real update lands at the same time as a mechanical problem or a setting that was never configured, and the update takes the blame. Checking the mechanical cause first is cheaper than rolling firmware back.