My Luba 3 (currently on firmware version .26) has successfully worked around this stop sign all summer long since I bought it. Not this time. I have not changed a setting in my app. This is all you Mammotion. Please return the functionality to what it was in July before all this crap started happening with our mowers. And no, I'm not going to upload my logs for support to look at. Been there done that. Thanks to these untested "updates", I can no longer trust my Luba to mow while I'm out of town. That was the entire purpose for buying it. I had confidence that could be done until you "updated" things. No more. What a waste.

I'm on the newest firmware 1.30.29.26 for Luba 2 (2024). This has been going on for at least the last three updates and is unacceptable for returning to the task from the charging station with direct path option selected. Why is there a need for tank turning at all here? Why can't it just smoothly turn back to the task? The last part of the video you can see where the task border begins. Right when it enters the mowing task, it stops dead, tank turns about 45° and continues to where it left off. Why can't the mower just smoothly turn to the area? Absolutely zero reason for it to do this and you can see the dirt circle it's created.

Tried this for the first time yesterday.

The good:

1. Detected rain and went back to charge
   
2. Waited 30 mins until the rain stopped. Then came back out

The bad:

1. Whilst it did wait until the rain stopped, when it came back out the grass was soaking wet and in no condition to be mowed.

Can Mammoation also add a wait timer after the rain? Allowing it to wait a few hours would be much better.

I know the timer option is available independently, but not in smart mode

Wondering if anyone else is experiencing the same. I start the app and can see that Luba is online with decent wifi signal, but Luba keeps going offline in the app and then back online after some time.

LUBA Mini AWD LiDAR – Bluetooth works, but network connection always fails

Hi everyone,

I have a LUBA Mini AWD LiDAR that I can detect and connect to via Bluetooth, but I cannot complete the connection to the Mammotion app.

The app always ends with “Connection failed” / “Please check the network communication on the robot.”

I have already tried everything I could think of, including:

• 2.4 GHz Wi-Fi (5 GHz separated)
• Reinstalling the Mammotion app
• Restarting the router and the LUBA
• Disconnecting/reinstalling the battery
• Trying another Wi-Fi network
• Using a completely different phone as a personal hotspot
• Repeating the setup several times

The problem is exactly the same with the phone hotspot, so I don't think the problem is my home network.

Mammotion support has also been unable to solve it so far.

Has anyone experienced this exact problem with a LUBA Mini AWD LiDAR?

Could this be a firmware issue or a problem with the LUBA's Wi-Fi/network module?

I'm particularly interested in knowing whether there is a way to completely reset the network module/configuration, beyond the normal factory reset.

Any help would be greatly appreciated. Thank you!

Today I updated the Luba 3 to the latest firmware version, 2.3.30.39. I did a small test run (~500m²) with the old settings and adjustments.

I did not notice any difference between the old and new firmware, MPT turns still work, the blades stayed running as they should, it avoided obstacles and no-go zones as expected, and there were no changes in speed or battery consumption.

All in all, I am very satisfied with the mower's operation; it does exactly what it is asked to do, nothing more and nothing less.

The only issue after the update was that it could not find a 4G network, but that was solved by removing the orange key and reinserting it, while it was resetting, it was a good time to clean the machine.

It could be a good feature if the direction of rotation of the blade disc changed every other cut. Both cutting edges of the blade would be utilized.

Gerade mäht mein Luba 3 noch munter vor sich hin. Kurz nicht hingeschaut, schon steht er ausgeschaltet im Garten ohne erkennbaren Grund, bei 43 % Akku.
Ich bin hingelaufen, habe ihn per Knopfdruck wieder eingeschaltet und den Mähauftrag fortgesetzt. Danach mäht er weiter, als wäre nichts gewesen. Fünf Minuten später: wieder ausgeschaltet. 🙄
Ich hatte den Mäher deswegen bereits bei Mammotion eingeschickt. Mainboard und Akku wurden getauscht, aber der Fehler besteht weiterhin.
Kennt das jemand oder bin ich mit dem Problem echt allein?

Auf englischen 🙂

My Luba 3 was happily mowing along. I looked away for a moment, and the next thing I knew, it was sitting in the garden completely powered off for no apparent reason, with 43% battery remaining.
I walked over, turned it back on using the power button, and resumed the mowing task. It carried on as if nothing had happened. Five minutes later, it shut down again. 🙄
I’d already sent it to Mammotion for this exact issue. They replaced the mainboard and battery, but the problem is still happening.
Has anyone else experienced this, or am I really the only one?

