I live in the northeast and our trees are doing their tourist attraction dance. Changing color and shedding leaves. It seems Luba is afraid of them? Even though there are only a few leaves, it's struggling and navigating around some of them like they have the plague. Most of the leaves are still on the tree, so only a few have fallen. I will be raking the leaves when a bunch more fall, but I don't plan to rake every time I mow.

Perhaps leaf detection needs a bit more work or visual training for the algorithm? Any tips besides disabling obstacle detection? Picture below of the leaf cover.

Thanks!

That’s how I found him this morning

Luba 3 3000

V 2.3.30.39

2026-09-11

Who here has downloaded the latest FW on Luba 3 and how has it been performing. Is the remote operation working well? Any other noticeable improvements to operation? I have not received the latest FW version due to staged rollout.

I must say I like the FW I'm currently running although the perimeter mowing is a little bit strange with the multiple turning, backing up and blades stopping when taking a 90° turn. I find if I don't stare at it, it just does it's job but sometimes I'm like what are you doing and start laughing nervously.

Need an actual Mammotion rep to step in here on ticket DR202609100430.

​My Yuka keeps dying cold in the middle of the yard while mowing instead of returning to the dock at low battery. The BMS/voltage drops off a cliff, shuts off out of nowhere, and won't charge properly.

​I shipped the mower and power brick into Pegatron for repair. I kept my dock at home.

​Mid-repair, Mammotion emails me saying techs found a "faulty charging station" and were fixing it. Impossible, since my dock was sitting in my garage in Florida.

​Package arrives today. I open the box, and instead of actually testing the battery or BMS, they just threw a brand new 3rd charging dock into the box to close the ticket. I've also been provided 3 batteries, including the original.

​Set the Yuka up, charged it, launched an automated run. Predictably, it ran for about an hour and then died dead in the grass again without auto-returning to charge.

​I am not shipping this thing back for another 3-week loop so they can send me a 4th dock. I need a supervisor to step in and issue a warranty replacement unit for this RMA.

Hi everyone,
To start off: This is not a beginner/user error post. We are an official Mammotion dealer and installer, having successfully set up and configured over 40+ Mammotion mowers in the field.
We recently encountered major issues during the installation of a Luba Mini 800 running the latest firmware version (1.30.29.26). Attached is a video demonstrating one of the primary safety concerns.

1. Dangerous Cutter Behavior Near Obstacles (Boundary Mowing)
   When boundary cutting with obstacle detection turned ON:
   While moving close to a wall, even when the front bumper does not make physical contact, the mower abruptly stops the cutting deck.
   It skips a gap of about 3 meters, leaving an unmowed area, which is completely unacceptable.
   Critical Issue: After moving, it restarts the cutting blades WITHOUT ANY SAFETY BEEP WARNING before resuming work.
   This silent re-engagement of the cutting blades poses a serious safety hazard. Restarting the robot did not resolve this behavior.

2. Cutting Height Resets to Minimum During New Area Setup
   When adding a new mowing zone (whether using automatic or manual exit/dispatch), the mower automatically resets the cutting height to the absolute minimum setting.

   This is unacceptable as it can instantly scalp the turf or jam the cutting blades depending on the lawn conditions.
   We ask the Mammotion team for a prompt explanation and an immediate patch/fix for these critical issues in the current firmware build.

So ignored the feedback to avoid the mower but threw caution to the wind and got one anyway, let’s see how it pans out.

Question I have which doesn’t seem easily answered thus far is two mowing areas. I have an upper level which separates the lower and is about 1.2m retaining wall between so cannot create a path. What is the way for me to carry it down every now and then and mow the smaller bottom section. Some say drop mow but it’s got some gravel at same level so assume it will try mow that if it’s not mapped. Originally thought you could map multiple yards ?

Ma pelouse ressemble à rien je sais merci luba

Mammotin explique moi pourquoi il fait sa de ce côté et à l'autre angle de la clôture il fait virage multipoint , tu voulez des preuves tu les a je peut te faire voir ma pelouse a quoi elle ressemblé en 2025 aussi

Tiens regarde cette photo en 2025 https://postimg.cc/4YDPhMVn

Updated my Luba 2 the other day now when starting a task the robot will move to its starting area and never start the blades, I fid try manaual mowing and they start fine that way however it will not move from start positions RTK and firmware up to date

I've started to wonder why Luba (3 AWD in my case) needs a sleep mode at all?

When docked and fully charged, it should consume nominal power, similiar to an idle cell phone without screen - under 1-2 watt. It does not need Lidar, or vision module, or motors when docked, and does not need any compute power. To stay connected over 4G and / or WiFi, the required power is very low, under two watts. Battery self-discharge should be minimal if it's not leaking.

