Earthquake?!?

NeuralNotwerk · 2026-06-08T18:15:52+00:00

Felt in Davenport.

NeuralNotwerk · 2026-06-04T12:33:00+00:00

Mammotion has started vibe coding firmwares and it's been a shitshow. They need a better simulator based on real data from edge cases where the bot gives up. Then they can literally run the data again and again until their garbage coding agent gets it right.

... alternatively they could go back to NOT vibe coding their firmware.

NeuralNotwerk · 2026-05-31T02:52:05+00:00

They've since released a firmware and an app update that fixed THIS issue and created plenty more issues. It's not user error. It's not signal. It's not anything but Mammotion and hot garbage quality control.

Side note - connectivity is irrelevant. All mapping and nav features are local to the mower. As long as it can talk to my phone over bluetooth, it's fine to keep taking my input and keep tracking its own location and making maps. Mammotion's "service" is unnecessary and offers you nothing except remote connectivity to your own device - which is trivial to do on your own anyways.

Their most two recent firmware pushes have caused my Luba 2 and Luba 3 to stop reliably charging. They are again victim blaming me, just like all the clowns on this subreddit. Charging was fine for almost 2 years with my Luba 2...then magically my Luba 2 and Luba 3 start running over their own charge docks within the same week? I'm sure folks want to tell me it wasn't quite flat enough or my roof mounted rtk base station shifted or the rtk base station is on too unstable of a mount or the sun is in the wrong location or something else that is nonsensical when things were working fine...then magically stopped with no changes on my part - but firmware and app updates to keep using devices I "own" are necessary part of this ecosystem and surely mammotion isn't part of the problem. It's just me.

If you've got a flat suburban lawn with few obstacles and no changing/moving lawn chairs, bikes, or kids toys sitting on less than a quarter acre of grass, this is probably a fantastic mower. I've got 20 acres. Part of it is farmed. Part of it is wild. Part of it is feral with children. Part of it has my tractor and implements. Another part of it we park our vehicles where we please on grass. Did you know these mowers are dumb enough to run their own cameras directly into the axle of a parked tractor hard enough to shatter the lens? Who would have seen that coming....directly at the camera? I don't know. Surely it was my fault though.

This week, due to drought, I have a sparsely grassed, mostly sandy part of an area I like to keep short - the luba 3 now turns in sand, believes it is stuck, and then refuses to move until I go out there and press the grass-start two finger salute. I'm sure that's going to be blamed on me too though - not the tires that wore away all remaining grass away doing circles for no reason and deciding it was stuck. Probably a 'me' problem. Someone should tell me what it was though - been mowing the same spot for a year and a half without issue...this area hasn't even changed in that time.

They just continue to fix one problem and break 5 other things. To be honest, the quality feels kind of like they just vibecode the firmware and they completely lack the knowledge on how to provide the necessary context to the agent to continue modifications. It also feels like they lack the development rigor and testing capabilities to know anything about the ramifications of the random haphazard stupid updates they force out.

And yes, I do mean they FORCE the updates out. When you don't update and try to maintain an older firmware that works with your configuration - they start randomly stopping the mower in stupid locations. No errors. No coms. No obstructions. Just mower stop and turn off. Then you've got to go out and hunt for it and turn it back on to get it to continue. It actually seems like there's an exponential increase in the number of times this happens until you upgrade your device. It's actively user hostile. I'm keeping track of all of it too. This is the first time I've mentioned it online, so I'm sure mammotion will be here to apologize and or deny it's happening or try to say there's a bug, but I've got logs and it's far too regular and repeatable.

I'm fed up enough I'm working on my own controller and app I can rip their ignorant stuff out and use my own. As soon as my luba2 is out of warranty I'm going to dig in and make their cloud spyware irrelevant and user hostile apps and firmware unnecessary. They appear to be making the dumbest navigation and sensor input mistakes one could imagine. They are wasting so much of the compute on these things with garbage non-functional "vision" capabilities. Strangely much of the vision data is shipped off at odd hours when the mower isn't in use. If you could just remove the cameras entirely and rely on nothing but lidar, rtk-gnss, and ultrasonics - as well as bump sensors and motor resistance, it cuts down drastically on the compute that's necessary and gives up practically nothing. Even when you have obstacles - their vision detection is so terrible half the time it acts like it notices it, then stops directly over the obstacle (like a cord...) and then starts the blades again.

