This has been addressed elsewhere, but I’m raising it as its own topic because this is ludicrous. Who on your software engineering team decided, “Hey, let’s change the algorithm so it’ll ignore no-go zones?” This is the third landscape light that has been shredded by the mower while plowing through a no-go zone. I’ve even increased the buffer to 12 inches, and it has no impact. Did I miss the bulldozer toggle?
Your software updates are the problem. Why, why, why? Did everyone get together and decide, “This is working too well, let’s screw it up”? Since the update, we’ve had problems again! That’s now $185 in landscape lights gone in 5 days, not to mention another swath of hostas shredded! Never have I had this issue. NEVER! Now every time it goes out to mow, it finds a new way to get into an area that it’s not supposed to. Has nothing to do with GPS. GPS is great. It’s just skip NGZ and plow right through, well documented by other users on this forum even after the hot fix for the hot fix.
@Yarbo-Forum - FIX THIS! Your hot fix for the hot fix sucks! Give us a rollback feature!! Give us the ability to never upgrade! If our systems are working, we don’t want more of your crap software engineered feature sets that break our products.
By the way, it realizes it’s in a no-go zone. I stopped it to prevent it from ruining itself or tearing out more landscaping lights, then tried to send it back to the charging station, and I got this error.
No, brand new behavior and it does not seem to be for all NGZ’s The only odd thing that does seem to appear, it shows the red blur in the NGZ like it detected an object on the one it does not honor the NGZ - does not do it on any of the others. I do not recall that being present in the past when it went by a NGZ, adding the object indicated red smudge. Maybe a red herring - not sure.
And by the way - I edited the work area for this part of my yard (for different reasons). After the edits were complete, the NGZ is now being honored again. So maybe a ‘fix’ for the issue is to edit the map area.
I called Yarbo, the WP032 error they said is unrelated to bulldozer mode for the NGZ. This of course is my fault; my map has a NGZ blocking a path they said - it of course does not and is the same map I have had for almost a year with no issues just a day before this great update. Well then, I must have an object blocking the path. Nope, strike two Yarbo. Had to send images to prove it!
So, let’s see, I have not changed anything, but Yarbo has been doing updates…hmmmm… yep, it’s on my end. Resolution, a specialist will diagnose the issue and get back to me in 6 hours which is code for “you will be calling us back so you can start this all over again because I don’t have an answer”.
@Yarbo-ForumMANAGEMENT - DO YOU NOT SEE HOW MESSED UP YOUR ENGINEERING DEPARTMENT IS! HOW LONG AND STILL THIS???!!!
I have had 4 issues in the past 4 days, I made tickets for or called in 3 of them, so far none are resolved or even explained with any logic.
The 4th one that I did not make a ticket for is the pro mower going from one grass area, crossing a crushed granite driveway to another grass area sees a vehicle when there are not ANY around. I let it try twice at it, and both times it said it saw a vehicle and was scared and going back to charge. I had to stop and manually drive it to the next area.
Marketing should read this and see how good the vision is on this thing.
The WP032 error I fixed myself. I love that when they add new features, they just turn them on by default, which is just beautiful. I think there were one, maybe two issues.
The perimeter buffer has been there for a while (I think), but I’ve never understood the point of it. Why would you need a buffer on your perimeter? Why wouldn’t you have mapped it with the “buffer” in the first place. I’m sure some snowflake had a use case and they added it. Set this to 0.
I had no-go zones right next to the boundary - so I assume #1 was the issue. I also see the new feature of Boundary, NGZ Edges - I turned this off. I assume that’s related to the trimmer? Maybe the culprit for the bulldozer toggle switch that’s chewing up my landscape lighting. I turned that one off for good measure as well.
Ta-da! It now will mow this area again without an error, the very zone that it had just mowed before the magical hotfix, without issue. Then again, maybe it was the invisible vehicle on the path that they kept claiming was there. Either way, it’s fixed and if someone runs into a similar situation, maybe they’ll find this in a search result and can try it.
Anyone want to take an over/under on how long it takes before support figures out what’s the actual issue? Given what @B-Mod said I think I know which way I’ll place my bet.
Yarbo originally had a forced safety buffer if 4 inches for the mower and 8 for the snow blower. They added it so you could adjust accordingly because most users would overshoot a boundary by 4 or 8 inches to compensate. When they removed the forced buffers…well…
the edges feature turns on mowing the NGZ mapped boundary line. With it off, it won’t do a perimeter lap following the boundary of the NGZ.
Why I got the update that added the NGZ Buffer adjustment. It defaulted to 12". I can see how this might cause some issues depending the map. Was yours at 12"
