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

What Mammotion announced on 21 August

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 22 August 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.

What Mammotion announced two weeks later, on 4 September

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 21 August):

• 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.

What owners are reporting since the 4 September 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 cutting, driving around outside of cutting 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 4 September 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 an update prior to 1.30.29.24 — both before the 4 September 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 mini 2 AWD 800 on default settings produced one of the highest-engagement reports on this topic (80 reactions, 56 comments): roughly 1-foot waves in the mow lines and a 2-inch uncut strip about 4 feet long after each modified tank turn, bad enough to require mowing twice at different angles for full coverage — working well "three months ago"⁶. Switching the turn pattern to zero-turn fixed the wavy-line symptom for one commenter; another reported the opposite experience (no wave issue, multi-point turning "back again") — consistent with a gradual, uneven rollout rather than a uniform fix or a uniform break.

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.

Separately, a LUBA 3 3000 had boundary/perimeter misses starting "since the last update this week" — posted in the same window as the 4 September 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

An unusually rigorous, measured account of a LUBA 2 AWD 5000X running 1.30.29.24 on a real 65m² test plot¹: 43 minutes 52 seconds to finish the task, an effective rate of 89 m²/hr, 453m driven to cut 65m² ("1.7x more driving than a clean back-and-forth," per the report), 51.7% of total time spent turning, 429 direction changes, and 52 of 53 turns done 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 adds a data point on the turning-quality symptom cluster from a different product line: a YUKA mini 2 1000 LiDAR repeatedly drove into a wooden structure and went out of bounds multiple times in one session, needing an emergency stop each time² — firmware version unknown, though one reply generalized the cause as "the .30 firmware" 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 described above from other owners and product lines.

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

One Facebook report is a useful caution here. A LUBA 3 had symptoms that read exactly like this guide's topic — losing the ability to navigate around an obstacle it had handled fine two weeks earlier, plus a new "25-point turn" pattern at each end of the yard (the same kind of excessive multi-point turning described elsewhere in this guide)⁹. The actual cause: a cutting disc had come loose and unscrewed itself, sitting in the lawn, with a second disc also partially unscrewed. Physically unbalanced or partially-attached blade discs can produce navigation and turning symptoms that look identical to a firmware regression. See our mechanical-causes checklist for this and other 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 KB is behind on both product lines covered here. LUBA 2 AWD X's page still lists 1.30.29.8 (31 July 2026) as its most recent entry¹¹ — 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 (18 July 2026)¹² — meaning 2.3.30.35 (the LUBA 3 hotfix from this same 4 September 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 21 August thread, Mammotion was directly asked "will Mammotion ever provide a way for us to BACK OUT of a bad firmware update?" (12 upvotes)³ — no response to that specific question is visible in the thread. If that changes, or if you've found a working downgrade path for this firmware line, let us know.