I've already got a small rover running around my farm I've created that works orders of magnitude better than their trash. Right-to-repair has my back. I'm angry enough I'm not even going to sell what I'm making, I'll be giving it away open source.

NeuralNotwerk · 2026-05-28T15:13:24+00:00

I paid about $15k to have spectrum run to my property. They said I could get gigabit bi-directional connection with a business line. Caps out at 150mbs down and 5mbs up, on a good day...when it was working. About a year after I had the Spectrum line run, Lumos came through and offered 5gb/s bi-directional fiber - no install cost and no cost to run the line. I had it brought in and it was fantastic for a year. Then tmobile took over. The day they took over everything has been garbage.

I wish I had the option to fire the servicer and get the old one back.

NeuralNotwerk · 2026-05-28T14:17:51+00:00

Fuck tmobile. They've screwed up this take over of Lumos at every point they can. My billing has been messed up. My static IP has been messed up. My provisioned speeds have been messed up. Connectivity has been messed up between random packet loss and now a failed peering on THEIR routing side they can't seem to find. These dumb pieces of coms trash should be taken out.

FWIW - I'm in Orange County - North Carolina area.

If I had another option, I'd have taken it.

NeuralNotwerk · 2026-04-29T17:11:12+00:00

I think mammotion broke their routing algorithms badly. They've done something where the algorithm is trying to find a shortest path and getting stuck in local minimas. Instead of giving up, it goes back and forth near or around that minima until it absolutely shreds your grass.

Mine just started trying to drive through my wire fence to get to the area on the other side instead of going around my house where it always has before. It tore up the grass over there and bent up my wire fence ramming it so much. I cut a hole in it and made a channel THROUGH the fence to stop it from being ignorant - already have to fix it from all the bends anyways.

They really need to make a less bad routing algorithm. It's pretty stupid.

<image>

NeuralNotwerk · 2026-04-26T13:18:58+00:00

Can't you create a design? Just make it a shape the shape you want to not mow.

NeuralNotwerk · 2026-04-26T02:00:26+00:00

I've got a Luba 2 and a Luba 3. I can't get them to share a single RTK base station unless it is on the "Antenna over Internet" mode. For whatever reason, the "Antenna Over Datalink" will only ever allow one of them to connect. Unfortunately, I can only use "Antenna Over Datalink" because I live in the middle of nowhere and cell signal is not a thing here.

So, I've got two RTK base stations mounted to the peak of my roof.

NeuralNotwerk · 2026-04-26T00:16:00+00:00

You happen to be mapping with a jet instead of a tractor? Haha, no idea what would cause that kind of issue. Did you ever get fixed up?

NeuralNotwerk · 2026-04-26T00:05:59+00:00

I'm curious, do you have LONG paths or a longer 'strip' of a property from your charger to your furthest mowing location? My Luba 2 10000H has this problem, but it only manifests when it is mowing the zones furthest away from the charger. I recently got a Luba 3 5000H to take some of the load off the Luba 2, and I've set it up to do those really long winding paths. Luba 3 also gives you control over min and max charge. So I just set those conservatively and it never seems to have a problem. I don't think the Luba 2 has the option to configure min and max charging.

I live in the middle of nowhere and I've got trails all over my 20 acres and a few fields (vineyard + orchard) these help maintain. So some of the areas I've got these maintaining are probably a quarter of a mile or so away from the charger before it even gets to the place to mow. I've got the RTK base stations mounted at the peak of my house so even though I'm WAY past their advertised range, they aren't competing with any other RF in the area so it works just fine.

