Tips & fixes that work across models

Charging and docking, and blade and deck maintenance, now have their own pages: charging and docking fixes and blade and deck maintenance.

How the counts work. Each tip shows how many owners it comes from. One report is worth trying with care; two or more is a pattern. Where the reports agree only in part, that is stated rather than rounded up.

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². One owner's report, not yet confirmed by another (LUBA mini AWD LiDAR 1500); likely generalizes to any NetRTK/iNavi-equipped model.

Moving an RTK base station to a new location. Telling the app the RTK station has moved triggers an immediate warning that all saved maps will be cleared, with no option to preserve them¹⁴, so plan for a remap rather than expecting to keep your zones. See the dedicated RTK placement guide for the full test this came from. Whether a relocation always forces a remap is disputed in the German forum (some owners report it does, others say no), but the app's own warning is what you meet first.

By contrast, moving the charging dock alone doesn't require a remap: just tell the app the dock has moved⁶. A separate owner corroborates this distinction directly: their charging station sits unscrewed against a garage wall and gets nudged occasionally; re-registering it as a "new position" in the app (not a full reset) has been enough, no remap needed¹⁴.

Map the charging dock's approach path explicitly if it's in a garage or similar confined space. One owner's mower would stop short of home and fail to dock because the charging plate sat slightly outside the mapped lawn area. The fix was drawing an explicit path/road connecting the mowing zone to the dock, not just placing the dock inside a zone¹⁴. One owner's report, not yet confirmed by another.

Placing the RTK antenna. It needs as few obstructions as possible around it and roughly a 360° view of open sky above, but it does not need a direct line of sight to the mower itself; the radio link reportedly works over several kilometers⁶. If you're troubleshooting a poor "Float"/"Single" reading, check the antenna's sky view before assuming distance from the mower is the problem. This holds even when a house sits between the RTK station and the mower, and multiple experienced owners corroborate that walls/buildings in between are fine unless the RF path has to cross several solid walls, in which case range drops; roof-mounting the antenna is a common fix for weak signal under trees or cloud cover¹³. One open question, disputed and unconfirmed either way: whether relocating the RTK station forces a full remap of mowing zones: some owners say yes, others say no.

A wobbling or wind-shaken RTK antenna can shift the whole map, not just degrade signal. One owner attributes recurring map drift to their antenna mast flexing in wind. If the antenna itself moves even slightly relative to its mounted position, the mower's whole coordinate reference moves with it¹⁴. Mount the antenna rigidly enough that wind can't flex or rock it, not just anywhere with open sky. One owner's report, not yet confirmed by another.

"Reset RTK station" can silently delete your entire map. One owner tapped this app option after a "station not recognized" message and immediately lost his whole saved map (~3,800 m², 1 acre), with no warning or confirmation first. He believes he confused it with the harmless "charging station was moved" reset, which doesn't delete anything¹⁰. One owner's report, not yet confirmed by another, but the described consequence is severe and irreversible. Back up your map (screenshot the layout, at minimum) before tapping any "reset" option you're not certain about.

Setup & connectivity

Where does a SIM card go on a YUKA mini 2? It doesn't: 4G/cellular connectivity on the YUKA mini 2 series comes from a separate, purchasable "4G Module for YUKA mini 2" accessory (a physical add-on, not a SIM slot built into the mower itself), confirmed directly on Mammotion's own store page⁵. Buying the module reportedly comes bundled with a three-year free 4G service trial⁵. Confirmed via Mammotion's own product page (September 6, 2026); doesn't address whether other model lines (YUKA, YUKA mini, YUKA mini Vision) handle 4G the same way. Check your own model's accessory listings.

Can you swap in your own SIM card? Not on YUKA models released in 2025. Mammotion says it does not support owners replacing the SIM themselves: "At the moment, the 4G module is only compatible with the SIM cards we provide"¹⁵.

