Correct it was a 3 day roll out.
1 Like
Thanks everybody, that was what I thought they said. If I don’t get it by tomorrow I will put a ticket in.
3 Likes
Sorry for the late reply. I just checked your support ticket and didn’t see any follow-up—has the issue been resolved?
If the problem still persists, please let us know, and we’ll be happy to investigate further and assist you in resolving it.
Thanks for your question! In general, the Smart Turn option causes the least wear on the lawn, as it avoids dragging the tracks as much as possible.
Hope this helps clarify things! Let us know if you have any other questions.
This is no longer true with our yarbo. We are now seeing a smart turn be 3 smaller zero turns which is causing turf damage ( removing grass down to the dirt) with our lawn planted last October.
We can’t use yarbo if while it causes extreme turf damage. We are waiting on further instruction from support ( we are requesting a RMA and refund) as at this point, the unit we paid for in June 2024 and delivered January 2025 has never completed a work plan.
Every firmware seems to introduce more serious issues than the last.
1 Like
Don’t know, yarbo went completly offline over night, can’t reach it at the moment, I’m not at home so no physical contact, will update when I know more.
Update: Yarbo had no network connection, had to Bluetooth into the unit and restart it, it’s now reachable again. Regarding my mapdirft support told me there is none, except I have the sreenshots of it saying so.
I set all may maps to smart turn, but as mentioned they changed something mad yarbo is not turning as smoothly as before.
After using the new firmware for almost a week, I can safely say that dead-ends are no longer usable for me.
- Yarbo’s horribly incompetant decision to make zero-point turns on all dead-end navigation is now tearing up the lawn. Yarbo’s official response (via support ticket) is that they changed to zero-point turns because there were too many people complaining of Yarbo hitting things.
- If the start of a dead-end happens to be on a hill, Yarbo will “dance” around the starting point, instead of just approaching it and pause (like it did previously). Yet again, another additional wear at that location.
With several months in between firmware updates, I’m assuming this is not going to be fixed anytime soon. Does anyone have any suggestions for how to make dead-ends work with this new zero-point turn nonsense? I’ve tried the dead-end “nubs” (very short dead ends) to force Yarbo to navigate from specific directions, but all this does now is move the problem to the nubs. I haven’t tried creating a series of nubs, and switching between them, but Jesus, that introduces a whole new set of inconveniences. When is Yarbo going to make this process easier not harder?
Totally unrelated question, anyone interested in buying a used 4-in-1 2024 Yarbo package? DM me 
2 Likes
“Stubby Deadends” - not “nubs”! F! See me after class! (I think you were talking about the short stubby Deadends anyway…)
Hmm…I typically line up the Stubby Deadends to where the rover will be coming from, so it hops right on. I haven’t been watching closely (even I get tired of looking at Yarbo’s maps sometimes). Has the behavior changed, even with Stubby Deadends in the direction of the rover’s travel?
@Ken yes your “stubby deadends,” exactly!
If Yarbo is coming at it straight-on, then there isn’t really an issue here. Yarbo approaches the dead-end, stops, spins up the cutting disks, and moves forward. The problem is when Yarbo is not approaching head-on, it will go through the same routine, but previously where it would smart-turn into the correct direction of the dead-end, it now zero-point turns. Do this for every job, the grass is getting tortured.
So, I’ve used your Stubby-Dead-Ends to force Yarbo in the correct direction, but that just moves the problem over to the stubs.
I thought, well, what if I create several stubs, and just enable/disable to give some variation so the zero-point turns aren’t constantly happening in the same spot? Ugh, but when you disable a dead-end, it takes it out of order and places it after all the enabled parts of the plan. Enabling/disabling parts of plan is now a maintenance nightmare when you just want to execute a job.
@jeremyj114 - Are you inside my brain? Also thinking along the lines of “great, you MOVED a problem, so NOW WHAT!?!?!” with the Stubby Deadends for navigation. I justified it with with, well, the rover goes straight onto them, so it’s not a big deal, and varying the Pathways seems to be a decent trade-off.
But, yeah, when mowing an Area with Deadends it will attack those Deadends with ferocity, and tracks and start points become visible. To work around this I have created two versions of Work Plans – one with the Deadends, one without, and I alternate, so the Deadends get hit every 6 days or so instead of every 3.
Which leads me to another question you raise that I also have: How do you manage all the Work Plans? Exactly. Not easy with the current GUI juggling the Work Plans and Deadends and all that. I wish we could dump our Work Plans into a file so I can have their contents right in front of me (and edit then import?), create duplicates of Work Plans, and do other things in the GUI to make this thing a little easier. I can probably use Bluestacks to look at Work Plans on my PC as I’m editing them on the phone – yeah, that’ll help.
And to Schedule the Work Plans…? Still manual. I was thinking that I’d define my Work Plans and build “Mowing Days” from them (basically the “Work Plans of Work Plans” feature request that was not accepted). These “Mowing Days” would be in a queue based on how often you want that “Mowing Day” to happen. They would not be tied to a day of the week. The Scheduler would just pick the next “Mowing Day” off the queue and run it that day, putting it back at the end of the rotation. But the “Work Plan of Work Plans” idea got shot down, and the Scheduler doesn’t work that way.
BUT…If we ever get REST API access and you have an Arduino, you know what to do. LOL!
The one thing we need to remember is that when we get this dialed in, it should require less of this kind of fiddly maintenance. I’m slowly getting there. My yard’s mowed for now, even though I’m the Scheduler.
2 Likes
And, the API is on indefinite hold. I was pretty disappointed when I read that one.
3 Likes
Yes. Very disappointing. It would be nice if HomeAssistant could get my yard mowed.
I guess it’s currently only a dream.
1 Like
Yes please! HA Integration.
1 Like
@Ken Yep, I have 2 areas right now (3rd coming soon, waiting for some new grass to mature). I have 4 work plans, 2 with dead ends and 2 without. I think the obvious answer is, as you said, alternating the dead ends.
I can see why an open API has been put on hold. That requires a mature feature set that is reliable. They are changing things way too much to open it up to end users. But, man I’ll tell ya, if they did have an API exposed, this would be much easier. I’d sit down with Claude Code and have some fun. Maybe one day.
@Yarbo-Forum get this crap fixed, this is becoming a nightmare to work with.
2 Likes
Wishfull thinking on my part and i completly agree. Doubt we’ll see any real fixes before end of the growing season based on prior release dates. Next year there will be a new model that supposedly fixes all issues.
5 Likes
Why does navigating through multiple areas to reach the target area trigger slow downhill slope behavior. The blades arent even on yet. Going downhill now takes 3 times as long to reach the destination - except in pathways where it increases to the set speed.
1 Like
Thanks for the update. I’ve seen your screenshot regarding the map drift issue. In some cases, this can be a false alarm caused by weak GPS signals, which may lead Yarbo to briefly misidentify its location. When that happens, the system may trigger a map drift alert, even though there’s no actual drift. That’s why, when we check from the backend later, no map drift is detected.
If this issue continues, please feel free to reach out through your existing support ticket — we’re happy to assist further.
Regarding the turning issue, we haven’t made any changes to the Smart Turn logic. However, there are certain scenarios where Yarbo may switch to zero-turn automatically, such as in tight spaces or when there are obstacles both in front and behind the rover.
Let us know if you have any other questions — we’re here to help!
We’re truly sorry to hear about your experience and the ongoing issues with your Yarbo unit. We understand how frustrating it must be, especially when it affects the condition of your lawn. Could you kindly share your support ticket number with us? This will help us follow up more efficiently and ensure your feedback is reviewed by the relevant team for long-term improvement.
Your input is very important to us, and we truly appreciate you taking the time to share it.
Thank you again, and we’re committed to working with you to resolve this.
Um, yes, you did make changes to turning logic. Pay attention to all the users complaining about dead ends
1 Like
Anyone still seeing the 5 sec delay No-Go warning screen on Android 3.15.4? I’m not seeing it on my Apple but it still comes up on my Fire Tablet. The app is sideloaded, so I’m thinking I might need to remove/reinstall.