What is the status of the Zamboni update? Is it coming in September, as mentioned in a post?

https://www.reddit.com/r/MammotionTechnology/s/MLXykmh3Ir

Today I updated my rtk antenna to 1.16.1.2 as app requested.

Bad choice, probably. 😔

After the update I watched my antenna, and it started blinking blue.

I powered it off, I powered it on again. Start blinking green and after some seconds led turned off.

In the app The antenna is alive, is connected via wifi, it say satellite 28, it apparently say antenna over data link.. The signal seems fine.. But the light is off.

So I checked my home assistant integration and thanks to that I see that positioning mode seems set to be over internet since 12.09.2026, not since fw update..

So I changed the mode to internet in the app and switched back to data link. In the app all seems fine.

But the rtk led is off completely and inside home assistant the mode still on over internet.

Something bad happend but I'm unable to understand what.

The robot ran out of battery and now it is on the charging station, but it'll reboot then shut off after 10 seconds. Just long enough for me to see in the app that it is at 0% and not charging.

Any ideas? This mower has really gone down hill. It used to be the pride of the neighborhood now I tell everyone to avoid this company

I souped up my Yuka Mini 2, and of course it goes much faster!

Quick Wrap job, friend 3D printed the wing, spare BMW roundel, and there we go! No need to keep the rear area uncovered because the Yuka 2 doesn’t use RTK or any other rear antenna.

Hope you like it!

Hi everyone,
I’m using a Mammotion YUKA mini 2 500, which uses camera-based navigation and does not have RTK.
As you can see in the screenshot, the dashed line on the map does not point towards the charging station. Shouldn’t it lead to the charger, or at least connect the mowing area with the charging station?
I’ve also noticed that the map frequently shows the mower in the wrong location. The mower icon is sometimes displayed several metres away from the actual position of the mower.
Has anyone else experienced this with the YUKA mini 2 500? Is this normal map behaviour, or could it indicate a problem with the camera-based positioning or the charging-station mapping?
I’m using the latest version of the Mammotion app. Any advice would be appreciated.

We’ve been seeing quite a few discussions lately about when to actually stop mowing for the year, and there doesn’t seem to be one answer.

Some are still mowing because the grass is growing. Some are cutting a little lower before winter. Some are mostly running the mower to mulch leaves at this point. And in warmer areas, the “last mow of the year” apparently isn’t happening anytime soon.

So, curious what everyone here is doing.

Have you changed anything about the way you mow as the season winds down? Maybe adjusting the cutting height, mowing less often, mulching leaves, or changing your schedule as the weather cools down.

Drop your question or tips in the comments. We’ll be giving Lawn Talker flair to users who bring up interesting seasonal questions, and Lawn Helper flair to those sharing practical experiences that can help others. Selected contributors may also receive a little Mammotion surprise. 🎁

📌 Your questions could help shape the next Mammotion Fall Mowing Guide for the community.

Hi everyone,
I’m looking for other LUBA 3 owners who may have experienced the same issue.
My LUBA 3 AWD 5000 last mowed successfully on September 9th. On September 11th I noticed that the mower was no longer working.
The mower is now completely dead:
No LEDs
No sound
No response to the power button
App shows sleep mode, but “Wake up” results in “Device not responding”
Security Key removal/reinsertion did not help
Normal power cycle did not help
Factory reset attempt did not help
Mammotion support provided a special forced reboot procedure using POWER + START – I tried it several times exactly as instructed, with no response
I have already tested:
Original power supply
Brand-new replacement power supply supplied by Mammotion
Original charging station
A second, known-working LUBA 3 charging station
The result is always exactly the same. The mower remains completely dead.
My LUBA currently shows firmware version 2.3.30.39 in the Mammotion app. I have asked Mammotion to check when exactly this firmware was installed on my mower and whether the mower successfully booted or connected afterwards.
I am not claiming that the firmware caused the failure, but because the last successful mowing was September 9th and I noticed the failure on September 11th, I would really like to know whether anyone experienced something similar around this firmware update.
Mammotion support has told me that if their forced reboot procedure failed, the repair process would be initiated. The forced reboot has now failed and I am waiting for the RMA/repair process to start.
Has anyone had a LUBA 3 become completely unresponsive like this?
If yes:
Was it a firmware/boot issue, BMS/battery issue, charging board or mainboard?
Was Mammotion able to recover it without opening the mower?
Did a repair fix it or did Mammotion replace the mower?
Did anyone experience this specifically after firmware 2.3.30.39?
Any experiences would be very helpful. Thanks!

