Recently mowing in the same areas it has been mowing for a year, my yarbo started running into trees. it used to back up, move, try again, etc. until it moved around the tree. Now it just keeps trying to plow through the tree with the track just spinning. eventually the plan stops and I get a track slippage error. I have to move the plan forward 1 percent or manually move the yarbo around the tree. I have tried different settings (Gentle contact, different obstacle avoidances, et.) and nothing works. Like I said, these are trees it has avoided in the past be going around them. Kinda defeats the purpose of a robot if I have to manually move it a dozen times during a work plan
Have you tried unplugging the battery for 5 mins and then reseating the mower module cable connector? Is your cameras in smart vision working?
I’d suggest you create No go zones around the trees.
That will both avoid the possibility of Yarbo ramming into them, but also avoid the wasted time and energy when Yarbo does the obstacle avoidance dance and ends up missing spots.
Really sorry to hear about this. As a temporary workaround, you could try setting the trees as No-Go Zones. This allows Yarbo to avoid them more efficiently.
Check to make sure the bumper sensor is working. Manually drive into something to see if you receive a Collision Occurred alert.
I’m thinking your bumper may not be working too, like @cobradunn mentioned.
I manually ran it into a door and I did get the collision occurred message.
I suspect it’s the angle of the bump on the tree, not triggering the collision. Happened to me on a little tikes tug boat sandbox. The mower head protected the bumper from making contact with the slanted side of the sandbox.
What if you carefully tap the bumper. Does it show the collision then? Wondering if the angle of the “hill” to the tree is preventing the bumper from activating.
Tuned into quite the trencher though. 
Problem is it does it on every tree in multiple work areas. I live on 2.5 acres and have 4 mowing areas, all but 1 has trees. It does it in all of them on every tree. It never used to do this, until maybe 2 weeks ago
Understood. A No-Go Zone sounds like the best solution in this case
If you don’t have a ticket, I’d submit one and include times that the incidents happened. If you can share this thread and or videos and app recordings it would help them identify what the issue might be. In the interim, NGZ’s would get you through mowing uninterrupted like @cobradunn mentioned.
We recommend submitting a support ticket so our team can help investigate the issue.