LUBA 3 / LUBA mini 2 / YUKA mini 2: the version history Mammotion's own knowledge base is missing

The gap

Mammotion's own support knowledge base for LUBA 3 lists 2.3.27.23 (July 18, 2026) as its most recent published release¹, the same gap already documented on the LUBA 2 / YUKA / mini-series side of the product line.

What has happened since then

A LUBA 3 3000 owner installed 2.3.30.21 on August 13, 2026, and read out Mammotion's own in-app changelog on camera⁴: an earlier, previously undocumented release the knowledge base has never listed either. Per that changelog: a basic mode for AI obstacle detection, a "real view map" (built from the mower's own camera data once it completes a task, rather than a hand-drawn boundary), a travel-speed setting for non-mowing transit, auto-reverse mowing direction to reduce grass matting, configurable rain-protection behavior (smart mode plus customizable resumption delays). It also lists support for resuming an unfinished task from the task report, optimized blade on/off logic, a fix for the robot moving outside the boundary due to wheel slipping during self-recovery, enhanced positioning accuracy, better detection of small animals/tall grass/backlit scenes, and an optimized turnaround mode for certain models. The same owner reports that installing this firmware alongside the required app update restored multi-point turning in place of the mower's prior "tank turn" in-place spin. See the tank-turn guide for the parallel LUBA 2/YUKA-line story.

Around 2026-08-29, a separate device was running 2.3.27.23 with "2.3.30.26 up next" per the Mammotion app², a dated report of a further intermediate release the knowledge base has never listed. Mammotion confirmed 2.3.30.35 as current for LUBA 3, LUBA mini 2 Series, and YUKA mini 2 Series on September 4³.

That gives a version progression of 2.3.27.23 → 2.3.30.21 → 2.3.30.26 → 2.3.30.35: at least three releases the official knowledge base has never published. 2.3.30.21 is confirmed by direct owner installation and an on-camera read of the in-app changelog, but is still a single report; 2.3.30.26 is known only from a single, unconfirmed app-screenshot report rather than an official announcement. 2.3.27.23 and 2.3.30.35 are both confirmed from official sources.

Since then: 2.3.30.39 and 2.3.31.69

The ladder has moved on twice since this page was written. 2.3.30.39 followed, and has its own page. Then on September 27 Mammotion announced 2.3.31.69 for LUBA 3, LUBA mini 2 Series and YUKA mini 2 Series⁵. 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. Also listed: a fix for charging that occasionally failed to reach the set battery level; faster LiDAR-based obstacle avoidance on the LUBA 3, LUBA mini 2 LiDAR and YUKA mini 2 LiDAR models; better obstacle detection in glare and shadow; and improved positioning and navigation stability. 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⁵.

An owner who tested the remote driving on a LUBA with 2.3.31.69 reported on October 4 that it works over 4G, with a live camera view, in daylight and in the dark, and called it good for a first release, with a few bugs⁶. The poster confirmed in the thread that the remote control cannot drive in reverse. A LUBA mini owner who received it on October 17 says the app warned that it works only in mapped areas, and wonders whether that helps a mower that has slid out of bounds on a hill⁶.

An owner who updated hoping for the remote driving could not find it. Another owner answered that tapping the camera shows the controls, and a Mammotion staff account on 17 October said the same: tap the camera icon in the app to enter the FPV view, and the mower can be controlled there⁸. The first owner had also lost the mower's location after the update, and the mower crawled. He then drove it straight for 30 feet by remote control and wrote that positioning worked again⁹. The staff account's own answer to the lost location was to check the network connection and move the mower to an open area, and to send a feedback log with the device name and signal screenshots if it persists⁸. A second LUBA 3 owner on the same update described the mower moving at normal speed for a couple of seconds and then crawling for the whole task. That is a single report with no cause found, so it is not a finding.

Not every old complaint is gone. A LUBA 3 1500 owner wrote on October 17 that the mower still leaves strips unmowed beside no-go zones. It happens less on 2.3.30.39 and again on 2.3.31.69, but still happens. Part of the cause, in that owner's view: when the mower meets anything that might be an obstacle, such as an unusually tall blade of grass, it stops cutting, drives on about half a metre to a metre before it starts again, and never comes back for the gap⁷.

Owner reports that name 2.3.31.69 are on these pages, each with its own sources. Naming the version does not mean the update caused the problem:

• LUBA 3 AWD: front bumper repeatedly triggering (error 1207)
• Error 1425 (vision module fault)
• LUBA 3: the app's battery max capacity reads low
• LUBA 3: turns tear up the lawn
• LUBA 3: cutting discs spin the other way
• Charging stops part-way, where the release note's charging fix is covered

As of October 20, the knowledge base for the LUBA 3 still stops at the 2.3.27.23 entry of July 18, so none of the later releases appear there.