Anyone else have problems with Yarbo skipping a pass when mowing? This is a replacement Core due to a GPS issue previously that couldn’t be fixed. Haven’t had this issue before. Any suggestions?
Yes, it happens sometimes especially with obstacle avoidance. It’s a path planning issue if it wasn’t triggered by obstacle avoidance. What avoidance setting are you configured for? If you run a pattern like checkerboard, it’s a good way to get any missed spots on a second cut. The other possibility is there was a temporary GPS issue and it deviated off course for a bit.
I have Avoidance set on “Gentle Contact” with “Ultrasonic Sensor” on, and everything else turned off because it would see ghosts and not move if I had “Boundary Obstacle Avoidance” turned on and anything higher than gentle contact on. Maybe I should turn off “Ultrasonic Sensor” too?
Depends on if the grass is tall and it’s detecting it as an obstacle. If it’s doing it a lot, then you might want to consider it. It should be putting red splotches on the map if it’s doing obstacle avoidance. Otherwise, could just be some path planning oddities.
It’s a mower. It kinda needs to know what grass looks like and not avoid it. ![]()
LOL, true, but if it’s tall it can look like trees in those cameras ![]()
I can’t help but wonder how much more affordable Yarbo would be if they just removed all of the components that don’t work? Seems like an awful a lot of expense to add cameras and sensors to a unit that don’t work just to say they are on it for marketing purposes.
That almost looks like a stalled blade with a lot of overlap.
Missed cuts can be caused by a few different factors. I noticed from your other posts that you’re currently experiencing GPS issues, so this could potentially be related.
It would be a good idea to first resolve the GPS issue and then check whether the missed cuts still occur afterward. That will help narrow down whether it’s a positioning issue or something else.
Please feel free to share an update once you’ve tested it—we’re happy to help further if needed!
Anyway to verify if it is a stalled blade? And, what causes it so I can try to prevent it in the future?
To me your pic looks like classic non-existent object avoidance. I’m not sure what steve saw. In my experience blade stalls cause Yarbo to slow to creep or stop, not swerve.
I’ve had this happen. Not so much when the grass is at a normal height, more when it’s a bit too long. Here is a picture of that happening then a second pass of 90 degree or a spiral cut cleans everything up.
The core generally will figure it out if there’s a physical jam.
A wiring fault might not dump enough current to be an issue, and I’m not sure if there’s a “cutting motor unplugged” detection. Probably the easiest thing to do is listen when they spin up, since the blades start in a sequence.
The dumber test is to just turn on the blades and drive forward over uncut grass. If both are cutting, you’ll know it. If not, you’ll see that, too.
Just and FYI and update for others, and to put a note here in case I forget this setting in the future. I turned off “Ultrasonic Sensor” and all seems to be working as normal. I’m just dumbfounded of how much tech are on these things that don’t work!
That’s strange because both of mine are enabled and I don’t have any issues. You sure it wasn’t the GPS issue?
Thanks for sharing the update—really helpful to know.
In taller grass, the ultrasonic sensor can sometimes misidentify the grass as obstacles, which may lead to skipped passes. Turning it off in those conditions can help improve performance.
Please feel free to keep us posted on how your machine performs after this.
What is the status of the ultrasonic sensor in the non Pro mower? Is there a plan for it to be enabled?
I was wondering the same. Why enable in one model and not the other.
Another feature to get you to buy the pro that’s not offered on the standard
It was enabled last year and was causing a lot of false positives (ghost object detections). It was disabled to let them refine the algorithms for it more. The Pro sensors are higher up and far less susceptible to whatever issues were occurring with the M1 sensors. Hopefully they re-enable those soon too.

