Mammotion: changed after an update

18 pages. Start with the one that sounds most like yours. Each one opens on what to try first.

Check these first

• Do this first: common mechanical causes before you blame firmware

  A checklist of physical, mechanical, and setup issues that produce symptoms commonly mistaken for firmware bugs. Cheaper and faster to rule out than a rollback, and sometimes the actual fix.

• Tips & fixes that work across models

  Find what your mower is doing, then the fixes owners found for it, newest first. Each fix is dated and works on more than one model.

Suggestions

• Known issue LUBA 2 / LUBA 2X / YUKA / mini series: firmware 1.30.29.24 → 1.30.29.26, the same perimeter issue fixed twice, two weeks apart

  Try first: Note your version, and update to 1.30.29.26 if you are on 1.30.29.24. The perimeter/boundary-crossing fix is the one item both official posts describe in essentially the same language, two weeks apart.

• Known issue LUBA 3: cutting discs spin the other way since the latest update

  Try first: Film the discs from behind at a distance, with the mower mowing on open ground and everyone clear of it. Use slow motion if your phone can. Look at where the cut grass goes: thrown to the sides or forward, instead of behind the mower.

• News Firmware 2.3.30.39: multi-point turning fixed on LUBA 3 AWD and LUBA mini 2 AWD; early owner reports are mixed

  Try first: Check the obstacle-avoidance mode in the app before blaming the update. A mower left on Basic drives into things Sensitive avoids, and that explained at least one destructive-behaviour report. Then widen any No-Go Zone that is too small. One owner still hit a bush because of that.

• Known issue LUBA 3: shuts off mid-task with battery left, or runs flat without going home

  Try first: If you have set a charge limit such as 80%, raise it to 100%. Let the mower charge fully on the dock, then mow again. Owners say a restart in the app can show a sudden drop in the battery figure; charge to full after it.

• Guide Software rollback on Android: what's actually possible

  Try first: Note your app version, back up anything the app does not sync to your account, uninstall. Install the previous known-good build from an APK archive with unknown sources enabled, then turn off automatic updates for this app in the Play Store.

• Known issue Charging stops part-way, around 40 to 75%: LUBA 2, YUKA and YUKA mini 2

  Try first: On a LUBA, open the app's battery page (tap the battery icon, or Settings, then Battery). Check no charging upper limit is set below where your charge stops. LUBA owners report this setting; it may not exist on a YUKA. Then clean the contacts on the mower and the dock and make sure the mower sits square on the dock.

• Guide Rolling back on iOS: what we know so far

  Try first: Work out whether it is the phone app or the mower's body firmware that changed: body firmware has no manual downgrade path on any platform, iOS included.

• Known issue LUBA 1 after firmware 1.11.1.11 and 1.11.1.16: slower turns, spinning in place, crossed boundaries

  Try first: Check which firmware the mower is on in the app. If it is 1.11.1.11 and 1.11.1.16 is offered, read its notes: owners quote a fix for crossing lawn boundaries and smoother multi-point turns. One owner also suggests a cut height of at least 2 inches (5 cm), so the wheels grip grass rather than soil while turning.

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

  Try first: 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.

• Known issue RTK station after firmware 1.16.1.2: a blinking blue light and "RTK Reference Station Is Not Ready"

  Try first: Power the mower down, then cut the power to the RTK station for a few minutes and plug it back in. Watch the station's light: owners saw it blink green and then settle on solid green within a few minutes.

• Known issue YUKA mini 800 will not charge after an update: three owners, one workaround

  Try first: Confirm the mower reaches the dock but does not charge. A mower that never docks is a different fault. See error 1200 and the stuck-contact-pins page instead.

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

  Try first: 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.

• Known issue LUBA 2 AWD X: mower gets stuck / fails to return to dock on recent firmware

  Try first: Read your exact firmware version out of the app's device info and write it down. This page cannot name one, so yours is the number that makes it specific.

• Known issue LUBA mini 2 (1500 LiDAR): firmware 1.30.25.16, NetRTK disconnected and stuck in Single positioning

  Try first: Write down both numbers your setup reports: the mower's firmware and the companion app version. The report this page is built on lists 1.30.25.16 and app 2.3.12.11, while Mammotion's own notes for this model list only 2.3.x firmware strings, so which number is which is still unresolved.

• Known issue LUBA 3: firmware 2.3.25.12, WiFi/4G drops and docking failures

  Try first: Note your version, then check whether it matches the reported pair: the app disconnecting after a second or two, and "Return failed" / "Charging failed (1000011)" at the dock.

• Known issue YUKA mini: firmware 1.15.20.2303, NetRTK activation failure

  Try first: Note your version. Then check whether the antenna has stopped switching modes and NetRTK activation is failing, as opposed to a general signal problem.

• Known issue YUKA mini: firmware 1.14.2.2304, loud/screeching noise at medium blade speed

  Try first: Note your current version first. Then check whether the noise is a screech at medium blade speed rather than at low or high speed.

• Known issue LUBA 2: rolling back firmware 1.15.21.1

  Try first: 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.

None of these match?

Contact Mammotion support with your model, firmware version and what you have tried. Then tell us what happened, so the next owner finds it here.