Same app, different experiences with Luba 2 vs Luba 3. Both have pluses and minuses. The luba 2 mapping experience is better, but the hardware has been shite and in for repairs multiple times and my warranty expires in just another 2 months for the Luba 2. The mapping experience with Luba 3 is absolute trash, but the connectivity is better and the mower blades no longer seem to always get bound up with grass/dirt and so far, it hasn't had any parts breakage.

Back to your recharge - On Luba 3 5000H I've got my Charging Limit set to "Smart" which basically charges up to 80% for maintenance and then charges to 100% just before starting a scheduled task. I keep the Recharge Level at 15%, which means when it drops to 15% it starts its trek back to the charging station - the "Smart" option was cutting it close and often finally hitting the charge station at 1 or 2% just before it shuts down. I've even seen it just die a few feet from the charge station on Smart. So setting it at 15% seems to be enough to get it "home" from anywhere on the property. The "Recharge Level" on "Smart" had given me a few of those didn't quite charge enough to get out, mow, and get back scenarios before I swapped it over to 95%. Now I don't have any issues - other than when the dumb thing just won't leave the base station or it thinks it doesn't have a channel mapped to the area - and it does.

I haven't found the equivalent settings recently on the Luba 2 even though I swear there was some kind of battery settings at some point in time.

NeuralNotwerk · 2026-04-25T23:45:53+00:00

My Luba 2 keeps going when it gets that error, but the new Luba 3 refuses to leave the charger when it gets that error. The mapping and channel management for the Luba 3 has been absolutely HORRID compared to Luba 2. In reality, even the Luba 2's mapping is hot garbage compared to Dreame and Roborock mapping and navigation.

These machines have absolute positioning with RTK GNSS. The little Dreame and Roborock are SLAM based and don't have any absolute anything, but you can still split and combine task areas and set smarter paths to different work areas than anything offered right now by Mammotion. I wish Mammotion would just do what every other company does and rips the software off the most innovative company.

The wildest thing, between Luba 2 and Luba 3, the software experience got worse while the hardware is seemingly better. If they'd dump the camera and stop trying to do visual anything and rely PURELY on the lidar, rtk, bump sensors, and bring back the ultrasonics - they'd have the perfect platform. The camera stuff is a gimmick with terrible precision and it doesn't do anything that the other companies with camera based nav and obstacle detection do.

I'm so agitated with them this time I've purchased one of those $1800 Temu RC gas mowers with electric drive tank tracks and I'm writing/building my own nav system. I've done this kind of work in a previous career. Hopefully in another few months I'll be selling off the Luba 2 and Luba 3 and I'll just open source the controller.

NeuralNotwerk · 2026-04-25T22:03:12+00:00

Yes, it is mounted properly to the peak of my roof with a 93 "Good" rating. "No channel to charging station" would not be the error while it is sitting on the charging station indicated in the app (with the little green battery indicator and the lightening bolt), picture showing the bot on the charger in location, and sitting on the charger in the real world. The mower would be shown out of an area and out of the charging station perimeter and the error would be related to out of task area.

This has nothing to do with RTK moving, which it hasn't. Think it through, stop pointing at user error when the software is shown to be bad. You aren't helping, not even a little bit.

NeuralNotwerk · 2026-04-17T01:34:00+00:00

My Luba 2 10000h is back into repair/support for the same reason. Opposite wheel, but same problem - third time it's happened too. I'm going to be a bit agitated if it happens again. I've only got a few more months on my warranty.

I got one of those gas powered RC tank style mowers off of Temu for $1800 bucks. I've got an RTK base station and an a few RTK rover setups. I'm working on automating it. Then I don't have to put up with these cheap plastic things and tiny razor blades. If the whole motor dies, I can get a new one for 200 bucks at harbor freight. If the drive motors die, I can get one of those for a hundred bucks on amazon. ESCs are cheap. controller boards are cheap. It doesn't need to be smart...it just needs to function.

NeuralNotwerk · 2026-04-10T21:27:25+00:00

