What you are describing all sounds normal to me. It will charge up and show 100% but continue to “trickle charge” for a while. It will cycle through charge and not charging and I suspect the flashing blue when charging is active in the app is it bleeding off power. You will usually see flashing green after this. All part of their “Battery care”.
This is what the wiki says about the lights on the dock.
Dang and I thought it was just me
@alpineracing Regarding a simple way to reboot the system, you can refer to Bryan’s suggestion above—it provides the easiest and most effective method without needing to reset Wi-Fi, Bluetooth, or other settings.
As for the recharging and docking issue you described, we recommend submitting a support ticket and including the approximate timestamp when the issue occurred. This will allow our support team to review the relevant logs and investigate the issue further.
Thank you for sharing these details—they’re very helpful for troubleshooting.
Sorry to hear about the issues you’re experiencing—an update should definitely not impact the robot’s ability to operate autonomously like this.
Regarding the “failed to plan route” error, this can sometimes occur if a No-Go Zone fully blocks a valid passage within the working area. It may be worth double-checking whether any No-Go Zones are unintentionally blocking required paths.
As for the camera disconnected message, this may possibly be related to a firmware version that is not fully compatible with the current app version. Ensuring that both the firmware and the app are updated to compatible versions could help address this.
For the other issues you mentioned—such as the robot not recognizing sidewalks or paths between zones, and not returning to recharge—these will likely require further investigation by our support team. Could you please submit a support ticket regarding the issues you encountered after the update? This will allow us to review the logs, identify the root cause, and work toward providing a smoother experience in future updates.
Thank you for bringing this to our attention—we appreciate your feedback and want to help get this resolved.
Sorry to hear about the issues you’re experiencing—that sounds extremely frustrating, especially since this behavior only started after the update.
Regarding the recharging and docking issues, could you please submit a support ticket and include as much detail as possible (such as when the issue occurs and any patterns you’ve noticed)? This will allow our support team to investigate the problem further, review logs, and better understand what’s causing the behavior.
Your feedback is important to us, and we want to help identify the root cause and work toward a resolution as quickly as possible.
This issue will need further investigation by our support team. We kindly ask that you submit a support ticket so the team can review the logs and look into this behavior in more detail.
Thanks for providing these details. We’ve reviewed all the issues you reported in support ticket #153194. We kindly ask for your patience while our support team goes through each item and investigates them thoroughly.
We appreciate your detailed observations, as they are very helpful for our investigation. We’ll follow up once we have more information or next steps to share.
Thank you @bryan.wheeler and YARBO support team, my app showed EVERYTHING offline so I had no option to do a “safety settings restart” - anything like that (I was looking for a way to reboot when this occurred and anything with this verbiage was “greyed out” unless I am missing something… GOOD NEWS is I am back up and running… Support told me to simply push and hold the power button (under the cover) for 3-4 seconds ONLY (NOT a full reboot) and then after it powered back up and went thru it’s self tests, I tried to reconnect bluetooth and was on the struggle bus as that was not working nor reconnecting to wifi and then BAM, everything simply went back online. PS: My Data Center was ALWAYS in the green during all of this. I have heard a lot in the blogs about people losing maps and settings and wanted to let everyone know to definitely try the 3-4 second power button hold BEFORE doing anything else. In my case and if it happens again in the future, I will be a bit more patient and wait approximately 5-15 minutes to see if all comes back on line after doing so before further trouble shooting.
#1 I don’t have no go zones…
Your update made changes to the path system regarding how they handle chute discharge direction…. Paths no longer allow the ends to be included in discharge direction… this is a problem for anyon who needs a very short path to go from docking station to sidewalk or zone…. I require a super short path to get robot to drive from docking to sidewalk, without it robot will turn sideways on docking station and drive into bricks (im running out of shear pins)…. Disallowing the ends to be used mand i am unable to get a 1m discharge area…. This is the can’t plan route issue…
As for failing docking it is simple…. Whatever changes made in update cause robot to back up too far during the second part of positioning and so it will keep trying to backup which it can’t do to snow so tracks slip forever….
Robot approaches dock.. cleans it… backs off.. spins around and does some wiggling to line up… then it backs unto docking station (too far)… endless repeat
Funny that the forum lists this thread solved! Being a mower not a blower here in Texas, I’ve had mine shut down for the last couple of months.
Booted and sent it out to start a leaf blower job (just to force it to run a bit.) Got the update notification and accepted it.
After the reboot, the unit wont navigate anywhere as it believes a NGZ is in it’s path. (WP032) It’s not. Couple of reboots etc. No luck.
Yarbo has to do better. Hoping someone else has seen this.
Les
can you post a pic of your map?
Try editing the NGZ’s that are blocking off these areas so that they fully encompass the cutoff area. Because there isn’t a path to those cut off sections of the areas, it can’t calculate the plan.
Bullshit!
The bottom NGZ doesnt prevent it from taking the marked path to the north area.
The entire yard adjacent to the charger (with the patch from the charger to the area (hell for that matter it’s in the area now) doesn’t work. I’ll try turning them off, but we both know the software from yarbo is weak at best and neither NGZ was an issue before the “upgrade”
Les
I’m not a huge fan of that functionality either…but overall the update is an improvement. Hopefully it’s in the cards to “fix” correctly in the next few updates. What is the need for that large no-go zone? Can labeling the areas prevent undesirable access now?
Great response to someone trying to help. I’m sure you’ll get it solved eventually, but don’t be surprised that you have to solve it yourself.
The fact that the unit has negotiated the acreage for a full year with proper avoidance of the displayed NGZs. The fact that the error occurred in any of the zones, with or without NGZs made it clear it was a result of the software change. Being that the area tasked to work had NO NGZs, there shouldn’t be a reason for the unit not to work the area.
So I tried his suggestion.
Have the unit in the area I want to work.
Turned off all the NGZ in the area.
Guess what happened?….. Same error.
So I guess that suggestion was ROSES AND RAINBOWS (but didn’t solve the problem.)
Turns out the software is buggy. Turning on the large NGZ in a completely different area of the yard will prevent the unit from working a separate area with NO NGZs. Shouldn’t be that way.
Maybe Bryan knew the software had issues. Maybe he’s seen it before. The fact that a NGZ in a non related area will prevent the unit from working is in fact BS!
Les
I just flagged him. This is nonsense. No way to treat someone who’s trying to HELP you.
So interesting discovery.
Started turning off NGZs in other areas of the yard. Turning a NGZ off in an unrelated area allowed the unit to work one of the the areas in question.
Will have to try othr areas as well and report back.
Still don’t understand why a completely out of zone NGZ would hinder the unit from working an area with NO NGZs.
Les
Knock yourself out.
His suggestion shouldnt have anything to do with the error I posted!
Les
