News
LUBA 2 / LUBA 2 AWD X: the version history Mammotion's own knowledge base is missing
Mammotion's support knowledge base for both lines still shows 1.30.29.8 as current, while real and official reports put it at least two releases further ahead.
- Models
- LUBA 2 & LUBA 2 AWD X
- First reported
- 21 Aug 2026
- Last updated
- 24 Oct 2026
- Affects
- Robot body — not the app
LUBA 2 & LUBA 2 AWD XFirst reported 21 Aug 2026Details
- Models
- LUBA 2 & LUBA 2 AWD X
- First reported
- 21 Aug 2026
- Last updated
- 24 Oct 2026
- Affects
- Robot body — not the app
What to do next
-
Do not treat Mammotion's knowledge base as the current version: it still lists 1.30.29.8 (July 31, 2026) for both lines, while Mammotion's own announcements put them at 1.30.29.24 (August 22), 1.30.29.26 (September 4) and 1.30.31.19 (announced September 27, rolling out in phases).
More about this step
Applies when: you are checking what the newest release is for a LUBA 2 or a LUBA 2 AWD X.
Worked if: you know which number is actually current before deciding whether to update.
Didn't work? Next: step 2 — Read the perimeter and blade-stop guide rather than the version...
Method: the two knowledge-base pages, set against Mammotion's own three announcement posts
-
Read the perimeter and blade-stop guide rather than the version numbers here. It covers the substance of the two unpublished releases: the perimeter/boundary-crossing fix announced twice, and the blade-stop item.
More about this step
Applies when: you are deciding whether to update, or troubleshooting something those releases touched.
Worked if: you know what the missing releases contain, not only that they exist.
Didn't work? Next: step 3 — Tell us if the knowledge base has caught up since July 31. Also...
Method: this page's own pointer to the regression guide
-
Tell us if the knowledge base has caught up since July 31. Also tell us if a release after 1.30.31.19 exists that this page has not logged.
More about this step
Applies when: you have a newer version, or a catch-up entry, in front of you.
Worked if: the page tracks the real version line rather than the published one.
Method: this page's own closing request
Robot body — not the app. See our app vs. firmware vs. RTK guide if you're not sure which one you're dealing with.
On this page
The gap
Mammotion's own support knowledge base lists 1.30.29.8 (July 31, 2026) as the most recent published release for both LUBA 2 and LUBA 2 AWD X1, 2: identical changelog text on both pages (rear-wheel-lift detection, BeiDou baseband tuning, dandelion-tolerant obstacle detection, proactive blade shut-off on wheel lift, memory-usage optimization).
What actually happened since then
Mammotion announced a boundary/blade-stop fix on August 21, applicable to this line among others3. A screenshot in the later hotfix thread shows this shipped as version 1.30.29.24, dated August 22, 2026. A second, "Hotfix Firmware Update" post two weeks later confirmed 1.30.29.26 as current for LUBA 2, LUBA 2X, YUKA, LUBA mini Series & YUKA mini Series on September 44.
That gives a version progression of 1.30.29.8 → 1.30.29.24 → 1.30.29.26: two releases the official knowledge base has never published, over five weeks behind as of this writing. Both 1.30.29.24 and 1.30.29.26 are confirmed from Mammotion's own official posts, just never carried over to the release-notes knowledge base pages.
Since then: 1.30.31.19
On September 27 Mammotion announced 1.30.31.19 for LUBA 2, LUBA 2X, YUKA, LUBA mini Series and YUKA mini Series5. Its own list of changes: remote control from anywhere in the FPV view, to recover the mower after an unexpected stop without being on site; zigzag paths that cover closer to the edges, reducing redundant boundary laps and missed spots; and improved detection stability for some obstacles. It needs the Mammotion app at iOS 2.3.25.1 or Android 2.3.20 (30) before the update appears on the mower, and it is being rolled out gradually, so not every mower will show it yet5. In the same thread a Mammotion staff account told an owner that the multi-point turn "has been back", and another owner replied that their LUBA 2X still makes tank turns on perimeters and in other areas5.
What owners report on it. A LUBA 2 3000H owner installed 1.30.31.19 in mid-October. About an hour later the mower stopped in open lawn with its battery apparently drained, with none of its usual low-battery warnings, and it would not charge on the dock. The owner first advised others to hold off, then updated the post: other owners had updated without trouble, so the owner asked readers to disregard the caution. The mower came back after the dock's power supply and the mower's security key were left out overnight, and the owner later saw it warn at 25% battery and return to charge at 15% as normal, so the timing looks like a coincidence6. A Mammotion account had offered to look at the device further before it recovered6. In the same thread a second owner says their battery also died after a recent update, without naming the version. Several others say 1.30.31.19 works fine for them, one of them across six mowers of different models, and one says theirs does after restarting the mower and the RTK station6.
More owner reports. A separate thread of about 50 replies, started on October 12 when the version appeared, adds more. A few owners who installed it call it the best version so far or say it works well. A LUBA mini AWD owner of long standing says it fixes many of the regressions that had built up over the updates, that the small multi-point turns no longer damage the grass, and that it starts mowing close to where it enters the area. The same owner says the mower still bumps a retaining wall at the perimeter, stops the blades and moves about 1.5 m before restarting, which leaves uncut patches along the edge, and that this is no better than before7. A LUBA owner on 4G says it ploughs the lawn far less but still makes tank turns in narrow places; a Mammotion account answered that in narrow areas the mower may make small multi-point moves that can look like turning on the spot, and asked for photos7. A YUKA mini 600 owner reports remote steering over WiFi and a better zigzag and border pattern7.
A perimeter before-and-after. A LUBA 2 AWD 3000HX owner timed the same 5,554 sq ft lawn: on the old firmware, two perimeter laps took 4 h 40 min and left strips; three laps took 5 h 04 min and cut clean; on 1.30.31.19, two laps took 4 h 53 min and cut clean. They conclude Mammotion appears to have fixed the perimeter gap8. It is one owner on one lawn, and another owner in that thread, also on the latest firmware, still sees missed parts and full turns on the spot after a remap9. A YUKA 2000 owner says the update immediately deleted one of their two mapped channels, which worked again once they redrew it; they do not name the version10.
On the new remote control, the thread's starter installed the update and says it works for rescuing the mower from outside the mowing area, but tested that it cannot drive in reverse. Two others call that a serious limit; one explains that a mower stuck in a hole or against a hedge can usually only get out by backing up. One owner says remote control is very slow even when standing next to the mower7. A Mammotion account said the version is rolling out gradually in batches, and two owners on 1.30.29.26 said it had not been offered to them yet7.
That makes the progression 1.30.29.8 → 1.30.29.24 → 1.30.29.26 → 1.30.31.19. As of October 20, the knowledge base for both lines still stops at the 1.30.29.8 entry of July 31, so none of the three later releases appear there.
Sources
- S1 Mammotion support knowledge base: LUBA 2 release notes (most recent entry: 1.30.29.8, 31 Jul 2026)
- S2 Mammotion support knowledge base: LUBA 2 AWD X release notes (same 1.30.29.8 entry, 31 Jul 2026)
- S3 Reddit r/MammotionTechnology: "Recent Firmware Update" (official Mammotion post, 21 Aug 2026)
- S4 Reddit r/MammotionTechnology: "Hotfix Firmware Update" (official Mammotion post, 4 Sep 2026)
- S5 Reddit r/MammotionTechnology: "Latest Firmware Update" (official Mammotion post, 27 Sep 2026)
- S6 Reddit r/MammotionTechnology: a LUBA 2 that died an hour after 1.30.31.19, then recovered, and owners saying the update works
- S7 Reddit r/MammotionTechnology: owners on 1.30.31.19, mostly better cutting, remote control with no reverse, the edge blade pause still there
- S8 Reddit r/MammotionTechnology: a LUBA 2 AWD 3000HX owner on 1.30.31.19 who says two perimeter laps now cut clean
- S9 Reddit r/MammotionTechnology: an owner on the latest firmware whose mower still misses parts and spins on the spot
- S10 Reddit r/MammotionTechnology: a YUKA 2000 owner whose update deleted one of two channels
Did this work, or not?
Telling us what happened helps the next owner with the same fault.
Tell us what happenedFixed it? Share with other owners.
Post directly to Reddit or use link in text, email, Facebook, etc.