Multi-point turning: removed, brought back, and what owners report after each update

Update by update

Where it stands. Owner reports on 2.3.30.39 are mixed and still settling (as of September 21, 2026), and LUBA 2 owners are not on it yet. 1.30.29.20 is not on Mammotion's release-notes pages (checked September 5, 2026), and 2.3.30.39 is not in the newest LUBA 3 release log (checked October 20, 2026).

The removal: Mammotion's own statement, and what it does not say

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 acknowledged². 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 turns³. 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.

1.30.29.20: the feature comes back

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

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.

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

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, the same structural gap owners describe in the 2.3.30.39 threads. 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.

2.3.30.39: what owners report on turning

The report many owners were waiting for: 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⁴.

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.
• Staff said the rollout would be quick, and that the app comes first. On September 9 a Mammotion staff account wrote that all users would get 2.3.30.39 that week¹⁵. Another told an owner the app has to be updated first, to 2.3.19.6 or newer, to receive the firmware version 2.3.30.35¹⁶. On September 24 a staff account told a LUBA 3 owner that app 2.3.18.19 or later is needed to receive 2.3.30.39¹⁷. The two app numbers are as given in the two replies; the app is where to look first if the update has not appeared.

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

Turns work, but differently, owners report (first week, to September 21, 2026)

• Smoother turns, in more steps. 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² (⅛ acre) 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"¹¹.

On the rear wheels

An owner asked that the rear wheels stop spinning in opposite directions on multi-point turns. On 9 September a Mammotion staff account answered that "the firmware 2.3.30.39 has accomplished this feature"¹⁸. One reply in that thread says "No, it hasn't", and another owner who tested it wrote that it is "still doing 7-9 point turns just to rotate"¹⁸. The original poster, who ran it the day before and did not watch it, wrote that it "didn't seem to rip up my lawn too much"¹⁸.

Early reports on the release as a whole are 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² (¼ acre) 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⁷.

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

The damage 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. In their words 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⁹. The owner's text on the manual-remote comparison is cut off, so that part is reported 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"⁹. That 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 that reply says the update removed; 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 updating to 2.3.30.39, 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.

Other things owners reported in the same release

These came in with 2.3.30.39 in the first week (to September 21, 2026) and are not about multi-point turning:

• 4G missing after the update, and a two-minute fix. An owner in that same thread had one post-update problem: 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.
• An app change that broke something that used to work: 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.

On the per-zone report, a Mammotion staff account replied on September 15 that the app does not currently support different mowing angles for several zones within one task, suggested a separate task for each zone, and said the team hoped to improve per-zone settings¹³. The reply does not say whether the setting ever worked, so whether the update broke it is still one owner's account. The same owner's report of the cutting discs rebooting repeatedly at low battery was acknowledged the same day: the team said it was investigating the logs¹⁴.

Apart from those replies, 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, and the company's own reply says the setting is not supported.

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.