DC crashed again overnight (13-days since last reboot). I noted in my last post that I had disabled 4G to see what would happen. Well, it didn’t didn’t failover to 4G. The rover just became unreachable. I restarted the DC via a smart plug I added just for this eventuality. The rover popped right back up. This failure has now occurred every (2) weeks, consistently.
4 Likes
I have the same issue. I’ll start keeping a log to see if my DC issues are consistent as well.
4 Likes
Happened to me this morning again!!! Exact same behavior. I got 4g only. When I restarted the mower I was not even able to connect to it. Power reboot everything (router, DC, 60 seconds Yarbo reset, poe reset). Fixed the issue
2 Likes
In my case I only need to bounce the DC for it to remedy itself.
4 Likes
Well… I’ll try that next time. I did all of this recursively… (a bit alike our other recursive discussion on this forum haha).
I first rebooted the robot and the router remotely (was not home). Lost all Contact to the rover. When I was back home I did a 60s reset, did not work. Then I turned off the robot, walked to the DC. Disconnected everything and then reconnected… Then turned on the robot…
I guess next time I’ll try the DC first! Smart plug time!
3 Likes
I went through the same routine the first time it happened before I figured out the problem was the DC.
5 Likes
I have also have the same issue periodically. My work around is to reset the DC first if there is an issue. In my experience, it happens each time there is an update or a hotfix sent out OTA. Hopefully, it will be corrected at some point but until than, I will continue to reset the DC after each update.
1 Like
I read that support had identified a bug causing the spamming virtual MAC and IP requests. I wouldn’t be surprised if this is somehow related. It’s a repeatable failure. It just took some time to figure out the pattern.
@Yarbo-Forum can you please recommend next steps in identifying/correcting this?
5 Likes
I went through my router’s logs and made notes of the ISP disruptions caused by the spamming of Mac addresses and submitted those time stamps along with the mowing processes that were occurring simultaneously. I included all that information in my support ticket
4 Likes
Spammy Mac… sounds like a rapper name. 
3 Likes
Do you refer to Ryan’s case? Your situation is different from that one. We’ve identified Ryan’s case as a known issue, and our R&D team has indicated that this behavior may occur in some data centers due to the use of MAC address randomization. We plan to address this in a future update.
As for your case, as we discussed in your support ticket, if the issue occurs again, please follow the instructions we provided to replace the data center. This may be due to the initialization process not being fully completed when you first set up the data center.
2 Likes
I’m not sure shotgun troubleshooting and just replacing things is the answer. There are multiple people is this thread reporting the same issue. I’ll wait until happens again and update my ticket. In the past, it has taken support 2-3 days to respond and I can’t have Yarbo down for multiple days when I know a reboot of the DC will correct it.
6 Likes
I’ve reconfirmed with our field service engineer. Yes, rebooting the DC can currently serve as a workaround for this issue. Our R&D team is actively working on a long-term solution to optimize automatic HaLow re-pairing and self-recovery, aiming to minimize the need for user intervention.
5 Likes