Lawn mower is running for the first time with firmware 3.12.0 this year. I’m seeing a new problem since last season. After completing the main portion of the plan but before starting the perimeter laps it stops and the app reports “Suspended by User” I not doing anything in the App when this occurs. Anyone seeing similar behavior?
I had two unexpected “suspended by user” with the S1 this season, as well. I do not know if they were related to the perimeter.
1 Like
Hi there, we’re unable to confirm the root cause of the issue at this time.
Could you please submit a support ticket so our support team can investigate further and provide you with a solution? This will help us look into the issue more thoroughly and identify the cause.
Thank you for your understanding.
I don’t think I have enough detail to open a ticket yet. I don’t feel like going in circles with support this early in the season 
I’m going to try a couple things like changing the Mowing Order to Boundary 1st and Area 2nd, and separately changing the Perimeter Direction. That option is new to this firmware and maybe something isn’t being initialized correctly until it’s changed once. We’ll see.
2 Likes
Started cutting a new area tonight that hasn’t seen 3.12.0. Out of the gate it’s starts cutting the perimeter laps clockwise even though Perimeter Direction is set to Follow Original Path. This is unchanged as this option wasn’t available last year. Clearly this doesn’t work.
As it’s going clockwise, it’s running into everything, buildings, fences, etc. This is a result of the back end of the tracks ignoring the boundary.
It gets to area under a tree stops and reports unable to navigate around obstacles. There are no obstacles and it won’t continue no matter what I try. Finally it reports cannot continue from No Go Zone. GPS is green the entire time. Lost it’s way for no reason.
Finally I stopped the plan, reset the direction to counterclockwise, turned vision Off and started again. Everything is working.
More untested garbage completely breaks the mower. I would expect nothing less from Yarbo at this point. Repeated regressions are norm.
Curious if that’s the direction that you originally mapped that area? It should follow that way, if that’s how it was originally mapped.
Mapping was counterclockwise (right antenna to border) It started the perimeter opposite of that and ran into everything. This area was set to do the perimeter first from last year.
I never made it through the first lap to see if t continued to the main area. After I reset the direction, it did proceed to the main without stopping with “suspended by user error”. A little more data but, it didn’t make me feel any better about the performance. The vision is still trash.
That’s really odd. While it isn’t perfect, I’ve had really good luck with the vision in the one area I run it.
This is what I curious about in my initial post. Does it have something to do with initialization of the direction option after the update. This is only anecdotal, but still a data point.
The dismal perimeter performance running opposite of mapped is not encouraging. Since this firmware update was done in mower off-season for most of us, I doubt there’s much user feedback with the mower module. Honesty, the internal testing feels like it’s done in a Teams meeting. This is exactly what I was concerned about testing before the season was in full swing.
I’m done sugarcoating things in year 2 of ownership.
Guess I’m the only one! Just my luck.
I reset all my areas and toggled the direction to counterclockwise. I don’t have time to babysit right now.
Thanks for sharing the detailed description — this does sound abnormal and will need further investigation from our support team.
If the setting is set to “Follow Original Path” and the area was originally mapped counterclockwise, Yarbo should follow that exact direction. It shouldn’t reverse or behave differently from the mapped path.
If you continue to see unexpected behavior even after switching the direction to counterclockwise, please feel free to reach out to our support team so we can take a closer look and assist you further.
Appreciate your feedback!
Had another “suspended by user” over the weekend. It wasn’t related to the perimeter laps. It was in the middle of the area this time.
In a different large area, it didn’t complete the area after a recharge. It sat on the dock and charged to 100% until hit Resume. It seems more flakey than ever.
Thanks for sharing this. Based on the information provided, it’s a bit difficult to determine the exact cause. I also wasn’t able to find any related support tickets from you in our system.
To help prevent this from happening again, we recommend submitting a support ticket. Our team can then look into the logs, identify the root cause, and provide a proper solution.