MyRobotDoc

Independent guides for robot mower owners

Not affiliated with or endorsed by any device manufacturer. All trademarks belong to their respective owners.

← All guides

known-issue

LUBA 2: RTK connection lost mid-task even though the RTK unit shows green

Models covered
LUBA 2
Last updated
5 September 2026
Exact firmware version not confirmed. Neither report states a version string. Documenting the symptom and workaround as reported, not attributing it to a specific firmware release.
Neither source gives even an approximate firmware-update timeframe (only "the day before" relative to each other), so there's nothing to check against Mammotion's official release notes here — an official-source match would be a guess, not a confirmation.

What happened

LUBA 2 5000 stopped mid-task after losing its RTK connection, despite the RTK reference station's own light showing a normal green status, not an error state. Rebooting both the mower and the RTK unit twice did not resolve it1.

The identical symptom was reported the day before, with a workaround that resolved it: a full power-down of both units, removing the mower's key, removing the mower's "head" (top cover/sensor module), waiting 30 minutes, reassembling, and restoring the map from a backup2.

Why this is worth documenting even without a version number

Two independent, dated reports of the same symptom — RTK connection lost mid-task with no error indication on the RTK unit itself — plus a specific, repeatable workaround from one of them, is a useful known-issue entry even without a firmware version to attribute it to. If you're hitting this, a simple reboot may not be enough; the full power-cycle-and-remap sequence above is the only reported fix so far.

If you've hit this and a simpler fix worked, or you can confirm which firmware version was involved, let us know.
Advertisement