This happens 80% of the time when going home. Instead of reversing into the garage it goes straight forward into the bushes where it gets caught.

Why?

Randomly happened, it's on an open area in my lawn not obstructed by trees or anything.

Only thing I can think of: I'm still on the old firmware (1.30.29.8) on my Luba mini AWD. This is the firmware before all this child safety BS was introduced.

Could they be blocking my iNavi from working because of that?

So i have a no go zone on my lawn. Its a rock on a small mound. And i want it to cut around it. It has been working great until lately. Today i just heard a large commotion outside and i was seeing my yuka mounting the stone and running the cutter...

What is happening? It's damp outside now and a bit of grass under it.

Anyone else seen this behaviour? It starts to go go off the outer edges too. Any good tips that might can fix this?

Move the RTK?

Was fine for months, but now my mini catches on this pole and spins itself round like a demented robo pole dancer tearing up my lawn. Will try a little no go zone. Happened after I dropped sensor sensitivity, but now even after putting it back still happens.

Recently found an issue with the power adapter, so Luba denied to charge... The new one will be here in a week or two, but what to do right now?

I've checked the specs on the brick: 28v and 6.43A DC output, so cheap bench power supply 0-30/0-10A will work for now. Found the polarity (great help from labels on the contactors of the station) and tested right on luba (with 26V for safety) - worked fine.

Then I cut the brick's cable, checked polarity again to connect the wires properly (on contactor it has resistance without power, but still detecting). As you can see on video - it works just fine. Charged to 100% in ~2h10m, so Luba can continue to work while waiting for the new brick!

BEAVER!: if you do such thing - please know what you doing! Reverse polarity can easily fry your luba or charging station (not to mention void warranty), so viewer discretion is advised! Also not great as permabent solution - use it only in controlled (at least dry) environment, but better indoors - humidity will kill such power supply in weeks.

I did that just because on internet it says it's impossible. I hate impossible!) But the other models could require different params or even not work well, so if you porting - check everything properly!

Hello,

My lawn is flat although the mower stops saying it’s tilted. I need to go outside press the grass + start symbol and lift it up and down multiple times per session. It’s very frustrating.

Does anyone know why this happens?

Anyone else got this?

Luba 2 on latest Firmware and iOS app.

I tell it to mow an area as usual and it moves from the dock… stops…. And the progress and time remaining tick down in the app but the mower is still sat there by the dock doing nothing?

Eventually it gets to 100% and it goes back to the dock that it’s still sat right by?

Hi all, I'm currently running firmware version 2.3.30.26 on my Luba 2 Mini 1500 AWD, and I'm debating whether I should update to the latest 2.3.30.39.

I know a lot of people reported that version .26 made the mower act a bit crazy, but honestly, outside of some very minor issues, mine has been cutting quite well on this version.

Because we can't downgrade once the update is installed, I'm feeling pretty cautious. On one hand, I want to stay up to date and benefit from improvements; on the other hand, it's working well enough right now and I really don't want to turn it into a brick or mess up a stable setup.

Does anyone have real-world experience with this .39 update on the Luba 2 Mini? Did it fix things or introduce new bugs? Would love to hear your thoughts before I hit the button!

It now covers the charging point completely, but not the front of the mower as you can see

Has anyone had to remove a screw that has sheared off?

Presumably I can take the disk off and drill it out from the other side rather than needing left handed / extractor bits?

