Again 1 of my cores has no idea what a NGZ is for.
Again and again I find my core totally unaware of its own dimensions and has put the mowing head through a NGZ only for the whole F N to get hung up on a stump that I now have to drive over an hour to get unstuck!!!
Why bother with NGZs if the unit isnt going to adhere to them?
This problem has been around for a while now. Never used to have to deal with this crap!
People doing the coding need to step it up a notch or 2. You are driving new potential customers away and causing a whole bunch more current customers to regret buying these machines!
Yep. I watch mine spin through NGZs repeatedly. This has been reported by lots of users. There have now been (2) firmware updates since and nothing has been done to correct it. SAFETY ISSUES need to be addressed promplty.
Please rest assured that our team is continuing to investigate the issue of Yarbo moving outside mapped boundaries or entering No-Go Zones.
Could you please submit a support ticket and include the approximate date and time when the issue occurred? This will help our technical team locate the relevant logs and investigate the case more accurately.
We take every related report seriously, as each case helps us identify the root cause and work toward a reliable long-term solution.
Could you please submit a support ticket and include the approximate time when the issue occurred, along with the pictures? This will help our team review the related logs and investigate the possible root cause more effectively.
Thank you for your cooperation, and we’ll do our best to assist you.
I already have a ticket open…226649. I’m experiencing several issues with the latest firmware, including navigation errors, inability to return to the docking station, etc.
Thanks for letting me know. If the collision shown in the picture happened recently, we would appreciate it if you could share the approximate timestamp of when it occurred in your support ticket.
Our team will review the relevant logs from that time and investigate further to help identify the root cause.
For the other issues you mentioned, I have also asked the FSE team to follow up on your case and provide an update as soon as possible.
@Yarbo-Forumwe have ALL submitted so many support tickets that you people have more logs and more pictures of our yards than we do personally. Clearly, adding more tickets with more noise over the same issue is not going to fix this!! I will bet that if you take a survey, there are hundreds of tickets that have been opened on this topic. Maybe I’m misinterpreting what your overall customer base is, but this has been going on now for months.When are you going to accept the fact that your last few software updates have been an utter disaster? Roll back to when this was stable!
I’ve seen your latest updates regarding the obstacle detection and GPS-related issues. To identify the root cause, our support team will need to review the relevant logs and further investigate the situation.
I’ve already asked the FSE team to follow up on your case as soon as possible. We’ll continue monitoring the progress and keep you updated once we have more information.
I now have a brand new replacement Pro mower and unit hung up on something that Is inside a no go zone!
Yay for me as I now get to plan an 1 hour and 20 min trip, 1 way, out of my way to go rescue it.
Note to programmers. Please consider the fore and aft dimensions of these things when writing code as it is always the front or the rear that has issues with this problem!
Suppressing my iner sailor here!
All I can say is at least it isnt in the pond!
Maybe if we all pitch in and get these guys some coloring-in books?
Hi there, I’m really sorry about this, especially knowing it now means a long trip just to get Yarbo unstuck.
Your point about Yarbo needing to better account for the full front-to-rear dimensions of the mower is completely fair, and I’ll make sure this feedback is passed along to our product team.
In the meantime, as a temporary workaround, you may want to increase the No-Go Zone buffer around that obstacle and run a quick test before leaving the property. I know adjusting the map shouldn’t be something you have to rely on to prevent this kind of issue, but it may help reduce the chance of Yarbo getting caught there again while we continue improving the navigation behavior.
Sorry again for the inconvenience, and thank you for taking the time to document the issue so clearly.
We’ve already shared this feature request with our product team before, and I completely understand why it would be especially helpful with a more complex property and map setup like yours. I’ll make sure to reshare your feedback with the team, particularly the need to preserve these settings when restoring maps from the cloud.
