Mine continues to be a problem. Any changes fail with a network error. Here’s a video of what’s happening:
Can you connect VIA bluetooth and show me some screenshots of your diagnostics? RTK, status, DC, HaLow sections. Might be something else going on.
Hé, this issue is also discribed in another discusion I was in. Exactly the same. I replaced the DC, which was running on FW V1.1.2 ??? while the latest version said V1.0.25.
At this moment it works but in recent plan I stil saw the Yarbo loosing Halow and Network. Also during my DC change I saw that when Bluetooth was de-activated then suddenly Halow came forward in the app. Could the bluetooth be programmed as priority to show in the app in stead of the Halow?
Maybe the Halow should always first when present?
Bluetooth is priority one and will always auto connect when in range. I would love the ability to disable this in app. I do see frequent drops of bluetooth, even in range. Usually tapping the chain icon will reconnect if you’re having offline issues. If Bluetooth is causing you grief, just disable the app permissions for bluetooth.
What’s causing me grief at the moment is the loss of my maps. Something I did deleted them and now the only option on the main screen is “Create A Map”. I didn’t have anything extensive, main 1 acre field and the driveway next to it. Older, saved maps are from January 2026 and too old to use. Just adding to my frustration with Yarbo, app most specifically. Core, mower and trimmer are fine when things work.
Yeah something definitely isn’t right. Maps shouldn’t just disappear. Hopefully you have documented this in your ticket(s)?
Opened a new ticket for it…213707. Not sure where things stand since the response was we can’t help.
Loading a short video…
So that showed bluetooth wasn’t connected and everything seemed to be functioning. Does it still show offline in the main app view?
No, it seems to be working at the moment. I’ve got to remap everything next and see what happens. But, it’s 91 degrees and sunny right now so that will have to wait.
When you get done mapping, go into previous maps and save it. That will store one locally and simultaneously push it to the cloud. That way, if they wipe again, you will have a way to restore your maps.
Going to do that but thought it was saving automatically.
Better safe than sorry.
Hi there, we will follow up on both of your issues through tickets #213599 and #213707. We’re currently reviewing the details and will update you as soon as we have more findings. Thanks for your patience while we work toward a proper conclusion.
Exactly same thing happened to me. This is their software issue as they confirmed. But still not fixed yet. My Ticket Id: #207488
Timeline of My Yarbo Issue (June 2026)
1. June 8 – Initial Mapping Bug
-
After several app/firmware updates, my map shifted approximately 2–3 ft.
-
Existing maps still mowed correctly, but any attempt to edit the map or add new areas frequently resulted in WP005/WPG005 errors.
-
RTK remained healthy (Fixed, ~20+ satellites), suggesting this was not a GPS issue.
2. June 18 – Troubleshooting Made Things Worse (suggested by yarbo engineer)
-
Following Yarbo Support’s instructions (Data Center reboot, Yarbo reboot, Clear Map Drift), remote connectivity became much less reliable.
-
Before this, I could monitor and control Yarbo from inside my house over home Wi-Fi (approximately 300 ft away).
-
After rebooting, the rover often appeared offline unless I was standing nearby.
3. June 18–19 – Bluetooth Became the Only Reliable Connection
-
The app would connect only through Bluetooth.
-
Previous Maps frequently failed to load with “Request failed, please check your network.”
-
Wi-Fi and cellular no longer provided reliable remote access.
4. June 19–24 – Extensive (personal) Testing
-
I spent many hours testing different combinations of:
-
Bluetooth ON/OFF
-
Home Wi-Fi
-
Cellular ON/OFF
-
Different distances from the rover
-
-
I collected numerous diagnostic screenshots and shared them with Yarbo Engineering.
5. Repeatable Bluetooth / Wi-Fi Behavior
A repeatable pattern emerged:
-
Far from Yarbo (Bluetooth disconnected):
-
Home Wi-Fi works normally.
-
Previous Maps appear.
-
Map editing is available.
-
-
Walk close enough for Bluetooth to connect:
-
Previous Maps disappear.
-
Map editing becomes unavailable.
-
Adding new areas still fails.
-
When Bluetooth disconnects again, cloud functionality usually returns.
- Diagnostic Findings - after personnel test without Yarbo help.
Hardware appears healthy:
-
RTK Fixed
-
Strong HaLow signal
-
MQTT Server usually = 1
-
Good Wi-Fi signal
-
Normal satellite count
The issue appears to be related to software or communication, not GPS or Wi-Fi coverage.
Observed PRP values include:
-
Bluetooth OFF:
-
[0,0,0] -
[-12,-12,0]
-
-
Bluetooth ON:
-
[1,0,0] -
[0,4,0]
-
I still do not know what these PRP values represent. (Anyone know the PRP code??)
7. Current Status (June 26–27)
The original map can still mow in many cases, but I still cannot:
-
Add a new mowing area
-
Expand my existing map
-
Reliably edit boundaries
-
Resolve WP005 errors
The problem is therefore much more than simple connectivity—it prevents future expansion of my property.
8. Engineering Request
At this point I believe Engineering should investigate:
-
Bluetooth ↔ Wi-Fi/cloud handoff
-
Why Bluetooth appears to disable cloud map functions
-
The meaning of the PRP values
-
Why WP005 occurs only after map editing
-
Whether this is a software regression introduced in recent firmware/app updates
Hopefully this timeline helps anyone experiencing similar behavior. If your symptoms match mine, please comment below so Yarbo Engineering can determine whether this is an isolated case or a broader software issue.
Based on my numerous tests for solving this same issue;
- PRP [0, 0, 0] doesn’t look good.
- Battery Temp shows number of 31 which is normal; but CPU, Memory, Disk show “zeros” - something is not right.
- my case, all of sudden, wifi connected but limited; still other issues remained. I added detail below.
Hi JBS,
I had similar issues shortly after the last updates wwre issued, i had to stand behind the core to send it out to move, when out it would cut perfectly but i couldnt connect until it would return. Did all the usual but no difference until i checked the software the data centre was using, it was still running on old software with a newer version available but not automatically installed. I installed and powered down everything, waited 15mins ans after restarting it has worked without fail since that. Might be something that would be worth checking out. Hope you get up and running soon.
PRP means Plan, Recharge, Plan. These are numbers which align with internal mapped area numbers. 0,0,0 is expected if it’s not in an active plan. I don’t think there’s any significance here. If the CPU values aren’t populating that means the app isn’t communicating with the core. So default values or dashed values are to be expected in diagnostics.
Thanks Bryan, that explanation helps. It makes sense now that PRP represents internal Plan/Recharging/Plan identifiers rather than network status.
One thing I’m still trying to understand is that my diagnostics continue to populate normally (CPU, Memory, Disk, MQTT=1, HaLow connected), yet as soon as Bluetooth connects, the app loses access to Previous Maps and all map editing functions. When Bluetooth disconnects, the maps become available again.
This behavior has been repeatable over many tests. Since diagnostics continue to communicate with the Core, it seems different from a complete communication failure. It almost looks like the app changes from cloud mode to Bluetooth/local mode and then loses access to the cloud map service.
Have you seen anything like that before, or could this still point to a software issue in the Bluetooth/Wi-Fi/cloud handoff?
No, this is the first I’ve heard of an issue like that. Bluetooth is usually very reliable for core to app communication, albeit very slow with some occasional network timeout errors. But it has never let me down for app to core communication when the internet is down/unavailable or the core isn’t connected to the DC, etc. The maps are stored on the core, not the cloud. So it’s something with either your phones BT app to core connection or something on the core itself. Try another hardware device if you can and see if you have the same problems. That will narrow it down to BT on the phone or a problem on the core.