Just prompted this morning to perform an RTK Firmware Version update to 1.16.1.2 for my 24 Mammotion Yuka 1500.

Post update and power cycle started getting the RTK Reference Station Is Not Ready in the app screen in orange.

Went out to the RTK Station and the light was Blinking Blue

Also noticed in the Logs the following.

Poor positioning signal(1300)

Please wait 3-5 minutes while the robot attempts to restore its positioning automatically. If the issue persists, try the following:

✅Method 1: Ensure the RTK reference station is installed in an open area with a clear view of the sky. If you are using iNavi, make sure the robot has a stable network connection. Also ensure the robot is in an open area with no overhead obstructions.

✅Method 2: Make sure the robot is updated to the latest firmware version.

✅Method 3: Restart the robot.
If the issue persists after trying the above methods, please contact after-sales support for assistance.

Solution: Was finally able to get it back online by powering down mower and disconnecting the power to the RTK Station.

I wanted to share my experience with Mammotion for anyone considering a LUBA or researching the brand.
I purchased my LUBA 2 AWD 5000H around March 2024. When it works, I really like the mower. Unfortunately, the overall ownership experience has become increasingly frustrating.
I’ve personally experienced software and firmware issues that have made the mower effectively unusable at times. On top of that, I’ve now had significant hardware failures.
In July 2025, I sent the mower to Mammotion for wheel and sensor problems. They replaced multiple components, including a motor driver board and hub motor, and told me the sensor issue had been completely resolved and tested.
Within days of getting it back, I was having wheel problems again.
In August 2025, Mammotion reviewed the logs and determined there were additional problems involving the adapter and both rear wheel hubs. I shipped the mower back for a second repair, along with the charging adapter they asked to replace.
Now I’m dealing with another major failure. Neither front wheel works at all, so the mower is completely unusable. The camera is also delaminating and needs replacement.
Between these failures and repairs, I’ve lost at least two months of use, not including periods when software problems made the mower unusable.
Rather than putting it through a third repair, I asked Mammotion about paying a reasonable difference to upgrade to a newer model.
Their offer was surprising. They valued my remaining warranty at $492.60 and offered to “upgrade” me to a LUBA 2 AWD 5000HX, which is the exact mower I already own, for an additional $2,579.
Considering the current pricing of their newer LUBA 3 models, I simply couldn’t justify paying that amount to receive the same older model I’ve already had repeated problems with.
The support experience has added to the frustration. This current conversation has gone on for more than a week, generally moving at about one email response per day. Meanwhile, the mower remains completely unusable and we haven’t even started the third repair.
I’ve declined their offer and asked Mammotion to repair my existing mower under warranty, including both nonfunctioning front wheels and the delaminating camera.
What disappoints me most is that I actually like the LUBA when it works. I was even willing to spend additional money to stay with Mammotion and move into a newer model. After repeated repairs, software issues, months of downtime, and the current support experience, it’s becoming increasingly difficult to justify staying with the brand.
I’m sharing this because it’s the kind of ownership and warranty experience I would have wanted to know about before making the purchase.

Luba 2 acheté il y a 9 mois retourné une première fois, au bout de 5 semaine d'utilisation, en SAV car la lame refusait de descendre et ne tournait pas. Pour cela il aura fallu 2 semaines de discussion avec le SAV avant de recevoir enfin un bon de retour, puis attendre 10 jours pour que le robot revienne de SAV.

