Work Plan Cancels Itself When Recharging

I have been having a problem with work plans being cancelled when Mow Howard returns to the dock to recharge in the middle of large cutting area. This problem was noticed a few weeks ago…before the latest update. Not to mention that settings for changes to work preferences won’t be retained. I have had a ticket in for a couple of weeks. Last week, Yarbo told me that knew what the problem was and the it would be fixed with the latest update. It was not. These two problems still exist, and they are incredibly frustrating, because I am cutting 6 acres a week with Mow Howard, so he obviously needs to recharge mid-workplan. I’m back to babysitting the thing, like I had to do last summer with the battery constantly overheating. But now we can add the latest issue. The battery won’t even charge to 100%. It stops at about 85% to 87%. I have tried the “unplug it for 4 hours trick” to no avail. So now I can’t even get as long of a cut before it heads back to recharge…and then he forgets that it was in the middle of cutting 3/4 of an acre. If I’m not paying attention, I have no idea how far it got before it went back to the dock. This latest problem popped up after this recent update. So instead of fixing my two problems (as promised), it added a third problem to the mix. I am told that they are working on it and to give them a couple days to get back to me…after two plus weeks of already waiting for a fix. Meanwhile, they keep asking me if they can close the ticket! UGH!

Have you tried using the manual wired charger after unplugging for 4 hours? Has support diagnosed your battery at all? If you drop your ticket number here, @Yarbo-Forum can look into it for you.

The battery was replaced in November with a new one…and I don’t have the snow blower, so it was only turned on once a month to keep it “alive”. Before the last update, it was working perfectly fine. But I have not tried the manual charger option and can give it a shot. But it is really forgetting/cancelling the work plan mid-charge that is the most annoying. The ticket is 181851. Thank you for your assistance.

Out of curiosity, are you using the Home Assistant integration?

I am not using that.

Any obstructions or collisions on the way to the charger? Can you tell when it cancels?

Do you get an plan cancelled notice or just the absence of the resume button?

I’ve noticed when mine is headed to the charger and has a collision the resume button is no longer available. I am able to resume the plan through the Home Assistant Integration.

May or may not be what you are seeing.

The issue you’re experiencing has been addressed in our latest firmware update. At the moment, the update is still being rolled out in batches, so it may take a little time before it reaches your device.

We kindly ask for your patience while the rollout is completed, and we truly appreciate your understanding. Thank you.

Don’t recall seeing this in the release notes???

No problems heading back to recharge. I noticed that at first the option is there to resume the work plan, but it disappears after sitting on the charger a few minutes. Hopefully the latest hotfix will actually correct the problem.

I saw this once or twice but could never nail down the cause. It seemed like it was after one plan completed and I manually started another plan from within the completed area. It had partial battery and I knew it wouldn’t complete the second plan without a recharge. It recharged to 100% and sat on the charger.

Today I was mowing 2 areas and had a chance to test out various scenarious.
At around 87% of plan Yarbo drove to some soil bump, threw an error or warning about blade speed and just instead of retrying anything just headed to the charger. As I accidentially noticed that in the app, I clikcked “End recharge” while the robot was not yet gone to the charger, checked the blades and then clicked Resume plan in app … The app said “Screw you, unable to continue the plan” or plan does not exist and all gone. I restarted it from those % and all good.
Later in the work plan history the first one is displayed as manually stopped.

Later, when mowing another area, Yarbo’s battery level reached 20% and it returned to the dock to charge. Funny thing that some random error about blocked camera was still present even if the camera is not blocked and is correctly showing the image.

And then, again, Yarbo drove into more dense grass or something, throw warning about blade speeds and … instead of trying to get going, returned to the dock to charge.

But this time I allowed Yarbo to go to the dock and almost right away resumed the plan. And Yarbo successfully returned to the place it left and successfully finished the plan.

So there are some questions - why such broken logic?

When blade speed issues - just go backwards a bit, try again to attack the grass and then, if unsuccessful for some times, throw a alert in the app and let user to decide what to do - either
a) try again attacking the grass (user can walk to the yarbo, clear the blades and click continue in the app)
b) send the yarbo to the charger and continue the plan manually later on (for example, in case user is not at home, so not to leave the yarbo in the middle of the field)

or .. in case yarbo automatically gives up and rushes to the charger, leve opportunity to cancel it’s idea to go to dock and force it back to work.

The auto return to dock should only trigger if the blades are blocked and there would be a clear warning of that. It would try several times to spin the blades if they were blocked before returning to the dock. So this might be an incompatibility of app and firmware or there is something deeper going on there. I would submit a ticket with the times that this happened and include this thread in the forum and any other video or photo evidence you have.

Ok, when checking the app I see both issues when Yarbo decided to rush to the charging pad


At 13:26 and then I cancelled it’s return to the charger and tried to continue the plan which failed with next error at 13:31 with “plan cannot be found” … wtf dude … you were literally running the plan and had the resume button and now you can’t find the plan :laughing:

And then the last error at 18:46 aligns with my last screenshot of the previous post where it also decided to rush back to the charger because of the blades.

But the fact that for the last error I did not even leave my chair and just sent the Yarbo back from the charger to finish the bloody plan, indicates that the issue was nothing severa as Yarbo was easily able just to continue from the exact place where it got that blade error.
So theoretically it shoud have been able to handle the situation without rushing to the dock.

I have experienced several times in the last week where all my work plans are gone when I want to start a new one, but I have not experienced them being canceled.

Did you restore a map? That will wipe all settings, work plans, and schedules.

That is a cutting height motor issue, do you have some blockages around the motors? What cutting height are you trying to mow at? 4 inches? If it can’t fully retract, that could be why it is erroring out. It may have knocked itself loose in the back and forth and up and down of the cutting motors. If everything is clear and clean and you can manually move it all up and down and spin the motors, etc, then I would get a ticket in so they can see what the logs say. Might be a glitch.

no. they come back again. or if you make a new plan the old ones come back. a bit strange.

Hmm, that new firmware will hopefully resolve that weirdness. I have noticed that sometimes the full settings haven’t loaded and if I go into settings my volume will be 100% but if I tap back to the main screen and go back into settings it will be correct at the 40% and muted that I have it configured for. App lag is real. And the forced bluetooth as a primary connection method doesn’t help.

You mean manually with the app or controller. Grab the motors with your hands and you won’t be able to move them up and down.

Correct, with the controller. Thanks for clarifying that.