My Robot Doc

Known issue

LUBA mini 2 (1500 LiDAR): firmware 1.30.25.16, NetRTK disconnected and stuck in Single positioning

The mower gets stuck on Single positioning mode with NetRTK disconnected, despite full WiFi and 4G signal.

Status Open

Models
LUBA mini 2 AWD (1500 LiDAR)
First reported
30 Aug 2026
Last updated
03 Sep 2026
Affects
RTK station — not the app or robot body
Rolling back from
1.30.25.16
LUBA mini 2 AWD (1500 LiDAR)First reported 30 Aug 2026Details
Models
LUBA mini 2 AWD (1500 LiDAR)
First reported
30 Aug 2026
Last updated
03 Sep 2026
Affects
RTK station — not the app or robot body
Rolling back from
1.30.25.16

What to do next

  1. Write down both numbers your setup reports: the mower's firmware and the companion app version. The report this page is built on lists 1.30.25.16 and app 2.3.12.11, while Mammotion's own notes for this model list only 2.3.x firmware strings, so which number is which is still unresolved.

    More about this step

    Applies when: the mower sits on Single positioning with NetRTK disconnected, while WiFi and 4G both show full signal.

    Worked if: you know exactly what you are running, which is the detail that settles this page's open question.

    Didn't work? Next: step 2 — Rule out the physical side before calling it firmware: check the...

    Method: this page's own version-discrepancy note

  2. Rule out the physical side before calling it firmware: check the RTK antenna's view of open sky and its mounting, since Signal Quality showing None with full WiFi and 4G is not a connectivity problem at the mower's end.

    Stop and get help if

    the station's position in the app no longer matches reality. Report that before moving anything physical, because telling the app a station has moved clears every saved map.

    More about this step

    Applies when: signal quality reads None despite good connectivity, or the app's station position looks wrong.

    Worked if: an obstructed or flexing antenna is ruled in or out, which firmware cannot fix either way.

    Didn't work? Next: step 3 — Take Mammotion's in-thread recommendation: update the app and...

    Method: this page's confirmed details, plus the RTK placement guide's map-wipe warning

  3. Take Mammotion's in-thread recommendation: update the app and the firmware, or ask support if no update is offered, and tell us which path it took.

    More about this step

    Applies when: the physical checks changed nothing.

    Worked if: the case is moving, and the model and version questions get an answer instead of another assumption.

    Method: the Mammotion representative's in-thread recommendation, and this page's own open questions

RTK station — not the app or robot body. See our app vs. firmware vs. RTK guide if you're not sure which one you're dealing with.

On this page
  1. What to do next
  2. What happened
  3. Related context
  4. Rollback procedure
  5. Sources
Before you start: confirm your mower's current firmware version and note it down. If this rollback doesn't go as planned, you'll want that number to ask for help.

What happened

A LUBA mini 2 (1500 LiDAR variant) got stuck in "Single" positioning mode, refusing to mow1. All mapped lawn channels had disappeared even though the lawns themselves were still defined, and the charging station shown in the app no longer matched its real position. Confirmed details:

  • Positioning Status: Single
  • RTK / iNavi Signal Quality: None (L1 0 | L2 0)
  • Mower firmware: 1.30.25.16
  • Companion app version: 2.3.12.11
  • Both WiFi and 4G showing full signal (3/3 bars), not a connectivity problem on the mower's end
  • A power-cycle (holding the power button until "powering off," then back on after 10-15 seconds) did not resolve it

A separate LUBA mini 2 AWD deliberately never updated away from the out-of-box firmware (2.3.27.0), specifically citing "the horrible recent updates" as the reason, with zero issues after several weeks of use2. That's not proof this specific NetRTK issue is tied to 1.30.25.16, but it's a real, dated data point that some owners on this model line are avoiding updates altogether right now.

Rollback procedure

There is no procedure here to follow. This is body firmware, and no confirmed manual downgrade path exists. The Android rollback guide covers what is actually possible today.

Prior known-good version not confirmed. No firmware version is confirmed yet as "the one before 1.30.25.16" for this model. No confirmed manual downgrade path exists for the mower's own body firmware regardless. See the Android guide.
Version string does not match Mammotion's own release notes. Mammotion's knowledge base3 for this exact model (LUBA mini 2, 1500 LiDAR) lists only 2.3.x-series firmware, including a 2.3.25.16 release dated June 10, 2026, the same last two segments as the reported 1.30.25.16, but a different major/minor version. We can't confirm whether the original report mixed up firmware and companion-app version numbers (the same report separately lists companion app version 2.3.12.11) or whether 1.30.25.16 is accurate and simply unpublished. Stating this discrepancy rather than assuming either is correct.
Model attribution also uncertain, added September 5, 2026. The original report's own thread title says "Luba mini AWD LiDAR 1500": Mammotion's original LUBA mini AWD LiDAR line, a physically different product from the LUBA mini 2 AWD (1500 LiDAR) this page is filed under. This page assumed "mini 2" when the guide was first written; that assumption is unconfirmed, not verified against the source. Combined with the version-string mismatch above, treat this page's model attribution as its own open question, not a settled fact. If you own either model and hit this symptom, the details here may still be relevant, but don't assume the model tag is correct.

Sources

Did this work, or not?

Telling us what happened helps the next owner with the same fault.

Tell us what happened

Fixed it? Share with other owners.

Post directly to Reddit or use link in text, email, Facebook, etc.

Reddit