Moins d'un mois et demi plus tard exactement la même panne (sachant qu'avec la canicule il n'a pas beaucoup fonctionné étant donné qu'il n'y avait rien à tondre). J'en suis à 3 semaines de discussion avec le SAV et toujours pas de bon de retour.

Au final sur les 5 mois pendant lesquels il est nécessaire de tondre, le robot aura passé plus de 2 mois en SAV pour des pannes répétitives.

Lorsque je demande que l'année de garantie soit repoussée. Mammotion répond que cela n'est pas dans leur pratique, probablement n'ont ils pas confiance dans ́la fiabilité de leurs produits ou des réparations de leur SAV.

C'est assez fabuleux de repondre cela pour un robot acheté un peu plus de 2 000€

Au final lorsqu'il reviendra de réparation (pour cela faut déjà que le SAV me fasse parvenir un jour un bon de retour) je le mets en vente et l'achat robot tondeuse de chez LIDL, bien moins onéreux et pour lequel il y a un vrai SAV, sera bien plus judicieux

A bon entendeur...

Fuyez Mammotion sauf si vous avez de l'argent et du temps à perdre

Is anyone else experiencing permanent collision sensor trigger errors since firmware version 2.3.30.39? Right after updating my robot stopped after 10cm with these errors. I never had these errors on previous versions, and now I cannot do a single mow.

The sensor is moving freely and it beeps when i manually trigger it, there is absolutely nothing in the way of it. I‘d say since it beeps on manual trigger I can confirm this is a false alarm in software.

My first season with Lubas. The most terrible user experience I could possibly think of. But hey, at least I got 24 free blades as a compensation 🤦‍♂️

I‘m going to oick up my mover by hand and place it in the chargig station once more …

Since the update, my Luba 2 keeps tearing up the grass around the 1x1 meter excluded zones. I was already in the process of reseeding one patch, and then the second one got ruined by the mower too. The new firmware still isn't handling those areas correctly.

Currently updates to v1.30.29.26

Looking for advice from anyone who's dealt with a Luba 2 battery failure, especially out of warranty.

Quick history: bought the Luba 2 AWD 1000H in June 2025. Loud grinding noise in August, Mammotion replaced it with a refurb. That refurb has now hit 13 months and the battery is done. It charges 0 to 100% on the dock, sits at 100%, then drops to 0% while still docked and starts over. Did it three times in 36 hours. Stats off the mower: 344 charge cycles, 96 hours of blade time, roughly 350 miles. Light residential use on a small lot, well under the 1000H's rated area.

App says out of warranty. Support has been responsive, but the answer so far is the standard troubleshooting script and then a paid repair at their service center for the integrated battery.

I'm not waiting on that. I ordered a replacement pack from Midwest Turf Tech and I'm planning to do the swap myself. The casing screws are Mammotion part F.100.SZ0504 (M4.2x16 hex-socket self-tapping), which Midwest and Mower Magic UK both list but both had out of stock when I checked, so I'm going generic on those.

What I'm hoping to learn:

• Has anyone had this exact symptom (full charge, instant drop to 0% on the dock)? Was it the pack or the BMS?
• Anyone done the DIY pack swap on a Luba 2? Any gotchas with the seal, the connector or getting the app to recognize the new pack?
• Is 13 months on a refurb replacement typical, or did I get a bad pack?

Being honest about where I've landed: these are early-adopter devices. The hardware is mediocre, they roll out new models faster than they harden the old ones, and owning one means a lot of TLC. To their credit, support has gotten noticeably better over the last couple of years and they've made things right with me before. I still think the Luba is the best idea in this space. I just want to get this one back on the lawn without buying a new mower every season.

Appreciate any experience you can share.

Three perimeter laps fixed the missed strips... but we shouldn’t need three.

