What happened to Deadends over the winter. In this example I have 4 Deadends that were sequentially mapped so each started 6” directly in front of the other. When it performed them, it only had to move forward a few inches to start the next one. This no longer works. It now does this back and forth left and right garbage, then zero-turns to the correct heading between each one. How does Yarbo continually break things in EVERY SINGLE update. Deadends are core functionality that can’t change basic behavior with firmware updates.
I’ve also seen similar back and forth 5 or 6 times and zero turn before starting perimeter runs in areas. This yard destroying behavior has got to get fixed. We’ve now been dealing with unwarranted zero turns for over a year and ZERO has been done correct it.
Could you post the map or other example of what your Yarbo was supposed to be doing?
I agree, it’s rather frustrating when a previously working plan is suddenly broken due to a firmware change.
Not sure what you’ll be able to discern from this, but here it is. This isn’t my first rodeo.
Here’s the entire map
Yea, that’s some weird new behavior for sure. Sorry to see it.
Probably should open a ticket and include the video & highlight on the map where the action was occurring. Unfortunately I suspect we are gonna be finding other weird new issues as we start using our mower modules this spring.
Great… now I have to retest my dead ends.
Out of sight, out of mind!
We’re really sorry for the frustration this has caused—especially with something as core as Deadends behavior. We completely understand how impactful this is on your lawn and overall experience.
Could you please submit a support ticket and include any videos or map references if possible? This will help our team investigate the issue more thoroughly.
In the meantime, I’ll also make sure your feedback is shared directly with our team.
Thanks for taking the time to highlight this—we truly appreciate it.
Make sure you have eyes on it. I hope it’s unique to me. I’m also seeing it not following the mapped routes and squaring turns off. When there’s a fence a couple inches away, this doesn’t end well either. I’ll post a ticket into Neverland and see what comes back.
And just to add, I remapped a couple other Deadends and found the backing into Deadends bug is STILL there. If you don’t map them in sequential order all hell breaks loose. Don’t try to delete the first one and remap it. In my option all of this is the result of unskilled coders working on things they don’t understand. That’s just me of course 
#186627. Super exited for the response.
Update: Provided timestamp for video today. Waiting for response.
