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

What Mammotion announced on August 21

Mammotion posted to r/MammotionTechnology³, applicable to LUBA 2, LUBA 2X, YUKA, LUBA mini Series & YUKA mini Series:

• Reduced unexpected blade shut-offs during mowing.
• Improved turning smoothness to better protect the lawn.
• Fixed occasional issues where the robot could cross boundaries or enter no-go zones.

The post didn't state an exact version number, but a screenshot in the later Hotfix thread shows this shipped to a LUBA mini as version 1.30.29.24, dated August 22, 2026⁴, one day after the announcement, consistent with a gradual rollout.

The same post confirmed LUBA 3, LUBA mini 2 Series & YUKA mini 2 Series were not yet included; firmware for those was still "being actively optimized and tested," per Mammotion.

In the replies that day and the week after, a Mammotion staff account gave dates. A hotfix for the LUBA 3 would follow "next week" to reduce the blades turning on and off²⁴, and one for the LUBA 1 the same week²⁵. On 27 August it said the hotfix was delayed and might take another five days²⁶, and on 28 August that it was under test, with a beta first before the full release²⁷. The next firmware post from Mammotion was the September 4 hotfix, two weeks after the first.

What Mammotion announced two weeks later, on September 4

A "Hotfix Firmware Update," same subreddit, cross-posted word-for-word to the Facebook support group^{4, 5}:

For LUBA 2, LUBA 2X, YUKA, LUBA mini Series & YUKA mini Series: firmware 1.30.29.26

• Fixed an issue of going beyond the perimeter.
• Reduced unnecessary blade stops during edge-following.
• Reduced uncut strips before blade engagement.

For LUBA 3, LUBA mini 2 Series & YUKA mini 2 Series: firmware 2.3.30.35 (their first fix, following the "upcoming" note from August 21):

• Reduced unnecessary blade stops during edge-following.
• Improved obstacle-avoidance performance.
• YUKA mini 2: fixed an intermittent issue of going beyond the perimeter.
• LUBA 3: fixed battery level fluctuation.
• LUBA mini 2 Series: improved blade-deck height adjustment accuracy.

Comparing the two: what actually overlaps

Reading both changelogs side by side, for the LUBA 2 / YUKA / mini-series line:

So: the perimeter/boundary-crossing fix is the one item both official posts describe in essentially the same language, two weeks apart. The blade-stop item is plausibly related but was reframed narrowly enough (edge-following specifically) that we're not calling it a confirmed repeat. Treat "same bug fixed twice" as applying to the perimeter-crossing item specifically, not the whole list.

Between the two posts, on August 30, a Mammotion account answered a LUBA 2 AWD 5000 owner on 1.30.29.24 whose blades sometimes stayed off after the mower backed away from a front-bumper collision: "we’re aware of the blade on/off behavior, and further optimization is planned for the next firmware version"¹⁹. So Mammotion treated the blade behaviour on .24 as a known problem, not only as a changelog line. It did not say whether the September 4 "reduced unnecessary blade stops" item is that fix.

What owners are reporting since the September 4 hotfix

Several boundary-crossing reports followed in the Hotfix thread's comments (including one with video): one mower climbing over a wood barrier "every time"⁴. Firmware version at the time of posting is unknown for these; Mammotion's post describes the hotfix as a phased, gradual rollout, so some may be from mowers that hadn't received 1.30.29.26 yet. Read these as boundary-crossing reports during the rollout window, not confirmed evidence the fix failed once fully applied.

One full, dated Facebook account is worth reading closely. A LUBA mini 2 1500 LiDAR and LUBA 3 3000 owner: "Updated to the latest firmware (.26). Had a lots of problems (not cuting, driving arround outside of cuttng area, leaving a lot of uncut areas…) But this week like they fixed themselves? Yesterday and a day before they cut quite well… no glitches… Don't get it but pleased"⁸ Read in full, this is not a report of an unresolved problem; it's a timeline: symptoms appeared after updating, matching all three categories the hotfix targeted, and then resolved on their own roughly two weeks later, with no action taken. A LUBA mini 2 1000 owner reports the identical pattern in reply: bad for about two weeks, then "quite better"; "they fixed something obviously." Read together, these two reports are consistent with a staged or server-side rollout that kept improving after the September 4 date, rather than the hotfix being complete (or broken) the moment it installed. That's a more specific picture than "the hotfix failed": it's "the hotfix, or something after it, took about two weeks to actually land."