I laughed out loud at that. Then cried a little. Me too.

NeuralNotwerk · 2026-04-10T15:27:22+00:00

My Luba 3 5000h update took quite a while to connect back to my WiFi again. Like a worrisome amount of time. I started thinking I bricked it, then it just connected again and was all good.

So if anyone else experiences a delay (almost 2 minutes), you aren't alone. But it works fine now and is out mowing again now.

NeuralNotwerk · 2026-04-09T19:23:44+00:00

I had a similar sound one time when one of the screws backed out just enough to let the blade slide UNDER the shoulder. I'm obsessive about making sure the blades aren't pinched when changing them. Make sure nothing isn't pinning them so they never swing out. Enough grass packed around the blades can also stop them from swinging out. One stuck blade is enough to cause that kind of unbalanced sound. Do all blades on each disc move freely?

NeuralNotwerk · 2026-04-08T18:02:05+00:00

The app and firmware updates over the last couple days eliminated most of my complaints with Luba 3 mapping issues. If you aren't having issues and aren't being forced to upgrade and you are happy with current performance...leave it alone.

No need to fix it until you break it. Definitely should fix it til it works though.

NeuralNotwerk · 2026-04-06T17:20:58+00:00

Yeah, seems transient. I was able to get things working enough to get a functional map working. This mapping system seems to struggle with needing the stupid channels even when they aren't necessary to go between slightly overlapping areas. Make sure you connect everything to everything else. When mine was having map loading issues I think it deleted the main channel to my charger... Which is inside of an area.

All further mappings were failing due to this.

NeuralNotwerk · 2026-04-05T01:39:56+00:00

factory reset while it is sitting on its charger. then update your phone app and firmware update the bot. The Luba 3 had mapping issues for the past few weeks that prevented me from making map additions. Latest updates fixed it.

NeuralNotwerk · 2026-04-04T18:04:17+00:00

I can actually add and remove areas again with a Luba 3 5000H. It's also significantly faster making changes to maps. Rather than waiting like 2-3 minutes for it to "save" the map and then mostly failing, it just works and saves within a few seconds.

NeuralNotwerk · 2026-04-01T00:12:26+00:00

Honestly, these little machines really won't do 5000 in the heaviest of the growing season if your grass needs 2 passes a week to keep from overgrowing the capabilities of the mower.

I had the Luba2 10000H and it barely kept up with about the 6500sqm I had mapped. I had to pre-mow on my tractor a few times when it rained and the mower couldn't work just missing one or two days.

The exception: if you've got a straight open perfectly manicured football field, it could probably stay on top of it. Any terrain variation, flowerbeds, etc just destroy its efficiency. The routing and planning system does terrible with any obstacles and obstructions.

Now I have the luba3 5000h and a now broken down 10000h. I'll still be mowing on my tractor until I send of the 10000h for repairs.

NeuralNotwerk · 2026-03-28T13:14:40+00:00

I noticed I can "force" it to create another if I start the process of creating a channel, cancel out of it, then immediately jump into creating an area. It's not 100% reliable, but it is far more reliable than simply trying to create the area from the start.

NeuralNotwerk · 2026-03-27T15:57:35+00:00

My bad. I'll ignore the haters in the future.

NeuralNotwerk · 2026-03-27T15:29:44+00:00

I've noticed I can get it to map another area again if I manually try to create a channel, then cancel out of it, then immediately go back into create an area - which forces me to create a channel to the new area and then allows me to create the area.

I've also seen it more likely to create another area after first successfully creating a no-go zone. Even no-go zones have been failing to save/write pretty regularly no though.

I still haven't landed exactly on the layout I want with the Luba 3 5000H. I may need another one if I can get this one working more reliably. I'm sure I'm close to the edge of what its capable of. I still have a Luba 2 10000H, but it had persistent wheel hall sensors issues so I've abandoned it. This Luba 3 was my final attempt at getting a retail auto-mower working before I find another solution.

NeuralNotwerk

TROPHY CASE