Independent guides for robot mower owners

Not affiliated with or endorsed by any device manufacturer. All trademarks belong to their respective owners.

← All guides

fixed-issue

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

Models covered
YUKA mini (500/500H, 600/600H, 800/800H) & YUKA mini Vision (700/700H)
Target version
1.14.2.2304 (fix released 31 July 2025)
Last updated
5 September 2026
Correction, 5 September 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.

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 (31 July 2025) explicitly list fixing a false "1425" startup error, alongside repeated obstacle collisions, charging voltage reporting, and battery estimates1 — see the companion guide for the blade-noise issue this same release introduced. 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 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 involved2. Others have needed an actual hardware fix: a separate YUKA owner's vision module was replaced by Mammotion support under warranty after their persistent Error 1425 turned out to be a genuine defective module3. 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.
Advertisement