Was waiting the new firmware but still having the issue with V3.13.1 & App V3.18.2 I’m going to open a ticket but wanted to see if anyone else is seeing this. You can even see the gap on the map. It’s set to 0.
Update: Ticket #188802 opened.
Yup, I’ve had quite a bit of missed grass. I actually got out my Toro for some quick cleanup
Did Yarbo revert the forced safety buffer?
@Yarbo-Forum if this is the case we need to know. Because if we tweak our areas and then Yarbo removes the safety buffer again we’ll be hitting stuff again.
Does Clockwise/Counter Clockwise make a difference?
Nope, even remapped a couple for just that reason. Always leaves 12" away from where I drove. I’m hoping someone can confirm this behavior and it’s not something specific to my config.
Also, It also only happens on NGZs. Area borders respect the setting.
Hopefully this is a bug, not a feature.
I suggest opening a ticket so they can look into it.
And yea, don’t go re-mapping yet. Cause when they end up fixing this, all of a sudden Yarbo will start ramming into things!
I’d give it a go, but I received the firmware update just in time for the rain. 
I’m curious what would happen if you made it a separate plan, just that strip that’s one mower wide, and set it to mow after the first job was done. All of your missed spots can be separate zones or all can be baked into one other plan. I’m not too familiar with paths and sidewalks, but if you can set Yarbo to mow while on a path, just make it a path and send it on the path after the job is done. No no-go zones involved. Let me know if this works for you.
I added a deadend beside my propane tank between it and some ornamental grass to help hide the big ugly white blob in the yard.
Might be worth a try. Although it shouldn’t be necessary. something has likely changed.
Yep, I’ve been considering a couple options. Motivation has been biggest issue
Again, shouldn’t be needed. Something has changed and it isn’t right. For something that advertises cm accuracy it seems to have trouble with accuracy.
Deadends are the only current option for the mower. This was the workaround we used last year when Yarbo had a 8" forced safety setback.
Pathways can’t included in plans. They’re only for traversing areas.
Maybe Yarbo is just leaving more for the trimmer to do, if only we had a trimmer…
On the same note, as anybody else noticed, the new version of the app has changed the minimum radius allowable for the template no-go zones? It used to allow you to make circular templates down to a one foot radius, but now it seems to stop at 1.7ft.
what if you made a 2 plans to combat this, each is a half circle, with the tank as the inner edge and just widened the area that needs to be covered by that plan, and did that in either side as separate plans so the system doesn’t try to mow where the tank is?
Please excuse my crude illustration here, but with the red as the tank I envision the yellow and blue as two plans, maybe 10 feet wide, and the tank is just the boundary of the plan, and not a no-go zone.
I appreciate your response, but I’m not looking for a workaround at this point. I would like it to work as it did.
Fair enough. Just trying to offer some solutions in the meantime as Yarbo isn’t exactly known for its lightening fast response times for these things, or anything really.
Seems like a solid idea if the issue is no-go-zone related but works properly with a work area.
I feel like this is a bug because my NGZ is mowing along the boundary as I would expect it to. I’m using checkerboard pattern though. Not that it should matter.