From January 28 2026 Yarbo Weekly News email.
yup
Honest thought here-
We’ve all experienced frustration with Yarbo (and other bleeding edge tech) before. We know what it feels like when things aren’t working the way they should.
The thing is, attacking another forum member who is only trying to help you will do nothing but cause others to NOT want to help. Ideally, we should all be helping each other. Not being rude to one another.
I honestly hope you figure out the NGZ issue. Sounds like you’re making progress.
And yes, it’s super annoying when a firmware update breaks functionality that was previously working just fine. Trust me, I know.
Tom C,
Seems totally reasonable.
Should not get a WP032 error when there are NO NGZs in the work area.
Current software will prevent area 1 or 2 from working if NGZ (3) is active.
This happens even if the unit is already in area 1 or 2. Turn off 3 and the world is right.
NGZ3 was just a large area drop because there are no trees with leaves there.
Area 1 2 and the large area adjacent to the charging station worked fine before the software “upgrade.”
Zero reason area 1 &2 should be affected by NGZ3
Les
The past firmware would use the outer perimeter of a no-go zone to bypass navigation routes between areas. You don’t want that functionality. To fix that bug they made the current NGZs overly strict in all areas Yarbo tried to calculate a route through. Does it suck, kinda, but better than the alternative. Hopefully in a future update they get the real issue narrowed down and fixed correctly, or at least better than what it is and was.
Never had an issue with the original issue you mentioned.
So where does that apply to area 1 or 2 when the yarbo is IN that area?
Not routing thru a NGZ. Nowhere near a NGZ.
Or even while at the charging station on the south side of that building with zero NGZs between the charger and the work areas?
Makes zero sense.
Les
NGZ3 screwing it up makes perfect sense, since the core calculates EVERY POSSIBLE PATH in order to pick what it thinks is most appropriate.
If any iteration of that foreach() crashes out with that dead-end error, the entire calculation bails out and WP032 results.
Previous firmware did not crash out that way, within each trial. It waited until all possible paths were tested, THEN you’d get a WP032 if none could work.
Yarbo probably needs to go back to not failing the solution within each iteration, but simply discard a path if it encounters that problem. THEN throw a WP032 if no solutions were found, AFTER all have been tried.
Considering I only have ONE connector path to area 1 and 2, how would the NGZ3 come into play? There is NO pathway from the charger to area 1 and 2 except the depicted track. If there was a way for it to get to area 2 counterclockwise around the building, that would make sense, but there’s not.
Now considering I’ve not run the mower in several months, does that mean the new firmware is “smart enough” to not take the same path every time it travels to a zone, no matter where it’s coming from?
I still have wear tracks in the yard from last season even with multiple paths between areas, it always takes the same path.
Even with a season of fairly sucsessful mows, I can’t help but think yarbo is alphaware.
Les
I won’t bother reading the rest of your reply. For real. I do not need to.
NGZ3 comes into play because you CREATED THIS.
THAT is a path, which you insisted does not exist, which IS included in the TSP iterations of the new firmware that walks through all the various module tags.
Good luck! Cheers, and leave us out of it.
Hi there,
After the update, if there are any no-go zones created in a way similar to what Tom C showed in his screenshots, the system may trigger a WP032 error, even if the work plan you’re trying to run does not directly include that no-go zone. We understand that this can be confusing.
At the moment, the best way to resolve this issue is to make sure all no-go zones are created according to the updated rules introduced in the latest firmware. In many cases, this can be addressed by slightly adjusting the no-go zone to cover any small leftover gaps so that the zone is considered valid.
Actually I did create that and it worked under the old rules.
Yarbo changed the rules and broke my maps!
So I turned off all my NGZs and audited what works. I get WP005 in two work areas. Says I need to follow the guide. Ok, I can read and understand rules.
Where are the rules documented at? I’ve looked at the wiki. I’ve looked at the owners manual. Maybe I’ve missed “the guide.” Yarbo came with a minimal amount of documentation, and several links to videos that half covered it’s operation. Have yet to see a guide.
Any suggestion as to why area 3 or 5 throw WP005?
Steve… Care to point out where zone 4 and 2 are connected?….It’s not with that path you highlighted…
With regard to the NGZ over paths “rule,” how does one solve this problem.
Two work areas. The only path between areas is in a low area that holds water after a rain.
Previously I could turn on the NGZ and let it work the left area and return to charge, or manually take it down the road to the right area, and it would work till finished and stop where I could bring it back. Do I have to section the low area into another zone?
Thanks,
Les
___________________________
At the moment, the best way to resolve this issue is to make sure all no-go zones are created according to the updated rules introduced in the latest firmware.
___________________________
Please provide a link to complete updated map rules .pdf
Les
And to think I got flagged….
I’m guessing you don’t have a useful answer either of the questions..
Les
I’m just trying to point out that we are all in this together experimenting with new tech. Some people here go way out of their way to try and help others. I am quite new here and appreciate the help I get. I have gotten quite a bit this winter. And when folks show up being rude to those trying to help it simply shows the type of person they are and worse yet makes others less likely to try and help in the future. I am fine with it being taken down. It was posted for an audience of one and I can see you saw it. Was hoping it might give you something to reflect on when considering your next post as apparently apologizing for your attitude is beyond you.
Have a nice day and good luck with your NGZs. If you get it sorted out please post your solutions in the hopes that they may help others in the future.
Thanks
Lane
If only release notes existed…
https://wiki.yarbo.com/release-note-and-new-feature/3120#:~:text=¶-,No-Go%20Zone%20Related%20Rules,-After%20this%20update
No-Go Zone Related Rules
After this update, if an NGZ fully blocks the valid passage within a working area, the layout will be treated as an invalid (illegal) plan geometry.
In previous firmware versions, the rover might attempt to cut across such areas, but this safety loophole has now been closed. As a result, while a preview may still be generated, the plan will not start.
_____________________
Nowhere near enough guidance here.
And the NGZ was not in the working area. It was in an adjacent area.
Les
I agree we’re in this together. With less than stellar support from yarbo in my opinion. Lack of documentation….
My original BS post was strictly out of frustration that a season of tuning has been thrown in the trash arbitrarily. The suggestion, while it turns out is somewhat correct doesn’t make the fact that past functionality is now broke!
There’s been lots of “see there’s the path” that still doesn’t address the issue. The only path to the work area is free from NGZs. The ability to block a path using a NGZ has been broken, with no solution suggested.
You spend the time to write a post rubbing my nose in it, while demonstrating the same tone I did. Reflect on that!
Then you ask me to share what I learn afterwards.
I’m glad to share what I learn. But I’ll also feel free to bitch about a half baked solution as well.
(And yes I work with more tech than you can imagine.)
Les
The best thing to do at this point is to move on. No need for any of us to rehash the conflict.
So in the interests of moving on…. It seems to me your best approach will be to modify how you’ve been using NGZ in the past.
The functionality changes were made in part to prevent Yarbo from driving through undesirable areas when trying to navigate from place to place. So they made a change to resolve an issue that has been widely reported, when then broke functionality that you’ve been relying upon.
Based on what you know now, what complications do you observe with modifying your NGZ?
LOL. Spend some time with South Park. Apparently sarcasm is too high.
All good. Good luck. From what I’ve seen it looks like everyone here is tech based. Should be a wealth of knowledge to draw on. You never know where a correct thought or solution may come from. I say throw out all ideas you have and work your way through. They got XIII home.
If the designers don’t have the answer right now we are on our own to find a work around. Let’s put our heads together and work as a team. You can bet the train drivers are paying attention to what we come up with as it makes their life easier in the long run.
Sincerely
Lane
A work area is any area you mapped for Yarbo to work in. I agree a lot of what’s posted is not specific enough or isn’t worded quite right. But it’s all out there.