Ok, so to start with, I already have a ticket #187402 that covers the first three of these topics. I’ve asked this question IN THE TICKET and have received no direction. The question is, I have several issues that I need support to help resolve, one of which has morphed and then split over the last month or two, and the others coming up along the way. To @Yarbo-Forum and anyone else, would it be better for me to keep the multi-issue single-MEGA-ticket I already have, or should I close the current ticket and split the issues into separate tickets? Which would be the preferred path?
Currently the issues i have on the single ticket are as follows:
1. On the subject of connecting to the data center, I did finally have an opportunity in good whether to get on the roof of the building to get to the data center, and I WAS able to connect to it. However, I CANNOT get a stable connection if I’m more that 2-4 FEET from the data center. Between 5-10 feet the app will at least see the data center, but cannot connect to it. Basically, unless I was practically sitting LESS than arms length away, it would not connect. I do not see this being an issue with the Bluetooth radio on my phone as I can regularly connect to the Yarbo from several meters away without issue, and I have several other Bluetooth accessories I use on a regular basis without issue. Is there a possibility that just the antenna on the DC has failed or gone bad? If not, then this feels like a faulty bluetooth radio in the DC itself. All that said, it seems I was able to complete a reinstall of the data center.
2. I don’t remember if I’d brought this up in my previous comments, but after one of my failed attempts to reinstall the data center, I noticed that the diagnostics for the Yarbo started reporting zero L2 satellites under all conditions, but a total satellite count in the 15-25 range. I tried doing an antenna swap on the Yarbo and both numbers went to zero. I was concerned that maybe I had a broken antenna cable, but I have a couple of alternate GPS antennas I’d order from another supplier and tried them. With one of the original antennas and one of the alternates I have I was able to get satellite reception back on the Yarbo and confirmed that one of the original RTK antennas has gone bad. If I swap the other original antenna back for the alternate I have, the L2 count goes back to zero. How do I go about making a warranty claim for the antenna? To be clear, there are no marks I can see or visible damage to the original antenna that is not working. It appears to have just died. Regarding the alternate antenna I have, while the Yarbo is at least operational right now, the reception is noticeably worse than the stock antenna and the Yarbo is regularly losing location while operating.
(This one I’ve already posted into the support forum here)
3. Since the most recent firmware update, I noticed some unusual action in my most recent operation (as in Yesterday the 18th around 5-6PM EST) that I think may be a logic problem. Since (with my alternate antenna) I was able to get the Yarbo operational, I sent it out to (finally) start mowing again. Everything was going ok, other than the poor performance of the alternate GPS antenna, until the Yarbo went back to charge. I noticed that it seemed to be having a LOT of trouble navigating the paths I had set up (which I figured out was due to the (new???) ultrasonic sensor setting for the paths. It managed to finally navigate one path after a number of attempts, but got stuck on the final path back to its charging dock. It would start to go down the path that leads across my driveway to where the charger is placed, but would then stop as it pushed through some tall-ish grass and say “Obstacle detected” and back up a few inches. It was doing this for several minutes and did not seem to be able to make progress. I actually lost count of how many times it attempted to go through the path. I thought this was odd as it had the same problem when I went to send it out to start mowing, but after a few attempts it would give up and issue an error. However, when I was watching on the app, I think what was happening, is that it was trying to pause the work plan after detecting an object, but because the battery was at 20% it was then automatically trying to recharge. This seemed to get it stuck in a loop. I took a screen recording of this loop and uploaded it to my Google Drive at the following location: https://drive.google.com/file/d/1KozK0Z7-vI85KF7DNWRDzMEdY8GlrlRz/view?usp=sharing
I was able to get it out of this loop by turning off the vision and ultrasonic detection for the path and then reactivating the charging request. The Yarbo charged right across the path without issue and then connected to the charger right away.
4. In our previous exchange I’d told you about me watch or driving the Yarbo and seeing it randomly losing connection for a few seconds, then coming back. You’d asked me to try and capture a screen recording of this happening and I agreed, but wasn’t sure what luck I would have doing so as the occurrence was not predictable.
NEW/SUBSEQUENT ISSUES
In regards to #1, when I first set everything up and for several months afterwards, I had no issue getting the app to see the DC from the ground in front of the pole building the DC is mounted on. It’s also worth noting that while I was trying to do the re-install, I had to try three separate times to get it to complete, and the GNSS signal was borderline unstable, which is not what I recall it being when I moved it from the end of the building to the middle of the roof.
In regards to #4 I’m still seeing the connection randomly drop out, but I’ve noticed in the last couple of days that the HaLo reception is degrading. The longest distance from the DC on my property is about 120-140 yards through some trees. When I did the mapping and first few mows, the rover had no issue maintaining the connection until it got to the very edge of that distance, and even then would only once in a while switch to cellular for a few seconds. Now it seems to be switching over around 70-80 yards away, and yesterday after the most recent rain, even when it was back on the charging pad, less than 60 feet from the DC, the rover was reporting a -81 signal for the HaLo. Now that things have dried out, it’s back to reporting -66 at the charging pad. I’ve got a new HaLo antenna for the rover on order as the whip part of it does have a slight (and I do mean SLIGHT) bend/kink near the base, but I’m doubtful that that is the issue.
I had an incident where the rover backed up through a NGZ while trying to “navigate around an obstacle” and immediately after backing all the way through the NGZ, proceeded to drive FORWARD right back through the same zone to get right back where it was. I’ve been advised that I should create a ticket for this with the date and time of the occurrence. This occurred approximately shortly after 8:35AM EST on Friday, May 22nd 2026.
Lastly, I’ve had an issue with a cover on the trimmer attachment coming off. I’ve posted about it here: Trimmer cover loose? but I’m wondering if I need to make a new ticket for this too or add it to my current one 
