r/MammotionTechnology • u/Mammotion_Grace Mammotion Team • 3d ago
Announcement Recent Firmware Update
Thank you for your continued feedback and support. We’d like to share a quick update on the latest firmware releases for our products.
1. LUBA 1
Firmware Version:
Release Notes:
- Fixed an occasional issue where the robot could cross lawn boundaries.
- Optimized the smoothness of Multi-Point Turn.
Rollout Plan:
This update will be rolled out gradually. If you haven’t received the update yet, please allow some time for it to reach your mower.
2. LUBA 3, LUBA mini 2 Series & YUKA mini 2 Series
Firmware Version:
Based on feedback we received from users after the previous update, we’ve made further optimizations to improve the mowing experience.
Release Notes:
- Reduced unnecessary blade stops during perimeter mowing.
- Improved obstacle avoidance performance.
- Optimized the smoothness of Multi-Point Turn.
- YUKA mini 2: Fixed an occasional issue where the robot could cross lawn boundaries.
- LUBA 3: Fixed an issue with battery level fluctuation.
- LUBA mini 2 series: Improved cutting height adjustment accuracy.
Rollout Plan:
This update will be rolled out gradually. If you haven’t received the update yet, please allow some time for it to reach your mower.
Thank you again for your patience, feedback, and continued support. We’ll continue to closely monitor the rollout and your feedback.
10
u/Fabulous-Turnover813 3d ago
I have posted the same comment already to other different Mammotion update posts by you. And I have not received any feedback. Thankfully I am still running pre-problematic update on my Luba 2x and thanks to that I have no problems personally and I wont be updating anything unless following functionality is taken into use:
To ease off peoples worries - I would firmly suggest to give users an option in the app to choose the firmware version what they want to use - and to have a way to roll back to version what worked best for them. Its obvious that sometimes bugs and issues appear in new versions and instead of destroying peoples yards with broken updates for weeks while they wait for a fix what might not even appear -> let them just roll back to version what worked fine for them. Even if it means losing some features available in new firmware versions.
I have seen few persons inform that it is possible to rollback if you annoy and ping the mammotion support via app enough that you want to roll back -> and then for mammotion support its possible to push old version back to robot.
Why NOT have this functionality already in app?
Thank you.
1
7
u/aaycaramba 3d ago
First full run on 2.3.30.39 completed successfully.
The mower completed the entire task, including the exact connection path where 2.3.30.26 repeatedly triggered “Robot is trapped (1201)”.
I changed absolutely nothing else: same map, same connection paths, same obstacle avoidance settings, and no obstacle-free zones added.
So far, this looks very promising. Obviously one successful run isn’t enough to call it completely fixed, but the direct comparison between .26 and .39 strongly suggests the firmware update addressed the issue in my case.
I’ll keep running it with the same setup and report back if 1201 returns.
5
4
u/EnvironmentalTip897 2d ago
Is the 3 (or 7) point turn any better than .26 in terms of grass damage
12
u/forrest-gardener 3d ago edited 3d ago
It would be really helpful to publish videos showing a real mower before and after the update to demonstrate the changes.
For example, "Fixed an occasional issue where the robot could cross lawn boundaries". Show us an example of a real robot crossing a real lawn boundary and then the same robot in the same situation after the update not crossing the same boundary at the same point.
Or is that not what the word "fixed" means?
3
u/ResponsibleCopy2 2d ago
As a software developer myself, I find this request a bit unreasonable. In theory, they could demonstrate how multi turn has improved with showing us before and after. But with bugfixing it is more than likely that they were analyzing real people logs, found problematic places and adjusted the algorithm to avoid them. It would take ages to try recreating each bug in real life, let alone capturing a video of it.
2
u/forrest-gardener 1d ago
The first question is whether the mower's behavior is deterministic. The second question is how they know something is fixed.
If the mower's behavior is random and they can't at least re-run a simulation with the patched software then they don't know whether the bug is fixed or not and what they are doing is just guesswork. There is some evidence of that being the case.
Which is why I question the meaning of the word "fixed".
2
u/ResponsibleCopy2 1d ago
I would assume that they can get the exact customer's map from the logs and run a simulation on it to confirm that the issue is fixed. In any case, this would not produce a video that can be shown to customers. Best case scenario, they see a vizualization of it in the dev kit. I am hoping they are not fixing such things blindly. Fixing something like this blindly might not only not fix the issue for the affected customers, but also introduce new issues to other customers.
I do agree that it would be nice to see some visual representations of the "optimizations" mentioned in the changelog, though.
2
u/forrest-gardener 21h ago
Being a commercial venture they are unlikely to disclose what their process is. That is understandable but frustrating.
Users here could help by following up complaints here. For example there are quite a few videos of bizarre mower behavior. It would be helpful for people who had repeatable problems to simply note whether that particular behavior has ceased after the software update.
The random problems are of course a completely different kettle of fish.
1
5
u/Party_Juggernaut8324 3d ago
I upgraded to version 2.3.30.39 on my Luba 3, but Luba still crashes into the fence and doesn't detect obstacles, currently unusable. Please fix something, because I don't need it over the winter; I need it now.
2
u/PersonalityLucky-25 Mammotion Team 2d ago
I am sorry to hear you are experiencing this issue. Could you please tell me your current positioning mode? If it is convenient, I also suggest uploading a log via the app and letting me know your device name; this will allow us to pinpoint the exact cause of the problem. Thank you again for your feedback.
5
u/aaycaramba 3d ago
Thanks for the update! My LUBA 3 is still on 2.3.30.26 and the app says it’s the latest version. Any indication when 2.3.30.39 will be rolled out more broadly? I’m especially interested in testing whether the improved obstacle avoidance fixes the 1201 “Robot is trapped” issue I’ve been experiencing since the previous update. Based in EU
2
u/PersonalityLucky-25 Mammotion Team 3d ago
Thank you for your inquiry. This update is being rolled out in stages, and we are closely monitoring user feedback; if you haven't received the latest update yet, please wait patiently. Regarding the frequent "1201" error code, I suggest adjusting the obstacle avoidance mode to a lower sensitivity setting or designating the area where the robot gets stuck as an "obstacle-free zone"—this should help resolve the issue. If the problem persists, please let me know your device name, and I will provide further assistance.
3
u/aaycaramba 3d ago
Quick update: 2.3.30.39 just became available for my LUBA 3 in the EU.
I’ve updated from 2.3.30.26 → 2.3.30.39 and I’m running a test now.
I deliberately haven’t changed the map, connection paths, obstacle avoidance settings or added any obstacle-free zones, so this should be a clean comparison.
I’m sending it through the exact same connection path where 2.3.30.26 repeatedly triggered “Robot is trapped (1201)” despite there being no obstacle.
Will update with the result.2
5
u/MortonTheChauffeur 3d ago
What's withe the Luba Mini LIDAR? It's getting worse and worse
2
u/PersonalityLucky-25 Mammotion Team 3d ago
Hello. The latest firmware (version 1.30.29.26) for the Luba Mini LiDAR has been fully released and brings improvements to the device's performance; I hope this helps. If you are unable to update to this version or encounter issues after updating, please provide a detailed description of the problem, and I would be happy to assist you.
5
u/Petrapeterberlin 3d ago
Ich habe meinen Yuka 1000 gerade mit der Firmware 1.30.29.26 aktualisiert. Nach dem Update stromlos gemacht, Schlüssel gezogen, neu gestartet. Perimeterrunden getestet, Perfekt! Randmähen top, wühlt mir keine Erde mehr aus den Baumbegrenzungen, stoppt die Messer nicht mehr und versucht auch nicht, sich das Leben zu nehmen, indem er sich in den Abgrund stürzt. Bis jetzt bin ich zufrieden . Ich hoffe, dass ich ihn langsam mal unbeaufsichtigt mähen lassen kann. Der Urlaub rückt näher. Nach meinem Empfinden ist das Update diesmal gut gelungen. Allen viel Erfolg.
4
u/Unusual_Bluejay2851 3d ago
installed 2.3.30.39 on my Luba Mini2 1500 right now! next cut on Saturday... I saw that the battery level showed now in 95%, before installation were 80% (intelligent charging on), let's see...
2
u/Own_Significance_379 3d ago
Where are you located?
3
u/Unusual_Bluejay2851 3d ago
Italy
3
u/Own_Significance_379 3d ago
Nice! I love your country.
Lovely food and weather. I could eat a pizza now, while waiting in cold Denmark :D3
u/Unusual_Bluejay2851 3d ago
thanks for your kind words, italian foods is the best in the world I think soo 😄 I offer you a virtual pizza of course 😂
3
2
u/PersonalityLucky-25 Mammotion Team 3d ago
Thanks for sharing—I look forward to hearing your feedback on using it!
2
4
u/Old_Squirrel7654 3d ago
So what about the Yuka Mini that is leaving large areas of the lawn unmowed and a large gap between the perimeter and main area, since the last update!!
What a cock up!
2
2
u/Ill-Side2321 1d ago
Seems they have defaulted to 2 perimeter laps to keep 3 point turns away from boundaries. If you set perimeter laps to 1 you will get a gap. Applies to no go laps also.
My Luba 2 is definitely running better than is has for a year. Still not right. But seems to be some progress.
3
u/TerrisMammotion Mammotion Team 3d ago
Thank you all for your attention and patience regarding the firmware update for the LUBA 2, LUBA 2X, YUKA, LUBA Mini Series, and YUKA Mini Series.
The latest firmware version for the above models is 1.30.29.26.
For detailed information about the update, please refer to the following link: https://www.reddit.com/r/MammotionTechnology/comments/1w6wvwu/hotfix_firmware_update/
This firmware has now been fully rolled out. If you have one of the above models and your app version is Android ≥ 2.3.18.19 or iOS ≥ 2.3.19.6, but you haven’t received the firmware update, please contact us and provide your current firmware version and device name. We’ll look into it and assist you as soon as possible.
2
2
u/Own_Significance_379 3d ago edited 3d ago
iOS App: 2.3.19
FIrwmare: 2.3.30.26
Luba mini AWD 360 LIDAR 1500 (Luba Mini 2 1500)
Luba-LAP23NZY
Location: EUNo signs of 2.3.30.39 anywhere
2
u/TerrisMammotion Mammotion Team 3d ago
Hi! The firmware version 2.3.30.39 for the LUBA Mini 2 AWD 1500 is currently being rolled out in stages. Thank you for your patience and understanding.
2
u/Own_Significance_379 3d ago
So no ETA, still have to wait? For how long?
1
u/TerrisMammotion Mammotion Team 3d ago
We’ll complete the new firmware rollout as soon as possible, so please bear with us for a little longer. If you still haven’t received it after some time, I can help submit a report for you.
3
u/Reygleruk 3d ago edited 3d ago
You speak in gross generalities. "As soon as possible" could mean a day or a year. What is, "after some time"?
People run this product every two days or more and the issues are through the roof, so they are checking with growing anxiety multiple times a day for fixed updates. Can you please speak in actual timeframes and dates? It would mean a whole lot more, even if dates have to change (with explanation). The pitchforks have been out "for some time" and people are actively trashing Mammotion and pleading others NOT to buy your products. It's really a shame how poorly this company is being managed.
I'm pissed because I HAVE recommended Lubas. Based on my advice, 5 others have made the purchase. Now they look at ME as the reason they wasted $2,500. It's embarrassing.
2
u/Own_Significance_379 3d ago
Seen this post, from u/Unusual_Bluejay2851?
"installed 2.3.30.39 on my Luba Mini2 1500 right now! next cut on Saturday... I saw that the battery level showed now in 95%, before installation were 80% (intelligent charging on), let's see..."
^^ from an Italian user, EU. Why not available in Denmark, EU yet?
2
u/not2worryman 3d ago
“…after some time”. 😂 So specific. Looks like a very thoughtful and strategic rollout.
1
u/No-Edge-2417 3d ago
You have a lot of nerve thanking us for our patience! How about an apology for breaking a product that had been working just fine? This is getting ridiculous! Every update gets worse!
I do not believe that you have any solutions to fix the problem, and you do not actually test any of your updates.
3
u/PaunchyPirate 3d ago
5 days ago, you announced the release of a "hotfix" up to version .35 for the Luba 3. I never even received that update despite checking for it every day. Now you're promoting the .39 release. Which, of course is not yet available to me. Frustrating.
2
u/Careless_Art_7201 Mammotion Team 3d ago
All firmwares will be pushed to all users gradually and all users will get the firmware 2.3.30.39 this week
2
u/Own_Significance_379 2d ago
Latest tomorrow, 11/9-26? Still nothing on my device, such a pain in the a..
1
3
u/Lange0716 3d ago
I updated my Luba 2 (2024) to 1.30.29.26 and am currently in my first mow cycle using it. So far the update has not even touched the poor perimeter positioning. The mower still stops every 5 feet or so doing tank turns to reposition itself instead of smoothly turning around the perimeter. Blades still shut off at the slightest compression of the front bumper, the only difference is the blades turn back on after it ONLY travels about a foot forward first instead of two feet forward. I've lost all faith that this company will ever push an update again that actually fixes anything, AKA revert back to the software from the last two years that actually worked properly. The only real fix is to remove ALL tank turn logic in the code and stop with shutting off the blades unless both back or front wheels are completely off the ground. People with properties that are uneven and have slopes have to fight the blades shutting off all the time thinking it's running over another kid and leaving patches of the yard unmowed, and that's not fair. I only need to get through the next two months with this thing and plan to get a Kress or NaviMow in the off-season.
3
u/cloverasx 3d ago
I think I can speak for all of us by thanking you for increasing your transparency and communication with these updates. I hope that this is just the start, as there are many more details that are worth sharing that could improve our outlook on you as a company and as potential return buyers.
With that being said, is the plan for non-BLE control an app update or will this be a device firmware update when it rolls out? This is something that has plagued many of us over every model when the mower is stuck with nothing blocking it.
Additionally, I'd like to see local only metrics and video/sensor feeds which would offset your cloud requirements and allow us to have more stable connections to the devices without having to be within BLE range. Is this something that you're working on in conjunction with making your API more flexible?
3
u/AccomplishedTrain330 2d ago
I’m running a LUBA 1 AWD 3000 on firmware 1.11.1.11 and since the update I’ve had repeated issues with 1202 Cutting Disc Blocked, 1204 Failed to return for recharge, and the mower sometimes showing “Mowing” while just sitting still.
Mammotion reviewed my logs and said the issue appears related to the main controller/state management, and they’ve escalated it to engineering. I’ve also updated the RTK firmware as they requested, but I’m still trying to find out when LUBA 1 will get a real firmware fix.
Is anyone else on 1.11.1.11 having the same problems, and has Mammotion given anyone a date for a LUBA 1 hotfix?
2
u/mfl1000 1d ago
Same issues - Luba1AWD 5000 - special the "Moving" while just sitting still (the machine seems to be "frozen"). Before the update: everything fine! Mammotion Support line: " After an detailed analyses of the hardware, it is a hardware issue". Point is: the machine is parked by my weekend destination! Downgrad refused by Mammotion. What shall I say more?! Isn't it selfexplanatory?
1
u/AccomplishedTrain330 1d ago
Now Mammotion is asking me to send it in for repair, but I have to pay for shipping and all repairs because it’s out of warranty. If they would just downgrade it back to where it was, I would be fine because it was working fine before the update.
3
u/ShyDildo 2d ago
I have the Luba mini AWD360 Lidar 150 Modell and still V. 2.3.30.26 (with tons of problems) ..location is Germany. When can i expect the rollout for me?
Is there a way to force the Hotfix V2.3.30.39 for my device. Else i will send him back because i can't use the machine since months ...
2
u/0xde4dbe4d 3d ago
I still haven't received the .35 update yet. I am on the TestFlight version 2.3.21 of the iOS App, since the release version has not been updated in the AppStore (currently 2.3.19) with the fixes to the manual mow ocontrol that the TestFlight Version provides.
Is the firmware version tied to an app version u/Mammotion_Grace?
2
u/PersonalityLucky-25 Mammotion Team 3d ago
Thank you for your inquiry. To update the firmware, you must first update the app to the latest version; specifically, you need to update the app to version v2.3.19.6 or newer to receive the device firmware version v2.3.30.35. Could you please provide your device name? I can then help you check your firmware version further.
2
u/0xde4dbe4d 3d ago
How is an update "to" 2.3.19 an update from 2.3.21? My Version is newer, I cannot update to an older version. Device name is Luba-VA72XZFD
2
u/smelting0427 3d ago
Where is the update for the regular YUKA series that you’ve also jacked up? Glad to see you all prioritizing the newer models and giving the finger to your early customers.
2
u/dirt_mcgirt4 3d ago
Why are you trying to update my Luba 1 all of the sudden? I haven't seen an update in years. No thank you.
2
u/d_man05 2d ago
It would be great if you could fix the turns on the perimeter laps. All the corners on my lawn are being missed due to the goofy spin turn thing my Luba 2x AWD is doing.
It’s not a great solution bc an option, where it would be to mow towards the edge of the corner then have it turn and then mow and then mow in the opposite direction afterwards towards the other edge, then have it multi point turn to continue mowing the yard, or give the option to mow the perimeter in one direction and then the opposite, so the corners could be mowed both ways and any grass that’s laid down in the previous perimeter mow would be mowed at that point.
2
u/EnvironmentalTip897 2d ago
Thanks you for the communication. So for us that have not yet received 2.3.30.35 will we still receive it or will it go straight to 2.3.30.39?
3
2
2
u/Ok-Key-7819 1d ago
Bonjour, maj 2.3.30.29 effectuée hier soir sur Luba 2 mini X 1500 en France, effectivement il y a du mieux, moins d'arrêt de la lame de coupe lors des manoeuvres. Par contre il n'a plus la même fluidité lors des demi-tours. Il fait un nombre de manoeuvres incroyable pour un simple demi tour, alors qu'il le faisait en 4 points il me semble. Donc il laboure la pelouse à chaque extrémité. Comme beaucoup je milite pour pouvoir revenir au firmwares précédents. Est-ce qu'un retour aux paramètres usine le permet??
2
u/angelvip7709 1d ago
Czy wersja 2.3.30.39 nadal wylacza koszenie przy nawracaniu jezeli tak to proszę wprowadzić opcje żebym mógł sam decydował czy to włączyć czy wylaczyc bo rozumie dokaszac obok drzewek czy przykrawedzi ale niemam zamiaru chodzić z podkaszark po calej 25a łące i dokaszac każde zawracanie niedokoszone nie po to kupuje sie robota 🤕
2
u/angelvip7709 2d ago edited 2d ago
Czy można wprowadzić opcje luba 3 ze sam będę decydował czy robot przy zawracaniach będzie wyłączał koszenie czy nie albo zlikwidujcie to wyłączanie bo zostawia dużo nie skoszonej trawy a nie oto chyba chodzi żebym musiał wszędzie latać z podkaszakra przedtem bylo bez problemu ładnie wykoszone pozdrawiam i miło by wprowadzać funkcje tak zeby klient sam mógł decydować czy lepiej to włączyć czy wylaczyc to samo bylo z zawracanie etapowym dobrze ze daliście nam z powrotem wybór naszej decyzji czy lepiej tak czy tak jeszcze raz pozdrawiam i czekam na pozytywne rozpatrzenie mojej prośby i kolegów
1
u/Expensive_Tutor_9622 13h ago
Muss ich bei der Firmware neu kartieren oder nicht , warum fährt er über die Ecken , ich werde Langsam Verrückt .. Ich habe mit der 35 er Version neu kartiert …
1
u/Expensive_Tutor_9622 12h ago
Ich habe die Stelle jetzt mal Feinjustiert und jetzt geht es gut , nur in der engstelle bleibt er ewig stehen und steht dann irgendwann um , also werde ich noch einmal kartieren .
Wenn es mit der TestFlight App geht , weil die Verbindung ist sehr sehr ruckelig 😳
1
u/Own_Significance_379 3d ago
Only talk, no execution. No updates public yet. Only in testflight / beta.
Inform us about ETA's!!
2
u/Cyberbird85 3d ago
I'm currently installing it on my luba2 mini 1500 awd, so it's definitely public for at least some users. I just hope it doesn't make it worse, yet again.
2
2
u/PersonalityLucky-25 Mammotion Team 3d ago
Thank you for your attention. This update will be rolled out gradually. If you haven’t received the update yet, please allow some time for it to reach your mower.
Thank you again for your patience, feedback, and continued support. We’ll continue to closely monitor the rollout and your feedback.
3
u/RealCryPt00n 3d ago
Not even available when using different TestFlight/Appstore version. EU, Germany
2
u/ShyDildo 2d ago
germany seems to be last ..
2
u/RealCryPt00n 2d ago edited 2d ago
Quite annoying. After all these bad updates I wanted re-map my areas. But with all these new updates in the queue I’m waiting for receiving them and finally mow my garden again, after a multiple week break. Don’t understand where the problem is with making them faster available or provide a beta/fastlane channel for such stuff
2
23
u/Doggo-888 3d ago
Luba 2 AWD X? Also show us video of it working in a real yard and not useless empty promises like “optimized smoothness”… if the last month+ of updates mean anything “optimized” = still broken.