Turning off boundary obstacle avoidance as Ben mentioned will help on the perimeter passes. I would also use “Gentle Contact” mode for obstacle avoidance (bumper only). Looks like you have a NGZ already, but make sure you create some for anything you aren’t comfortable with it bumping into to do the avoidance.
BTW, this is very common for all robotic mowers. Most have instructions that state you are to use your mower to mow the lawn down to the set cut height first, and then send the robot out to maintain that cut height. Pretty common for the razors. Those mowers will avoid tall grass too. Yarbo does recommend this too, but unlike some of the other mowers, they let you tweak the settings a lot to get around things like this.
Hi there, as others have mentioned, you can try turning off the Boundary Obstacle Avoidance mode and adjusting the Obstacle Avoidance setting to “Gentle Contact” to see if this helps reduce the behavior.
These settings may allow Yarbo to handle the area differently and improve the mowing performance in situations where grass is being incorrectly detected as an obstacle.
Change Moderate bypass to Gentle touch.
It should help.
Sad the official recommendation from yarbo is to turn off “features” we paid for and yarbo marketing touted as why yarbo is so great.
We’re sorry for the inconvenience this has caused. Our team will continue to work on improving the visual recognition system to make it more reliable and effective in different environments.
Thank you for your feedback and patience as we continue to improve Yarbo.
How can I get “Gentle Contact” back. If I turn of Vision in the area settings, it reverts the setting to “Moderate Bypass”. If I turn on Vision, I’m able to select “Gentle Contact”, but then it still seems to try avoid blades of grass, which makes me think it’s not actually “Gentle Contact”.
(I should note that I just got a core replacement. I didn’t have this issue before and I used Gentle contact everywhere because vision was so unreliable. I have no idea what happened now though to cause the setting to break.)
If I toggle off Vision. I can’t select Gentle Contact. Pressing it does nothing. The only way I can get a checkmark next to Gentle Contact is if I have Vision Enabled.
So with Vision Enabled, I select Gentle Contact and see the checkmark. I click done, then save (top right check in the area settings). When I go back, Gentle Contact is selected (but so is vision). I then disable Vision and Gentle Contact is still checked. Click Done then the area checkmark to save. When I go back, Moderate bypass is selected and vision is disabled.
Here’s a screen recording. https://photos.app.goo.gl/huHjJSMR4jEgGpyu8
What’s not clear is that I can’t select anything in Obstacle Avoidance Mode if Vision is disabled.
That does seem weird. No vision with moderate bypass would effectively be Gentle Contact though. Does it still avoid tall grass with the “No Vision” obstacle avoidance mode?
I found that with gentle contact mine will still see tall weeds and freak out
Pro mower ultrasonics will do that. M1 vision will cause it to slow down. Have to turn those off if it’s causing you issues.
I have them off, it still did it anyway, we chatted about this before. Something is odd with yarbo’s software, lol,
Hi there, this behavior does seem unusual and requires further investigation from our team.
Could you please submit a support ticket regarding this issue? Our team will review it further and help investigate the cause.
Thank you for your cooperation and support.
I opened one yesterday afternoon (223962)
Thank you!
Sorry for the slow response.
Despite the tone of my initial post, I do understand and respect the fact that the system is designed to protect itself.
With that in mind, it seems surprising to me that there’s no way to manually override an area that the bot detects as “unsafe”. I do want it to detect areas that may be harmful to it. I want it to complete work jobs safely. I do not want to turn off safety features to accomplish this. I want the bot to protect itself with more than just the bumper, as that’s a very fallible system if used alone for protection (not a slight, just statement of fact).
Additionally, it surprises me that the bot was unable to path its way around the two no-go zones by just taking the “long” way, of which it has multiple to choose from not visible in the picture. It hung up twice trying to navigate the area between the two zones.
The bot’s inability to path itself prevented it from reaching the charger without manual intervention.
A meaningful system that allows me to manually override zones that the bot detects as unsafe would resolve this. This, to me, is the ideal solution to this problem as it would allow me to ensure that the bot is safe to continue mowing an area that it’s unsure of.
That said, better pathing parameters that would allow the bot to make full use of all routing options available to it in any given zone, or yard as a whole, would also work. This would allow the bot to finish the job in question to the extent possible, at which point I can just manually take care of what the bot doesn’t.
I’m sorry but ‘you can fix this issue by turning off feature X’ is a response that falls short of my expectations from a company that many of us have given thousands of dollars to.
While I’m not exactly enthused with the answer, I will mark this question as answered.
Thank you all for the replies.
