Fixed issue

YUKA mini: false Error 1425 startup error, fixed in firmware 1.14.2.2304

A false Error 1425 on startup, officially fixed in the same release that also introduced a separate blade-noise issue.

Status Reported fixed in 1.14.2.2304

Models: YUKA mini (500/500H, 600/600H, 800/800H) & YUKA mini Vision (700/700H)
First reported: 01 Aug 2025
Last updated: 07 Sep 2026
Affects: Vision module (on the robot) — not the app
Target version: 1.14.2.2304 (fix released 01 Aug 2025)

YUKA mini (500/500H, 600/600H, 800/800H) & YUKA mini Vision (700/700H)First reported 01 Aug 2025Details

Models: YUKA mini (500/500H, 600/600H, 800/800H) & YUKA mini Vision (700/700H)
First reported: 01 Aug 2025
Last updated: 07 Sep 2026
Affects: Vision module (on the robot) — not the app
Target version: 1.14.2.2304 (fix released 01 Aug 2025)

What to do next

Safety first
Before you try anything below, read the safety rules from your mower’s manual.

Update to 1.14.7.2301 or later: the false start-up error was fixed in 1.14.2.2304 and the same fix text shipped again four weeks later, so the later build is the safer bar.

More about this step

Applies when: a 1425 error flashes once on start-up and clears by itself.

Worked if: the start-up flash stops and mowing is unaffected.

Didn't work? Next: step 2 — Power down the mower and the base station, unplug the base...

Method: Mammotion's release notes for 1.14.2.2304 and 1.14.7.2301
Power down the mower and the base station, unplug the base station's power supply, remove the security key. Wait 30 minutes, then reverse the steps.

More about this step

Applies when: the error does not clear on its own: the mower actually stops.

Worked if: a persistent error clears with no firmware change involved.

Didn't work? Next: step 3 — Contact Mammotion support about a possible hardware fault. One...

Method: a YUKA mini 2 owner's power-down fix, quoted here
Contact Mammotion support about a possible hardware fault. One YUKA owner's vision module was replaced under warranty. Read the across-models 1425 page for the cases this page does not cover.

More about this step

Applies when: the power cycle did not clear it, or the unit is new.

Worked if: the case is with support rather than stuck on a firmware angle that does not apply.

Method: the warranty-replacement case cited here, and this page's own scope note

Vision module (on the robot) — not the app. See our app vs. firmware vs. RTK guide if you're not sure which one you're dealing with.

Correction, September 5, 2026: this page previously cited a roboter-forum.com thread and a firmware version (1.14.2.2414) that turned out, on a full read of that thread, to describe an unrelated LUBA 2 hardware vision-module failure: a different mower, a different root cause (defective hardware needing warranty replacement, not a firmware bug). That thread has been removed as a source here. This page now covers only the YUKA mini's own, officially-documented false Error 1425.

Correction, September 6, 2026: the two supplementary reports below (persistent Error 1425 and a hardware-replacement case) were previously attributed to "YUKA mini" without re-checking the original posts' own wording. On a direct re-read: the persistent-Error-1425 report was posted as "Yuka 2 mini", read here as YUKA mini 2, the only Mammotion product line that name plausibly describes, but flagged in case the poster meant something else. The hardware-replacement report says only "my YUKA", with no sub-model named. It is not confirmed to be a YUKA mini at all, and is presented below without that assumption.

Correction, September 7, 2026: this page previously cited Mammotion's generic YUKA mini release-notes hub (undated) and stated the fix shipped July 31, 2025. A closer check of Mammotion's own knowledge base turned up the actual dated article for this specific model and firmware string: it's dated August 1, 2025, not July 31 (that earlier date belonged to a sibling model's release note for the same firmware wave). Corrected throughout this page.

What happened

A false Error 1425 ("vision module not ready") appeared on startup on YUKA mini and YUKA mini Vision units, even though the mower continued to work normally.

The fix

Mammotion's own release notes for firmware 1.14.2.2304 (August 1, 2025) explicitly list fixing a false "1425" startup error, alongside repeated obstacle collisions, charging voltage reporting, and battery estimates¹. See the companion guide for the blade-noise issue this same release introduced. The same fix text ("resolved the 1425 error occurring on startup") shipped again for YUKA mini in firmware 1.14.7.2301 four weeks later, August 28, 2025². Mammotion's own knowledge base doesn't explain why a false-1425 fix needed re-shipping, so treat "update to 1.14.7.2301 or later" as the safer bar if you're still seeing the flash on 1.14.2.2304. If you're on an older build than 1.14.2.2304 and hitting a 1425 error that clears on its own (the mower keeps mowing despite the error), updating forward is the documented fix.

If your Error 1425 does NOT clear on its own (the mower actually stops, or the error is persistent rather than a one-time startup flash), this may not be the same issue. One YUKA mini 2 owner's persistent Error 1425 cleared after a full power-down (mower and base station), removing the security key, waiting 30 minutes, and reassembling. No firmware change involved³. Others have needed an actual hardware fix: a separate YUKA owner (sub-model unconfirmed) had their vision module replaced by Mammotion support under warranty after their persistent Error 1425 turned out to be a genuine defective module⁴. If updating to 1.14.2.2304 or later doesn't resolve it, try the power-cycle sequence first, then contact Mammotion support about a possible hardware fault rather than continuing to chase a firmware angle.

Error 1425 has also been reported on LUBA 3, unresolved as of the last check. This page covers only the YUKA mini's own officially-fixed case. See Error 1425 across models for the full picture, including the LUBA 3 case.

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.