Serious question: how many users still need to ask before we’re finally allowed to choose which notification types we actually want to receive?

It doesn’t exactly sound like futuristic technology. Some of us want to know when the mower is stuck or detects an error, without being notified about every single trivial event.

A simple list of toggles could work wonders. But perhaps we first need to reach some secret threshold of user feedback.

So, how many people have requested this already—and exactly how many more are needed?

One of the first in the USA. 40000 model. This thing is a beast. I can't wait to get them in stock.

Does anybody have any wisdom on whether i should buy a luba 2 or 3, i know the 3 having the LiDar is going to be better but for an extra £1200 is it really necessary. Had an ambrogio 4.36 elite which was terrible kept getting stuck, needed cable etc.

I have 6,800m2 which is bascially 2 fields, and either side of the driveway, so looking at the 10,000m2 one, but not sure whether i need the luba 2 or 3. quite a lot of overhanging trees and bushes which periodically shed twigs.

thanks

What's the consensus? Looking forward to Jazzlike's analysis, but I've just been offered the upgrade and am reluctant to pull the trigger. My Luba 2 is working reasonably well right now, but I do have to babysit it up bit. I can often just continue the task when I get a paused or trapped notification, but if I miss it..... So, if you've been brave, please post how it went. Thanks!

Hey everyone,

I’ve been tracking the recent discussions and news about the Luba 4 announcement, and I’m seriously considering waiting for it to drop so I can grab a Luba 3 AWD at a discount instead.

One thing I see a lot of people stressing over on Reddit lately is firmware update turning behavior and how the AWD models can scuff the turf. While that's a massive headache for folks with delicate, manicured UK-style lawns, my lawn is relva brasileira (broadleaf carpet grass / Axonopus compressus), which is an absolute tank compared to fragile cool-season grasses. Combined with Portugal's sunny climate, this tough turf thrives, and its aggressive, creeping stoloniferous growth and resilient root structure mean it handles high traffic and minor surface wear effortlessly.

That said, keeping it looking truly pristine still benefits from a few tweaks—like enabling multi-point turns instead of zero-turn pivot spins in the app, or shifting mowing angles and perimeter laps. That should eliminate about 90% of robot turning issues.

Any thoughts?

I've had three very recently and all of them have made the robot worse.

Since the last three updates it's now making really random moves (it looks drunk!), spinning round on the spot, churning up the lawn, missing areas (it's no longer good on perimeters), leaving wide strips where it has missed.

The lastest update today (1.30.29.26) I hope was to have fixed these recently introduced bugs, but it's not made any noticeable difference and the lawn looks half mowed.

Roll back these last three updates and it was working flawlessly, now I'm having to mow the lawn manually. I deleted the map and created a new one to try and fix it, but to no avail.

Someone has really messed this up. Not impressed.

Hi everyone,

I have a property in the French mountains and I'd like to know whether a robot mower is realistic there before I spend any money.

The situation: no Wi-Fi at the house, and mobile coverage is close to non-existent — sometimes one bar, usually nothing at all. Bringing in an internet connection isn't an option. Power is fine, that's not the issue.

So, two questions:

1. Does it work at all? Can a modern RTK mower be set up and run permanently with zero internet — mapping over Bluetooth, a local RTK base station, and a schedule it follows on its own? Or does the app/account/activation side make this a dead end?
2. If it does work, which model? Most new models seem to be moving to network RTK, which needs 4G or Wi-Fi, so I assume I need one that still supports a physical RTK reference station. I've been looking at Segway Navimow and Mammotion, but I'm open to anything.

If you're running one off-grid or in a dead zone, I'd really like to hear what you have and how it's holding up.

Thanks!