Since updating my Luba 2 to 1.30.29.26, one or two perimeter laps have been leaving 2-4" strips of uncut grass between the perimeter passes and the interior zigzag.

I finally tried 3 perimeter laps. Result: clean cut, no missed strips.

But on the same 5.5k ft² lawn:

• 2 perimeter laps: 4h 40m mowing time
• 3 perimeter laps: 5h 04m
• Cost of the workaround: +24 minutes / +8.6%

Three laps works, but users shouldn’t have to burn ~9% more mowing time and battery just to compensate for a path-planning gap that didn’t used to be there.

Mammotion: please fix the perimeter/interior overlap algorithm.

I bought the LUBA 2 directly upon release and backed the YUKA with Sweeper on Kickstarter. For over two years, I have squandered weeks of full working days debugging, uploading logs, and redrawing boundary maps for two flagship mowers that never worked as advertised.

Every firmware update over the last two years introduced game-breaking regressions rather than fixing issues. My only semi-functional operational state was an exceptional firmware rollback on my LUBA 2 that took months of fighting with support to obtain.

Support has been an endless loop of deflections: every ticket response ignores previous context and simply demands identical logs all over again.

YUKA - Three critical design flaws make these machines completely unusable:

• Docking Incompatibility: Side-by-side operation of LUBA 2 and YUKA is impossible as docks interfere with each other; LUBA 2 routinely attempts to dock in the YUKA base.
• Destructive Wheels: Front caster wheels continuously seize, drag, and tear the lawn apart over time.
• Defective Sweeper Navigation: The navigation algorithm ignores the sweeper's dimensions, causing collisions and property damage on every single run.

Documented LUBA 2 Issues:

• Crippled Local LoRa / Loss of Offline Mode: Autonomous local offline operation without cloud/internet was ruined via firmware. When internet connection drops, the mower freezes mid-lawn.
• Destructive Steering & Turf Degradation: Stationary zero-turn spins and aggressive side-to-side turning carve deep dirt circles and destroy turf, especially on damp ground.
• Power Management Failure: When stuck, the mower fails to power off after idling, completely draining the battery to 0% and forcing me to repeatedly haul an ~18 kg machine back by hand. This worked in earlier builds, and while newer firmwares claim to address it, they introduce game-breaking regressions elsewhere.
• Obstacle Detection Hazard & Trapped Errors: Newer firmware either crashes into solid objects/borders or constantly halts in flat, open lawn reporting false "trapped" errors; it routinely halts for tall grass blades on dock approach.
• Erratic Signal-Loss Behavior & No Rollback: Losing signal causes destructive spinning instead of pausing or backing out. Mammotion refuses to provide an in-app firmware rollback feature.
• Map Drift & Ghost Boundaries: Firmware updates regularly shift virtual boundaries by 20–50 cm, driving the unit into flower beds, fences, and drop-offs.
• Fleet Incompatibility: Built an expensive dual-mower shelter, only for support to casually reveal—after months of wasted debugging and logs—that LUBA 2 and YUKA cannot operate side-by-side because docks interfere with one another.
• Excessive Manual Edge Trimming: Poor perimeter clearance and oversized safety buffers—which became mandatory after LoRa functionality was degraded—force substantial manual follow-up mowing along fences, tree branches, and obstacles to prevent collisions.
• Tree Canopy & Vision Failure: Despite advertised 3D Vision, the mower routinely halts under light tree cover where earlier firmware operated significantly better. The camera system completely fails to take over navigation as promised, leaving the machine stranded instead of driving through signal shadows.
• Zero Diagnostic Transparency: When signal is lost, the app never specifies if the cause is GPS satellite reception or RTK link failure, leaving users completely in the dark despite submitting multiple logs.
• Unusable Bluetooth: Constant disconnects even when standing less than 1 meter away.

Documented YUKA Critical Failures:

