Hi there, I’ve seen your support ticket in our system, and the behavior you described does appear abnormal and requires further investigation from our team.
I’ll help follow up on this ticket to make sure the team reviews the details and works toward the correct resolution.
Areas disappeared - Your pic show you’re connected via BT. This can happen when at the edge of BT range. I disable BT for the app to prevent this type of issue.
GPS icon flickering - I’m seeing similar with 3.14.0. It actually starts showing PPVS meters moved for several seconds while the icon remains green. It shouldn’t be using PPVS with green GPS. Something isn’t right the icon color update.
if it was actually in the red status with GPS it should stop immediately - If PPVS is enabled it will use that in yellow or red GPS condition.
I am unable to connect with my unit and not home to try restarting. Version setting shows no ( 0 ) firmware installed.
I don’t think there’s much you can do unfortunately
I have not enabled mow around NGZs since the update. Now I’m curious what speed it will use for those. I’ll have to try that tonight.
Well the upside is that cuts just got a LOT faster since most of the wasted time is on perim laps. For now I’m just going to manually adjust the speed to slowest for sensitive border areas then crank it back up after the first lap - so much for fully automated.
Support did respond this morning but i think they were just throwing a dart. I adjusted all by a foot and it didn’t make any difference.
Thank you for granting permission for the remote diagnosis and for providing such detailed information. I completely understand how frustrating it is when the perimeter laps are being performed at the same speed as the area speed, especially when it causes repeated collisions with fences and other boundary objects. I’m here to help, and I’ll continue working with you until this issue is resolved.
In the meantime, I’d like you to try the following:
Open the Yarbo App.
Go to Settings → Yarbo Lab → PPVS.
Locate Boundary Travel Distance and adjust it according to your yard’s layout.
Save the settings and run the work plan again to see if the behavior improves.
That suggestion makes no sense.
It’s funny. They generate those AI responses that sound so detailed and thoughtful, but the response doesn’t even address the actual issue.
PPV also had some downstream impacts from this new release FYI
I like the release of the tow mode. Been waiting a long time for it. 
Report back how it’s working. I’m on the road working so I can’t mess with it.
I’m interested of anyone have already tried this tow mode and what are the results?
Thinking of getting some needed attachments for the robot but is there any point buying them
My favorite part is “in the meantime” which implies it already knows the suggestion is trash 
I suggest setting up a theoretical ‘Tow Mode’ area in your yard and do some experimenting.
I think the biggest drawback is that it can’t really handle no go zones inside the tow mode area.
Aside from that, there are quirks that make sense when you think about it. Like Yarbo can’t dock and recharge after a Tow Mode run.
Also, you need to like Yarbo up next to the start of the Tow Mode area. You can’t just start it if Yarbo is in a different area somewhere. Gotta manually drive it to the starting point first, and have it pointing in the right direction.
I am using Blower and as I see latest firmware is not about blower, but in this case what is the point to Regress Navigation Logic for Blower and make it non functional? Previously Blower was nicely blowing to 1 direction as specified on the map, after firmware update it blows to all locations and if I modify map after update navigation look like for Roomba - all zigzags. This is not about blowing at all. I need my working Blower Navigation Back!!!
Why so difficult to make snapshot of the map at the end of task and add it to he Work Plan History together with stats to have good reference in the future like Roborock RockMow for example?
Wait,
Is there separate setting for perimeter/NGZ perimeter speed? Or does Yarbo just run slower there? And now after latest firmware Yarbo races the perimeters with the speed set for the Area?
Not a separate setting, but it does normally mow the perimeter at a much slower speed.
Mine is mowing still same old snail pace the perimeters as it did before this update…
I seem to be only one with this issue currently. I also confirmed tonight that mine also cuts NGZs perims at the Area speed, also not good. But, Dead Ends are cut at the correct speed. I’m currently cutting an Area perim at Slowest which even slower than the typical perim speed.
Confirmed NGZs are cutting at Area speed, also bad, but Dead Ends cut at correct speed.
