My recently replaced core has been running pretty much non-stop since I received it on Tuesday morning. However I am having two issues that I’m wondering if anyone else has seen. I have also opened a ticket.
The Halo range has been significantly reduced. In fact, in just a few days it has fallen over to cell so much that I’ve consumed over 200MB of 4G cell data. The signal strength sitting just a few feet from the DC is -58, and at approximately 100 feet it falls to -77 and disconnects.
Starting this morning, it is having trouble charging. Although the battery is showing only 37 degrees Celsius, it charges for a moment, and then stops, then repeats. I started a log recording at 9:47 US Eastern time this morning (7/31/2026) where the battery status switches back and forth between 100 and 300.
Have you done the usual unplug both devices for 5 mins, plug in the DC, then plug in the battery cable on the core and turn on? Check the core’s antenna, may be loose. You can try removing that rubber washer underneath to see if you get a better signal. Did you replace the DC at all or is that all original still?
As for the charging, if I recall, this is a fairly new docking station? Make sure it is clean, the core is lined up properly between the 3 yellow lines (metal bumper on the line in the back).
Do you have the latest hotfix 3.14.1 and app 3.19.2?
Support got back to me already. They’ve instructed me to unplug the battery for a couple of hours. The data center the charging dock and the core are all brand new. They have also completed their remote diagnostic. I’ve lost the ability to connect to the core remotely at all, but I’m hopeful once the two hour unplugged is complete that all will be good again.
So, unfortunately the 2 hour unplug was unsuccessful . The core seems to enter a loop of flashing Red, Yellow, Blue and the Dock just shows Red now.
We tried to do put the core in Bluetooth pairing mode, but the cycle was only broken by one extre blue flash, and then they app would have the BT insignia light up for a moment, but then report a connectivity error. Awaiting further instructions from support.
Support gave me the same instructions. Unfortunately I was unsuccessful in getting it to work before it was decided to escalate to an FSE.
I did keep trying and eventually I did get it to connect to Bluetooth long enough to reach the network settings and confirm that it still could connect to my WiFi.
However, I don’t know if anyone will look into it over the weekend. In the meantime the battery must have completely drained because the core was dead this morning.
One of the initial instructions support gave me was to leave it on the dock and not connect the DC charger so they could do their diagnostics. At this point it seems that they need it to have power to do anything so I’ve gone ahead and plugged the DC in and will let it charge a couple of hours and power the core back on in case someone does want to look at it over the weekend.
Interesting follow up. After charging for an hour, I hit the power button and the core has booted up successfully and even remembers where it was in the work plan when everything went haywire. I’ll let the battery finish charging and then I will plug the dock back in and see if the dock now mysteriously has started working too.
Additional follow up: after charging 48%, I unplugged it and plugged the dock back in; the light turned blue. So then I told the core to go back to the dock to recharge and it did so successfully, and everything appears to be working normally now.
I am completely baffled by what caused all the failures yesterday and further what caused it all to start working again today, but happy that it is. I’ve left a note with Support updating the status and offered to be of whatever assistance I can if they choose to pursue a root cause analysis.
Wow. Although I’m glad that your Yarbo seems to have been resurrected and is now operable again, it would be really comforting to know exactly what happened in the first place, and assurance that it won’t happen again.
I hope Yarbo Support gives you some clarity. In the mean time, give it a try and see if it continues to work properly. Fingers crossed!
Maybe your robot joined the union and was just taking its mandatory “break” time!
This sounds like maybe the battery calibration could’ve been off and it thought the battery was more charged than it actually was. Just a theory. Might be worth asking support to run some tests on the battery and also apply the battery charging fix they have for the calibration issue.
Your comment is probably right on point. Although the core continues to charge on the dock, it’s doing it at an extraordinarily slow rate even though the temperature remains below 40°C. It normally takes approximately 90 minutes to go from 20% to 80% but it’s been charging for over four hours to go from 48% to 73%.
You might be able to “fix this” by plugging in the wired charger and letting it charge up until the charger light turns green, then unplugging the battery for 4 hours, turning on the machine and seeing where the actual SOC is at (comparing before power down and after power up). Then charge up to 100% if it isn’t full. But that could take up to 24 hours.
So, I i’m almost wondering if Support is fixing things for me in the background. Before I could go try your suggestion suddenly the rate of charge jumped up back to its normal rate.
So, at this moment at least, my only remaining open issue is connectivity at range. I haven’t had an opportunity to test that because of the charging issues so that is my next agenda item.
Just reached 100% charge so going to test out tow mode in a small rectangle with no obstacles and without a trailer attached to just see what it does and if it can maintain a network connection.
My communication issues remain. I have only 4G connectivity once my core exceeds approximately 100 ft from the Data Center. Bluetooth can be established for a few seconds by pressing the power button for 5 seconds but is quickly lost.
I still have a learning curve before I can effectively use towing mode. Video of part of my attempt is attached for your viewing pleasure.
Well the tow mode is beta. So no expectations there from me.
The communication issue is tough, but at least when it powered back up this morning, I was able to access the core and issue it commands. It’s just problematic when it moves further away I have to wait for the cell connection to reestablish. As long as it’s not an emergency command, the impact is minimal. I have confidence will get through this one.
Honestly, the thing that bothers me the most is that after two years, I was forced to go out and buy fossil fuel and dig my old zero turn out of the barn.
