Request a Correction

Think something on this site is wrong, out of date, or shouldn't have been attributed the way it was? This is the channel for that, whether you're the owner who originally reported something, a manufacturer or its representative, or anyone else who spotted a problem. There's one channel for everyone; nobody's dispute gets priority handling over anyone else's.

Email corrections@myrobotdoc.com with the page URL, the specific claim you're disputing, and what you believe is wrong. What happens next depends on who's asking and why:

• If you're the original source of a cited report and want it removed, we'll honor that by default: the citation and any quote from it come down, and the page is re-evaluated against our corroboration standard. If it no longer clears the bar without your report, the page is downgraded or the claim is removed.
• If you're disputing a claim's accuracy (including as a manufacturer), we act on evidence: a release note, a reproducible counter-finding, or a demonstration that a source was misread. An objection without evidence gets a reply inviting you to submit it; we don't retract on assertion alone.
• In either case, if a claim rests partly or entirely on a private-group source, we can share the specific disputed excerpt directly with you (the quote, its capture date, and its link) with any name or handle stripped. This is limited to the one claim you're asking about, not a bulk records request.

Every request and its outcome, including "no change, no evidence provided", is logged. If something does get corrected, the fix happens on the page itself, dated and in place, and is added to the corrections log below. Nothing is ever corrected silently.

Corrections log

When something we've published turns out to be wrong, we say so on the page itself: dated, in place, then logged here. This list points to each correction where it actually lives; read it there for the full detail.

• November 4, 2026: Turns tear up the lawn: the LUBA 3 version of this page put a Mammotion staff reply about the turning mode under LUBA 3, but it was posted in a thread about the LUBA 2. Two other replies were also placed under LUBA 3 although their threads name only "Luba". They now sit under LUBA 2 and under "In other threads".
• October 24, 2026: What owners report about Mammotion support repairs and LUBA charging power adapter not waterproof: both told a LUBA 2X owner's case only up to a €125 charge. The owner later wrote that Mammotion had acknowledged the warranty and agreed to send the power supply under warranty. The outcome is now on both pages.
• October 24, 2026: Error 1200, recharge failed: Case 1 said the YUKA owner had no reply from Mammotion support and that there was no confirmed fix. In the owner's own thread, a Mammotion account followed up and asked for a log, the owner sent one, and in May 2025 the owner wrote that a new charging station docked on its first test. Case 1 is rewritten with those dates, and the page no longer calls the fault unfixable.
• October 21, 2026: LUBA 2 AWD X channel page: the bush and small-incline details were attributed to the second owner but belong to the first. Also corrected: the two posts were from the same evening, not about 24 hours apart; the Off workaround was offered to the first owner, who had already tried it, not to both; and one source's quote was about a different topic and is replaced by the owner's own words.
• October 21, 2026: Android app version history: the July 2024 launch hang was said to have resolved 24 to 48 hours later, confirmed by all three owners. The thread shows it was fixed the same evening, two owners confirmed it, and the third did not post again. The page now says that.
• October 19, 2026: Charging stops part-way: step 1 told every owner to check a charge-level setting in the app. A YUKA app does not show one. The step now points LUBA owners to the app's battery page and says the setting may not exist on a YUKA.
• September 7, 2026:YUKA mini Error 1425: the official fix date was cited as July 31, 2025, from Mammotion's generic release-notes hub; a closer check turned up the actual dated per-model article, which is August 1, 2025 (July 31 belonged to a sibling model's release note for the same firmware wave). Corrected, and the specific dated article is now cited directly instead of the generic hub link.
• September 6, 2026: YUKA mini Error 1425: two supplementary sources had been attributed to "YUKA mini" without matching the actual reports' own wording: one was posted as "Yuka 2 mini" (corrected to YUKA mini 2), the other named no sub-model at all. See the page's own correction callout for full detail.
• September 5, 2026: YUKA mini Error 1425: a previously cited roboter-forum thread was removed as a source after a full read revealed it described an unrelated LUBA 2 hardware vision-module failure (different model, different root cause). The page now covers only the YUKA mini's own, officially-documented false Error 1425.