Error 1425 (vision module fault): reported across YUKA, YUKA mini, YUKA mini 2, LUBA mini AWD, LUBA 2 (base & AWD X) & LUBA 3

What the error means

Mammotion's app shows "Error detected in the 3D vision module (1425)" when a mower's front camera/vision system reports itself not ready or faulted; the mower typically stops the current task. Error 1425 does not appear in any of Mammotion's official product manuals; it's an owner-reported and app-surfaced code, not one Mammotion documents in writing outside its own support replies (see the fault-codes reference for the officially-documented codes this is not one of).

Confirmed cases, by model

YUKA mini, YUKA, LUBA mini AWD & LUBA 2 AWD X: false startup flash, officially fixed on four model lines

A false Error 1425 appeared on startup, even though the mower kept working normally. Mammotion's own release notes list a fix on four separate model lines, on the same day or within a day of each other. They are YUKA mini (firmware 1.14.2.2304, August 1, 2025)¹, LUBA mini AWD (1.14.2.4304, August 1, 2025)², YUKA (1.14.2.2414, July 31, 2025)³, and LUBA 2 AWD X (1.14.2.4415, July 31, 2025)⁴. Each release note uses near-identical fix text ("resolved the 1425 error occurring on startup"), consistent with shared upstream code and per-model release numbering. The identical fix text then shipped a second time, about four weeks later, on the same four model lines: YUKA (1.14.7.2411, August 28, 2025)⁵, LUBA mini AWD (1.14.7.4301, August 28, 2025)⁶, YUKA mini (1.14.7.2301, August 28, 2025)⁷, and LUBA 2 AWD X (1.14.7.4411, August 29, 2025)⁸. Mammotion's own knowledge base doesn't explain why the same fix needed re-shipping. Full detail on the YUKA mini case specifically, including the companion blade-noise issue introduced in the same release, is in the dedicated YUKA mini Error 1425 guide.

YUKA mini 2: persistent error, at least three different outcomes

A persistent (not startup-only) Error 1425 on a 4-week-old YUKA mini 2 cleared after a full power-down of both the mower and base station, removing the security key, waiting 30 minutes, and reassembling, with no firmware change involved⁹: cheap, fast, and worth trying before assuming a hardware fault needs a support-shipped replacement.

YUKA (sub-model unconfirmed): hardware fault, vision module replaced under warranty

A separate persistent Error 1425 turned out to be a genuine defective vision module; Mammotion support shipped a replacement, which resolved it once installed¹⁰. The reporting owner's post names only "YUKA," not a specific sub-model.

LUBA 2 (base/AWD, non-X): hardware fault immediately after unboxing, two independent reports

Persistent, near-minutely Error 1425 hit two independent LUBA 2 (base/AWD, non-X) owners immediately after unboxing a new unit; the mower kept running but repeatedly reported the vision module wasn't ready. For both, reinstalling/reseating the existing camera did not fix it; both were resolved only by a full vision/camera unit hardware replacement from Mammotion support (about two weeks' turnaround), after which both owners also had to redo a firmware update on the new vision unit and remap their whole lawn¹². Unlike the YUKA mini/YUKA/LUBA mini AWD/LUBA 2 AWD X case above, this is a hardware defect on new units, not a firmware-side false positive.

LUBA 3 3000: persistent error, unresolved

Unresolved: constant Error 1425 warnings appeared on a LUBA 3 3000 with a visibly clean camera; Mammotion support had, as of the report, only said the case was "passed to the relevant team for in-depth analysis," with no fix reported¹¹. A second LUBA 3 3000 owner, in Canada, reported a vision module failure code 1425 after about six months of use. Mammotion's technician decided the mower had to be returned, then an email said the case needed review by the R&D group first. The owner updated to 2.3.31.69 when Mammotion suggested it and still had 1425 on 28 September 2026. A Mammotion account asked for the case ID and said it had asked the team to review it. By 30 September the owner said Mammotion had been in touch about shipping, and asked for a courier pickup from home¹³. The thread does not say how it ended. If you've hit the same thing on a LUBA 3, let us know, especially if you find a fix.

A replacement front bumper: 1425 and a positioning failure

An owner whose mower runs firmware 2.3.30.39, with the Android app freshly updated to 2.3.20 (30), fitted a new front bumper that Mammotion had sent under warranty because the old one gave ghost-collision signals. The mower at once showed error 1425 and a positioning failure (1000019); with the old bumper refitted, the errors stopped. The owner downgraded the app to 2.3.18 (21) and says the odd behaviour, including strange turns, went away¹⁴. A Mammotion account told them to reinstall the new bumper by following its video, and to send the device number and logs if the error stayed¹⁵. Another owner says to click the new bumper fully home, and that if it clicks and still will not come out, the bumper itself could be bad¹⁶. That is one owner's case, and what caused the error, the bumper or the app version, is not settled.

If you're hitting this

1. Confirm the camera lens is actually clean and firmware/app are current. A genuinely dirty or obstructed camera can trigger unrelated vision errors (see fault codes for those).
2. If it's a one-time flash on startup and the mower keeps working: likely the YUKA mini case above. Update to the latest firmware if you haven't.
3. If it's persistent and the mower actually stops: try the full power-cycle sequence. It resolved a YUKA mini 2 case and may be worth trying on any model before you assume hardware failure. Remove the mower from its base station, power down both the mower and base station (unplug the base station's power supply), remove the security key, wait 30 minutes, then reverse the steps.
4. If the power-cycle doesn't fix it, check for a dusty LiDAR module next: cleaning it resolved a separate YUKA mini 2 case without needing a hardware replacement.
5. If neither works: contact Mammotion support about a possible hardware fault rather than continuing to chase a firmware or cleaning angle. A confirmed case on each of three model lines needed an actual vision-module/camera replacement. See what to have ready before you contact support.
6. If it starts immediately on a brand-new unit, right out of the box: don't waste time reseating the existing camera; two LUBA 2 (base/AWD) owners confirmed that doesn't fix it. Go straight to requesting a hardware replacement, and plan for a firmware update plus a full remap once the new vision unit is installed.
7. If it started just after you fitted a replacement front bumper: take the bumper off and refit it until it clicks fully home, following Mammotion's video, before treating it as a vision module fault¹⁵.