Issues we're watching

LUBA 3

Mower stopped connecting after updating to firmware 2.3.23.12. Neither WiFi nor Bluetooth would reconnect after the update completed; Mammotion support was engaged but unable to resolve it¹. Watching for a second independent report of connectivity loss tied specifically to a firmware update.

Cutting height displayed as 1 inch instead of the real ~2.2 inch minimum, after an update. ² A reply in the same thread describes this as already fixed by Mammotion (clear the app from the background, then restart it) and notes that the S and H variants have different height ranges, which can look like the same bug — but that reply is a secondhand paraphrase of a Mammotion statement made elsewhere, not something we've read directly from Mammotion's own account yet. Watching for the original Mammotion reply, or a second independent report.

Front bumper detached during initial setup, breaking the wiring underneath. The bumper appeared to click into place while mapping the yard for the first time; continuing to press it in, as the assembly instructions suggested, broke it loose and severed the wiring behind it³. Reported once.

Mower powers itself off after completing a scheduled mow, and won't start its next scheduled job without manual intervention. ⁴ Mammotion asked for further diagnostic detail in the same thread; no public resolution was visible as of capture. Reported once.

Forced update to firmware 2.3.25.16 blocks all app actions until installed. The app refuses any action — stating the robot firmware and app version don't match — until the mower updates, with release notes reported as identical to the prior version⁵. A similar forced-update lockout has separately been reported on LUBA 2 (see Tips & fixes that work across models). Watching for enough independent LUBA 3 reports of this exact behavior to treat it as a confirmed cross-model pattern.

General navigation and reliability complaints, without a specific symptom or firmware version. ⁶ Replies to this report were mixed — other owners of the same model described it working reliably. Too vague as captured to treat as one issue; the full comment thread hasn't been read past the first few replies and may contain a more specific, corroborated pattern.

YUKA mini

Two units, two different failure modes, both blamed on a firmware update in spring/summer 2026 — no specific version named. Both mowers had worked reliably for over a year (bought roughly a year apart) with no hardware or setup changes; the owner reports the only thing that changed was software updates. One unit starts a mowing job, returns to the charging station as expected, then never resumes the task. The other leaves its mapped mowing area without an apparent cause, inconsistently rather than at a fixed spot⁸. Repeated diagnostic-log submissions to Mammotion support reportedly drew only generic "update to the latest version" replies. Watching for a second independent report of either specific symptom — a general "updates broke it" comment in the same thread wasn't specific enough to count as corroboration.

LUBA 1000H

Six-point critique from a single detailed owner review: the advertised coverage area far exceeded what the battery could actually mow in one charge cycle; a simple back-and-forth mowing pattern left visible missed spots; the mower repeatedly declared a zone "done" partway through the job; there was no way to set a minimum charge level before the mower left the dock to resume work; frequent navigation confusion drained the battery and required manually retrieving the mower; and the app's reported battery level didn't match the mower's actual remaining charge⁷. Reported once, from 2024 — watching for independent corroboration on any of these points. Firmware and software have very likely changed since this report; treat it as historical unless someone reports the same thing recently.