Yep. The vision is worthless.
Put your new bumper on, switch to Gentle Contact and life will be back to normal again 
Hoping that is the case. Indeed that is how I was mowing before and was much nicer with less of this…really wish that vision would be better though. There are certainly areas I like it on. Nice you have the option to define these areas. I feel like that was done because of the limitations, none the less helps.
There’s a bunch of things I wish worked better, including the vision. I’ll bet there are over 100 known bugs that keep getting ignored.
Running into the same issue on the latest firmware, app, and pro mower module. Support suggested I increase the overlap, then my Yarbo broke down and I’ve not tested the recommended settings. The weird thing is that it only happens in a few areas, then goes back to mowing everything. When I encountered this, it always seemed to be in the first part of the area. Not sure if that’s relevant or not.
Yes I have seen that suggestion. I say no to it. That big one is a full Yarbo width off. Even with 8 in would still be there. I suspect some of the small ones too as they are leftovers after course corrections. Then having to mow 2x with checkerboard is crazy on top of that overlap. This is a VERY small part of my yard. I will say that in my open field this is much less, but still misses 1-2 in rows. That gets pretty well cleaned up on the checkerboard. Again making it easier to do checkerboard would be a big help instead of constantly modifying the area…
The ones in your picture look to me to be from phantom object avoidance based on the visible pathing. Sometimes it gets back onto the intended line quickly, others it takes the entire run and gently eases back over where it belongs. It should not behave like this, but as we know there’s plenty of things it shouldn’t do.
That’s my thoughts also. With their twice a week mowing recommendation, increasing the mowing overlap would increase the mowing time and I can’t see how it would finish my yard in time. Maybe if they optimized the turning or something. Seems like 25% of the mowing time is spent trying to turn itself around. 
Zero turns and U-Turns will cut the time considerably. But you need tough grass and to rotate the patterns/turns frequently.
Could be, which I am happy I will be putting a new bumper back on and see. I certainly have had many more issues since relying on vision. I will say though as you can see it is a bright day, no shadows there(also can see Yarbo so not like it was a long time ago). I do suspect it has something to do with avoiding the tree and not properly repathing. Even though it was avoiding nothing as it can clear the branches with no issue. I will be glad to turn this feature back off…
Thank you Yarbo for the new bumper. I am happy to report it is working as expected. I know you closed the ticket, don’t want to re-open. Watched it gently bump my red maple and correct.
Not sure what to think of this, but it feels like the ultrasonic sensors may be tied into the bumper. Makes sense in a design aspect. I can say after changing the bumper the whole feel has changed. Use to plow right into things, now it again slows then bump, move.
At least yours moves. Mine hasn’t cut a blade of grass yet and going on 3 weeks old
If you watch carefully, I’m curious if yours slows, approaches it carefully, then floors it and slams into the object for the last inch.
I can’t really say when the bumper was not working. Now that the bumper is working again I would say no. When the bumper was broken it seems it kept normal speed and just went in to it. Weirdly even with vision on. With vision it would just totally avoid if it saw it. If it didn’t see it, seemed to just keep going.
I can say after bumper replacement for what ever reason it is like a new mower. I turned off vision, it properly detects objects in front presumably with the ultrasonics, slows, bumps, course corrects. I am back in business and having to go save it is much less. Vision is just too unpredictable, I feel the ultrasonics actually do a good job.
Pretty sure for the M1 it’s using vision for that currently.
Certainly possible, not really sure. It mimics the same thing my Luba 1 5000 did, which had no cams and relied on the ultrasonics. If it was using vision I would think it would be slowing down under the tree branches it sees, but are not in its way. Although like mentioned in other posts, the app makes it look like the ultrasonics is not working. My sensor experience tells me that could just be a software bug though, and may actually be making readings and correct elsewhere in code. They all have a calibration routine and the numbers are wildly off from sensor to sensor even among same make and model.