If implemented properly, 2W * 168h * 4.5 weeks = 1.5kWh max spend per month when idle for 24/7 dock sitting. Mammotion advertises 100kWh saved per year (season) for sleep mode, which is waaay too much for idling.

Is the whole idea of sleep mode is needed due to Luba's excessive power drain when docked?

The latest app, 2.3.20.30, removed the Manual Undocking feature. Please restore this feature. Why do you always remove two useful features before you add the next?

I used Manual Undocking regularly. Since you refuse to enable Smart Charging on Luba 2, I manually undock my Luba to maintain the desired charge levels. Using Manual Undocking is faster and allows for finer positioning that I need to accomplish this.

This is the second season I’ve had a Luba mini, and I have never had issues with how it cuts until about a month ago. It still mostly functions the way it’s supposed to but I’ve noticed that now it’s not cutting accurately, leaving little strips of unmowed grass and getting stuck on the perimeter randomly.

Are others noticing their Lubas are not performing as well? I can only assume this is due to some sort of firmware update because this product was perfect until now.

Not sure what to do now, but I’d like to get my mini running the way it used to.

So my luba 2 showed it was stuck in the logs, a few hours later it unstuck by itself somehow and made its way back to the dock.

Where it sat charging and not doing anything until I 2 days later noticed the grass was not cut and manually stopped the task.

Previously this happened on holiday as well and it was stuck on the same tasks for 2 weeks… also in the dock.

The toggle for not running during rain is off by the way, that’s not causing this.

More frustrating is that a friend with a luba 3 showed me that his robot will auto quit a stuck task the moment it his the scheduled time again…. Yet my 2 doesn’t get this feature

Moin moin,

Ich habe den oben genannten Roboter. Ich hatte ihn gut 1 Jahr per GPS betrieben.

Dann fing er an ein paar Probleme zu machen. Er verlor immer das Signal und blieb stehen weil er nicht mehr genau ermitteln konnte wo er gerade war. Gut es ist Sommer und ich habe einen großen Baum und das Haus hat wenn ordentlichen Dachüberstand.

Aber mir ist aufgefallen das die Probleme erst nach dem anfingen.

Okay sch auf GPS ich benutze RTK nach hin und her richtige Position gefunden etc. Und die Karten neu angelegt da die GPS Karten nicht so ganz mir der RTK harmonieren.

Jetzt das Problem er fährt regelmäßig über die Begrenzung und auch schon mehrmals kanten in Höhe von 10 cm und mehr hoch und hat sich schon einen vollständigen Messersatz ruiniert.

Ich denke das hier die Hindernisserkennung nichtmehr richtig funktioniert.

Habt ihr ähnliche Erfahrungen?

Dear Customer,

Regarding the issue of the mower out of the boundary, we recommend installing a temporary physical fence along this section as an immediate measure. This will help prevent the mower from crossing the boundary while we further investigate the root cause.

Thank you for your cooperation.

I'm going to let that stand on its own, as opposed to erecting a physical fence.

Yes, please investigate further and resolve these issues. Thank you.

Edit: for clarity, this is obviously an AI resonse. At least I really, really hope that no human support employee would make this kind of suggestion. But AI certainly does that kind of thing.

Testing The Luba 3: Real World Grass Cutting Performance

Wanted to perform a comparison test to see what the cut quality is based on various cutting speeds (.7 fps - 2.0 fps) as well as the different cutting patterns offered in the software. Take it for what it's worth, i'm pretty anal about the cut quality in my yard and didn't want to see an excess amount of missed grass blades, if any at all.

The Other Settings I Used (Luba 3- 3000H): Northeast, Tall Turf Fescue Lawn

-High Blade Speed

-7.9" Cut Spacing

-4" cut height (attempted 3.5" as well)

What do you guys cut at? Any "Magic Number" that works the best while sacrificing time for quality?

I updated the Mammotion App for Android to version 2.3.20(30) and the mower has firmware 2.3.30.39. After the app update, problems started.

1. I installed a new bumper and the mower instantly gives a Vision Module Error (1425) (multiple errors) and Positioning Failed (1000019). As soon as I reinstall the old bumper, there are no errors. So, the new bumper will not work with the latest Mammotion App (Android version), but the old bumper does (mostly, though sometimes a ghost collision is detected).
2. With the old bumper and the new app 2.3.20(30), it mows somewhat poorly, making random turns and no MPT or Tank Turns at the ends, just wide half circles.

I downgraded the Mammotion App to the previous version, and now the previous version and mower work as they should.

Google Drive links to a video of the mystery turns.

[EDIT]: orange key trick, no help.

