I agree with everything you typed, but will add the software development team needs a house cleaning. They are spitting out garbage.
I am lucky my yard only has dangerous things for Yarbo farther from the edge, but I did get a few scrapes in my Pro Mower last fall and this spring. Lucky for me I had an issue and they had to send me a new mower, so that got reset.
Hi there, first of all, thank you for sharing your honest feedback with us. It helps us better understand where the overall user experience still needs improvement.
Regarding obstacle avoidance, the latest hotfix includes an optimization for Moderate Bypass Mode that should help reduce false obstacle detections caused by tall grass. We’ll continue working on obstacle avoidance performance and improving its overall reliability.
As for AI support, we do have to acknowledge that the experience since its launch has not always been smooth enough, especially when it comes to more complex after-sales cases, and we’re sorry for the frustration that has caused. We’ve been continuously refining the workflow since launch, and so far it has helped improve overall support efficiency. That said, we know there is still more work to do to make the experience better and more effective for users.
We also want to clarify that using AI in the support process does not mean we are reducing our investment in actual support personnel. We are continuing to build and strengthen the support team as well.
Thank you again for being so open with your feedback.
Thank you for the reply. I actually did not expect one from Yarbo-Forum Official. I look forward to trying the hot fix V3.14.11 with the changes made to Moderate Bypass Mode and obstacle avoidance. I want to particularly see how it performs with the fence boundaries.
I keep the Yarbo active enough so tall grass is less of a problem. In my case, if the obstacle avoidance sensitivity is less along the fence line, the majority of my frustration goes away. I have tried increasing the Perimeter Mowing Laps but that did not work with the previous firmware. Avoidance went from acceptable to extreme in the last firmware change. (Too bad we cannot have a slider in the app to adjust obstacle avoidance sensitivity for each area but that would be a significant programming change with adjustable variables in the algorithm.) Let’s see how V3.14.11 does.
Also thank you for your acknowledgement that the AI experience has not always been smooth enough. I expect a lot of us beforehand search the forum to try to diagnose problems ourselves and only then when we cannot resolve the problem we contact support. Good Yarbo is continuing to build and strengthen the support team but customers still have to go thorough an ineffective AI resolution each time before escalating their need for support. This can remain very frustrating even with the increased staff.
AI - For example searching in the forum for “Yarbo lift” the Discobot responds
"Based on the current Discourse instance, there are no specific topics found regarding a “lift” service or product named “Yarbo.” It is possible that: Yarbo refers to a specific external company or platform not discussed in this forum. The query refers to weightlifting or fitness, and “Yarbo” is a typo or specific brand not indexed here.
Interesting isn’t it? Yarbo is an external company and no product is called Yarbo in the Yarbo Forum. Just Saying. When the AI system improves then it will be an asset.
Back on point - Thank You again for the hot fix and acknowledgement.
@Welles Thank you for the thoughtful feedback.
Just to clarify, the forum AI here has not yet been systematically trained or optimized around Yarbo-specific content, which is why you may sometimes see responses like the “Yarbo lift” example you shared.
The AI I mentioned previously was mainly referring to the AI within our support system. That is an area we’re actively working on, with the goal of making it more accurate and more helpful before a case needs to be escalated to a support specialist.
As for the forum AI, we may look at giving it more Yarbo-specific training and improvement in the future as well. Thanks again for pointing this out.