We’ve received a feature request regarding global area settings, which you can check out here: Global Area Settings. Our product team is currently designing this feature, but before moving forward, we’d like to gather your feedback to help us decide whether to implement this feature, as it may involve significant changes to the current settings system.
Based on our current design, this feature will allow you to set global area settings while still enabling you to designate certain areas as independent, treating them separately and unaffected by the global area settings.
We’d love to hear from you on the following:
Would you like the option for global area settings + independent area settings?
Yes, I would.
No, I prefer the current area settings system.
0voters
Do you have any additional thoughts or ideas on this feature request that could inspire our product team? Please share your thoughts by replying to this post.
Would you like elements such as pathways, dead ends, and no-go zones to also have the global + independent settings feature?
Yes, I would.
No, I prefer to retain the current design.
0voters
Your feedback is invaluable to us as we continue to improve our product based on your experiences and suggestions!
This feature would be extremely useful for overriding settings across multiple areas. It would be optimal if you could specify which global settings to apply to all areas or select specific areas. It should always be optional and be able to be overridden per area.
Please include a global parameter to randomize paths to avoid lawn damage caused by repeated travel on the exact same location. This new field would include a maximum distance in inches that the rover can deviate to on each side of the shortest optimal path, and apply to pathways as well as crossings to other areas and travel to no go zones when mowing their perimeter.
I’d like to also see a global parameter for overlaping please.
My knee jerk reaction to the request was a yeah. Now I’m wondering if it’s worth putting so much effort in and if Yarbo can instead have engineers help with my snowblower vs. mower map issue (I haven’t forgotten! LOL!) and bringing Sidewalks to the mower (I’m not going to stop asking! ).
A better question might be “What would folks want to have globally settable for a module on a semi-regular basis?” For me: Mowing Height, as @bryan.wheeler has mentioned – he raises this mowing height as we get into summertime. I may do the same as we get into drought. Else everything is set pretty much the way I’d want it and won’t change.
The original enhancement request mentioned Pattern and Obstacle Avoidance. How often will those need to change…really? Obstacle Avoidance may make sense because strong sun can fool Vision, so being able to set it to Gentle Contact everywhere might be useful. For Patterns I always do a Preview to make sure the pattern is right for that Area, so I’d never do something global.
Yes, when we get Perimeter Mowing Laps 0, folks are going to want to change that, but it’s a one time change. Boundary Set Back? Set per Area, left alone, usually, until that specific Area has a need for a change of that setting, as when bushes begin to crowd in there.
If we’re talking priorities, major changes to the Settings code, and limited coding/testing resources, this feature could be scaled back to a real sweet spot to “Apply (this change) to (these Areas)” and have a scant few options. Code it so it can be expanded later.
For the snowblower it could be auger height and auger speed, as those are adjusted frequently for the snow conditions, and I believe those are per Area/Sidewalk/Pathway. Forward motion is global, as with the mower. As I recall anyway.
I think a global setting would be moderately useful… much more useful would be the ability to set up groups or templates for settings (multiple). And then you could apply those to any number of zones. You could have things like “Tall Grass Areas” “Mannicured Areas” really whatever made sense for you… For me i have multiple work areas that are my front yard for example… and multiple areas that are my side / back area. If i want to say mow the front yard shorter, i have to update multiple areas, but don’t want to update ALL the areas…
I am sure there are other use cases that this woukd work for as well and could cover your global setting scenario if you wanted to use it that way.
Edit: would also make it simple to apply settings to a new zone / zone that you needed to re-map.
Yes I would add that when creating new areas or restoring from a saved map it would be nice to have user specified global default settings that automatically apply vs the Yarbo default.
give the possibility to inverse the spin, maybe if you are warried for grass cloat (not for me, i removed the guards) make a warining. but PLEASE give the possibility to all people are using mowler withoit guard (IT WORKS LIKE A GOD) to inverse the spin woth some settings.
It would be the only one in the world with a cutting efficiency and blade wear ratio never seen before.
simply give a warning and an assumption of no liability or damage.
Very, very, very much, this.
“Setting” templates. Have one that is the default selection that cannot be deleted.
An area / deadend / etc can specify which template it uses? I’d suggest they MUST specify which template it uses. Remove settings from areas, deadends, etc.
I’d strongly urge that settings should be properties of templates, and zones, only.
Migrating to this strategy would entail making each existing area/deadend/etc’s settings into its own template. Users who ignore the new strategy would be fine. Users who care would simply consolidate templates. New users would never know, and simply edit (and fork) the single default template into news ones, when needed.
Keep the settings abstracted from the polygons as best you can, for the sake of the expansion modules you’ll be creating.
I would like to have connected areas where the outer perimeter is mowed together, but within it different heights can be mowed or obstacle detection modes can be changed.
).