My Robot Doc

Known issue

YUKA mini: firmware 1.15.20.2303, NetRTK activation failure

The RTK antenna stops switching modes after this update, despite the changelog claiming improved remote-connection performance.

Status Manufacturer-acknowledged

Models
YUKA mini (500/500H, 600/600H, 800/800H) & YUKA mini Vision (700/700H)
First reported
30 Apr 2026
Last updated
03 Sep 2026
Affects
RTK station — not the app or robot body
Rolling back from
1.15.20.2303
Target version
1.15.6.2300
YUKA mini (500/500H, 600/600H, 800/800H) & YUKA mini Vision (700/700H)First reported 30 Apr 2026Details
Models
YUKA mini (500/500H, 600/600H, 800/800H) & YUKA mini Vision (700/700H)
First reported
30 Apr 2026
Last updated
03 Sep 2026
Affects
RTK station — not the app or robot body
Rolling back from
1.15.20.2303
Target version
1.15.6.2300

What to do next

  1. Note your version. Then check whether the antenna has stopped switching modes and NetRTK activation is failing, as opposed to a general signal problem.

    More about this step

    Applies when: an RTK fix is hard to establish or hold after updating to 1.15.20.2303.

    Worked if: you know whether you match the reported case rather than assuming you do.

    Didn't work? Next: step 2 — Before calling it the firmware, check the antenna's view of open...

    Method: the release thread's owner report on this page

  2. Before calling it the firmware, check the antenna's view of open sky and that its mount is rigid: a station under cover or flexing in wind degrades positioning on any version.

    More about this step

    Applies when: signal quality is poor or the fix is intermittent.

    Worked if: a physical cause is ruled out, which no firmware change would have fixed.

    Didn't work? Next: step 3 — Contact support with your version. The release before this one...

    Method: this site's own RTK placement guide

  3. Contact support with your version. The release before this one is 1.15.6.2300 (March 23, 2026), but no confirmed manual downgrade path exists for body firmware. Tell us too: Mammotion's changelog lists this switching failure as fixed by this version, an owner reports it appearing after it, and only evidence settles that.

    More about this step

    Applies when: the switching failure persists after the physical checks.

    Worked if: the direction of the defect gets evidence instead of an assumption, and the case is with support.

    Method: Mammotion's changelog text, set against the owner report, both quoted on this page

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 changed in this release
  3. What's been reported
  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 changed in this release

Released April 29, 2026. Mammotion's own changelog for 1.15.20.2303 describes improved remote-connection performance, reduced iNavi NetRTK data usage, and optimizations to thin-pole detection, docking, and open-field positioning drift.

What's been reported

The opposite of the intended improvement: after this update, the RTK antenna stopped switching modes, causing NetRTK activation to fail1. If your mower is having trouble establishing or maintaining an RTK fix after updating to this version, this is a documented match.

Manufacturer statement. Mammotion's own changelog for 1.15.20.2303 lists "Fixed switching failures between 'Antenna over Internet' and 'iNavi NetRTK' in poor network conditions". It documents the same NetRTK switching-failure class, while framing it as fixed by this version2. A single owner report above describes the failure appearing after this update, so the changelog alone doesn't settle the direction; treat it as a known, acknowledged switching-failure area rather than a confirmed new fault from this update.

Rollback procedure

There is no procedure here to follow. 1.15.6.2300 (March 23, 2026, the release immediately prior to 1.15.20.2303, per Mammotion's own knowledge base2) is what to ask Mammotion support for, not something an owner can run: this is the mower's own body firmware, and no confirmed manual downgrade path exists. The Android rollback guide covers what is actually possible today.

No confirmed manual downgrade path exists for the mower's own body firmware (see the Android guide). Treat this version number as what to ask Mammotion support for, not a procedure you can run yourself.

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