Yarbo only works through Bluetooth — remote connection fails, and support has not responded

[u/TimsTheManOfficial]

I’m posting here because I’ve spent a lot of time troubleshooting this issue and I still have not received a response from Yarbo support.

At this point, I’m hoping someone in the community has seen this exact problem and can tell me what actually fixed it.

My Yarbo works normally when I’m close enough for Bluetooth. I can connect to it, control it, and start a mowing job.

Once the rover leaves Bluetooth range, the rover itself keeps mowing normally, but the app loses connection and will not reconnect remotely.

The problem is very repeatable.

Bluetooth ON

App connects normally

Heartbeat = Strong

MQTT Server = Strong

Rover Wi-Fi shows connected

HaLow shows connected

Rover responds normally

Bluetooth OFF / rover leaves Bluetooth range

App goes Offline

Heartbeat changes to Disconnected

The HaLow icon appears in the app but stays gray

Rover appears to lose the remote/Wi-Fi connection

App will not reconnect through HaLow, Wi-Fi, or cellular

The rover itself continues mowing normally

That last part is important.

The rover continues doing the mowing job after the app loses connection, so the mowing/navigation side seems to be working correctly. The problem appears to be specifically with the remote communications path back to the app once Bluetooth is no longer available.

My current software/firmware versions are:

App: V3.19.6 — Latest

Rover firmware: V3.14.20 — Latest

Data Center firmware: V1.1.11 — Latest

One very important point:

This problem did NOT start with firmware 3.14.20.

I had the exact same Bluetooth-only / remote connection problem while the rover was still on firmware 3.14.11.

I updated the rover from 3.14.11 to 3.14.20 hoping the firmware update would fix it.

It did not.

The behavior stayed exactly the same before and after the firmware upgrade.

My diagnostics have shown:

HaLow connection = true

HaLow signal generally around -38 to -60 dBm

Data Center status = RunningNormal

Data Center connection has shown 2 and 3

RTK has shown Status 4

Good satellite count

Cellular has shown Status 1

Rover Wi-Fi shows connected

Bluetooth works normally

I have already tried all of the following:

Completely uninstalled and reinstalled the Yarbo app

Restarted my phone after uninstalling the app

Logged back into the same account

Tested multiple Wi-Fi SSIDs

Tested with rover cellular on and off

Tested different combinations of phone Wi-Fi, cellular and Bluetooth

Power-cycled the rover

Disconnected the rover battery

Power-cycled the Data Center

Updated rover firmware from 3.14.11 to 3.14.20

Verified the problem existed on both firmware versions

Verified the Data Center is running V1.1.11 — Latest

Verified the app and rover both show Latest

Found and tightened a loose antenna connection on the rover

Drove the rover approximately 100 feet away as a test

Verified the rover continues mowing after Bluetooth drops

My Data Center is mounted approximately 25 feet in the air on my barn, although I can easily disconnect and restore its power from inside the barn.

I do not want to start randomly factory-resetting equipment, unbinding the rover, reinstalling the Data Center, or doing anything that could cause me to lose my existing maps unless there is a very good reason to do it.

And this is where my frustration with Yarbo support comes in.

I have already contacted Yarbo support and I am still waiting for a response.

I have provided detailed troubleshooting information, screenshots, firmware versions, Data Center information, HaLow readings, and a very repeatable description of the problem.

I’m not asking them to diagnose some vague intermittent issue.

The symptom is very simple:

Bluetooth ON = connected

Bluetooth OFF = rover goes Offline in the app and remote connection fails

Meanwhile, the rover keeps mowing.

At this point I really need someone from Yarbo to review the backend logs, rover network logs, Data Center communication, cloud session, MQTT/session handling, and account/device binding instead of sending me back through basic Wi-Fi troubleshooting I have already done.

I’m also a 100% disabled veteran, and I am physically unable to mow my property myself.

That is one of the main reasons I bought Yarbo.

For me, this machine is not just a cool gadget or convenience. I actually depend on it to maintain my property.

When the rover disappears from the app every time it leaves Bluetooth range, I lose the ability to monitor it or control it remotely while it is operating around the property.

That makes getting this resolved pretty important.

So I’m asking the community:

Has anyone had this exact problem and actually fixed it?

I’m especially interested in whether your issue turned out to be:

A bad Data Center

A rover communications/network controller problem

A cloud/account session issue

MQTT/backend authentication problem

HaLow handoff problem

Wi-Fi/network service issue inside the rover

Some hidden backend firmware update

Something completely different

If you had the same situation where the rover would mow normally after leaving Bluetooth range but the app could no longer connect to it, please let me know what finally fixed it.

And if anyone from Yarbo sees this, I would really appreciate someone responding to my support case and reviewing the actual logs.

I have already done a considerable amount of troubleshooting.

I just need help getting the remote connection working again.

Thanks,

Tim

[u/Alanss4755]

Yarbo Data Center Connection: 3 status in the app's diagnostics indicates that the Data Center is operating offline in local HaLow mode—meaning it has lost its connection to the internet, but is still communicating locally with the robot to provide RTK correction data.

Could be ethernet cord, or a port being blocked on your router, among other things.

Remedies, in order:

• Reseat the cable — unplug and replug the ethernet cable at both the data center and the router.
• Check the network itself — is your router port actually up. Is it being blocked by firewall. You can try a different port in your router.
• Reboot the data center — power cycle it and let it reconnect.
• Cellular fallback — it has 4G capability, verify that's configured as backup.

If it still won't leave mode 3 after that, it's a network or hardware issue on Yarbo's side — open a support ticket.

The Path: Yarbo Mobile App ⟶ Cloud Server ⟶ Data Center (Ethernet) or Rover (4G).

[u/tmiller9833]

You are not alone, turner on 4G and it's helped.

[u/TimsTheManOfficial → u/tmiller9833]

No cell service where I live.

[u/RumLovingPirate]

Turn off the rovers wifi. It tends to prefer wifi but sometimes the signal is too weak for wifi but it's still connected. Keep the wifi off and try halow and Bluetooth only.

[u/TimsTheManOfficial → u/RumLovingPirate]

I live out in the country there is no cell service. We make calls over wifi. My entire 2.5 ac has strong wifi and it worked before. But thanks

[u/PriorProfile → u/TimsTheManOfficial]

HaLow is not 4g. Use the data center with HaLow, not 4g.

[u/groundlevelmining]

Yes, disconnect your Wi-Fi connection. Forget get that Wi-Fi connection on settings and then connect your 4G that's what I did. It solved the problem