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

What 2.3.30.39 fixes

The headline is the one many owners were waiting for: multi-point turning works again. An owner who tested the update and published a video pass over the edge routine and multi-point turning reports the problem fixed in 2.3.30.39 on LUBA 3 and LUBA mini 2¹.

Multi-point turning had previously been removed and then restored once before, so a fix arriving inside a normal update (rather than as a rollback) is consistent with how Mammotion has handled it previously — see Firmware 1.30.29.20 — "multi-point turning" restored after being removed.

Which models, and when

• LUBA 3 and LUBA mini 2 are reported as getting 2.3.30.39 now¹.
• YUKA mini 2 is also reported as receiving it⁵.
• LUBA 2 owners are not on it yet. The rollout note Mammotion published for this version names the LUBA Mini 2 AWD 1500, rolled out in stages, and a rep account confirms that in reply to a LUBA 2 owner asking about it² — so treat a 2.3.30.39 report as the LUBA 3 / mini 2 line until a LUBA 2 owner reports otherwise.

That is the mower's own firmware — the robot body — which updates on its own schedule, separate from the phone app.

The early reports are genuinely mixed

Positive. A YUKA mini 2 owner reports a real improvement after updating: "it seems to be doing a pretty good job and I can probably let it work without watching it all the time"⁵.

Negative. A separate LUBA 3 owner reports the mower "spins in the middle of nowhere and comes back without obstacles since the update" — corroborated by four separate replies in that thread ("same for me", "idem" three times) and countered by one owner who mowed two ~1000 m² plots with no problem³.

A German-language report describes the mower still stopping with no visible obstacle after the latest update, the mowing system switching itself off while the robot goes back and forth, and a wider margin being kept at the map edge than before, and a reply describing how difficult it is to obtain a downgrade from Mammotion⁴.

What a week of Reddit reports adds (updated 2026-09-21)

The picture after the first week is more specific than "mixed", and one part of it is new:

• Multi-point turning works, but differently. A LUBA 3 owner updating on day one reports the tank turns are gone but the turn radius is smaller than they remember⁷. Replies characterise the new behaviour precisely: most turns are smoother and take three to four small backups, the edge routine is better, and the blades barely switch off any more⁷. A second owner on a different thread puts the same thing at four or five steps per turn — "much much better than the previous iterations", though still less efficient than the original⁹. One owner's complaint is simply that turns now take much longer than they did before the update that broke them⁷.
• A clean run with nothing changed. The most useful positive report is a controlled one: a LUBA 3 owner ran about 500 m² on 2.3.30.39 with the same settings as before and found no difference at all — multi-point turns working, blades running as they should, obstacle and No-Go avoidance as expected, no change in speed or battery⁸. In the same thread, an owner whose previous version made tank turns even with multi-point turning enabled — ruining their lawn edges — reports the mower "now works with this version"⁸.
• 4G missing after the update, and a two-minute fix. That same owner's only post-update problem was the mower failing to find a 4G network; removing and reinserting the orange key brought it back⁸. If your mower goes offline straight after updating, try that before anything else.
• A new app-side regression: per-zone stripe direction. A LUBA 3 owner reports that the mowing/stripe direction can no longer be set zone by zone — changing the direction in one area changes it in all of them, which they call "very annoying" and ask Mammotion to investigate⁹. The same owner had to remake some boundaries because they had shifted by a few centimetres after the update, and notes the half-turn in front of the charging station has changed as well.

None of that is a manufacturer statement, and the per-zone stripe report is a single owner so far — tell us if you see it too, with your app version, because this one looks app-side rather than firmware-side.

One piece of wider context, added 21 September 2026. A Swedish news report from July describes a robot mower reversing over a 15-month-old, and states that the mower has no sensors for obstacles behind it yet keeps mowing while it reverses — the same structural gap owners describe in these threads. That report names neither manufacturer nor model, and nothing in it connects it to this firmware; both records are kept without asserting a link. See Reported injuries during self-driven turns.

Why multi-point turning was digging up lawns — an owner's diagnosis

The damage this fix removes had a mechanism, and a LUBA 2 owner set out to identify it. On firmware 1.30.29.26, they report that when the mower reverses into a turn to the right, the right front wheel stops driving — their wording is that it "seems to be UNPOWERED so does not make traction" — so the rear wheel ends up carrying the mower and digs into the lawn. Reversing into a left turn powers both of the left wheels and does not produce the same effect. They also note the behaviour does not appear under manual remote control, which is why they describe it as specific to the automated multi-point turn rather than to the mower itself⁶. Our capture of that post ends mid-sentence, so the manual-remote comparison is quoted here only as far as it goes.

A reply in the same thread reports the newest firmware fixed it — "The newest firmware was just released, fixed the issue. V39"⁶ — which is the 2.3.30.39 update covered above, still not released for LUBA 2. So for owners who have it, this is the symptom the update removes; for LUBA 2 owners, the diagnosis is what to look for while waiting.

Before blaming the firmware, check one setting

The most useful single report here is a correction. A YUKA mini 2 owner who "had been blaming the recent destructive tendencies" of their mower on the previous firmware noticed their obstacle avoidance mode was set to 'Basic' — they could not tell whether that was their own change or a glitch — and after updating to .39 and setting it to 'Sensitive', the mower behaved much better. They still hit one collision, because the No-Go Zone around a bush was too small, and Mammotion's reply recommends widening that zone⁵.

So if your mower is behaving destructively after this update, check the obstacle-avoidance mode in the app first: a mower left on 'Basic' will drive into things that 'Sensitive' avoids. That one setting explains at least one "the firmware ruined my lawn" report.

If you have updated

Reports that move this page forward state which model you have, which version you updated from and to, and whether the problem is new. That is what turns a set of mixed early reports into a settled known issue or a confirmed fix — send us the details.