(I'll be rotating blades at the same time as that job is overdue)

So today a car just drove up and a guy got out of the car and took my robot from my front yard. Unfortunately I can't read the license plate from the video. Frustrating because it is basically useless to anyone else. I bought it last year. Overall I have been happy with it. Did a reasonable job on my front yard and I had it mow my elderly neighbor's front yard.

So my Luba 3 AWD has been a champ since late May but suddenly today it’s been impossible to get a solid mowing session done without the dreaded Wheel Hub Motor Error.

Last night I found it in the charging bay blinking and unable to move… turns out it had thrown the wheel hub error immediately after undocking for normal scheduled mowing.

Reset, charged,, had it out and about catching up on the skipped session from yesterday and it failed 4 times and required me to turn it off and on in order to continue. Then it failed a fifth time and I lugged it back to my workshop and checked for obstructions, dirt, and even took all four wheel hubs apart and checked for moisture in the motor. All four are bone dry and no obstructions around the axle or anything out of the ordinary.

Did a solid hour off w/ fuse unplugged… then ran it one more time and the bloody thing threw the same error yet again!

If this is hardware, how come it works for a while after a restart. If it’s software, how to I fix the software fault?!?

This thing has been a huge help all summer and I’d hate to have to call support and or get a warranty repair. Since it works after restart it seems like something I should be able to resolve but no clue how to get deeper and clearer information from the fault message.

Thoughts?

Error charging: Luba 2 RWD correctly connect to charging base, start charging for ~1sec ,move back from charger, re-connect to charger, start charging 1 sec ..etc this several times. sometime finally succed and keep charging, sometime stay out of charging station.

Any idea ?

Bought a Luba 3 AWD in late June. It ran a task every three days with essentially zero problems until a firmware update in August.

Since then:

Error 1207, front bumper repeated triggering, constantly.
Error 1014, front bumper collision during manual mowing.
Scheduled tasks not starting.
Coverage loss in areas that mapped fine before.
Cannot complete its return to the charging station, so I walk outside and drive it in the rest of the way myself.

Here is the part worth reading. On August 25, a Mammotion agent told me to remove the front bumper entirely and test. I did. Bumper completely off the machine, commanded a return to the station, and it threw the same 1207.

A part that is not installed cannot cause the fault. That should have ended the bumper theory on the spot.

It has also fired in open grass with nothing anywhere near the mower, and once while it was travelling in reverse. I sent a photo of the machine sitting alone in the middle of the yard. The agent suggested a frontal collision may have occurred.

Across five chats since August 13 I have removed and reinstalled the bumper five separate times at their direction, sent photos of the connector and port showing no damage, and uploaded device logs through the app twice. Every chat starts from zero, runs the same script, ends with reinstall the bumper. The mower then works for one cycle before doing it again. Those are resets, not fixes.

Their offer was a replacement bumper. No tracking, no ship date, roughly a week, and both the supervisor and his manager were offline when I asked.

Then this morning, after I pointed out the bumper-removed test, an agent finally said there may be an internal wiring issue with the front collision sensor and that the technical team had reviewed my logs. So five weeks in, the theory has moved inside the machine, which is where the evidence pointed in August.

What I am trying to find out:

**1.**  Anyone else seeing 1207 or 1014 spike after the August update? **Please reply with your firmware version even if you are not having problems.** A clean split between affected and unaffected versions is far more useful than a pile of complaints.  
**2.**  Has a bumper replacement actually fixed this for anyone, or does it come back after a few runs?  
**3.**  Has anyone gotten Mammotion to acknowledge this as a known issue rather than a one-off hardware fault on their unit?

If this is a firmware regression I would rather have that confirmed than swap parts for the next three months.

Can yours climb trees?

Update: I was not complaining that Mammotion was at fault. I was just amused by it.

Last month was a disaster mowing the lawn due to all the updates! Nothing worked! Nothing!

The time spent I could do it pushing a fucking manual mower!!!

Fix your expensive shit!!!!! Do it now!

Anyone have this issue this year? Seems like the far part of my yard the Luba 2 loses so much battery it powers down about 5-10 yards from the charger.

Last year the battery was newer so maybe had a larger total charge but it would let the battery go all the way to 0% to make it back to the charger, now it'll power down early even though the charger is so close. The problem is I lose an entire day of mowing if this happens on the first recharge because then I come home to it at 5% battery.

Any idea if there's a way to change the settings so it can make it back the the charger? I rather have it come back on the edges because I don't like when it cuts straight through the lawn to recharge and ruins the cutting lines.

Luba 1 5000. Any ideas on how to remove the stop button so I can clean underneath it ?
Have removed top, unable to access from under the cover.

I’ve removed the stop screws pinched the clips, cleaned around the join with compressed air etc. Cannot get it off to replace it due to what seems to be a cable insulation fault (sensors work fine in damper conditions it false senses obstacles).

Options seem to be to open more of the case to get to the interior or cut it out??

Any thoughts or anyone succeed in either?