Currently we can only edit the name for NGZ. Is allowing edits within the app on the roadmap? It’s rather time consuming the need to drive Yarbo to an area to remap when it can be simplified with a few easy changes through the app. I’ve also used templates, but again they can only be replaced, not edited.
Was there a change to the resent firmware update that more accurately produces the time remaining? I’ve noticed a much shorter time to complete and seems much more accurate.
I would like to be able to edit NGZ’s on the fly for sure. That would be very handy.
They made some changes to the algorithm that makes it more efficient in mowing. Still a lot of work to be done there, but I was noticing 45 min gains on average in a lot of my areas. But, slope mode tends to steal some of that time back with the slow down and or GPS pauses. But overall, I am seeing it cross areas less frequently to get the peices it leaves out when planning.
We understand your need for editing NGZ on the map. After confirming with our product team, this feature is not something we plan to implement in the short term due to potential safety concerns. However, I’ve passed along your request to our product team, and we will reevaluate this feature in the future.
The safety concern could be mitigated by having a test button. It’s no different than me deleting one and recreating it in the same spot. Except in that scenario I am more likely to mess it up and misplace or misalign it.
Resizing it would just give more granularity and fine tuning to ensure it works appropriately. I’d argue it’s safer (for templates).
I agree with @bryan.wheeler here. This is short-sighted thinking from the product team, and they should reconsider. The lack of ability to fine-tune the positioning/sizing of a NGZ after it has been saved is not a safety “feature.” Manually deleting and recreating the no-go zone is no more “safe” than allowing one to be edited. At the very least, allow templated NGZs to be edited. These were placed into the map virtually anyway.
100%
The editing and a no-go test button is essential as Yarbo does not seem to understand its footprint and orientation. It only seems to understand the location of the left antenna.
I have quite a few tree trunks less than 12" diameter and it seems the minimum reliable no-go zone radius is about 4 feet. Instead of going around the tree trunk Yarbo’s paths now have shorten rows and therefore more turf wear.
If safety was a priority, Dev should have the User test and approve every no-go zone creation and edit.
Thanks for sharing your thoughts — our product team has reviewed your feedback and now has a phased plan in place for this feature.
Version 0.1 will introduce the ability to adjust the size and location of No-Go Zones (NGZs) created using templates. For NGZs created by manually driving the rover, we plan to allow repositioning, but not changes to size or shape at this stage.
Version 0.2 will expand on this by enabling full boundary adjustments for NGZs, regardless of how they were created.
This is our current plan, but the exact approach may evolve based on further evaluation and testing. We really appreciate your input — it helps us make smarter, more user-centered decisions.