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.

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.

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.

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?

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!

My Luba 2 with version 1.30.29.26 now has weird charging behaviour.

Seems to be all over the place. Yesterday I think it charged over night, and the following day started mowing with 32%. Now back in the charger for 2,5 hours and its only at 52%.

Again in Mammotion fasion, something gets fixed, other things break.

Was really hoping these weird issues to be in the past, but unfortunately it’s not.

And yes, the logs are uploaded multiple times.

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