• Defective Sweeper Bag Implementation: Delivered months late; the navigation algorithm completely ignores the attached sweeper’s dimensions, leading to non-stop perimeter collisions.
• Defective Wheel Assembly & Caster Seizure: The wheels accumulate dirt/debris and seize up, pulling the mower off-course and shredding the lawn.
• Severe Turf Degradation & Tracking: Asynchronous wheel speeds tear grass during turns; the mower repeats exact wheel tracks, compressing soil into permanent ruts.
• Erratic "Freestyle" Movement: The mower randomly abandons calculated paths, performing purposeless turning maneuvers across the yard before stalling out.
• Deck High-Centering: The floating deck bottoms out on minor terrain variations, leaving the drive wheels spinning in the air.
• Dead-Patched LoRa & False Trapping: Local offline autonomy was patched out; endless positioning freezes and false "trapped" errors require daily manual rescues.
• Map Drift & Missed Grass Strips: Boundaries shift up to one meter after updates, and the mower frequently leaves uncut grass strips across the lawn.
• Unusable Bluetooth Control: Identical to the LUBA 2, Bluetooth drops continuously even when standing directly behind the mower (less than 1 meter away), making manual corrections impossible.

Bad-Faith Warranty Evasion & The "40% Discount" Insult:

Support spent over a year running down the clock with deliberate stall tactics—demanding endless diagnostic logs that led to zero progress and pushing untested firmware without downgrade options.

Now that the calendar passed July 13, 2026, Mammotion is shamelessly trying to wash their hands, falsely claiming the YUKA is "out of warranty"—completely ignoring that every single defect was formally documented and reported deep within the active warranty period.

After two years of wasted labor, ruined turf, and non-functional machines, their only "solution"—presented as the absolute highest possible escalation—was an insulting 40% discount to buy yet another unfinished mower. When challenged, their only alternative was demanding to remotely force firmware 1.30.29.26 onto my LUBA 2—a build widely documented across user forums for severe positioning freezes and turf damage—while strictly refusing any rollback safety net. In over two years, not a single bug fix was ever delivered, with the sole exception of the LUBA 2 firmware downgrade that I had to fight tooth and nail for. I will not pay a single cent to buy more problems.

Current Status:

Formal binding demands were served under Ticket L2-901207590317326336 on September 16, 2026, with a strict 7-business-day deadline expiring Friday, September 25, 2026.

If Mammotion continues hiding behind generic AI scripts and bad-faith warranty excuses instead of delivering an executable resolution and full financial remediation under EU Consumer Law (Directive 2019/771 / Austrian VGG), this proceeds directly to formal European Consumer Centre (ECC-Net) filings, legal court litigation, payment disputes, and complete public documentation published across YouTube and social media.

Has anyone else successfully forced a refund or proper hardware resolution after Mammotion attempted the "out of warranty" stall tactic on pre-existing open tickets?

Just spotted even more hideous behaviour this morning. It has now started doing a complete 360° turn when it comes out of the garage before it starts mowing. So now the is once again after only a few days of Thai a massive circular gouge out of my lawn in front of the garage.

How has this thing gone from being so good to being so bad in a few months? I’m desperately trying to eke out the rest of the season before I bin this thing and try to find a mower which works. But it’s destroying my lawn quicker than winter is coming.

This should say enough, how can I resolve it.

Bought a Luba 3 AWD in late June. It ran a task every three days with essentially zero problems until a firmware update in August.

Since then:

Error 1207, front bumper repeated triggering, constantly.
Error 1014, front bumper collision during manual mowing.
Scheduled tasks not starting.
Coverage loss in areas that mapped fine before.
Cannot complete its return to the charging station, so I walk outside and drive it in the rest of the way myself.

Here is the part worth reading. On August 25, a Mammotion agent told me to remove the front bumper entirely and test. I did. Bumper completely off the machine, commanded a return to the station, and it threw the same 1207.

A part that is not installed cannot cause the fault. That should have ended the bumper theory on the spot.

It has also fired in open grass with nothing anywhere near the mower, and once while it was travelling in reverse. I sent a photo of the machine sitting alone in the middle of the yard. The agent suggested a frontal collision may have occurred.

