Just received yet another rebuilt core, yesterday. 10th core in around two years. So far, no GPS, no Halow, constantly going on and offline by it’s self, no app control of blade height but works with physical. Don’t know what else I’ve yet to find, still reloading.
Sent me 2 flexible RTK mounts but with only 1 set of screws to mount them with.
Received an email saying:
"We’d like to share an update regarding your refurbished Yarbo Core under warranty exchange.
To ensure every unit arrives in the best possible condition, we have implemented an additional round of thorough quality inspections before shipment. This has slightly extended the preparation timeline, but it allows us to deliver a more reliable and consistent experience."
Apparently bowing smoke. Had to wait weeks for this core. Is Mother nature supposed to wait for Yarbo?
I half wonder if all these core replacements flying around are just an easy substitute for real troubleshooting. Were they really all hardware failures or just that they couldn’t figure it out and did a swap?
I’m on my 1st core in year 2 with 4 acres. I can’t just be that lucky.
Yes, I think it’s probably a lack of experience on the support side that leads to the swap. But it is also about trying to get the user back up as quick as possible and I am sure if the user is extremely frustrated and taking it out on support that might be a factor.
I have 2. One from October 2024 and one from August 2025. Both are good.
Sorry, wouldn’t you be frustrated? I’m 69 and bought Yarbo to simplify my life. So far it has made it exhausting. Having to chase, wait on tech support, unpack, reconfigure (started with no cloud with first 4 cores so had to re-walk all areas), test, repack and ship, has turned into a lot more work than mowing.
Just reconfiguring the settings and plans for each core, since you have to mount each module separately, takes 5-6 full days, before you can start.
That is good news at least for one problem. Ok, blade height control. This app change is finicky. You have to tap and hold until you see it hit the right setting and even then it may take a few tries. That’s something they are aware of and it will hopefully be fixed or refined in the next app release. Does it at least take your setting in the area settings and mow at the right height then when you send it out on automation?
Hi there, we’re very sorry to hear about the experience you’ve had and for the inconvenience this has caused. We completely understand how frustrating this must be, especially after going through multiple core replacements and waiting weeks for the replacement unit.
Regarding the blade height control issue, the case has already been escalated to our Field Service Engineer team for further investigation. They will continue reviewing the logs and system behavior to identify the root cause and help resolve the issue for you as soon as possible.
We truly appreciate your patience and understanding while we work on this for you.
Disabled DS pathway offsets and at least it starts to run the plan. Got a lot of funny errors including vehicle parking blocking path. There is no vehicle parking in front of DS pathway, it had moved forward just off the DS.
With the amount of NGZ’s I see, offsets are going to cause those weird issues I’m sure. As for the other weird errors, disable obstacle avoidance on the problem pathway setting.
