MyRobotDoc
known-issue
LUBA 2 AWD X: mower gets stuck / fails to return to dock on recent firmware
- Models covered
- LUBA 2 AWD X (3000X/3000HX, 5000X/5000HX, 10000X/10000HX)
- Last updated
- 3 September 2026
1.30.29.8 (31 July 2026) — a full month earlier, and the only official candidate for "latest firmware" at the time. We can't confirm the mower in the report was actually on that build, so we're naming it as the likely candidate, not a confirmed match.
What happened
An in-app event log (31 August 2026) on a LUBA 2 AWD X shows repeated errors: "Failed to return to the charging station (1200)," "Robot is lifted or tilted (1030)," and "Robot is stuck in complex terrain (1032)," across multiple sessions over two days1 — firmware version unknown.
The same pattern shows up repeatedly in replies: the mower driving into a no-go zone and getting physically stuck against a tree, and the same behavior "WITH a lidar sensor on the latest firmware." Part of this may be a hardware limitation rather than a pure software regression — the bumper bar's distance from the wheel, combined with single-direction LiDAR that doesn't cover the sides — worth ruling out before assuming a firmware rollback alone would fix it.
Why we're not giving a specific rollback target here
No exact firmware version is confirmed in the source thread, so this page can't responsibly point at a specific "roll back from X to Y." If you can confirm your exact firmware version (and, ideally, whether a specific prior version was better), that's genuinely useful — let us know so this page can carry real version numbers instead of a general description.