My Robot Doc

Known issue

Error 1028 ("drivetrain motor error detected"): owners link it to a stuck wheel; Mammotion calls it occasional

Not in any official manual. Owners saw it right after a wheel got physically stuck. Mammotion's reply in the forum thread called it an occasional problem and said safety is generally not affected, without naming a cause. Reported on YUKA, YUKA mini, and (per one forum regular) LUBA.

From owners' reports in German, not from Mammotion's own pages.

Status Manufacturer-acknowledged

Models
YUKA, YUKA mini (also reported, less specifically, on LUBA)
First reported
09 Jun 2025
Last updated
03 Nov 2026
Affects
Robot body — not the app
YUKA, YUKA mini (also reported, less specifically, on LUBA)First reported 09 Jun 2025Details
Models
YUKA, YUKA mini (also reported, less specifically, on LUBA)
First reported
09 Jun 2025
Last updated
03 Nov 2026
Affects
Robot body — not the app

What to do next

  1. Free the wheel that got stuck (in the grass-catcher basket, dense grass, a small hole), then restart. Mammotion's own reply calls 1028 an occasional problem and says safety is generally not affected, but names no cause; the stuck-wheel link is the owners', and error 363 logged at the same moment in one owner's log supports a stuck-wheel overcurrent origin.

    Stop and get help if

    the mower will not move at all once the wheel is free: that is the point to escalate, not to restart again.

    More about this step

    Applies when: 1028 appeared right after a wheel got physically stuck.

    Worked if: the mower moves again and the code stops appearing.

    Didn't work? Next: step 2 — Contact Mammotion support if it recurs without a stuck wheel....

    Method: two detailed owner reports and Mammotion's in-thread reply, both on this page

  2. Contact Mammotion support if it recurs without a stuck wheel. Say if a motor or hub repair failed to clear it. The official reply (ambient conditions, voltage fluctuations, temporary communication interruptions, safety generally not affected) is non-committal on cause. Keep separate the other pattern on this page: a persistent 1028 with no subcode after months of storage, no self-recovery, whole unit returned, on a 3000-class LUBA 2.

    More about this step

    Applies when: it recurs with no stuck-wheel trigger, or a repair did not resolve it.

    Worked if: the recurring case is with support holding the right detail, and the two failure modes are not treated as one.

    Method: Mammotion's quoted reply, and the separate single-report case recorded here

What this page is: error 1028 isn't in any of Mammotion's official manuals (see the fault-codes reference). Owners see it in the app, and several have hit it under the same trigger, and Mammotion support gave an official, if vague, explanation in the thread. One more severe case is a single report so far and is not the same issue; see the note at the bottom.

The common trigger: a wheel gets physically stuck

In both detailed reports, error 1028 ("Fehler im Fahrwerksmotor erkannt" / drivetrain motor error detected) appeared right after a wheel got physically stuck: once against the sweeper's grass-catcher basket, once in a general stuck-wheel event. It has been seen on a YUKA 1000 with the grass-catcher sweeper attachment and a YUKA mini 500; a long-standing forum regular adds LUBA, without naming a model or date1.

One owner's error log backs this up: error 363 ("Phasenstrom Überstrom des linken Radmotors": left wheel-motor phase-current overcurrent, meaning a blocked wheel or hub) was logged at the same moment as 1028. That points to the stuck wheel, not a separate drivetrain hardware fault1.

Mammotion's official response

Mammotion's reply confirms one thing: it doesn't treat an occasional 1028, on its own, as a safety issue that needs a repair.

The owner had asked about a recurring 1028 that a motor/hub replacement hadn't fixed. Support replied in German; our own translation says it is "an occasional issue that can be caused by factors like ambient conditions, voltage fluctuations, or temporary communication interruptions", and that "device safety is generally not affected"1. The original wording is in the linked thread. The reply doesn't pin down a cause, and it doesn't explain why the hardware repair didn't fix that owner's mower.

If you're hitting this after a wheel gets stuck (in a grass catcher, dense grass, a small hole): free the wheel and restart. Mammotion's reply above calls 1028 an occasional problem and says safety is generally not affected, but names no cause; the stuck-wheel link comes from owners. Only go to support if it comes back without a stuck wheel, or the mower won't move at all afterward.
Not the same case: one owner reports a persistent 1028 with no subcode. It appeared after several months of winter storage, not after a stuck wheel, on a LUBA 2 AWD 3000-class mower that had run 172 problem-free hours the season before. Repeated restarts didn't clear it, and the owner was told to ship the whole unit back for repair. It's a single report so far, and it reads as a different failure from the stuck-wheel cases above: no trigger, no recovery on its own, and a full return. We're following it separately.

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