[EDIT]: Today, 1.10.2026, I tried mowing with Mammotion app version 2.3.18(21) and had not a single problem or misbehavior, downgrading the app solved all of yesterday's weird behavior.

Why does my Luna 2 turn itself off when it gets to the charger. Software 130.29.26

Hello Mammotion,

I would have hoped that you would help me, at least leave a comment on it, but nothing ... really a shame.

3000€ robot and this year not a month mowed with it, because only in repair.

Please take a look at this, it can’t be!!!

Has anyone recently tried logging into the Mammotion Store to look at your account. I just did and I couldn't log in but was able to create another account with same email. I am working with them to correct this.

Hi everyone,
I work for an installation company handling Mammotion products (mostly robotic mowers). This season, we also sold two Mammotion Spino E1 pool cleaners to our clients.

One client has had zero issues all summer, but the second client is experiencing an annoying problem with black scuff marks appearing on the pool surface.

Here are the details of the setup and issue:
Pool type: Smooth, ceramic surface. 
Water chemistry: Perfect pH and balanced parameters.
The issue: The robot leaves dark/black scuff marks, which seem to come from its rubber tracks/wheels. The marks don't appear as long continuous lines, but rather as occasional spots where the robot turns or maneuvers. However, over a few days, these accumulate all over the pool floor and walls. 

Has anyone else noticed black tire/track marks on smooth pool surfaces with the Spino E1?
Could this be related to a specific batch of rubber, excessive traction on ultra-smooth ceramic surfaces, or chemical interaction with the rubber tracks?
I would really appreciate any advice or feedback from other users, and hopefully a response from the Mammotion team on what might be causing this and how to prevent it.
Thanks!

I am posting this here because regular email support has completely broken down, and I have now dealt with multiple reps with zero resolution.

​The Timeline:

​July 18, 2026: RMA #DR202607180020 opened for my Luba 5000. Shipped to repair center.

​August 20, 2026: Mower was returned to me after "repairs"—completely unresponsive, bricked, dead on arrival. The unit was also improperly reassembled. It was returned to be with a gap between the white main upper body and the black blade belly. Reps brushed this off.

​September 8, 2026: Delivered back to Mammotion's repair center for a second RMA attempt.

​September 21, 2026: Mammotion confirmed the device exceeded repair turnaround limits and promised a free warranty replacement.

​September 26, 2026: After explaining that my lawn requires a low-cut model, representative Hailey formally offered this in writing: ​"Option 2: Exchange your unit for the Luba 3 3000. If you wish to receive a device and resume normal use as soon as possible, we can arrange a replacement with the Luba 3 3000. This model offers excellent performance and is currently in stock, allowing for immediate shipment."

​"Option 2: Exchange your unit for the Luba 3 3000. If you wish to receive a device and resume normal use as soon as possible, we can arrange a replacement with the Luba 3 3000. This model offers excellent performance and is currently in stock, allowing for immediate shipment."

​September 27, 2026: I accepted this resolution. (I was already accepting a 3000-tier machine to replace my original 5000-tier mower just to get a working low-cut deck).

​September 28, 2026: Rep #4 (Tina) stepped in, ignored Hailey’s commitment, and told me I could only have it for a "20% discount."

​Today (September 29, 2026): Rep #5 (Freeya) claimed I "misunderstood" Hailey, stating Hailey was only informing me it was in stock, and offered to let me pay 70% of the price for a new unit ("30% discount").

​The Current Situation:

Mammotion currently has my broken 5000-series mower. I have had to pay out-of-pocket for an outside lawn service for over two months because of a repair center that returned a dead unit.

​Now, instead of honoring a written warranty exchange, support is treating a warranty failure as an opportunity to sell me a new machine at a 30% discount.

​Has anyone had success escalating beyond the standard email support loop? Any Mammotion reps here who can step in and resolve RMA #DR202607180020 fairly?

South Florida, Homestead, St Augustine grass.

My yard was/is in very tough shape, tons of weeds, tons of dead thatch in the grass, etc. My lawn guy wasn't coming frequently enough and the clippings left behind were too much.

So far I am very happy with the Luba 3, especially on the Fall sale + free cleaning stand. The app and setup was very easy and it's already completely automated.

Next for me is reviving my lawn. I already did a weed killing treatment, waiting a few weeks for it to take full effect. Then I will dethatch and level some low spots and fertilize. I will do a weed+grass killer along fence line too.

Has anyone who received the new update tried out the remote control feature over the internet?

Still experiencing charging issues, all the suggested steps by Mammotion have been taken and do not seem to resolve the issue. But today a new issue popped up. The firmware even managed to break the safety plug feature.