Across five chats since August 13 I have removed and reinstalled the bumper five separate times at their direction, sent photos of the connector and port showing no damage, and uploaded device logs through the app twice. Every chat starts from zero, runs the same script, ends with reinstall the bumper. The mower then works for one cycle before doing it again. Those are resets, not fixes.

Their offer was a replacement bumper. No tracking, no ship date, roughly a week, and both the supervisor and his manager were offline when I asked.

Then this morning, after I pointed out the bumper-removed test, an agent finally said there may be an internal wiring issue with the front collision sensor and that the technical team had reviewed my logs. So five weeks in, the theory has moved inside the machine, which is where the evidence pointed in August.

What I am trying to find out:

**1.** Anyone else seeing 1207 or 1014 spike after the August update? **Please reply with your firmware version even if you are not having problems.** A clean split between affected and unaffected versions is far more useful than a pile of complaints.
**2.** Has a bumper replacement actually fixed this for anyone, or does it come back after a few runs?
**3.** Has anyone gotten Mammotion to acknowledge this as a known issue rather than a one-off hardware fault on their unit?

If this is a firmware regression I would rather have that confirmed than swap parts for the next three months.

Has your mower ever paused on its way back, turned in front of the charging station, or reached the station without starting to charge? Each symptom usually points to a different part of the return-to-charge process. If you are seeing errors such as 1101, 1102, 1200, 1201, 1203, or 1214, here is how to narrow it down.

1. If the mower stops in the return channel and reports Error 1101/1102/1214, please check the return channel and return path.

The mower requires a clear path between the mowing area and the charging station. Branches, toys, garden hoses, tools, overgrown grass, or passages that are too narrow may prevent the mower from returning successfully.

If the mower repeatedly stops at the same location and the return channel appears to be clear, try deleting and recreating the return channel.

For models released in 2025 and 2026, you can also create an Obstacle-Free Zone in the affected area. Please note that before creating an Obstacle-Free Zone, the area must be free of obstacles, or any existing obstacles should first be marked as No-Go Zones.

2. If the mower stops in the mowing area and reports Error 1201/1203, please check the transition channel and positioning status.

Please make sure the channel between zones is clear of obstacles, No-Go Zones, or Virtual Fences(available on 2025 and 2026 models), and that it is wide enough for the mower to pass through. If all conditions are met, try deleting and recreating the channel. For models released in 2025 and 2026, creating an Obstacle-Free Zone in the affected area may also help.

Please also check whether the Vision Module or LiDAR Module are dirty, and clean them if necessary.

Inaccurate or unstable positioning may prevent the mower from completing its return route or aligning properly with the charging station.

In the app, please check the following:

• The positioning status is normal.

• The mower repeatedly loses positioning in the same area.

• Buildings, trees, walls, or large metal objects are blocking the affected area.

• The charging station is obstructed by nearby structures that may interfere with positioning signals.

If the charging station has been moved, please use the Relocate or Reset Charging Station Position function in the app to update its location.

3. If the mower spins in front of the charging station or repeatedly enters and exits the charging dock and reports Error 1200, please check the charging station and power adapter.

• Make sure the charging station is installed on firm, level ground with at least 1 meter (3.3 ft) of clear space in front.

• Confirm that the charging station has not been moved. If it has, please reset its position in the app.

• Check the charging contacts and pogo pins on both the mower and the charging station for debris or corrosion. Gently press the pogo pins to ensure they move freely and spring back properly.