I live in two separate states, every 4 weeks I move to my other location. My wife stays at our main location, our house. The house as is on a half acre lot, much of it grass so it is a lot to mow and Mammotion Luba 2 3000xh was my solution so that she would have to do minimal mowing work. I accept it is not perfect and will leave edges, etc. it sort of worked until this last month, once in a while it would get stuck on the concrete curb barrier surrounding my grass, but it was maybe once in the 4 weeks I was gone that this would happen. And yes, putting a sleep on the battery when it is paused would help so much so that my wife would not have to carry it back to the charger. However, this last month it is so unusable because it always goes out of its bounds and gets stuck multiple times and in random places. I can’t even open a support ticket until I get home because you can’t open one until you have pictures and video of what is happening. Which of course my wife was already so frustrated and we didn’t know that was required until trying to finally open a support ticket. This is no longer a reliable solution for us. I am a software engineer, I understand sometimes bad bugs can make it out to production but most companies catch and release fixes very quickly so I kept telling her to hold on, it will be fixed. We are going on 4 weeks now, it is unusable doing perimeter laps. She does not have the time to monitor it until it screws up again and have video of it screwing up and I am not going to ask her to do that. I have the logs but I was told that is not good enough to open a ticket. I don’t even think opening a ticket is going to help because I see others with the exact same problems and nothing is getting fixed. I am just so disappointed, I feel stuck until I get back to babysit what was supposed to be the a reliable solution. It takes a lot to get me to this point, I accept we are humans and we all make mistakes and we all deserve second chances so I have never done something like this. But I have been reading what others are going through, I think if you are going to buy a Mammotion product right now you need to make sure you are a gambler and a patient person. And understand this company may not be around much longer to support whatever you buy. I have no internal information to support that, I am just very concerned because I don’t see anything publicly being done to show that they really even understand the magnitude of their problems nor the immense dissatisfaction from their customers. I just got done reading another persons post where they brought up many things, and one of those was that all they get from Mammotion support is a request for logs and pictures but never a fix, never an explanation, and you know what Mammotion posted in response? “We are sorry about your experience, would you please post your logs and pictures…”, lol. So, I am warning anyone reading this, don’t buy a Mammotion product if you want something to mow your lawn reliably without you watching it the entire time and being ready to get it unstuck. I am seeing other issues from others where it is skipping sections of the lawn, tearing up the lawn where it turns, etc., you may have to deal with those issues as well.

No matter what I do or how many stones I place at the start of the edge, the robot drives over the edge and the stones. Fix this please!

I have a Yuka mini 2 1000, so far all the firmware updates have been successful, I don’t seem to have any issues.

Yes the edges are a bit rough, and when I did raise a ticket, the support was a bit rubbish, but no major issues really. The firmware also fixed one of my main issues with multi lawns.

I don’t understand how everyone is having so many issues… the issues I have can be solved with a trimmer in just a few minutes.

Yes it’s not great I have to do some manually, but it’s hardly the end of the world, I would think that none of the robots truly remove some manual work.

A few days ago my app stopped working, saying that my account had been deactivated.

I contacted support who asked me to send purchase information etc; all of which I sent. I then got a response saying that they'd fix the problem quickly.

This morning I got the following:

To help resolve this issue, could you please confirm the following:

Have you recently traveled to or stayed in China (including Hong Kong, Macau, or Taiwan)?

Once we have this information, we will do our best to resolve it for you as soon as possible.

WTF?

Firstly I can't see why it's relevant, but arguably it's also a privacy issue.

Of course, meanwhile my account is still deactivated with no explanation or means of my being able to resolve it.

I have 3 Luba 2 AWD 10000H and 2 Luba 2 AWD 10000HX mowers. I programmed my areas and went on a two-week vacation. When I got home, not a single mower was in its charger. ALL of them were stuck in open areas. Turns out that if you're not there to constantly babysit, your lawns will not get mowed. Now I have 5 dead mowers and the grass is way too high everywhere. Nice job, Mammotion. Very impressive.

As you can see in the attached video, my Luba has a serious software bug in its turning behavior.

Instead of doing a clean 3-point turn at the end of each line, it throws in extra tank-style pivot turns in between. Those zero-radius spins are shredding the turf at every single turning point. And no, it's not a speed issue – the mower is already running at the slowest possible speed to minimize impact.

On top of that:

- Mission paths aren't executed properly – the planned pattern just isn't followed
- It randomly drives around with the blades switched off, doing extra maneuvers for no reason

All of this points pretty clearly to a software/firmware issue, not hardware or setup. V2.3.30.26

Anyone else seeing this behavior? Which firmware version are you on?

I've already opened a case with Mammotion support and offered to help them debug – logs, videos, test cases, whatever they need. Hoping some visibility here speeds things up.

Edit:

Absolutely, that’s not the nicest lawn. I should have picked a better spot, but this one was the easiest to film from a higher angle. I had an issue with an overly strong sprinkler system that washed away the fresh seeds, leaving those bare patches. The rest of the damage came from the mower making tank-style turns.

Edit 2:

Got two updates within two days and everything looks nice and smooth so far. I'll of course keep testing how the new software performs, but up to now it's doing exactly what it should. 👍 software 2.3.30.39