MyRobotDoc
Independent guides for robot mower owners
Not affiliated with or endorsed by any device manufacturer. All trademarks belong to their respective owners.
When an update breaks something that used to work, you shouldn't need a developer account to undo it. Step-by-step, verified guides for reverting robot mower firmware, plus release history and real owner-reported outcomes per version. Launching with Mammotion as the first fully-documented brand.
Browse mowersLUBA 2 and LUBA 2X drive into obstacles like lawn furniture even with obstacle-avoidance sensitivity set to sensitive — a recurring, corroborated issue present since launch, not tied to any specific update.
5 September 2026 MORE →
A LUBA 2 returned to its charger, shut off, and stopped responding to the power button entirely, two weeks after a firmware update.
5 September 2026 MORE →
LUBA 2 loses RTK connection mid-mow with the RTK station's own light showing normal — a corroborated report, plus the full power-cycle/remap-restore sequence that fixed it.
5 September 2026 MORE →
The first version-history entry on this site for this model — compiled straight from Mammotion's own per-model release-notes hub.
1.17.0.43125 September 2026 MORE →
A version-by-version changelog for the Mammotion companion app on Android, compiled from third-party APK mirrors — not the mower's own firmware.
5 September 2026 MORE →
Real, dated issue-and-fix reports from owners, organized by symptom rather than by model or firmware version — newest evidence first within each issue.
5 September 2026 MORE →
A plain-language guide to the three separate things that update independently on a Mammotion mower — the phone app, the mower's own firmware, and the RTK station's firmware — and why mixing them up leads to the wrong fix.
4 September 2026 MORE →
A checklist of physical, mechanical, and setup issues that produce symptoms commonly mistaken for firmware bugs — cheaper and faster to rule out than a rollback, and sometimes the actual fix.
4 September 2026 MORE →