Obstacle detection & mapping

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³. One owner's report, not yet confirmed by another (on both LUBA 3 and LUBA mini AWD), worth trying before assuming a hardware or mapping problem.

Multiple mowing zones must overlap or be connected by a path, or navigation between them (including return-to-dock) breaks. If zones are separate, either overlap them slightly or add a connecting "diamond"-shaped path segment linking them¹¹. Community discussion, single thread.

What the three obstacle-avoidance levels actually do. "Off" relies on the bumper only, useful in tall/uneven grass where proactive detection causes false stops; "Standard" proactively avoids obstacles; "Sensitive" also proactively avoids patches that don't look like grass⁷. Per an experienced owner's explanation, not confirmed by Mammotion directly. If your mower is stopping unnecessarily in tall grass, try "Off" first rather than assuming a hardware fault, but be aware it also means the mower won't dodge anything left lying on the lawn.

Individually-marked small obstacles close together cause excessive spinning/turf damage. If no-go zones around several nearby small obstacles (e.g. trees or posts less than about 4m (13 ft) apart) are drawn separately, the mower can end up maneuvering excessively between them. Merging them into one larger no-go zone and mowing that patch manually was suggested as the fix⁸. One owner's report, not yet confirmed by another, but mechanistically consistent with this site's separate tank-turn/turf-damage research.

Mowing patterns & edge handling

Sharp corners get worn from repeated turning. If a corner is narrow enough to force a near-180° turn, the mower will wear that exact spot on every mow. Two things help. Set the path angle to "random" so the mower turns in a different spot each session instead of the same one every time. Then check whether your mower does a "tank turn" (pivoting in place, hard on the lawn) or a forward/backward three-point turn (much gentler) at that spot. If it's tank-turning, a slightly larger manual turn radius plus hand-trimming the corner is the practical fallback¹². The "Rand mähen" (edge-mow) feature is a separate option worth checking for cleaning up any strip the mower's parallel-line pattern leaves unmowed near an odd-shaped boundary. One owner's report, not yet confirmed by another. "Tank turn" is confirmed as real, distinct terminology (German: "Panzerdrehung"), not interchangeable with a three-point turn.

Map 5–10 cm (2–4 in) inside the actual lawn edge, not flush against it, and plan to hand-trim the strip. One owner initially mapped within 2–3 cm (¾–1¼ in) of a discount/border edge, which caused the mower to clip the boundary; remapping the whole lawn 5–10 cm (2–4 in) further in, then trimming the resulting uncut strip with a separate trimmer or riding mower, resolved it¹⁴. Near a ditch or drop-off specifically, the same owner intentionally maps 10–15 cm (4–6 in) outside the true edge so the mower risks going slightly into the buffer rather than into the ditch, accepting the wider uncut strip as the tradeoff. This is a deliberate margin-of-error choice, not a bug. Budget for some manual edge-trimming regardless of how tightly you map. One owner's report, not yet confirmed by another.

Rotating mowing-pattern angle across a multi-day-per-week schedule can clear tufts a single checkerboard pattern misses. One owner, mowing a zone three times a week, runs a different stripe angle each session (diagonal, then straight, then vertical, skipping a day between each) rather than relying on the app's built-in checkerboard coverage mode, which they found slower and unnecessary for their case. The angle rotation reportedly cleared tufts of grass that a single fixed stripe direction kept missing¹⁴. One owner's report, not yet confirmed by another. It's a manual workaround, not an app setting; worth trying if a fixed stripe direction keeps leaving the same tufts uncut.

Update strategy

Don't run a firmware update while the mower is parked on a slope. A restart during or after a firmware update releases the wheel brakes, the same as powering the mower off. One owner had their mower start rolling down a slope right after the restart that follows a firmware update (no damage, but a near miss)⁹. If you can, park somewhere flat before starting a firmware update; if the dock itself is on a slope with weak WiFi (forcing longer update times there), consider temporarily relocating the mower to update. One owner's report, not yet confirmed by another.

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 nothing broken by a firmware update, 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.