Could not connect to rover unless my phones bluetooth was turned on.
Diagnostics when rover is not connected to my home wifi.
Diagnostics after rover is connected to home wifi
Seems like there is an issue with either your DC or the core HaLow connection it would appear. You could switch to NetRTK and use WiFi/Cellular. Just save your map first, it may wipe it when you switch. You can restore it from the cloud after if it does.
Right under the data center in diagnostics it says “Status … Running: 22 NodeError” which is the error I got when I was trying to run a work plan. Do you know what that means?
Make sure all antennas are tight.
And the pin is not bent for connector to antenna.
Just to rule out the easy stuff support can’t see.
My guess is it has something to do with the HaLow module. If you do try NetRTK, don’t forget to correct for map drift afterwards.
Its something because I’m still getting the node command error. When it happens the plan pauses and waits then it starts up again. I’m thinking it may have something to do with the GPS and HaLow.
I just dont understand. It worked fine one day then ceased all functions, then I got the motherboard error. Support said they remoted into it and now it’s half way working (okay a little more than halfway)
Your main control board may be toast. Either way, I think you’re getting a replacement core.
Hi there, sorry for the delayed response. I’ve asked the FSE responsible for your case to review your ticket as soon as possible and follow up on the current progress. We understand that the issue is still affecting your Yarbo’s normal operation, and we’ll continue tracking this case to help get it resolved.
Thank you for your patience and understanding while we work on this.
Hey Comccon, di they ever get this sorted for you? This just happened to my Rover and so far support has not made any progress. I am not even sure if they have successfully connected yet. Mine is still fully Brain Dead and offline, just as yours was originally.
Drop your ticket number here for the moderator to follow up on.
My case is #230727
They “approved a Refurbished Core for me”. Oh well, whatever bricked our Cores they must know it is not remotely fixable at this point.
Well at some point yesterday they must have done something. I did not receive any contact via the ticket or anything beyond saying they approved my refurbished core. This morning I decided to check one last time and low and behold the lights had stopped cycling. In the app it showed up normally and all diagnostics were good. I re-attached the mower module and it recognized it fine without a reboot. The work plan it was in the middle of even showed up at 58%. I hit Resume and it went to work. All 4 cameras online as well, for once. It has consumed 8% of the battery and is now at 63.5% on the 1.5 acre work plan. Fingers crossed it keeps working. I noted in the ticket to hold off on shipping. I have not seen the Node 22 error Comccon had, so far. It is reporting 0 RunningNormal. Halow True, Data center connections bounces between 2 and 3.
Well that’s great news. Hope it continues to work well for you.
Update 2 months later (to the day), and my unit is still not functional.
At this point, I am very angry and completely done with customer support. Every time we have a conversation about the unit, it feels like it’s a brand-new support ticket in the FSE’s brain, and they tell me to let them remote in. I have already given them permission at least three times to remote into the unit.
Whether the positioning service is using the Data Center or NetRTK, the unit still has trouble acquiring GPS.
The last communication I had with the FSE was that my unit was fixed and that I should try running a job. While it did run the job, the GPS was still faulty. The unit was cruising into the road, ignoring the “Do Not Go” zones, running into the house at full speed, and I was still getting the darn Node Connection Error.
I contacted support again to let them know that while the unit was technically working, it definitely was not working as advertised. They told me to use the “Replace Data Center” button. Well, my unit did not accept the new Data Center.
They replied that they would need to remote into the unit again and asked me to please give them access…again, so they could look at the logs.
At this point, what does it take to get a replacement unit?
I fear at this point the next time I have a functional unit will be for the 2027 mowing season. Guess its back to cutting the grass the old way or hiring my old landscapers again.
And to support, please stop using AI-generated responses and the same standard copy-and-paste message every time. It’s annoying, impersonal, and honestly just pisses me off even more.
Yup, after dealing with them for months on end it gets very annoying. I hope you are in good health… Maybe if we start every ticket like that, they might get the hint.
Hi there,
First, we sincerely apologize for the frustrating experience you have been through. We understand how disappointing it must be to spend so much time troubleshooting the same issue while your Yarbo still cannot operate as expected.
Our priority now is to help resolve this issue as quickly as possible. I have reviewed your latest update in our system and understand your request for a replacement. I have already reached out to our FSE team to initiate the replacement process for you.
We are also sorry for the frustration caused during the troubleshooting process, especially with the repeated troubleshooting steps and communication experience. We truly appreciate your patience and the detailed feedback you have provided throughout this case.
We will continue to follow up on the replacement process and provide you with updates as soon as more information becomes available.
Thank you again for your understanding and patience.