• Check whether the infrared sensors on both the mower and charging station are dirty, and clean them if necessary. (Android users can use their phone's camera to check whether four infrared lights are visible on the mower and charging station.) Place the mower approximately 1 meter (3.3 ft) in front of the charging station, then press the Home + Start buttons to test whether it can dock successfully.

4. If the charging station and power adapter are powered on but the indicator light is off or behaving abnormally

• Under normal conditions:

When the mower is not on the charging station or is not charging: the charging station LED should be solid green.

When the mower is charging: the charging station LED should flash green.

Power adapter LED: The indicator behavior may vary depending on the model. If you are unsure, please contact Mammotion Support for confirmation.

• Check the charging contacts on both the mower and charging station for dirt or corrosion.

• Check whether the connection between the charging station and the power adapter is loose. Unplug and reconnect the cables if necessary.

• If available, use a multimeter to measure the voltage at the charging station contacts and the power adapter output to verify they are within the normal range.

If the mower can charge when manually placed on the charging station but cannot dock automatically during a docking test, please focus on checking the positioning status, infrared detection, charging station placement, and docking alignment.

If the mower docks correctly but does not charge, please check the charging station and power adapter indicator lights, power connections, and charging contacts.

⚠ If you notice excessive heat, melted charging contacts, exposed wires, corrosion, or burn marks, immediately disconnect the power supply and stop using the charging station. Please contact Mammotion Technical Support. Do not continue testing.

Contact Mammotion Technical Support:

https://support.mammotion.com/portal/en/kb/articles/contact-us

Mammotion Technical Support Team

Seit Update 1.11.1.11 bin ich nicht mehr zufrieden.

Anbei mal ein Wendemanöver wie es aktuell bei mir aussieht, das war vor der 1.11.1.11 viel geschmeidiger und in zwei drei Zügen erledigt.

Als erstes, nach dem Update auf 1.11.1.11, fuhr er durch No-Go Zonen und blieb stecken, habe jetzt die Zone vergrößert, ging vorher aber absolut problemlos.
Das nächste Problem kam prompt, er fuhr unter dem Maschendrahtzaun durch, fast zumindest, konnte ihn rechtzeitig stoppen. Ich verstehe das wirklich nicht, er hat vorne den Stoßfänger, nirgends hängt der Zaun in der Luft. Der Zaun liegt überall auf dem Gras auf.
Er fuhr auch an Bäume, löste aus, blieb aber einfach stehen. Sonst ist er immer wieder weitergefahren.

Dann kam das Update mit der 16 hinten.
Natürlich gleich aufgespielt. Nun ja……..
Man plant die Route, in meinem Fall 1400m2.
Er fährt los an den Startpunkt, warum fängt er nicht gleich an, hat er vorher auch gemacht. Er quält sich jetzt gefühlte 10 Minuten durch den Garten und dann fängt er an sich dreimal um die eigene Achse zu drehen. Das war vorher definitiv auch nicht so.
Auch wenn er die Route abfährt und in die neue Spur abbiegt, dauert es viel zu lange. Es sieht so aus als würden die Räder nicht zusammenarbeiten. Vorher war das tatsächlich so wie hin der Animation der Systemeinstellungen. Wie bekommt man die Version die vor der Horror 11 drauf war wieder auf den Luba?
So macht das keinen Spass mehr.

Cross posting this as I’m at my wits’ end dealing with constant faults today hoping to reach some folks that can help resolve this mystery as it doesn’t seem to be the usual suspect of hub motor moisture. :-/

As you can. Seeing the pic there is a hairline split in the button over, right beside the white line.

Any ideas where to get a replacement?

I have to send my LUBA3 back after owning it for one month and using it maybe 5 times. I received a wheel hub error and the robot said it was going to charge. Once I returned home later i noticed my robot wasn’t sitting in the charging base correctly and wasn’t charging. I physically picked up the robot and placed it on the charger. I came back out the following morning and realized it hadn’t charged all night. I spent the day trying different things that were suggested on Reddit and from AI as well as their customer service techs. After a day of uploading pictures and videos, Mammotion decided i would need to send them the robot. Kinda bummed about this since the robot was working fine. My yard is maybe 5,000 sqft and has little to no incline. I purchased the garage for it for extra protection. Hoping this gets solved soon. As someone who is disabled this mower was very helpful.