Please add an option for a ‘randomize path’ option when creating them. It would allow the Yarbo to move the endpoints of a given path by some set amount (5 feet, 10 feet, etc) to limit lawn damage.
9 Likes
Something like this has been requested many times. They appreciate the suggestion, will bring it up to the dev team and will look into it.
3 Likes
Hi Tim,
Yes, as @JNS mentioned, we’ve received similar requests before. Our product team has carefully reviewed all the feature suggestions from Yarbo users aimed at reducing lawn damage caused by repeatedly following the same path, and we do have some design concepts in place to address this. However, the feature has not yet entered the development stage.
We truly appreciate your patience and understanding as we work toward providing a solution for this issue.
Move the path once a week… that is what I doing for now. If you don’t you will have a track for sure. Don’t try to leave the old ones there and hope it will take them sometimes, it doesn’t. It always takes the same one.
3 Likes
You can drop NGZ’s at the entrances and enable and disable them as you want.
It would be nice if you set outside boundaries of the path and then let it travel those boundaries. Sometimes you need it to be spot on but in a lot of other cases it could be several feet wide in my yard.
4 Likes
But won’t it skip this area when mowing? How big should the NGZ be?
So what you are saying is draw like 5-6 pathways that I want to alternate form and activate/deactivate them? That’s brilliant but again, it will leave an area uncut? Sure it will get it the next week but meanwhile? So you add a dead end on top of it?!?
Correct - it will avoid the active NGZ’s. I guess you could do a DE to cover the missed sections of all the pathways (try to get it all with one DE if possible). It’s not a perfect solution, but it will let you map it once and with a few taps adjust accordingly before starting. Can also be used for Yarbo to stop and wait when gates are closed or roads are being crossed. Let’s you be in control to move it across those areas.
While they figure out how to optimize pathway selection, if they could allow us to program all of this on the schedule (NGZ on/off, deadend, speed, pattern, etc), we could do a lot…
(not kidding I literally wrote a sham app using GPS data from my area and my Yarbo pathway coordinates and I can us a solver (ORTOOLS by google to be precise) to find among several pathways the best one… you can even add randomization factors and so on. Clearly they should be able to do this…)
2 Likes
@Yarbo-Forum if your developers are interested:
it can run natively in C++ and you can call it from basically any language… you can feed it GPS coordinates. It is lighting fast…
So when a « go back home » job triggers, you feed it current coordinates, the way points it has to choose from (including NGZ and others if needed) and it will find the fastest one… Might be worth spending a few hours of dev time? Thanks for considering!
2 Likes
@Micke Thanks for sharing. We appreciate the OR-Tools idea. I’ll share this with our engineering team.
2 Likes