I just updated the Yarbo App software and then started the mower remotley. I noticed when I started the mower the battery said 0 percent? I really didn’t think anything about it and let it start mowing. It worked fine for about an hour and then shut off completely. I got home and its completley dead? If i hold in the button on the back of the yarbo…the lights come on, but as soon as I release it…lights go off? I plugged it in using an extension cord and hopefully it charges enough I can get it back to the charging pad. Has anyone had this happen? Any suggestions. I sent in a ticket to Yarbo…he is the text for the ticket.
• Yarbo Core Serial Number: 25070102V3CAF564
• App Version: V3.19.1 (updated today)
• Firmware Version: [Check device after charging and report here]
• Battery: 36V/38.4Ah
Incident Summary:
I remotely started a mowing session via the app while at work. The app displayed zero percent battery, yet the mower initiated and ran for approximately 90 minutes before stopping mid-yard and becoming unresponsive. This has never occurred in prior operation.
Specific Issues:
Battery gauge displayed 0% in the app before remote start command.
Yarbo commenced a full mowing session despite the zero percent reading—normally it refuses to start below 20–30%.
After ~90 minutes of mowing, the Core became completely unresponsive (power loss).
Currently, the unit will only respond to button-hold on the rear power button; releasing the button causes immediate shutdown.
The mower is stranded mid-yard and had to be charged via external rear charging port with an extension cord.
Suspected Root Cause:
Either the battery lockout logic in V3.19.1 failed to prevent start-up at true zero percent, or the battery gauge in the new app version is misreporting actual charge state, allowing a dangerous remote start that should have been blocked.
Request:
Please advise whether V3.19.1 contains a known battery management regression, and whether a firmware rollback or hotfix is recommended before resuming normal operation.
I would charge to full 100%, then disconnect the battery for 4 hours, reconnect, hold power button for 60 seconds, release and then push it one time normally.
Hi there, thank you for providing such detailed information.
This behavior does appear abnormal. At the moment, we have not received similar reports, so we cannot confirm whether it is related to the recent App update or another factor.
Please continue following the troubleshooting steps provided by our support team in the ticket. We will use the diagnostic information collected there to investigate the root cause and determine the next steps.
We understand that having the mower stop unexpectedly in the middle of a task is frustrating, and we appreciate your patience and cooperation while our team looks into this.
Consider this another report, but the app version doesn’t matter. FW 3.13.15.
Recharge trigger was set at 15%. Core #7 was working a task, triggered the 20% in-app reminder, and later died at around 33.2V. Low Battery Auto Shutoff was enabled.
Battery was physically removed and charged with the external charger for an hour.
Reinstalled. Pressing power button starts boot of core #7, but upon releasing the power button, it shuts off immediately.
Threw the battery back onto the external charger for a few hours. Reinstalled back into core #7, with same result.
Threw the battery into core #6, pressed power button and it booted normally. App says Core #6 sees battery at 60%. Used Core #6 to drag the carcass of Core #7 back to the dock, then docked Core #6 to charge battery to 100%. (Core #6 had recently undergone the battery calibration process a week prior to Core #7’s arrival).
Moved “100%” battery to Core #7, but boot process still only happens as long as the power button is held down, otherwise it shuts off immediately.
Held the button down, booted it, docked it, and did the calibration process on Core #7.
Might or might not be related to the Low Battery Auto Shutoff feature.
Instructions might need to be updated to hold the power button during the boot process if LBAS was triggered, if that is the intended behavior.
Thanks for sharing the detailed information about this issue. The troubleshooting steps and the behavior you observed are very helpful for our team to understand the situation.
Do you already have an open support ticket for this issue? If not, we would appreciate it if you could submit a ticket and let me know the ticket number. I’ll help escalate it to our team for further investigation.
Updated my core to 3.14.0 this morning and now I’m getting a “Power Board Issue” message that wasn’t showing before the update. Going to restart it later (pull battery etc.).
Did you restore your map recently? It will reset all settings, work plans, and schedules to default. Reinstall docking station will also wipe the latter 2.
Unfortunately, I would recommend unplugging and removing the trimmer so you can mow and reinstall it when the core is idle so support can try and diagnose it.
For what it’s worth, I will pile on after the updates. I had to do exactly what Bryan and some of the others have suggested: hold the power button for 60 seconds, and then it came back online.
It also has a new feature that wasn’t published in the release notes. When it went back to recharge itself, it was parked diagonally, and it actually said it was charging, but it was sitting on the base station diagonally. Fully charged to 100%. Now that’s new, another feature brought to you by Yarbo.
You’d think I would know the answer to this, Bryan, but I don’t. Is there somewhere inside the diagnostics that shows us antenna strength left and right?
At this point, mine is too busy finding phantom pieces in the yard to even consider moving, so I’m not sure it much matters, to be honest with you. If it can’t move because of GPS, it can’t move because it says that it can’t navigate around an obstacle in the middle of the yard that doesn’t exist. I’m pretty sure the core is absolutely done, but my response from support today was that I have to sit up until 3:00 a.m. so that I can talk to China to beg my case for why my core should be replaced. The hits just keep on coming.
I really wish there was. You have to infer it from the diagnostics and because it’s a fused or shared reading it can be a little misleading sometimes. If you’d care to share your diagnostics, I’ll see if I can decipher it.
As we mentioned in your support ticket, the M25 connection may have poor contact, which could be causing the issue you’re experiencing. To resolve this, we are arranging to send you a replacement M25 spring directly.
Please keep us updated once you have replaced the M25 spring so we can continue to monitor the situation and provide further assistance if needed.
