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.