Separately, a LUBA 2 AWD on 1.30.29.24 ignored a manual pause-and-return-to-charger command during a storm, leaving the dock to resume mowing instead of stopping at the usual 80% charge threshold; a previous firmware version reportedly handled this correctly⁹. The pause behavior appears to depend on whether the mower had already started actively mowing versus still traveling to the mow area. Whether this connects to the perimeter/blade-stop changes above is unconfirmed, logged here as a different symptom in the same firmware window, the same class of "mower doesn't honor a stop condition" bug.

A YUKA 2025 on 1.30.29.24 separately left uncut grass strips mid-task, plus lawn damage in turning areas said to have started with a firmware update prior to 1.30.29.24, both before the September 4 hotfix shipped¹². That's notable because "reduced uncut strips before blade engagement" is specifically one of the items the 1.30.29.26 hotfix claims to address: independent evidence the underlying symptom existed beforehand, consistent with (though not proof of) the hotfix targeting a real, pre-existing issue rather than something it introduced.

On Facebook, a LUBA owner posted wavy cuts and missed areas in the middle of a level lawn the mower had cut the day before, after an update that morning. One commenter described the same "waves" after the 2.3.27.16 update, though it normalized for the second area; another reply asked whether the mower was a LUBA 3, so the model is not settled. That is an earlier firmware than this guide covers, so it shows the symptom is not new to .24-.26, not that .24-.26 caused it⁶.

Owners commonly refer to this turning behavior as a "tank turn": a 52-comment thread asking Mammotion directly "any word on fixing the turns so they are less destructive?" uses the term repeatedly, including a description of "a perfect 3 pt zig-zag" turn on a different firmware version¹³. In an unrelated return/refund post, one buyer sent their LUBA 2 back to the retailer citing "all the tank turns" as the reason¹⁴. Both predate this specific firmware window, indicating the turning-quality complaint is a longer-running pattern that 1.30.29.24/.26 are the latest chapter of, not a new symptom this pair of releases introduced. Owners use a second, self-coined name for it, "donuts": the same complaint appears as "my donut spinner" in a comment on the version-announcement thread¹⁶.

Separately, a LUBA 3 3000 had boundary/perimeter misses starting "since the last update this week"; posted in the same window as the September 4 hotfix, exact firmware version unknown⁷. One reply linked it directly to blade-engagement timing: "when the blades shutoff it always misses some of what should be mowed", the same pairing (perimeter misses + blade engagement) the .26 changelog addresses for this model line.

A measured baseline on 1.30.29.24: no A/B comparison yet

One owner measured a LUBA 2 AWD 5000X running 1.30.29.24 on a real 65m² (700 sq ft) test plot¹. The task took 43 minutes 52 seconds, an effective rate of 89 m²/hr (960 sq ft/hr). The mower drove 453m (1,490 ft) to cut 65m² ("1.7x more driving than a clean back-and-forth," per the report), spent 51.7% of its time turning, changed direction 429 times, and did 52 of 53 turns as multi-point shuffles rather than tank turns. An identical test on 1.30.29.26 was planned, for a direct A/B comparison. No follow-up post had appeared as of September 5, 2026 (last checked); if that's changed since, let us know. This is a real, dated baseline on the pre-hotfix version, not evidence either way about whether 1.30.29.26 improved turning efficiency. If the A/B comparison surfaces, it would be the best available quantitative answer to that question; until then, treat this as baseline data only.

A separate report on turning comes from a different product line: a YUKA mini 2 1000 LiDAR repeatedly drove into a wooden structure and went out of bounds several times in one session, needing an emergency stop each time². The firmware version is unknown. One reply blamed "the .30 firmware" for breaking multi-point turning "for every single person." That generalization isn't precise enough to attribute to a specific version in this guide, but it's consistent with the turning-quality complaints from other owners and product lines.

Still ongoing for at least one owner, four weeks after the hotfix (September 8, 2026)

A software engineer running a LUBA 2 AWD X 3000XH posted a detailed account: the mower worked with only occasional curb-barrier snags until roughly a month before posting, then became "unusable", going out of its mapped bounds and getting stuck multiple times, in random locations, every session. They couldn't open a Mammotion support ticket without live photo/video evidence of it happening, which their wife (who handles day-to-day mowing at the affected property) wasn't positioned to capture on demand¹⁵. The post states plainly that other owners are reporting the identical pattern with no fix yet. Read the replies as a small, dated sample of that claim, not confirmation of how widespread it is:

• Corroborating: a second LUBA 2 3000X owner reports new "tank turn" holes appearing where the mower turns, worse on hills, with holes growing further from rain erosion, the same turning-pattern complaint this guide already tracks, continuing.
• A specific counter-report worth noting: one LUBA 2 2024 owner reports zero issues, attributing it to disabling "multipoint turning" (i.e., the tank-turn behavior) in favor of a zero-turn pattern, plus contacting support proactively. They say support routed their specific complaint to engineering and a subsequent update addressed it. This is the same "turn off multipoint turning" mitigation this guide's turning-quality section already touches on, now with a direct owner claiming it worked for them specifically against this ongoing bounds/turning cluster.
• A staying-on-old-firmware data point: a third owner is still on the firmware/app version from June (before both 1.30.29.24 and .26). They are largely happy with their 3000X despite a big hill and difficult terrain, apart from rolling out of the task area about 1 in 20 sessions, and say results are noticeably better at 1fps speed rather than faster. Read as one owner's account that avoiding the update entirely sidestepped the fault the update brought in, not as an endorsement that older firmware is strictly safer in general.
• Two other replies report no issues at all on LUBA 3.

A Mammotion staff account said on September 9 that 1.30.29.26 for the LUBA 2X had "now been fully rolled out"³², which is the company's side of the same picture: the release is out, and owners' reports still differ.

This doesn't change the "staged/uneven rollout" read from the two-week-later reports above. If anything it reinforces it: nearly four weeks after the September 4 hotfix, outcomes are still split between owners who report the issue fully resolved and at least one reporting it as bad as it's ever been. The "turn off multipoint turning" and "stay on/revert to a firmware version from before the problem if you haven't updated yet" mitigations above are the two concrete, actionable data points from this round; the "it fixed itself over ~2 weeks" pattern reported earlier hasn't held for every owner.

The hotfix thread's own comments, five days on (September 9, 2026)

The official Hotfix thread kept collecting reports after the September 4 announcement⁴, and they point both ways on 1.30.29.26:

• Still failing on .26, version named. A LUBA 2 3000X owner on 1.30.29.26 reports, in French (translation ours), that the mower "still does not always make the join between the perimeter and the inner zone, leaving parts of the lawn unmown". The blades, they say, improved slightly but still stop whenever the bumper is active, "even though there is no reason for it, since it changes direction on its own". Their conclusion is that these problems did not exist on 1.30.29.8. The original French is in the thread⁴. This is the exact perimeter-plus-blade-stop pair this guide covers, dated nine days after the hotfix, from an owner naming the version.
• Working well on .26. In the same thread, a different owner reports the opposite: the update "is working perfectly on my Yuka and Luba minis. Turns are nice with no yard tear up and no more sudden stops and emergency shut downs," closing with "No more sudden updates please."⁴ Read with the .26-failing report above, the split outcome the earlier reports showed is still present five days on.
• A different symptom in the same window: map and zone data lost after updating. One owner reports the update "wiped out my zones and cloud is empty again. I have to create them all over for the 3rd time."⁴ Map loss is not the perimeter/blade-stop fault this guide covers, and the report names no model or version. It is logged here only because it landed in the same rollout window and is the kind of data loss worth watching for corroboration. A separate owner (LUBA 3000 AWD) reports the mower derailing in automatic mode after the update while manual mode works, in a version string that is ambiguous as written ("2.3.30.26"); single report, treated as unconfirmed⁴.
• Support side, for context: five days in, one owner's summary of the thread's mood was plain: "Still waiting. No news, and total radio silence."⁴

A dealer's report on .26, four weeks after the hotfix (October 2, 2026)

A poster describing themselves as an official Mammotion dealer and installer, with more than 40 mowers set up, reported three problems on a "Luba Mini 800" running 1.30.29.26²⁰. The first is this guide's own pairing. Edging along a wall with obstacle detection on, the mower "abruptly stops the cutting deck" without the bumper touching anything and leaves an unmown gap of about 3 metres (10 feet). Restarting the mower did not change it.

The other two are new to this page:

• The blades restart with no warning beep. After the stop, the mower moves on and "restarts the cutting blades WITHOUT ANY SAFETY BEEP WARNING". The dealer calls that a serious safety hazard. If your mower does this, keep people and pets clear of it while it edges.
• The cutting height drops to minimum when you add a zone. Adding a new mowing area, by automatic or manual exit, reset the cutting height to the lowest setting. Check the height after adding a zone, before the mower starts.

The replies narrow the complaint²⁰. Several owners say the blades stopping while the mower reverses on the perimeter is now deliberate: a safety behaviour, not a fault. The dealer accepts that part: "turning them off while reversing makes sense." The objection that stands is what happens next: the mower carries on along the edge for a few metres with the blades still off, "leaving a patch of uncut grass." Owners split on the beep: some want fewer alerts, not more, and one notes the volume can be lowered in settings but not muted. Another owner says a later update "did thankfully address the two issues somewhat", without naming a version.

