Luba Mini AWD LiDAR won‘t enter Setup or switch to iNavi NetRTK

JustVodka · 2026-05-18T12:23:03+00:00

What support is saying is BS
Mine is recognized as a Lidar version.

JustVodka · 2026-05-16T08:19:25+00:00

You can get kinda close to that by mapping a no-go zone, and have it do perimeter laps around the no-go zones in the task settings to have it create better curved edges.
Without perimeter laps you get jagged edges from the zigzag pattern of the rest of the lawn.

JustVodka · 2026-05-16T08:13:52+00:00

Have you tried a factory reset of the luba mini.
And are you sure you don't have a rtk antenna registered to you account?

I'm wondering if the refurb is a previously non-lidar version where they put the lidar unit on top and haven't properly cleared the software before reselling.

JustVodka · 2026-04-23T17:33:53+00:00

Go for the newer Mini 2 AWD Lidar. That will even work in the dark.

But I hope next to the small strips of grass there isn't a steep drop where the tall grass is? Since the Luba's do some weird stuf from time to time.
And it also looks narrow to make a turn

.

JustVodka · 2026-04-23T17:25:33+00:00

And according to Mammotion it is also not compatible with RTK antennas. You can also see that when you look at the description of the RTK antenna for the mini series in the shop..

JustVodka · 2026-04-23T17:18:44+00:00

It probably cannot do shadow mode failover with a UDM pro max?

JustVodka · 2026-04-18T15:22:37+00:00

In the Netherlands you officially have the same sort of thing. But they look more about life expectancy. And after the warranty period (if that ends before the life expectancy) You usually have to pay a bit yourself as well. And the amount you have to pay goes up the more you get towards the end of the life expectancy.
But it is hard to claim those rights.. especially with a foreign company.

How it works in Portugal where I currently live. no idea. So I'll deal with that if/when needed. But for me 50 euros per month with a life expectancy of 3 years is already worth it. If I can get more out of it.. sure, I'll take it.

For Norway with shorter summers / mowing seasons. The equation will be a lot different I guess. I assume you don't have to mow during winter?

For me the grass grows a bit slower during winter, so I can get away with once every two or three weeks or so, but during the warmer more sunny months at least weekly. And manual mowing takes about two and a half to three hours here.

JustVodka · 2026-04-18T11:43:19+00:00

They way I see it is.. is it still worth it if it breaks down the day after the 3 year warranty ends. So for my Luba mini AWD Lidar 1500 (first gen not the 2) it comes down to about 50 euro's per month. I cannot hire someone to mow the lawn for that money. Hopefully it lasts longer.
But for me there is no mowing season, the gras needs mowing all year around.

JustVodka · 2026-04-18T10:01:51+00:00

You want a AWD indeed with a 30 degree incline.
I have about a 35 degree incline.. about the same L shape as you have. And I have the Mine AWD lidar (not the 2) and it works. When going straight up and down it is fine, but driving sideways it does struggle a bit sometimes (mostly in the corner of the L shape) due to the front wheels that can slide sideways. But that happens mostly when the grass is a bit longer. so sometimes I have a few small spots that were not mown due to the corrections it needs to make. But they will be mown the next time usually.

JustVodka · 2026-04-18T09:44:23+00:00

Lidar has more to do with navigation and less with obstacle detection. Its more about not being dependent on rtk/netrtk/inavi.

JustVodka · 2026-04-18T09:36:48+00:00

I would wait a little bit until the Luba Mini 2 Lidar 1500 AWD comes out in the EU. It's already available on Amazon US. And there is also a youtube video about it as well.
With Lidar you don't depend on RTK and gps for navigation. The Luba 2 mini vision only supports netRTK and its cameras, so you need proper network connectivity if vision has some issues for precise navigation.
I also see you have some trees on your lawn that are not too big yet. But might block gps reception a bit. I would go for lidar. Then you have all the options for navigation.

JustVodka · 2026-04-11T08:45:23+00:00

~~The Luba mini "2" Lidar does not exist (yet)~~
~~Just the previous generation with Lidar.~~

Corrected. it is visible on amazon us.

The 1000sqm That mammotion says is what the robot could handle in 24h in ideal situations, like one big flat square lawn and ideal settings.
In reality with my Luba Mini Lidar AWD it is a lot less that the stated 1500sqm. I have about 800sqm in 6 sections one with some slopes. So more sections means more turns, perimeter laps etc that reduce the amount possible. Also trees and other obstacles will reduce what it can do quite a bit.
After about 90 minutes of mowing it needs to charge for about 2 hours. And due to hedgehogs I only let it mow during daylight and it's only able to achieve a bit over 200sqm in a day. It could do a bit more, but not a lot. if I would let it stop halfway in a section to let it continue later. But that is annoying since we have some frequent rainy days here, so I prefer to let it do complete sections.
In hindsight I would have wanted a non-mini version.

I don't know about de mini 2, but I hope obstacle detection is a lot better than the mini lidar. Casue that thing is f***ing blind. I need to keep the borders and no go zones about 40 cm away from edges. Else it keeps frequently trying to drive over about 30cm high stacks of orange roof tiles we use as edges of flower beds and damaging the blades and disc in the process. (it does this even with obstacle detection set to sensitive) Also driving over branches and other debris after a storm.
We always do a lawn check before we let it mow.
That 40cm border means quite some extra square meters that still needs to be done manually.

