Tips & fixes that work across models

Battery & charging

Charging repeatedly fails to start, or drops mid-charge with an audible reconnect loop. Before assuming a defective charger, brick, or dock: this can be an intentional thermal-protection cutoff triggered by hot weather. One owner replaced two charging bricks and the dock itself before Mammotion support confirmed the mowers have a thermal charge-protection feature³. Try charging during a cooler part of the day first. Reported on LUBA 2 3000 (5 September 2026); likely applies to any model sharing the same charging hardware/firmware generation.

Charging plateaus at a fixed low percentage (e.g. 45%) and won't climb further. Repeatedly driving the mower off and back onto the dock can nurse the charge up incrementally as a temporary measure while a power-supply replacement is arranged⁴. Single-source, unconfirmed elsewhere (5 September 2026) — likely points to a failing power supply rather than a fixable condition.

Mower dies mid-lawn instead of returning to charge. The return-to-charge battery threshold is a fixed ~14–15% and is not user-configurable. On larger lawns or longer tasks this can leave too little margin to actually make it back to the dock. Two independent owners report this exact failure mode⁵. Until Mammotion offers a configurable threshold, plan task/zone sizes conservatively rather than assuming a fault. Confirmed on original LUBA 2 (2024); likely a firmware-wide limitation, not model-specific.

"Lifetime free" iNavi/4G service shows as "expired" in the app. One owner's advertised lifetime-free connectivity showed as expired in the app UI; Mammotion support initially denied this was covered, then confirmed by email that it was in fact still active⁶. If you see an expired notice on a plan advertised as lifetime, push back with support rather than assuming you need to pay. Single-source — worth corroborating before treating as a general rule.

RTK & positioning

"Single" positioning or "NetRTK disconnected" despite full wifi/4G signal. This can be a local sky-view/GNSS obstruction rather than a connectivity or hardware fault. One owner fixed it instantly by manually repositioning the mower to a spot with a clearer view of open sky⁸. This is a different symptom from the "RTK unit shows green but still disconnects mid-task" issue covered in the dedicated LUBA 2 RTK guide — check which one actually matches before trying a fix. Reported on LUBA mini AWD LiDAR 1500 (single source); likely generalizes to any NetRTK/iNavi-equipped model.

Moving an RTK base station to a new location. If you relocate an RTK reference station — for example from an in-ground mount to a house-wall mount — you must remap the lawn from scratch. The mower can't reuse old maps against a repositioned RTK reference point⁹. Confirmed directly, general RTK-equipped models (5 September 2026).

Obstacle detection & mapping

Mower suddenly refuses to pass through a channel or narrow path it used to handle fine. Check whether a nearby bush or plant has grown new leaves since the path last worked — obstacle detection can start flagging seasonal foliage growth as a blockage partway through the season. Temporarily disabling obstacle detection for that specific path is a reported workaround¹⁰. Reported on LUBA mini 2 AWD 1000 (single source, 5 September 2026); mechanistically plausible for any camera/LiDAR obstacle-detection model. This is the opposite failure mode from obstacle detection missing a real obstacle — see the camera-avoidance-miss guides elsewhere on this site for that.

Mower reports "stuck" at a perimeter in high grass. Manually commanding a return-to-dock, then resuming the task, has self-resolved this without any other intervention for at least one owner¹¹. Reported on LUBA 3 and LUBA mini AWD by the same owner (single source) — worth trying before assuming a hardware or mapping problem.

Blade & deck maintenance

Extending blade life on dual-disk models. A LUBA 1 owner's 4-year rotation pattern¹: install new blades on both disks; at the next scheduled change, swap the left and right disks with each other (uses the unworn edge without removing anything); at the following change, remove the blades and flip each one to its other edge; at the next change, swap disks again; repeat. Always remove the cutting disks before removing or installing blades — pushing down on blade screws while the disk is still attached to the mower risks bending or loosening the motor shaft. If reusing screws rather than fitting new ones, use blue or purple threadlocker — bare screws have been reported backing out and losing blades entirely. Also check for an in-app Blade Replacement Reminder (Device Information → Maintenance) if your model has one — not available on LUBA 1 per the reporting owner.

Grass trapped under the arm skid guards. Don't remove these guards without a replacement retaining part — two independent experienced owners note the guards also keep water out of the mower's internals, not just prevent grass trapping². Look for a 3D-printable retainer part that holds the rubber boots in place if grass trapping is the problem, rather than removing the guards outright. Reported on LUBA 2; likely applies to the broader LUBA 2/3 family sharing similar arm hardware. (This is a different location from grass caught under the blade deck/spindle itself — see the mechanical-causes checklist for that.)

Persistent groaning noise from a cutting motor. Unconfirmed — one commenter attributes this to low-quality motor bearings (dust shields instead of proper sealed bearings) and claims they're straightforward for an owner to replace directly¹², but no one in that thread reports having actually completed and confirmed the repair. Worth investigating if you're hearing this noise, but don't treat it as an established fix yet.

Update strategy

Deliberately not updating. You can decline a pending firmware update indefinitely to stay on a known-good version rather than accepting every release. Two independent owners report doing this successfully for months with zero regressions, even on demanding terrain (steep slopes, multiple zones)¹³. The tradeoff: Mammotion's cloud-server dependency means an old version could eventually be forced to update for app-store or backend compliance reasons, so this isn't guaranteed to work forever. See app vs. firmware vs. RTK, explained if you're unsure what "not updating" actually controls.

Support process

Support defaulting to "it's your RTK signal." Several owners with independently verified strong signal report this as Mammotion support's default, somewhat dismissive first answer to "the mower is missing coverage / losing position" complaints⁷. If you've already confirmed strong signal, ask for escalation or a log-based investigation rather than accepting that explanation at face value. Anecdotal pattern from owner reports, not a confirmed company policy — stated as a heads-up, not a fact about how Mammotion support operates generally.