Battery at 0% how do you charge it

When we retrieve logs, it does not affect or suspend any active work plans. Your task should continue running as expected. Let us know if you notice anything unusual!

3 Likes

Did you ever can an answer to your suspended without cause issue? This has happened to me two days in a row now. Mowing fine then for no reason I get a suspended message and the rover stops mowimg. GPS and HaLow are fine. I press resume and it immediately resumes the job.

1 Like

@JNS - Ohhhhh how many times did I see that back in snowblower days…Not so much with the mower, once or twice ever, but regularly at one particular spot with the snowblower. Go out and check, all is fine, click Resume, and off it goes. Re-map? Nope, didn’t help. Wild.

No, not normal. I meant to click “Record” (near the bottom of the Diagnostics screen) and catch it for Support, but I ran out of snow. So if this is something you can reproduce, turn on Record and let it happen, get video if you can, note the date-time. If not, when it happens again, open a Support ticket and give them whatever information you can, including timestamps.

Also take a look at the Diagnostics when that happens. Maybe GPS burps or something else goes weird – I don’t know.

2 Likes

The first reply was they saw a “software restart command”. As in “restart Yarbo system” from the menu.

I informed them that was how I ended the Suspend and that they should look for a suspend before that.

I had a second recurrence shown above in the screenshots. And have not heard anything since.

3 Likes

Suspended without cause happened again today at about 16:02.
Screenshot 2025-07-27 at 4.49.19 PM

Yarbo sat in that status for 10 minutes. Then the work plan was suspended. Coincidentally once the work plan suspended the Battery, HaLow and GPS all returned to normal.

Or maybe it’s the other way around. Once GPS recovered the work plan suspended.

either way… it suspended.

Took me 50 minutes to notice Yarbo was stuck. I AM REALLY SLACKING on my babysitting Yarbo. :wink:

2 Likes

Did you get a notification?

Maybe I am doing something wrong but the only notification I get on my phone is when a job is complete (I am fortunate, my jobs complete most of the time). But when there is an issue, I don’t notice unless I open the app. No notification. Is that on purpose or an app bug? When there is an error or Yarbo stops, shouldn’t we be seeing a notification?

Did you have your screen caps running when it bappened?

You’re not doing anything wrong, that’s the only notification I have every gotten. None of the others work - if they’re intended to.

1 Like

@Yarbo-Forum this is another bug in your app that can be fixed easily and could help your users troubleshoot the robot and get less irritated by losing mowing time… Super easy to fix. For ios in siwft:

import UserNotifications

func scheduleErrorNotification() {
// 1. Define the content of the alert
let content = UNMutableNotificationContent()
content.title = “I’m stuck!”
content.body = “Yarbo is stuck! It needs your help!”
content.sound = UNNotificationSound.default

let trigger = UNTimeIntervalNotificationTrigger(timeInterval: 1, repeats: false)

let request = UNNotificationRequest(identifier: UUID().uuidString, content: content, trigger: trigger)

UNUserNotificationCenter.current().add(request) { error in
    if let error = error {
        print("Yarbo alert: \(error.localizedDescription)")
    }
}

}

Then each time you generate an error in the app, you add:

do {
// Placeholder for however errors are triggered in your code
try performSomeRiskyOperation()
} catch {
// Add a catch
print(“Yarbo error!”)

// Call your function to show the notification
scheduleErrorNotification()

}

I also opened a ticket regarding incorect charset encoding support. Can also be easily fixed at the client level.

1 Like

No notification that I saw.

Affirmative ghost rider the hard drive is full…

1 Like

Would be nice to do a pull request wouldn’t it?

1 Like

yes. They should push the code for their app on github. We could be a few working on fixing some quirks…

1 Like

Working fine:

8 screenshots one minute apart that look just like this:

And then suspended…

1 Like

Hopefully you have a ticket open on this issue

1 Like

Ticket 99079. Been open for 28 days.

2 Likes

I’m only guessing but I bet there is a large portion of code written in a language I don’t understand.

2 Likes

And fresh out of school.

This is basic iOS stuff… swift…

Lots of stuff is frontend development only. I am not talking about vision or anything. Just basic iOS programming…

Computer vision is another beast…

1 Like

Thank you for taking the time to share your insights and suggestions. I’ve also reviewed your support ticket regarding bug with charset encoding recognition. Both of your feedback have been passed along to our product team for further evaluation. We truly appreciate your input!

1 Like