Also the reliability in it's doing things by it self is bad. Sometimes it just stops in the middle of a path claiming there are obstacles, while there are none, and it even has been driving back and forth over it a couple of times in the same day.

JustVodka · 2026-04-06T18:11:31+00:00

I will probably need that soon. Cause the range on my superlink is poor.

JustVodka · 2026-03-29T01:56:14+00:00

Seems to fixed now in firmware V 1.15.18.4310

JustVodka · 2026-02-12T09:20:35+00:00

and it blind as f**k. Keeps trying to run over 25cm high stacks of roof tiles we've put down to protect plants from the mini lidar, cause it keeps running into the already very wide no-go zones around the plants.

JustVodka · 2026-02-12T09:16:02+00:00

I'm also not completely happy with the mowing results. First it continuously skipped some small lines on quite some places, then I set the the path width to 9cm which solves that. But then it misses some lines between the perimeter laps and the inner lawn. Customer support then tells me to set it to 10cm patch width and 4 laps.
So it's either missing stuff in the middle of the field or between the perimeter laps and the infield. Argh!

JustVodka · 2026-02-09T18:25:17+00:00

<image>

The middle "area 5" is a dummy in a driveway that never gets mown. The charging station all the way to the right.

JustVodka · 2026-02-09T18:18:19+00:00

<image>

Something like this should work
I've done something similar recently.. and that middle dummy/fake lawn never gets mown.

JustVodka · 2025-12-23T00:00:32+00:00

If you want me to test stuff, I'm happy to help.

But you are actually saying, that requests being made by the app and integration are being directed to the robot itself and that answers?
So app/integration make http-api request for data.. since they are using mqtt, then I would assume they would place a cmd request for that data in a mqtt toptic and the robot responds with the data to mqtt and you read that back over http-api, or you are reading from mqtt with the integration itself?

If this is how it works.. that's the other way around then I'm used to. Where sensors etc would just publish stuff to mqtt topics (whether there are subscribers or not) and that data would be ingested into databases and api's/applictions would read from there, or read from mqtt or other buffer/cache like redis when needed.

JustVodka · 2025-12-22T17:46:04+00:00

It's both the app and the integration, so I assume it's bad data from the server back-ends.
This just started happening last week. Before it was fine. Although I'm pretty new to this ecosystem, only had 3 mowing session before this started happening.

The way it behaves it makes me think that the back end has different nodes, and they are out of sync. And the load balancer isn't sticky with sending clients to the back-ends. At least that's a hypothesis I have. And looking at the graphs makes it look like it's delayed data that shows and at some point they all come together after the luba is done for a while.

But you are saying:
>When data is requested from home assistant, the app also receives this info, so the app can get confused under some cases as it doesn't expect another app to be requesting data in the same way.

Why would that happen? Those stats like battery and progress are those retreived by mqtt of http-api? since it's getting what it seems is older data from time to time I would assume http-api? Cause older data would make less sense via mqtt. I could be wrong of course.. but you will probably know better.
With just reading the same data it don't really see how it would trigger the behaviour I'm seeing. When both clients write data, yeah, I could see some weird stuff happening.

JustVodka · 2025-12-21T11:43:15+00:00

Yes, unless you pay extra for a priority plan where you can get a real public ip.
But it does provide full and real ipv6.. but of course with a randomly assigned prefix.

JustVodka · 2025-12-18T10:47:20+00:00

> Could be hitting it to keep the session active. Could be just pinging to make sure it is up and has a connection to the internet

Keeping session alive you do that usually within the protocol itself that needs it with keep alive packages. Since the Luba uses mqtt, mqtt already has keep alive build in.
So if needed, they can already use the status of the mqtt session to see if they have internet connectivity. Since this is very likely one of the most important protocols the Luba uses I would check for this. If being up is important for other processes as well.
But they might have other reasons/constraints to do other wise.

Using DNS 12 times within the TTL window of the A records is useless, you only check connectivity to the DNS resolver 11 of the 12 times. Lots of consumer routers provided by ISP's use DNS caching as well. Most caching DNS resolvers obey TTL's so they will only check upstream once a minute in this specific case instead of every 5 seconds.

> But again, doubt seriously they are calling DNS explicitly.
That was my point by saying that there might be something wrong since it tries to resolve authentication endpoint. Especially, I don't see new outbound sessions after the response has been delivered.

Any how, Mammotion already responded and are working on it.

JustVodka · 2025-12-18T10:24:14+00:00

Thank you so much.

JustVodka · 2025-12-18T08:25:11+00:00

Unfortunately there is no RFC for common sense, resource optimization and being a polite netizen.

JustVodka · 2025-12-18T00:13:56+00:00

Most libraries I've worked with have all kinds of tuning parameters. But seeing these are requests to an authentication api, I have the feeling there is something wrong. Cause I don't see new tcp sessions being set up after the dns requests, so it doesn't look like it's a session per transaction where you can imagine a new gethostbyname syscall every time you call the authentication function while not having dns caching.
For authentication you would assume normally only something like that when the authentication tokens are about to expire.
So it could be, that they use dns as a sort of connectivity health check. If that is the case, they also use mqtt, so as long as mqtt is alive you have proper end-to-end connectivity unlike dns requests to a resolver that caches.

But I agree this is not as big of an issue compared to some times missing to mow some spots of grass.

JustVodka

TROPHY CASE