Near-miss after firmware update — sharing so others check their edge areas
I’ve gotten very comfortable letting my Yarbo do its job, and this was a good reminder not to.
Just updated to the newest firmware and app version. GPS seemed noticeably improved — that part looked great.
Set the schedule to cut my front yard as usual. There’s a slope at the edge of that area where I’ll occasionally get a tip alarm along the driveway at the bottom of the area, so that wasn’t unusual. What was new: I checked in on the mower’s progress and saw a slippage error I hadn’t seen before in that spot — “Error - Suspended,” way outside my mapped boundary.
I instantly went WTF. Ran out to check, and here’s what I found:
There’s a 25’ gully just a few feet past where that tree is. I keep a 6’ boundary in that area that I cut with my riding mower, and the Yarbo ended up well beyond it. I’m honestly just thankful that tree was there — it could have been a very different outcome.
I’m not trying to bash Yarbo — I don’t know exactly what caused the slippage, and the GPS improvements genuinely looked good otherwise. My point in posting is just: if you have any drop-offs, gullies, or steep edges near your mow zones, never assume the boundary will hold, especially right after an update changes behavior. Go check in person. Glad I did this time.
I truly love the Yarbo and hope this only helps to improve the experience.
@Yarbo-Forum
Wow. That really sucks. Sorry to see your Yarbo went off on an unsanctioned adventure.
We have been in a drought over here as of late. So I haven’t had my Yarbo mow anything since the latest firmware. But my normal procedure is to do a test run or two after a firmware update with me either watching in person or via the cameras, to spot any changes in robot behavior. I do that with all my bots. Not just Yarbo.
This has been my experience with this new update as well, I’m not sure if it’s strictly related to the single antenna operation mode or what but we really need a fix or option to roll back. I’m afraid to run one of my areas right now because if yarbo goes out of bounds like he’s done on the other jobs he will likely be severely damaged. I’ve never had it ignoring no go zones and boundaries until this latest update
We’re really sorry to hear about this incident, and we’re glad that no serious damage occurred. We truly appreciate you sharing this experience with the community and reminding others to pay extra attention to edge areas and potential hazards.
At this point, we’re not sure whether this behavior is related to the latest update or caused by another factor. Could you please submit a support ticket and include the estimated timestamp when this happened, along with any additional details you may have?
Our team will review the logs and further investigate the root cause to better understand what happened.
Thank you again for taking the time to provide such detailed feedback. Your input is very valuable and helps us continue improving the Yarbo experience.
Assuming PPVS is enabled, what values are you using?
You may want to bring that in area travel distance down a bit until this issue gets figured out.
