Could there be any possible way to change an area into a no go zone? During the summer I mow the areas of grass within and around the drives in my yard, those same areas I would like to have set as no go zone for snow blower and vice versa.
Also when I have equipment/ vehicles in my yard I just put a no go zone there until it is moved, then if I could switch the no go zone to an area, I could just set it to mow (where it wouldn’t mow before)
You can certainly put NGZ’s over the entire areas now and turn them on and off as needed.
Yeah and being able to move/ resize is nice
But then i have to draw the area and if complex draw the ngz. But turning off a ngz where something was parked, i have to drive around the ngz and keep mowing it over and over to get it with rest of lawn.
Mow by multiple time would be nice for that too, mow this area 5x rather than having to manually set it 5 times
Hi there, thanks for sharing your experience and the way you use these areas throughout different seasons. I can definitely understand why being able to switch an Area directly into a No-Go Zone, and vice versa, would make things much more convenient.
At the moment, there isn’t an option to directly convert an Area into a No-Go Zone. As a workaround, you can create a No-Go Zone template over the area you want to exclude, then simply enable or disable that No-Go Zone depending on the season.
You can also use the Area Label feature to label an area for the Snow Blower or Lawn Mower. When Yarbo is performing a task, it will prioritize traveling through areas whose labels match the module currently installed.
I also understand your second use case, especially when a temporary No-Go Zone is created for parked equipment or vehicles, and you later want Yarbo to mow that spot once it’s clear. Being able to convert that No-Go Zone directly into an Area would definitely make that process easier.
I’ve moved your post to the Suggestions & Feature Requests category so we can collect feedback from other users as well. If we see more users interested in the same feature, I’ll help pass it along to our product team for consideration.
This would be cool, but with the current logic/design you’d end up with pathways starting or ending in a NGZ and that would make errors. Would be nice if overlapping areas could be selectively combined for transit paths based on the tags and other settings and pathways made optional
Or if you could enable and disable pathways…
Another feature asked for all the time but never gets implemented.
JUST LET US TOGGLE!!!
TOGGLE! 
organ music
TOGGLE!
organ music
TOGGLE!
organ music
Did you up vote? The OP didn’t even upvote his own
, that should probably be default