We hope you’re doing well. To improve your overall Yarbo experience, we’re rolling out Firmware V3.14.20 and App V3.19.6.
This hotfix will be released in batches and is expected to be fully deployed within one week.
What’s Included in This Update?
Firmware V3.14.20
Optimizations & Fixes
Improved 4G connection stability.
Retired all legacy MQTT servers.
Fixed false “Lost Battery Communication” reports after power-on.
Optimized log storage and retention.
Enhanced automatic recovery from false electronic error reports.
Improved “Plan Paused by User” error reporting.
Improved safety awareness and human/animal avoidance in Gentle Contact Mode.
Set ultrasonic obstacle avoidance to off by default.
Improved the wording of pathway obstacle notifications.
Enabled faster switching to single-antenna mode.
Reduced false detection of B010 power board issues.
App V3.19.6
General
Improved GPS/DR status display during GPS-critical setup flows.
Fixed an issue where the Android Back button did not return to the previous page or exit the app.
Lawn Mower & Lawn Mower Pro
Fixed an issue where the cutting height setting was not applied when perimeter mowing was disabled.
Leaf Blower
Fixed mismatched FAST/SLOW speed labels for the Leaf Blower.
How to Update
Please make sure your Yarbo is powered on and connected to the internet. The new firmware will be installed automatically once it becomes available for your device.
If you have not received the firmware update after one week, please contact us at support@yarbo.com.
As always, thank you for the continuous stream of hotfixes. Greatly appreciated!
One observation/ thought - Setting the ultrasonic to disabled by default suggests that it is not considered to be reliable for use. Is there a longer term plan to rectify and reenable?
And yet another update without addressing NGZ violations. Really! Yarbo’s priorities leave me shaking my head. Tell us one more time how seriously you take these issues.
Yep. NGZ incursions right now is the main thing which must be fixed. And as I have already written - 2 perimeter laps around NGZs would completely solve the issue and prevent yarbo from getting too close to NGZs while doing the mowing zig-zag.
It’s super neat that Deadends near a NGZ have now also figured out how to back into the restricted space. It obviously didn’t start in a NGZ. Adding more buffer to your NGZs won’t fix this stupid. I’m am so fed up with this trash software! Beyond furious is an understatement. Can’t wait for that new Pro Core, HA!
and before someone asks why it starts so far out, it’s to work around ANOTHER BUG that DEs need to be staggered to work without shredding the yard!
It is strange that the issues are randomly across all of us. I’ve had great sucess up until the previous update when gps went to crap. I’m probably jinxing it but a couple of nights ago, i had to manually dock because gps was so bad. I didn’t change anything other than this new update and didn’t have any issues, even in the really bad tree cover.
So when Support says load the latest firmware in response to a Power Board Issue (B010), where do you download it from or how do I force the Yarbo to find it and download it rather than waiting for the automatic update that might take a week ?
The only way for you to do it is to accept it when prompted. When it’s available for you unit, you should get a prompt (typically). Sometimes they just force update it. Updates are rolling out in batches. If you don’t have 3.14.20 yet, ask support if they can push it to you. Otherwise, the updates should be fully completed by Wednesday. Are you on a 3.14.X release currently at least or are on you on something older? If older, definitely get support engaged on it.
Thank you! I’ll that a try. I have a spot where I tried everything and can’t get it to smoothly run consecutive DEs. I kept playing with the start spacing and didn’t think to make them all identical.
I’d prefer we didn’t “ride the lightning”, or in this case, “ride the rock”, like this.
No-go zones are No Go.
I believe there is a “centering” bug on Yarbo right now. Perhaps the GPS coordinates are not providing the correct “center” dependent on the “direction” of travel, and this is inadvertently causing accidental “drift” into No Go zones.
Regardless, if it’s in a No Go zone for any reason, once again, policy should be STOP.
STOP.