I always cut on slowest speed and my perimeter is even slower.
Not what I’m seeing. It’s crawling on perim. Who knows what’s going on with mine. This is a software issue for sure.
I had something similar happen to me today. It traveled outside our boundary as well.
Not sure You’re the only one, as i saw this post on facebook. Obstacle covered perimeter would indicate on Yarbo racing around the perimeter.
So basically another separate speed setting fot perimeters/NGZ perimeters would be nice.
But I have a question - if now it will turn out that all devices are affected, then who is even testing the updates before they are released to public? Such issue should have been observed by testers.
Yarbo could send me another unit with settings to receive beta firmwares and i could put it in separate complex area (safe enough where yarbo can’t drown himself) to test it.
That looks to me like perimeter cut is set to last and taller grass on the perimeter with vision and or ultrasonic obstacle avoidance could trigger what is shown there. Cutting perimeter first with boundary obstacle avoidance disabled in theory would have fixed this for that situation.
Hi there,
Regarding the area disappearing issue, we have not received similar feedback before, but we will investigate it further. I have already asked the responsible FSE to review your case and help identify what may have caused this behavior.
As for the GPS icon flickering issue, could you please confirm whether you have enabled PPVS? If PPVS is enabled, this may be related to the behavior you are seeing. However, our team will continue investigating your case to confirm the root cause.
I will keep following up on your ticket and make sure both issues are properly investigated.
Thank you for your patience and for sharing these details with us.
Hi there,
I’m sorry that you need to solve the connection issue first. Please try restarting the unit when you get home and see if the issue can be resolved.
Thank you for your patience.
Yes. PPVS was and is enabled
I’m sorry to hear that you’re experiencing this issue. Could you please submit a support ticket so that our support team can further investigate and identify where we can make improvements?
We apologize for the inconvenience caused and appreciate your cooperation and support.
Thank you!
As we mentioned in the support ticket, could you please try adjusting the PPVS settings and monitor whether the issue still occurs?
Please let us know the results after testing. If the issue continues, feel free to share more details so we can further investigate.
Thank you for your cooperation.
I’ll know better next time 
And today’s less than helpful response:
Dear Eric,
Thank you for your update and for providing the additional details. We understand how frustrating it is to manually adjust the speed before and after each plan, and we appreciate your patience while working with us to improve this behavior.
Please try to reducing the Moving Speed to see if it helps prevent collisions during the perimeter laps.
You can adjust the Moving Speed by following these steps:
Open the Yarbo App.
Select your Yarbo device.
Select your Work Plan.
Go to Area Settings.
Locate Moving Speed.
Reduce the speed value and save the changes.
Additionally, please try increasing the Parameter Buffer setting, as this may help Yarbo maintain a safer distance from boundary objects.
To access the Parameter Buffer setting:
Open the Yarbo App.
Select your Yarbo device.
Select your Work Plan.
Go to Area Settings.
Locate Parameter Buffer and increase the value.
Save the settings and test the work plan again.
We hope these adjustments help resolve the issue. If the problem continues, please share screenshots of both the Moving Speed and Parameter Buffer settings in this same ticket so we can review them further.
Thank you for your cooperation and patience.
Best regards,
Steve
Yarbo Support Team
Doesn’t seem like they understand the problem you’re seeing.
Ridiculous. My response:
Of course reducing the speed manually fixes the perimeter issue. This is exactly what I said I’m doing!
Of course increasing the Buffer will reduce the collisions. This is not fix.
I’m an experienced user. Please stop regurgitating canned responses. This is a software issue that needs attention. Get someone looking at the logs and figure out what causing this. It’s new to 3.14.0
They test the yarbo on fields like those in live games, so they certainly won’t find the problems there… easy, expansive fields without obstacles, narrow points, fenced boundaries, etc. To demonstrate the validity of a product, it must be tested under harsh conditions in difficult scenarios, provided it can truly do so.
I am really sorry you are experiencing these stupid responses but if you just play the game for a few more days, you may win big prizes!
And don’t forget to send them some video! 
I lucked out - only requested screenshots - of a setting I’ve already explained I have to manually adjust in the middle of every plan.
Include a video of you taking the screenshots.
Just 'cuz.
I had to take videos of my tablet showing the screen in action. I guess they didn’t believe the video I had previously sent that showed the yarbo in live action doing bad stuff.