Help me not want to return this for a Luba

Support & Solutions
1

Hello, I am a new Yarbo user, and this will be a long post. A friend of mine has a Luba 3 lawn mower. He loves it and it works great. I was talking with my dad about them, he decided to order the luba. I wanted something bigger, as my yard is about 3 acres. I did some digging and was very intrigued by the Yarbo, and decided to give it a go.

We both ordered, his showed up first and he is not technically savvy, so he wanted me to set it up at my house and show him the ropes. So I did. and it was great. Didn’t need to use the base station, just net rtk. setup was fast and easy, didn’t tell it about any obstacles in the yard, it figured it all out and just mowed. It was incredibly accurate, really had only 1 complaint, which was you can only save 1.25 acres of mowable area, so they would be a pain for me as i would need to rewalk the boundary. So I was hopefull for over another 2k that this would be a better machine. Mine showed up yesterday. I was impressed with the packing, the instructions, and the all around build quality.

Set up went smooth, so I wanted to map an area. I switched to net RTK and turned on cellular to give it a quick test run. I could not get it to connect this way at all. So i stuck the base station in the ground, wired it into the house, to try to give it a test run before attaching it to the house. I mapped and area, and noticed i got alot of gps signal disruptions and it took forever to map a small area. I finally got it mapped, and set it to mow. Any time I am not within bluetooth, i do not get any notifcations and I cant connect to it. my understanding is that this should work through the base station, or wifi, or cellular to at least connect to see where it is and the progress. I cant get it to connect at all.

So today i put the base station up on the tallest part of my house, and reset the base station, and tried again. Same issues. Verified all firmware and software is up to date, tried resetting the yarbo, tried resetting the base station, force closing app, tried both with and without wifi connected to the house.

I have a support ticket in, but was hoping someone on here had some ideas before i eat the return shipping and send this back. The main issue is it says network error when I try to connect from the app and i cant get notifications or see progress. the accuracy seems very low. it rammed into my staircase off my deck, when the path i sent was over 1 ft away. It has all the sensors on, and someone did not see a full staircase and rammed it, where it should not even have been driving. The luba will drive exactly over where you taught it, and never had any collisions with anything, and the connection was great, all with no base station even hooked up.

2

Some screenshots of your diagnostics section would be helpful. RTK,status, Data Center, and HaLow sections.

3

Sorry to hear of your poor initial impression of Yarbo.

You are correct in that the RTK (Data Center) should be providing data connectivity back to your Yarbo. And in your case, it sounds like it’s not.

Once you post the screenshots @bryan.wheeler asked for, we can help you with the diagnostic process to figure out where the problem lies.

As someone who owns both Yarbo and a few Luba bots, I can tell you that both do well in some ways, but neither is perfect. Let’s get you up and running so you can get a better impression of what Yarbo is capable of.

4

I have both and they are very different. The Luba is easier to setup, docks better, and is more polished. It gives great notifications, the NetRTK and Lidar work great, it gets into small areas, climbs well, is quiet and and fast and accurate. The battery life is also very nice.

I like the Luba software interface but it is very limited. And it gets caught up on things like roots, even the “high” version. It has odd quirks like it refuses to enter a narrow mapped area even if it could fit, so with no warning, the rest of the map is cut off. If your area isn’t squarish, the mowing patters are CRAZY. It goes to one end, then the other, then the first again…the last 1% takes like an hour. It just doesn’t handle odd shaped maps well. And if you delete an area, it deletes all the no go zones and channels to it. It also doesn’t save your cutting settings per area, so you havr to choose each time. The AI obstacle avoidance is useless, as it avoids any weed taller than a few inches. And you can’t control it without being next to it.

The Yarbo can climb any friggin thing, roots and all. The pro has real blades rather than the Luba’s razor blades. The pattern and rotation choices are better. You can start a plan in the middle, save settings per area, it covers much more area much faster than the Luba, and the Yarbo is “unlimited” whereas the Luba has a software lock on the area it allows you to map. You can also drive the Yarbo with 4 cameras from halfway across the world. Not to mention, the Yarbo is modular with snowblowing, towing, etc.

So I honestly love both and use both. What I like about my Luba is that I don’t worry about causing an accident next to the road or driveway. It’s a 40lb toy so the worst that would happen is someone would smash it. The Yarbo on the other hand could seriously stop many cars and cause an accident if a delivery truck wasn’t looking, so I use it elsewhere.

The other thing is that all robots are fairly new technology, and even in the short time I’ve owned both, both have added useful features. So what is cranky now may not be later. I do think that Mammotion has a track record of abondoning their older models while Yarbo has tended to upgrade. And Yarbo has more spare parts available, Luba 3 has literally just two parts available.

So all this is to say that they are both good choices, Yarbo for tougher larger more open yards and Luba for smaller easier more complicated yards. Luba if you like simpler and Yarbo if you like customizing. The list goes on…

5

I had a similar problem.

I fixed it by reinstalling my network and making sure I had a stable connection. My mower still worked, but the app couldn’t track it in real-time beyond Bluetooth range.

After I reconnected the network, put the rover near the data center, and rebooted the rover (unplugging the battery for 30 minutes), then reconnected the data center’s Power over Ethernet (PoE), everything worked again.

6

Sorry to hear about the issue. This will require further investigation from our team. We will follow up to help you resolve it, and please feel free to tag me if you need any assistance with tracking the case.

Before you decide to request a refund, we kindly ask for your patience while we work on resolving the issue for you.