Can't connect to Yarbo

Today wanted to connect to yarbo and got the error. Figured out that this might be strange issue with some celluar data or something.
Got back home. From wifi the same.

Went to yarbo, bluetooth icon turned green, but still can’t connect. (yarbo back lights were red, top lights glowing - all as usual)

Power-cycled the data center .. no improvements.

What is causing the issue?

From wifi tried now - again nothing

Hard power DC and core off and bull battery cable for 5 mins. Hold power button for 60 seconds when turning it on. Power up the data center first.

This happens to me about twice a month. I powercycle the DC, while the DC is starting up I reboot the bot. I also exit and restart the app while the bot is booting up. That seems to fix it for me.

Something doesn’t seem right, I haven’t had to do that…

Are these good metrics for connectivity?

My gos says 326 feet on main screen. Not sure what that means.

Scroll down farther and post more of the data

Looks like you have an issue with your data center. Unplug it for 5 mins and the battery cable on the core for the same. Fire up the DC then the core

Hi there, could you please try the suggestions shared by our community members first and let us know the results? If the issue persists, please submit a support ticket so our team can investigate further.

Hi there, as Bryan mentioned, it looks like there may be an issue with your Data Center. Could you please try his suggestion first and let us know if it helps? If the issue persists, please submit a support ticket so our team can investigate further.

Yes. Turned off DC for some 5 minutes, powered it on and meanwhile rebooted the yarbo by holding the power button for some 20 seconds. Issue solved.

Works in my end too now. That said I created a pathway and now my yarbo immediately turns off the docking station and starts running. Doesn’t follow pathway and doesn’t even undock properly. It just shot tons of my rocks everywhere as it hasn’t snowed yet. Jesus. Now what.

Get a ticket opened with the time that happened so they can pull the logs and see why.

Hi there, this is definitely not normal behavior. As Bryan mentioned, please submit a support ticket and include the exact time the issue occurred so our team can retrieve the logs and investigate further. Sorry for the inconvenience caused.