So to confirm - your Yarbo mows along NGZs exactly same line as you draw them?
Yes. It’s a drawn NGZ, not a template.
Ok. Let’s see - today I received the firmware update. Will check on further jobs. If I’ll observe the issue, then I’ll raise a support ticket.
Hi there, thanks for sharing this.
We haven’t made any changes to the safety buffer logic, so this behavior isn’t expected. We recommend submitting a support ticket so our team can take a closer look and investigate the issue further.
Appreciate your patience, and we’ll work to get this resolved.
I’m also using Checkboard and my NGZs are also drawn. Like I said, I even remapped a couple. I guess I’ll open a ticket since you’re not seeing it.
Ticket #188802 opened.
My templated no go zones worked as expected and so did my drawn NGZs. (parallel pattern)
I did redraw a couple after successful mow but that was just because they were misplaced. (my fault not Yarbo’s).
Wonder what’s unique to mine. What were your area settings? I’ll try changing an area to match.
Thanks. I’ll give her a try tonight.
Here’s support’s suggestions. This is why people get frustrated.
- Increase the Overlap slightly (for example, from 4" to 6") to allow better edge coverage
- First, there is no 6" setting. Second, this has nothing to do with edge coverage. - Try toggling No-Go Zone Edges OFF and then ON again to refresh the setting
- Done, makes no difference. - Reduce Perimeter Laps to 1 and test if there is any improvement
- Wow! this setting doesn’t exist. - If possible, slightly adjust or redraw the NGZ boundary to ensure optimal mapping alignment
- Already noted that I recreated NGZs and it made no difference.
Yeah the only useful suggestion there is the toggle on and off again if there was a mismatch somewhere.
Deleting/Recreating a new NGZ crossed that one off the list. But I have tried toggling as well.
yea, that’s pretty unhelpful and casts a bad light on Yarbo’s support structure.
Way too cold in PA to mess with this tonight. Supposed to warm up the next couple days.
Hi there, thanks for the update and for opening the ticket.
If you’d like Yarbo to mow along the edges of your No-Go Zones, please check your Area Settings and make sure the No-Go Zone Edges option is enabled for each area.
After adjusting this, you can run a quick test to see if there is still any uncut grass around the No-Go Zone edges. If the issue persists, feel free to continue updating your ticket (#188802), and our support team will be happy to assist you further.
I went to update this ticket, and its completely gone. It doesn’t show up at all!
Tried your settings. Unfortunately, no love 
I’m at a complete loss if no one else is encountering this. On top of that, I went to update the Ticket and it’s not there. It’s not Closed, just gone.
I Deleted and remapped NGZ again and hard rebooted Yarbo just to be sure.
Here’s where I mapped. I took this pic right before starting to map.
Here the video of where it cut.
I wouldn’t say you are the only one. There are others with the same complaint. Has to be a bug.
… and the Ticket reappears today.