Updates Coming

Dear Yarbo Family,

We hope you are doing well.

To enhance the stability and reliability of Yarbo, we are rolling out Hotfix Firmware V3.14.1.

The hotfix will be released in batches and is expected to be fully deployed within a week.

What’s included in this update?

General:

  • Optimized system memory usage for enhanced stability.
  • Optimized the positioning logic for single-antenna mode to improve stability and accuracy.
  • Updated Privacy Policy.
  • Fixed an issue where Yarbo failed to automatically start charging when placed on the docking station.

Lawn Mower (Pro)

  • Optimized the speed control logic during perimeter mowing and No-Go Zone (NGZ) edge mowing to improve mowing performance and stability.

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.

Please note: There is no new app version with this release.

If you have not received the firmware update after a week, please feel free to contact us at support@yarbo.com.

Best regards,
Team Yarbo

I didn’t even get the last update yet, and now there is another.

I really appreciate the rapid hotfix release cadence, but I am concerned about their QA and UAT test processes.

We have seen a lot of bugs/defects/regressions in these hotfixes as of late. That needs to stop ASAP.

The optimized speed logic during perimeter mowing is tagged “Lawn Mower (Pro)”. I assume this fix applies to the M1 and the Pro heads? The wording could be confusing.

I asked, it does.

I have Hotfix Firmware V3.14.1 already,

and it is a major step backwards for me - Memory Path No Reverse Back - #20 by B-Mod

Update, I freaked-out too soon.

Yarbo just completed my that first Work Plan after V3.14.1, which is my toughest WP, and it just had this one work-stopping error. Prior to V3.14.0 it was much worse.

So I calling it not a step backward for me, but just an anomoly.

Was able to complete my neighbors tree area with no stoppage. In fact it appeared as if GPS was pretty good all the way through. This is a major improvement for me. Just received my pro antenna, not installed yet. So far no issues.

Yes, this optimization applies to both the Lawn Mower module (M1) and the Lawn Mower Pro module.

Sorry for the confusion caused by the wording in the release notes. We’ll make sure the description is clearer in future updates.

Thanks for pointing this out!

Wow my Yarbo jist updated to 3.14.01. Now its running 2’ outside of the boundaries and mowing down my wife’s flower beds (and a chunk of plastic from an egress well)!

Why in the world would a firmware fix change the map so drastically?

Appears I’ll have to remap the yard as I can’t trust what it’s currently doing!

Try resetting the drift

Ya I thought of doing that, but then read the Yarbo wiki that said only do it when the error message appears (which I dont have).

Guess it can’t hurt though, will give it a shot.

Make sure it is on the dock and charging before doing map drift, also make sure gps is good also.

@B-Mod yup yup

Well that didnt work. Corrected drift and sent him back, and caught him hanging over the edge of my egress well, about to go through a window.

Thats a good 3’ out of bounds. Looks likeI’m remapping, cuz at this point I dont trust it.

delete.

Could you please check your Data Center version?

Also do you have you PPVS enabled and what are the settings?

Data center version says 1.1.1

I’ve run through this area three times now. Twice with PPVS and once without, each with the same result.

To be clear this is an area I’ve been mowing successfully since I got this Core replacement, and the first mow after the firmware update revealed these issues.

I’ll be remapping later today and see if that fixes it. Can’t run the risk of Yarbo causing more damage or going through my basement egress window.

As a follow up test I set Yarbo to work in my backyard, which only has obstacles on the border so its mich safer if dimensions are off).

Yarbo kept constantly crashing into a fence which was mapped about 8" outside the boundary. As I watch Yarbo moving and compare it to the app, the app shows Yarbo still inside the boundary when he’s clearly outside.

Something had to get screwed up by the update, so I’ll map today and report back if it solves this.