# Hotfix Update: Firmware V3.14.11 & App V3.19.5

**URL:** https://forum.yarbo.com/t/hotfix-update-firmware-v3-14-11-app-v3-19-5/7393
**Category:** Updates & Product Releases
**Created:** [August 31, 2026, 2:30am UTC](https://forum.yarbo.com/t/hotfix-update-firmware-v3-14-11-app-v3-19-5/7393 "2026-08-31T02:30:52Z")
**Posts on this page:** 20
**Page:** 5

<div class="post-metadata">

### Author: ![Yarbo-Forum](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.yarbo.com/yarbo-forum/32/126_2.png) [@Yarbo-Forum](https://forum.yarbo.com/u/Yarbo-Forum)
#### Post date: [September 4, 2026, 10:18am UTC](https://forum.yarbo.com/t/hotfix-update-firmware-v3-14-11-app-v3-19-5/7393/82 "2026-09-04T10:18:35Z")

</div>

Could you please share the ticket number you’re referring to? I’ll help follow up on it and make sure the case gets the attention it needs so we can work toward a reasonable solution.

---

<div class="post-metadata">

### Author: ![Yarbo-Forum](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.yarbo.com/yarbo-forum/32/126_2.png) [@Yarbo-Forum](https://forum.yarbo.com/u/Yarbo-Forum)
#### Post date: [September 4, 2026, 10:22am UTC](https://forum.yarbo.com/t/hotfix-update-firmware-v3-14-11-app-v3-19-5/7393/83 "2026-09-04T10:22:38Z")

</div>

Please try Bryan’s suggestion first and see if it helps resolve the issue.

---

<div class="post-metadata">

### Author: ![Yarbo-Forum](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.yarbo.com/yarbo-forum/32/126_2.png) [@Yarbo-Forum](https://forum.yarbo.com/u/Yarbo-Forum)
#### Post date: [September 4, 2026, 10:27am UTC](https://forum.yarbo.com/t/hotfix-update-firmware-v3-14-11-app-v3-19-5/7393/84 "2026-09-04T10:27:35Z")

</div>

Thanks for sharing your feedback. Please rest assured that we are continuing to work on improving the overall experience.

We currently have optimization work planned for the turning behavior, and we also have a team looking into the missed-cutting issues you mentioned.

We hear your concerns, and we’ll continue working on improvements in these areas in future updates.

---

<div class="post-metadata">

### Author: ![Yarbo-Forum](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.yarbo.com/yarbo-forum/32/126_2.png) [@Yarbo-Forum](https://forum.yarbo.com/u/Yarbo-Forum)
#### Post date: [September 4, 2026, 10:28am UTC](https://forum.yarbo.com/t/hotfix-update-firmware-v3-14-11-app-v3-19-5/7393/85 "2026-09-04T10:28:43Z")

</div>

This definitely shouldn’t be happening. Please submit a support ticket so our team can take a closer look and investigate the issue further.

---

<div class="post-metadata">

### Author: ![andris.leja](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.yarbo.com/andris.leja/32/503_2.png) [@andris.leja](https://forum.yarbo.com/u/andris.leja)
#### Post date: [September 8, 2026, 1:35pm UTC](https://forum.yarbo.com/t/hotfix-update-firmware-v3-14-11-app-v3-19-5/7393/86 "2026-09-08T13:35:14Z")

</div>

How hard it can be?

 ![image](https://canada1.discourse-cdn.com/flex007/uploads/yarbo/original/2X/b/b5e449f30d5c6acab243fe1499bc4f9bb3f2115e.jpeg)

This is pure route calculation, right?  
It’s done by Yarbo executing some algorithm, right?

You have all our maps in your cloud, right?

Just run the algorithm against all the areas, cycle it through path offset and/or route angle settings and then put AI to work to find wrokplan route areas where there is no full coverage (missed stripes). Then analyze and figure out usecases where there are missed stripes and fix it.

---

<div class="post-metadata">

### Author: ![Gabriele](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.yarbo.com/gabriele/32/5860_2.png) [@Gabriele](https://forum.yarbo.com/u/Gabriele)
#### Post date: [September 8, 2026, 6:00pm UTC](https://forum.yarbo.com/t/hotfix-update-firmware-v3-14-11-app-v3-19-5/7393/87 "2026-09-08T18:00:06Z")

</div>

I tested the update on my current Yaro, waiting for the arrival of the replacement… I must say I found significant improvements in maneuvering around obstacles… I didn’t encounter any particular issues except for the lack of correct line recovery when reversing around a no-go zone, as it used to do, leaving small uncut spots… Maintaining a safety distance of 10 cm from the NGZs, the Yaro respects them without colliding… I didn’t encounter the false error of non-recharging when returning to the base, as others here on the forum have.

---

<div class="post-metadata">

### Author: ![Yarbo-Forum](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.yarbo.com/yarbo-forum/32/126_2.png) [@Yarbo-Forum](https://forum.yarbo.com/u/Yarbo-Forum)
#### Post date: [September 9, 2026, 7:41am UTC](https://forum.yarbo.com/t/hotfix-update-firmware-v3-14-11-app-v3-19-5/7393/89 "2026-09-09T07:41:09Z")

</div>

Thanks for sharing the suggestion. We do have a dedicated project currently working on the missed-stripe and incomplete-coverage issue, including scenarios related to route calculation and line recovery.

The team is continuing to analyze the different cases that can lead to missed areas and is working on further improvements to the routing logic. We know this has been a frustrating issue for some users, and it’s something we’re actively following and working to improve in future updates.

---

<div class="post-metadata">

### Author: ![Yarbo-Forum](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.yarbo.com/yarbo-forum/32/126_2.png) [@Yarbo-Forum](https://forum.yarbo.com/u/Yarbo-Forum)
#### Post date: [September 9, 2026, 7:55am UTC](https://forum.yarbo.com/t/hotfix-update-firmware-v3-14-11-app-v3-19-5/7393/90 "2026-09-09T07:55:42Z")

</div>

Thanks for sharing your feedback. I’ve passed your comments about the missed cuts around the No-Go Zone along to our team for further review.

---

<div class="post-metadata">

### Author: ![andris.leja](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.yarbo.com/andris.leja/32/503_2.png) [@andris.leja](https://forum.yarbo.com/u/andris.leja)
#### Post date: [September 9, 2026, 11:50am UTC](https://forum.yarbo.com/t/hotfix-update-firmware-v3-14-11-app-v3-19-5/7393/91 "2026-09-09T11:50:08Z")

</div>

Again … grinding noise, I look at the app and of couse yarbo is mowing a rock in NGZ.

And why? Looks like it was just turning around in that ‘tip of the needle’ in its mow path.

 ![Screenshot_20260908_225843](https://canada1.discourse-cdn.com/flex007/uploads/yarbo/original/2X/3/34b2aaf68f115323649badafecba3fe7d38481d4.jpeg)  
 ![Screenshot_20260908_225915](https://canada1.discourse-cdn.com/flex007/uploads/yarbo/original/2X/1/10e7270e65ff0813b43739fc749fc6b3c3aaeb19.jpeg)

---

<div class="post-metadata">

### Author: ![cobradunn](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.yarbo.com/cobradunn/32/298_2.png) [@cobradunn](https://forum.yarbo.com/u/cobradunn)
#### Post date: [September 9, 2026, 12:01pm UTC](https://forum.yarbo.com/t/hotfix-update-firmware-v3-14-11-app-v3-19-5/7393/92 "2026-09-09T12:01:12Z")

</div>

It looks like if the pathing algorithm creates a route into or too close to NGZ. It overrides it’s awareness of NGZs. This is a permissions layering failure. NGZs should ALWAYS have final precedence.

This should not be taking them months to correct. There have been (3) updates that haven’t addressed this. There is clear potential for something very bad to happen. Go ahead and “pass that on to development”

---

<div class="post-metadata">

### Author: ![andris.leja](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.yarbo.com/andris.leja/32/503_2.png) [@andris.leja](https://forum.yarbo.com/u/andris.leja)
#### Post date: [September 9, 2026, 1:17pm UTC](https://forum.yarbo.com/t/hotfix-update-firmware-v3-14-11-app-v3-19-5/7393/93 "2026-09-09T13:17:53Z")

</div>

I’ve been writing this 100 times. While calculating the route, Yarbo is not aware of it’s own dimensions. Even with way older firmwares (when yarbo was still more or less, but respecting NGZs), I had a place in my yard one and a half Yarbos wide (between perimeter and ngz) and the calculated mow route had a ‘spike’ in that gap - meaning that yarbo must turn around there. It physically can’t turn there, because its too narrow. It tried, demolished a bit structure in NGZ and got stuck. Then i decided to exclude that NGZ from area and cover the gap with 2 deadends.

---

<div class="post-metadata">

### Author: ![Yarbo-Forum](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.yarbo.com/yarbo-forum/32/126_2.png) [@Yarbo-Forum](https://forum.yarbo.com/u/Yarbo-Forum)
#### Post date: [September 10, 2026, 8:09am UTC](https://forum.yarbo.com/t/hotfix-update-firmware-v3-14-11-app-v3-19-5/7393/94 "2026-09-10T08:09:50Z")

</div>

Really sorry to hear this happened again. We understand how concerning it is when Yarbo enters a No-Go Zone, and this is definitely something we take seriously.

For now, could you please try increasing the NGZ buffer distance as a temporary workaround? This may help give Yarbo more clearance around the restricted area while our team continues looking into the behavior.

---

<div class="post-metadata">

### Author: ![andris.leja](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.yarbo.com/andris.leja/32/503_2.png) [@andris.leja](https://forum.yarbo.com/u/andris.leja)
#### Post date: [September 10, 2026, 8:31pm UTC](https://forum.yarbo.com/t/hotfix-update-firmware-v3-14-11-app-v3-19-5/7393/95 "2026-09-10T20:31:54Z")

</div>

Yes. Increasing ngz clearance sounds like only viable option at the moment. I really hope you fix it soon. It’s pure math and nothing else.

---

<div class="post-metadata">

### Author: ![cobradunn](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.yarbo.com/cobradunn/32/298_2.png) [@cobradunn](https://forum.yarbo.com/u/cobradunn)
#### Post date: [September 11, 2026, 12:32am UTC](https://forum.yarbo.com/t/hotfix-update-firmware-v3-14-11-app-v3-19-5/7393/96 "2026-09-11T00:32:22Z")

</div>

I ran this area again tonight. It’s on diamond pattern but the tit in the blue circle is the spot it backed into the tank. It successfully completed this spot tonight, but the route rotation has incremented and they applied some unknown fix to my firmware, so take that for what it’s worth.

 ![IMG_0321.PNG](https://canada1.discourse-cdn.com/flex007/uploads/yarbo/original/2X/f/fe95f1234c9e7cb58da7641b303bb132c7618ea4.jpeg)

---

<div class="post-metadata">

### Author: ![Kolbe](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.yarbo.com/kolbe/32/508_2.png) [@Kolbe](https://forum.yarbo.com/u/Kolbe)
#### Post date: [September 12, 2026, 1:19pm UTC](https://forum.yarbo.com/t/hotfix-update-firmware-v3-14-11-app-v3-19-5/7393/97 "2026-09-12T13:19:20Z")

</div>

After the update and hotfix, you can no longer set the trimmer direction for dead ends.

---

<div class="post-metadata">

### Author: ![Kolbe](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.yarbo.com/kolbe/32/508_2.png) [@Kolbe](https://forum.yarbo.com/u/Kolbe)
#### Post date: [September 12, 2026, 2:50pm UTC](https://forum.yarbo.com/t/hotfix-update-firmware-v3-14-11-app-v3-19-5/7393/98 "2026-09-12T14:50:10Z")

</div>

Strange. I couldn’t before, but now I can again. 🤔

---

<div class="post-metadata">

### Author: ![john.c.brobston](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.yarbo.com/john.c.brobston/32/233_2.png) [@john.c.brobston](https://forum.yarbo.com/u/john.c.brobston)
#### Post date: [September 12, 2026, 9:57pm UTC](https://forum.yarbo.com/t/hotfix-update-firmware-v3-14-11-app-v3-19-5/7393/99 "2026-09-12T21:57:02Z")

</div>

I’m currently on this new update. The map is showing my Yarbo about 8 feet away from the dock that it is sitting on top of. The same thing happened with the last update, only difference is that it was 8 feet away in a different direction.

Looks like I’m going to have to remap my whole yard _again_. This is the second update that has done this.

Somehow Tesla has managed to roll out a dozen updates since I got my Yarbo and never had this kind of issue, so why is it so hard for Yarbo?

Please provide a feature to allow me to prevent future updates from installing. I don’t want another update until you are willing to guarantee in writing with penalties that it will not screw up the map.

I made a choice between a Yarbo and a new zero-turn. I feel that I made the wrong choice.

---

<div class="post-metadata">

### Author: ![bryan.wheeler](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.yarbo.com/bryan.wheeler/32/215_2.png) [@bryan.wheeler](https://forum.yarbo.com/u/bryan.wheeler)
#### Post date: [September 12, 2026, 10:22pm UTC](https://forum.yarbo.com/t/hotfix-update-firmware-v3-14-11-app-v3-19-5/7393/100 "2026-09-12T22:22:01Z")

</div>

Have you corrected for map drift? You shouldn’t have to remap. Map drift correction should fix this. Is your DC firmware up to date?

---

<div class="post-metadata">

### Author: ![Shanie](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.yarbo.com/shanie/32/2343_2.png) [@Shanie](https://forum.yarbo.com/u/Shanie)
#### Post date: [September 13, 2026, 1:26am UTC](https://forum.yarbo.com/t/hotfix-update-firmware-v3-14-11-app-v3-19-5/7393/101 "2026-09-13T01:26:11Z")

</div>

I’m just wondering why being in a No-Go zone for any reason doesn’t result in an EMERGENCY **STOP** order and a notification?

I think people would be more accepting to a “Yarbo has stopped because it entered a No-Go Zone” over the blades and discs getting damaged against rocks or submerged in the castle moat…

---

<div class="post-metadata">

### Author: ![bryan.wheeler](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.yarbo.com/bryan.wheeler/32/215_2.png) [@bryan.wheeler](https://forum.yarbo.com/u/bryan.wheeler)
#### Post date: [September 13, 2026, 1:30am UTC](https://forum.yarbo.com/t/hotfix-update-firmware-v3-14-11-app-v3-19-5/7393/102 "2026-09-13T01:30:01Z")

</div>

Or out of bounds…

[Previous page](https://forum.yarbo.com/t/hotfix-update-firmware-v3-14-11-app-v3-19-5/7393.md?page=4)

[Next page](https://forum.yarbo.com/t/hotfix-update-firmware-v3-14-11-app-v3-19-5/7393.md?page=6)
