MyRobotDoc
known-issue
LUBA mini 2 AWD: LiDAR fails to initialize during mapping
- Models covered
- LUBA mini 2 AWD (1500/1500H)
- Last updated
- 3 September 2026
This page documents a known issue, not a rollback target — Mammotion has acknowledged it directly rather than owners needing to work around it via a version change.
What happened
LiDAR fails to initialize during mapping attempts on LUBA mini 2 AWD1. Mammotion describes it as a "temporary batch problem" caused by firmware, and noted it as a high-priority fix internally.
Status
Reported as partially resolved by a later firmware release, though some affected owners needed direct remote support from Mammotion rather than the fix alone resolving it. Firmware version, both broken and fixed, is unknown.
Mammotion's KB2 shows
2.3.25.19 (17 June 2026) as the closest release published before this report's date (25 June 2026), and 2.3.27.20 (14 July 2026) as the closest one after — either could plausibly be the "broken" or "fixed" build the report describes, but the thread doesn't name a version, so neither is confirmed.
If you hit this and can confirm the exact firmware versions involved (broken and fixed), let us know so this page can carry real version numbers.
Advertisement