LUBA 3: the app's battery 'max capacity' reads low within months, some after a firmware update

What owners report

• A LUBA 3 3000 reads 86% max capacity after four months, mowing two or three times a week for about four hours, with two charges a session¹.
• Other owners in that thread read 81% after 64 cycles and under three months, 88% after one month, 87% on a mower bought in June, and 88% on one bought in May¹. A 5000X owner reads 89%¹. One LUBA 3 AWD 3000, half a year old, reads 80%, and its owner reports a one-point loss in a single day¹.
• A LUBA 3 AWD bought in June read 63% in the app after the latest firmware update, and its owner says it now barely finishes tasks it used to complete with more than half its charge left. It came back to the dock with under 10% left³.
• A second owner there reads 92% after 22 cycles. A third updated to 2.3.31.69 and posted on 24 October that they see the same thing afterwards³.
• Not every mower reads low. A LUBA 3 AWD 3000, five months old with 191 cycles, still reads 100%¹. In the second thread, two LUBA 3 owners also read 100%, one at 85 cycles and one at almost 90. The first has been on 2.3.31.69 since 17 October³.

What Mammotion support is reported to have said

Two owners say support gave them the same answer. In September an owner wrote that Mammotion support confirmed a battery-calibration fault: after a firmware update, the saved data about the battery's state can be lost. According to that owner, support said the fault is fixed and the fix comes with the next firmware, which was not yet released on 24 September. After that firmware, the owner was told, switch the charge limit off one last time and charge to 100% once; the step should not be needed again². In October another owner wrote that support told them the problem is on the software side and will be fixed with the next firmware update³.

Those two are owners' accounts of what support said. In the second thread a Mammotion account (Mammotion-Luna) answered in its own words on 24 October: the technical team is aware, it is "an incorrect display bug in the app", and the display error is to be fixed in an upcoming firmware update, after which the value shown should return to normal³. That is a Mammotion statement, but it names no firmware version or date, and the owner's run-time complaint is not addressed in it. A Mammotion account in the first thread asked only for the device number, the device logs uploaded through the app, and a screenshot of the battery capacity¹.

What is not known

• Whether the figure is a measured loss of battery or only a wrong display. A Mammotion account calls it a display bug³, and support's wording as the owners relay it is about stored data being lost after a firmware update; no source gives a measured result.
• Which firmware first showed it. Owners report it across several versions², and one saw it again on 2.3.31.69³.
• Whether a low figure shortens your runs. The 63% owner says it does³; the others only report the number.

Not the same as a mower that shuts off with battery left

A mower that switches itself off or stops with charge showing is a different report, on its own page. A charge that stops part-way on the dock is on another.