Aaaaaa ok
I want my extra spool, for a trimmer I can’t use…….
I’m honestly surprised Yarbo hasn’t sent out an email or post confirming the issue with the Trimmer and outlining their plan to address it.
Also, seems odd to me that they’re still asking people to open tickets about it. Unless maybe there isn’t a way to deploy a universal fix to everyone, and they plan to login and fix each one individually (not a good solution).
Probably still trying to diagnose what the root cause is. It may be more complex than it seems.
Hi there, the coil order is not related to your Trimmer replacement. It was sent as compensation for the delay in the original Trimmer delivery.
Regarding your Trimmer replacement, I saw your latest update in the support ticket regarding your choice to request a refund. Our team will follow up with you about the refund process soon.
We sincerely apologize for the confusion and inconvenience caused. Thank you for your patience and understanding.
Hi there, I’m sorry for the response you received and for the confusion it caused.
I’ve asked the FSE responsible for your case to recheck the issue, and we are also working with our R&D team to further review the logs and details you provided. We will double-check your case carefully to better understand the root cause and provide a more accurate conclusion.
Thank you for your patience and for providing the detailed information and logs. We’ll follow up with you once we have further updates.
After months of my ticket being open, countless replies, videos, logs saved, support playing with my core and trimmer, this is what they found. I will let their wisdom speak for themselves……
Dear Yarbo Owner,
Thank you for your patience.
After analysis, we found that the trimmer is running backward because it started from the end of the memory path. The memory path is directional — when the machine starts from the designated starting point, it will run in the correct forward direction.
To prevent the machine from starting at the end and running backward, we recommend that when you start a “front and south trimming” plan, you position the machine within the mowing area and slightly away from the memory path.
We appreciate your cooperation and support.
Best Regards,
Sherry Cao
Yarbo Team
So they never heard of this issue before, but now they are experts and it is a feature that it can run the memory path in reverse.
They also ignored the fact it did the wrong memory path in reverse, and once mowed and trimmed across my front yard to get to a memory path starting point.
Two months and what a waste of time…..
I honestly don’t know what to say about that.
Yet another spectacular nonsense response. It does the SAME THING on Dead Ends!
They have. 
Ok. I re-read what Sherry said. And I think I figured it out…
She is basically saying that you started the Trimmer while Yarbo was physically sitting ‘on top of’ a memory path.
And now that I think about it, it makes sense….
Yarbo can only drive around autonomously when it’s in a work area. So if it’s sitting on top of a memory path when you tell it to do something, Yarbo’s logic thinks it has to follow that path (or sidewalk) and exit the path into a working area before it can freely drive to where it needs to go.
Does that make sense??
It would make sense to me to error out if it is not in an area when starting the plan. Or if it was in an area when the plan started, that it would drive to the start point and play the plan back as recorded.
Dumb logic, why not have the logic be, MP engaged, drive to the START of the memory path, and then do the path, from the START. So if I do a work plan, and it happens to park on part of the memory path, the smart logic is to go in reverse on the memory path? Not smart.
i agree, it doesnt make sense.
But reading what she said, i am almost 100% sure that’s the root cause of the issue. And should easily be testable by parking Yarbo on top of a pathway or memory path, then try starting another task. I’ll bet it follows that path until it exits the path, then starts doing what you asked it to do.
If that is the case, why does it go in reverse, why not finish the memory path in forward mode?
But it is still stupid logic, user picks a memory path, just go to the START of the memory path and do the path in a forward direction as it was mapped.
A flaw is still a flaw, and they can easily fix it instead of trying to sugar coat it and call it a feature that it should be doing. Wrong is still wrong.
Here’s my assumption about how Yarbo’s path planning is designed…
- Yarbo can only drive autonomously in a ‘mapped area’
- Yarbo considers sidewalks, memory paths, dead ends, etc. as ‘mapped areas’
- When you ask Yarbo to start a work plan, the routing logic needs to get Yarbo from its current position to the starting position of the work plan. And it is only allowed to drive through mapped areas to get where it needs to go.
- If Yarbo is currently sitting on top of a sidewalk, memory path, or dead end and you start a Workplan, Yarbo’s path planning logic says “ok, I’m currently on this path, and I need to follow this path to the end so I can then keep driving to the Workplan starting point”
That’s what I think is going on. My theory perfectly fits the symptoms.
But it is not following it to the end, it is following it in reverse trying to get to the start, but it can’t even do that because it can’t do corners as it smashes the trimmer into stuff. Why would it be programmed to do something wrong? I know why because yarbo programmers suck, that is the point to take from this. It is not doing the correct action.
This is another example of why I think Yarbo needs to develop and release a completely new Yarbo OS 2.0 that properly addresses all of these weird issues without workarounds and patchwork coding.
The company has learned a lot about what works, and what doesn’t work. A new software stack can incorporate all of those lessons learned and give us a much more usable and scalable platform.
100% they need to do a do over!!! Admit it is a design flaw, they don’t have to write stupid responses trying to tell me it is a feature, and that is how it is suppose to work.