“Johnny 5” used to mow around the no go zones right up to the edge, but now all of my no go zones are about 6" out and do not get mowed. I have checked the “mow along no go zones” toggle and verified that is on. I even turned it off and then back on, but still no change. Were there any changes concerning the “mow along no go zones”?
Curious what your Boundary Set Back is. I’ve always wondered if that setting also affects No-go Zones. No-go Zones are independent of Areas, so I’m doubting it.
They’re changed in the most recent firmwares where it doesn’t ride the NGZ boundary line. It only does the second perimeter line cut instead. It’s a temporary safety measure to keep it away and from potentially entering a no go zone. Hopefully this will be put back in the future.
3 Likes
Yawp, forgot they did that – gave No-go Zones some extra buffer I think 2 FW drops ago.
1 Like
On the good side, we can temporarily use DeadEnds to manage at least some of those boundaries even into a No-Go, at least where traversing backwards won’t cause an issue.
2 Likes
Setback is set to 0.
2 Likes
This sucks… I had entire zones no longer working due to a no go zone being a meter away from the boundary…
Guess we all need to stop updates from being allowed in so they don’t trash a working yarbo
1 Like
You would also need to block app updates too. They are pretty closely coupled. It will even update over cellular so connectivity would only work Bluetooth unless you completely firewalled it in your local LAN.
1 Like