This is one dealer's report, and the dealer status is the poster's own description. It names the version, and it lands four weeks after the hotfix on the unresolved side of the split above. A Mammotion account replied the next day, October 3. It said a newer version was rolling out gradually, with a shorter interval between stopping and restarting the blades after a front obstacle, and that the feedback on the beep had been noted. It called the cutting height dropping to the lowest setting when a zone is added "generally part of the normal blade deck reset process", and asked for the device number and logs²⁰. The dealer's own workaround, posted the same day, is to mow the edge as a separate task with obstacle detection off, which stopped the deck cutting out²⁰.

Owners on .26 in October (October 8 to 11, 2026)

A LUBA 2 owner on 1.30.29.26 posted on October 8 that the mower had dug up whole strips of the lawn in checkerboard mode by turning round on them, while the strips between went unmown. Asked about the turning mode, the owner said there is no option for it in the job and that the cutting path angle was set to optimal²². Another owner replied that turning mode is set in the robot's route settings, not in the job, and a Mammotion account made the same suggestion on October 9, asking the owner to check which turning mode was selected²². The poster said they had never changed the setting. The turns page holds that advice and what owners say about an update resetting it. Owners disagree about zero turn itself: one has used it for three years without damage, and another says the mower cannot do zero-point turns without tearing up the lawn²². A LUBA 2X owner replied that theirs does the same, and had just installed a newer update without yet trying it²².

The next day a LUBA 2 AWD owner of 17 months wrote that turn damage had made them stop using the mower on the lawn it was bought for, and another owner described dead spots from zero-point turns chewing the boundaries²³. Neither of those two names a version.

Before you assume it's this firmware issue: rule out hardware

Before you assume this is the firmware, rule out the physical causes: a symptom that looks like an update that broke something can have a mechanical origin. See our mechanical-causes checklist for the physical checks worth doing before assuming a firmware rollback is the fix.

Why there's no official release-note page to check yet

Mammotion's own support knowledge base is behind on both product lines covered here. LUBA 2 AWD X's page still lists 1.30.29.8 (July 31, 2026) as its most recent entry^{10 21}; neither 1.30.29.24 nor 1.30.29.26 has been published there, five-plus weeks behind. LUBA 3's page is even further behind, stuck at 2.3.27.23 (July 18, 2026)¹¹, meaning 2.3.30.35 (the LUBA 3 hotfix from this same September 4 announcement) isn't documented there either, seven-plus weeks behind. Right now, Reddit and Facebook posts are the only place any of these versions are documented at all, a real gap for anyone trying to look up what changed before deciding whether to update.

Rollback status

Neither official post mentions a way to roll back, and no confirmed manual downgrade path exists for this firmware generation (see the general Android rollback guide for what's actually possible today; it's app/account-level, not mower-firmware). In the August 21 thread, Mammotion was directly asked "will Mammotion ever provide a way for us to BACK OUT of a bad firmware update?" (12 upvotes)³. Mammotion staff did answer rollback questions in that thread, the same day: one account wrote that the company can technically provide a firmware rollback, but iOS owners still cannot get the previous app, and that the answer it prefers is a new, more reliable firmware²⁸. It added two days later that the new firmware creates files the old firmware and app cannot deal with, so every rollback would need many combinations tested²⁹. Support also answered by email, and an owner posted the reply publicly on September 13: "Mammotion does not currently support user-initiated firmware downgrades." The same reply offered a stop-gap for the uncut strip along the boundary while the firmware itself is worked on. In the app, open the map, go to the task's Settings, set the cutting path mode to "Perimeter Laps Only" and raise the number of perimeter laps¹⁷. One LUBA 2 owner on 1.30.29.26 measured what that costs. One or two perimeter laps left 2-4" strips uncut between the laps and the zigzag, and three laps cut cleanly. On the same 5,500 ft² lawn the third lap took the job from 4 h 40 min to 5 h 04 min, "+24 minutes / +8.6%"¹⁸. Mammotion staff have said a fix for this is coming: on September 10 a staff account told an owner still seeing zero-point turns at the boundary that the team was "actively working on a solution"³⁰, and on September 22 another told the owner who timed the workaround that the company was optimizing the zigzag path to cut more grass near the perimeter, with a firmware release later³¹. No version number or date was given. "User-initiated" is the operative word: two owners have since had support push an older body firmware to their mower after refusing at first, which the Android rollback guide sets out. If that changes, or if you've found a working downgrade path for this firmware line, let us know.