I had to record it this time, when the obstacle avoidance mode is on, it gets scared from grass, when where I have recorded a trimmer path it will detect an obstacle everything in the path of the trimming map, making it unusable, to the point that today it just started going in circles, I stopped it and in the app there was some type of delay and even if the Yarbo was off it was just moving in the app.
when I turn obstacle avoidance off it climbs my trees almost falling over, today it happened again into a rain barrel and broke a peace of the trimmer since it sat on it and damaged the barrel, I don’t understand why if the robot goes to the ski it wouldn’t have a safety that it stops immediately (should bump into tress and just keep in going in the first place).
Hi there, we’re really sorry to hear about the issues you experienced with obstacle avoidance and the potential damage caused. We understand your concerns, especially regarding the safety of the machine during operation.
Regarding ticket #222354, our support team will need to further investigate this case and review the related logs to better understand what happened and identify the root cause.
We kindly ask for your patience while the team completes the investigation. I’ll also continue to follow up on this ticket to help ensure it is properly reviewed and that the issue is addressed appropriately.
Thank you for taking the time to provide the video and detailed feedback. This information will be very helpful for our team’s analysis.
The trees have been the most impressive lol but I didn’t have my phone I’ll snap some pictures next time since this will surely probably happen again, yes the barrel is that circle no go zone.
It’ll be really nice once Yarbo fully respects no go zones again.
I had my Yarbo try to back up onto an object outside of the working zone once last week. First time it happened for me. Thankfully I was standing there watching it at the time and was able to quickly slap the emergency stop button.
At least in my case, I think the behavior was caused by the trimmer being attached.
The issue with climbing trees was already known last year… I had reported it several times, and then it seemed to have disappeared after the updates… but it has reappeared since I installed the trimmer.
If anything, it’s gotten more flagrant! It’s now at the point where I can watch it examine my NGZs by 12" every mow. Ticket after ticket after ticket submitted by countless users. There’s no way they don’t know what’s going on. Yarbo had made a choice NOT to fix this. I wish I understood the endgame. The first time someone gets injured by this behavior, all of this dialog on 10 different outlets and their ticket log will all be part of the lawsuit Discovery.
Wait, let’s pretend this is a completely new issue we’ve never heard of followed by requesting data that’s either unrecoverable or they’ll never actually do anything with. This is the culture of the company we’re all now tied to. Let’s see what AI has to say. Maybe it’ll start with “I’m sorry” followed by “regurgitated complaint”, finished with “in a future update”. End of story. Ticket closed with some nonsense response.
It’s a problem that has persisted since it went on the market last year, but only in reverse… I’ve never had it happen when driving forward. Check to see if the vision cameras were dirty.
Here’s another neato one mapped right through a NGZ. I’m sure they’re all over it. Glad I moved the glass cat feeder that was here. It already ate one earlier in the season.
Edit: Also notice how if perimeter laps extend around a NGZ it ignores the outer lap turnaround point aand goes to lap one. Don’t recall this being documented anywhere.
@cobradunn@rgloverii@Gabriele Please rest assured that we have not chosen to leave this issue unresolved. Our team is continuing to work on improvements.
There can be different causes behind similar NGZ intrusion behavior, so we need to identify and address each case carefully rather than applying a single fix to every situation. We understand how frustrating this has been, especially for users who have reported it more than once, and we’ll continue working through these cases step by step.
