You’d better send them at least 2 or 3 videos…. Lol
Send videos. You aren’t immune. 
Do it, everyone is doing it.
We should start a website, dedicated for them.
If they like videos so much, why is there file size so small you have to host the videos and send them a link? They only like small videos?
Here it is. 1st lap running at fastest. Use sound to hear gear whine.
And this response just showed up. It’s clear that AI is randomly replying and this is how they’re dealing with a massive # of open tickets. Drag them out for weeks 1-day at time with stupid answers. But hey, the ticket was answered. No human is this F’ing stupid. This company is going under, and sooner than we think. Yarbo group is not even smart enough to use AI competently. What do you think is writing the bot code? It makes complete sense when you see the end product it spits out.
Dear Eric,
Thank you for reaching out, and I hope you’re doing well.
Thank you for providing the detailed information about the issue you’re experiencing. I understand how frustrating it is when the perimeter laps are performed at the same speed as the area speed, causing the mower to collide with fences and other boundary objects. I sincerely apologize for the inconvenience.
To help resolve this issue, please try the following steps:
In the Yarbo App, go to Advanced Area Settingsand make sure Extend Area Boundary is set to 0.
If the issue still persists, please edit the affected work area and shorten the boundary slightly so that it maintains sufficient clearance from fences, walls, and other nearby obstacles.
After making these changes, please run the work plan again and check whether the mower completes the perimeter laps more smoothly.
If the issue still persists, please send us a short video showing the mower performing the perimeter lap and any collisions that occur. Additionally, could you please let me know the date and approximate time when this issue first started? This information will help us investigate the logs more effectively. If the issue remains after these steps, I’ll escalate your case to our relevant technical team for further investigation and assistance.
Also, could you please confirm that the following shipping address is correct?
After the update I see that I have way more missed patches and missed stripes. It seems that Yarbo is avoiding even 2 inch hight of grass and going around that. This is only since the new update. Anyone else experiencing this?
I will try with gentle contact and see if this improves. But I think the avoidance mode is to sensitive now.
I may be in the minority, but I never use object avoidance and I never see any difference in these updates. I also have a Luba with Lidar. Neither one can tell the difference between a weed and a fence.
The only solution seems to be to map only what gets mowed, no go zone the rest, and keep everything else clear.
Here is a new one, but I have a new yarbo so maybe that is part of it, but with new firmware, as soon as I open app, core parked on dock next to my house, with dog house over it, has instant great GPS. That has never happened before.
So are they leaving GPS on now while it sits on the dock, or is GPS that much improved? I have HA-609 antennas on, but still never had this, ever.
So we are in a drought here, so grass is not really growing. But I ran my refurb core on my smallest area, I left boundry obstacle avoidance on and the thing would not mow, it just sat there making red spots, jerking back a forth, moving just slightly forward. I had to stop the plan and turn boundary obstacle avoidance off to get it to mow.
Historically it’s been about the core waking up the GPS module which can take several seconds to lock in. It didn’t really have anything to do actual reception. I haven’t noticed a change, but also haven’t watched for a difference.
Turn all of the vison off. It doesn’t work.
Oh yeah I usually do, but I just wanted to try it and see if they made any improvements, nope, it is worse than ever, could not even start mowing.
All of my robots (Yarbo as well as other brands) have their vision features turned off. Vision almost always leads to uncut grass.
It leads to uncut grass, but it causes other problems as well. Once the object is identified, the unit (even the Luba with Lidar) makes a wide route around the obstacle (weed), backing up 3 times and missing not just the weed, but like a foot on either side of it, tearing into the ground all the way.
I don’t necessarily blame it. Some of my weeds are substantial and must look like a sapling to a computer. But I can’t rely on it either. If it’s mapped, it’s mowed, full steam ahead, no avoidance, AI or otherwise.
My problem with just turning off features, is I am turning off what yarbo marketing sold me on, vision and AI smart robot VSLAM, ultrasonics. And here I am just running a dumb mower acting like it is in the dark and can’t see. And now 2 years later it is even worse than when it started.
Yes. That’s my point. When the vision thinks it sees something to avoid, it overcorrects and causes a bunch of grass to not get cut.
With Yarbo it’s worse cause the clunky algorithm can’t smoothly drive around an object. Instead, it does that jerking back and forth stuff. Thus I have vision turned OFF.
I’m sorry for the delayed response, and please disregard the previous reply from the ticket.
We truly value your feedback, and I have personally shared it with our R&D team for further investigation. After testing, we have confirmed that this is a bug, and our team will work on a fix in a future update.
Thank you again for providing such detailed feedback. We sincerely appreciate your help in improving Yarbo, and we apologize for the inconvenience this issue has caused.
you’ll generally find if you actually look at the GPS by tapping the icon it will read “disconnected” so it seems like the icon can be misleading in this new update