I think you are on to something with obstacle avoidance. I think it may just be ignoring the fact that it should not enter that zone whenever the avoidance is triggered. Definitely a major bug.
Agreed, 2 very bad bugs.
You’re lucky… my unit completely died when the update came through.
Hi there, really sorry for the inconvenience and frustration this issue has caused. We completely understand how serious this situation is, especially with the damage to your landscape lights and plants. Please rest assured that we truly value your feedback and have taken your report seriously.
I’m also glad to see that you’ve currently found a workaround and are able to mow the area again without the error. I’ve checked your support ticket and saw the updates you provided, including when the issue occurred and the exact location involved. Our support team will continue following up and investigating this further to better understand the root cause of the issue.
I might be a bit late to the party on this one, but I watched (unfortunately didn’t react fast enough to screen cap it) my rover do something very similar just a day or two ago. It was mowing around a NGZ (it was a fire pit), it detected an obstacle (a piece of wood it dragged out of the fire pit), then when it tried to “navigate around” the wood, it backed up while turning 180 degrees and backed right through the NGZ it was next to. It stopped on the other side, and then drove BACK THROUGH IT to where it had been and went past the piece of wood…
Like I said, I was so dumbfounded by it that it didn’t occur to me to hit screen record as I watched it happen.
If you have the times that happened, open a ticket so they can pull the logs.
Unfortunately, it was either Tuesday or some time last week, and I cannot remember… OH!! Wait! I just remembered I had to text my friend to move the wood initially to clear a lift error! So I do have the date and time. 
Might be too far back, but worth a shot.
What did it show in the app? Did it plan to drive through the NGZ? Could you see lines extending into the NGZ?
I hope Yarbo fixes this issue soon. This is a big safety hazard for sure. Glad in your case nothing bad happened!
No, my experience was different in that respect in that my NGZ violation was not “planned”. It just did it.
So your Yarbo decided to surprise you! How nice. Lol
Hi there, we also suggest that you submit a support ticket regarding this issue so our team can further investigate it.
Well, let me just tell you @Yarbo-Forum what my very last reply was from support, you cannot make this up. The suggestion was to delete my no-go zone. I guess that would be one way to fix this unit going through a no-go zone. If you delete it, it technically isn’t violating the no-go zone. Does anyone actually pay attention to what the support department says and does? If there’s one person here who thinks that’s the solution to a unit going through NGZs, I don’t know what to say.
I have received a few odd suggestions in the past 2 weeks, some very odd and totally wrong solutions.
They’re so backlogged, seems like they’ll say anything to close a ticket. The answer is technically accurate, but it’s up there with the dumbest responses I’ve seen.
They have to be aware of the issue. I’ve seen multiple reports of it not respecting NGZs. It should have been elevated.
I feel like they forgot to state the obvious of delete and recreate
The worst part was that they asked for screenshots and log timestamps showing when the incident happened. When I provided a 15-minute window, they told me they no longer had the log files because they had done a rollback, and that I would need to provide the exact time again.
If you don’t have the logs, what difference does it make if I can pinpoint the exact time to the second? Mind-numbing. I have never seen such extremes from the same company. When it works, it’s amazing. When they do software upgrades and other enhancements they don’t even tell us about, it’s a disaster.
Seriously @Yarbo-Forum? In one breath, you’re saying we don’t have the log files because we rolled back and lost the data, and in the very same sentence, you’re asking us to provide additional detail so you can look at the logs.
BUELLER, BUELLER, BUELLER…
A 15-minute window is not precise enough. Just say you lost the logs! We need the exact time it happened? What difference does it make now, your logs are gone. I don’t know who here is sitting there watching minute by minute what this robot is doing anyways, but if that’s what I wanted to do, I might as well go out and mow the lawn myself.
@bryan.wheeler - no that was not what they asked, they asked that I delete it period, very specific on the ones they wanted deleted base on the map screenshot.
Was trying to give them the benefit of the doubt, but if that was the intent, I am baffled.