3-days on new firmware 50+ times mowing this area previously. The only reason I knew is the tank kicked the Emergency Stop button. Pardon the language but this shit has been going since the spring release. These are straight up safety and risk of life issues. It’s been reported dozens if not hundreds of times on multiple platforms. WHAT IS BEING DONE TO CORRECT THIS, as I’ve I’ve asked several times before? The typical “Passing this on for a future update” response no longer works! What catastrophe has to happen before this is taken seriously.
Agreed. This needs to be addressed ASAP.
So far I have been lucky with this, but I don’t have many no go zones. My biggest is it dipping out of bounds and getting damage to the mower, and taking out shear pins on the snowblower when it goes outside of a pathway and rams my concrete steps.
Centimeter accuracy they say.
Sorry for the trouble this has caused. We completely understand how concerning it is when Yarbo enters a No-Go Zone, especially when there’s a risk of damage.
This is something we take seriously, and whenever we’re able to retrieve the relevant logs and data, our team reviews each case carefully to identify the root cause. Since this behavior can be triggered by different factors, we need to look at the specific data from your Yarbo to understand what happened in this case.
Could you please submit a support ticket and share the ticket number with us here? That will allow our team to pull the logs, review the incident in detail, and investigate it properly.
I’m sorry … You take this seriously? Really?
If development team took this seriously, everything would improve, not vice versa …
I agree - it’s getting worse with every update. Areas and NGZs which were handled correctly dozens of times, now are being drove in by Yarbo mower.
If you can’t figure out otherwise, make Yarbo to do 2 NGZ ‘perimeter’ laps instead of one therefore giving more clearance from regular zig-zag route.
That would avoid Yarbo’s ass or head crossong the ngz while mowing.
I had 100% similar case with bater tank, where contact with it engaged the Emergency Stop button. That case was also looked at and concluded that “this will be fixed in next release”
Ridiculous!
Ticket #240661.
Just yesterday I had Yarbo ram into a heavy concrete planter and knock it over. The planter is in a NGZ and nothing has ever touched it before.
Only thing I could come up with is Yarbo “forgot” the trimmer was attached and rammed the back of the trimmer into the planter.
Highly plausible. Trimmer and module dimensions in the path planning and maneuvering are still interesting in certain circumstances.
I can assure you the Trimmer is not required for it to make up it’s own trespassing rules.
Really sorry for the inconvenience this caused. I’ve passed your feedback along to our team for further review.
Todays Response:
Thank you for your message — and first of all, I am truly, deeply sorry for what happened. This is a serious situation, and I completely understand your concern. Your safety is our top priority, and this should never have happened.
I really appreciate you providing the exact time — that was extremely helpful. Our team has already pulled and analyzed the logs from that moment (just before 8:05 PM EST on September 7th), and we have identified the issue. I’m glad to confirm that we’ve already applied a backend update to your unit to address this behavior.
As an additional precaution — and to improve overall GPS stability — I will also send you a pair of enhanced RTK antennas at no cost. These should further improve signal reliability and help prevent similar incidents.
Again, I sincerely apologize for the scare and the potential danger this caused. We are taking this very seriously, and I want to thank you for your trust and patience.
If you notice anything unusual in future runs, please let me know immediately. I’m here to help.
Very nice of Yarbo to send me the Pro Antennas, but no explanation of cause or what “…applied a backend update to your unit” actually means. What about everyone else with these issues?
What ever they did also impacted the HA integration. I had to reauthenticate this morning as well.
Yeah I hate when they tell you they made a change. It is even worse when you find out that it still does it makes the error again. Next they will tell you it will be fixed in the next update.
Is this the disclaimer for breaking stuff in the background while trying to fix stuff?
This is not the proper way to solve these issues.
Individualized opaque ‘fixes’ should never be applied to people’s Yarbos behind the scenes.
Defects should be corrected uniformly across the entire Yarbo fleet via formal patch distribution methodology, and include descriptive Release Notes outlining the changes.
One-off fixes behind the scenes only serve to fragment the Yarbo fleet’s firmware and configurations which increase the difficulty of providing ongoing support down the road.
/Rant
While I don’t disagree with you. It does however allow the current issue to be resolved immediately for the individual having the negative experience.
There is at least one other robot mower company that does something like this. Albeit a little different and more refined. Caveat that I don’t own one, but from what I’ve seen this company custom builds fixes and publishes them to the user as a firmware update that the user can chose to apply when they open the app.
It is incorporated later into the broader firmware updates. I would also imagine that it could be toggled on for any other users experiencing the issue in the interim. The other thing they do differently is when you open a ticket in the app it simultaneously submits the logs to the ticket. Logs aren’t lost and they are captured immediately close to incident and available for the teams to review and not have to go back and forth with the user to pull them or try and reproduce the issue (unless that is necessary).
I wish Yarbo would adopt this model along with changing the entire firmware update structure. Closed Beta → Public Beta (any user can opt in) → Production (available optionally to all users to apply when comfortable or necessary). No forced updates. Updates can be installed automatically on a schedule if desired. And you can check for updates and install them directly in the app without needing intervention from support. Rollback to previous version(s) by the end user would also be ideal.
I like the approaches you describe, especially the Public Beta.
I’m not upset they deployed a fix on my unit, but without any context of what happened or what they changed, how do I know what to watch for.
Exactly, they treat us like we are kids, don’t tell them what we did, just tell them it is fixed.
Today’s response - Answered part 1 of my question but not part 2. The solution always seems to be leave MORE uncut grass.
As someone else mentioned, adding a second NGZ perimeter lap would be a great solution in most cases.
Thank you for your message — that’s a fair question, and you deserve a clear explanation.
The issue occurred because the unit was making a turn near the boundary of a No‑Go Zone. The boundary itself is irregular, complex terrain, . the turning precision wasn’t sufficient, and the rear of the unit swung into the No‑Go Zone, making contact with your propane tank. This is a known limitation we’re aware of, and we’re actively working on improving turning accuracy in future updates.
Currently, the most effective short-term method to prevent such incidents from recurring is to increase the buffer distance of the exclusion zone around the propane tanks. Expanding the zone gives the unit a wider margin, which significantly reduces the risk of contact during tight turns or complex maneuvers.
I’m sorry this happened — and I appreciate you asking for a clear answer. Let me know if you’d like help adjusting the NGZ buffer.
Agreed. It’s never an “individual issue” except for when your item physically breaks. Because we all have the programming. You just may not have the parameters.
I’ve noticed that mine backs right into my firepit bricks in my yard when turning around. It’s shifted them and knocked a few over (it’s just a ring of retaining wall bricks, nothing is mortared in), and I’ve watched it back up partially over the no-go zone perimeter (the back end of the rover goes up in the air). The firepit is a no-go zone, and when mowing around it, it leaves the expected buffer. I would also vote for being able to add additional NGZ laps, like you can for the perimeter.
I’ve seen this too, also when it’s turning or maneuvering from the front. It’s like it thinks it’s allowed to exceed the NGZ boundary more than it should be allowed to. It’s always frustrated me that you can watch it back up over boundary lines (perimeter and NGZ).
The only time it should cross this mapped boundary line is when it’s riding it at the center of the core to cut that boundary. The boundary line is the center between the two antennas when you’re mapping. Outside of that, it should never cross it in my mind.
They changed or broke something in the firmware a few updates ago that needs to be put back or adopt the strategy I just described. Extra laps wouldn’t be necessary. Not that I’m opposed to that as an option. But I think the root cause of crossing those boundary lines needs to be addressed first.