Can we please remove the “Mow Along No-Go Zone” default Setback. When I 1st received my Yarbo, it mowed right up to the No-Go Zone when slider is activated. Now after a few firmware updates, it now leaves a 6" patch unmowed around my no go zones. I tried using dead ends to get right up to the No-Go zones, but now it crashes into things and runs over my
edging. I have since removed the dead ends after damage to my edging. As a recommendation, put the default number to 0, but add a slider to adjust to a offset from the no go zones.The yellow around the no go zones is where I had added the dead ends. The video is the result with the dead ends added.
3 Likes
Thank you for your detailed feedback—we truly appreciate you taking the time to share your experience.
After confirming with our product team, the current setback around No-Go Zones is designed for safety purposes, to help prevent Yarbo from accidentally entering restricted areas.
We understand your concern and the inconvenience this may cause, but at this stage, we do not plan to change this default behavior. That said, we’ll continue to pass along suggestions like yours as we look to improve future updates.
1 Like
@Yarbo-Forum - I understand the line of thought, but there’s a problem: We’re all noting our No-go Zone borders because of the unmowed grass and shrinking the No-go Zones, defeating the set back. Should Yarbo now turn this No-go Zone buffer off, everyone’s flowers are going to get mowed. Yarbo will need to add a “No-go Zone Set Back” setting and default it to the current buffer size to keep my GF’s irises from becoming salad.
3 Likes