# Upcoming Update: Firmware V3.13.0 & App V3.18.1

**URL:** <https://forum.yarbo.com/t/upcoming-update-firmware-v3-13-0-app-v3-18-1/5763>\
**Category:** Updates & Product Releases\
**Created:** [April 9, 2026, 1:30pm UTC](https://forum.yarbo.com/t/upcoming-update-firmware-v3-13-0-app-v3-18-1/5763 "2026-04-09T13:30:16Z")\
**Posts on this page:** 20\
**Page:** 2

<div class="post-metadata">

**Author:** ![Don-Yarbo](https://avatars.discourse-cdn.com/v4/letter/d/7c8e57/32.png) [@Don-Yarbo](https://forum.yarbo.com/u/Don-Yarbo)\
**Post date:** [April 10, 2026, 4:49pm UTC](https://forum.yarbo.com/t/upcoming-update-firmware-v3-13-0-app-v3-18-1/5763/21 "2026-04-10T16:49:10Z")

</div>

Wait, so WIFI can be turned off on the rover? will that help eliminate any noise?

---

<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:** [April 10, 2026, 5:27pm UTC](https://forum.yarbo.com/t/upcoming-update-firmware-v3-13-0-app-v3-18-1/5763/22 "2026-04-10T17:27:58Z")

</div>

Yes, you don’t need your home WiFi on the core at all if everything is functioning properly. HaLow for primary, turn on cellular for backup just in case. As for noise, can you elaborate on what issue you are having?

---

<div class="post-metadata">

**Author:** ![steve](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.yarbo.com/steve/32/816_2.png) [@steve](https://forum.yarbo.com/u/steve)\
**Post date:** [April 10, 2026, 9:33pm UTC](https://forum.yarbo.com/t/upcoming-update-firmware-v3-13-0-app-v3-18-1/5763/23 "2026-04-10T21:33:48Z")

</div>

\*\*

# Outstanding!

\*\*

> [@Yarbo-Forum](#):
>
> Follow Me Mode now supports **background operation** ,

> [@Yarbo-Forum](#):
>
> Added a **toggle for perimeter mowing laps**

> [@Yarbo-Forum](#):
>
> Fixed an issue where Yarbo could enter sidewalks rear-first

> [@Yarbo-Forum](#):
>
> Added **NetRTK service integration**

> [@Yarbo-Forum](#):
>
> Added a **Pathway Offset feature**

> [@Yarbo-Forum](#):
>
> Added **Path Offset** ,

> [@Yarbo-Forum](#):
>
> Added an **offset option for Work Twice**

> [@Yarbo-Forum](#):
>
> Added **Light Snow and Heavy Snow modes** , along with **Perimeter Blowing Laps**

> [@Yarbo-Forum](#):
>
> Refined the Yarbo Settings layout

> [@Yarbo-Forum](#):
>
> Enhanced PPVS functionality and UI by introducing global and per-area settings,

---

<div class="post-metadata">

**Author:** ![jules](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.yarbo.com/jules/32/340_2.png) [@jules](https://forum.yarbo.com/u/jules)\
**Post date:** [April 12, 2026, 2:47am UTC](https://forum.yarbo.com/t/upcoming-update-firmware-v3-13-0-app-v3-18-1/5763/24 "2026-04-12T02:47:15Z")

</div>

![IMG_6960](https://canada1.discourse-cdn.com/flex007/uploads/yarbo/original/2X/a/a4d3228138e886620187eac9c991bbeef15666a6.jpeg)

 ![IMG_6962](https://canada1.discourse-cdn.com/flex007/uploads/yarbo/original/2X/e/e476eab3c6b9e924101d8fa0b39d0282aea74abf.jpeg)

 ![IMG_6961](https://canada1.discourse-cdn.com/flex007/uploads/yarbo/original/2X/7/75b617fdbd6623e8e700524e654e4fadc0232e8c.jpeg)

---

<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:** [April 12, 2026, 2:49am UTC](https://forum.yarbo.com/t/upcoming-update-firmware-v3-13-0-app-v3-18-1/5763/25 "2026-04-12T02:49:47Z")

</div>

There is a problem with your data center. RTK status is 1 and HaLow is false. Have you tried unplugging the DC power and core battery for 5 mins and then plugging in the DC followed by the core?

---

<div class="post-metadata">

**Author:** ![kinglerch](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.yarbo.com/kinglerch/32/489_2.png) [@kinglerch](https://forum.yarbo.com/u/kinglerch)\
**Post date:** [April 12, 2026, 12:31pm UTC](https://forum.yarbo.com/t/upcoming-update-firmware-v3-13-0-app-v3-18-1/5763/26 "2026-04-12T12:31:07Z")

</div>

> [@B-Mod](#):
>
> What sucks is yarbo finally makes potential improvements to the snowblower AFTER the season is over. Maybe instead of working on 15 things at once, try to improve the issues that are currently being used and are needed to function better.

The most common firmware complaints:

- Yarbo made changes _after_ the season that doesn’t help last season
- Yarbo made changes _during_ the season when it was working fine

---

<div class="post-metadata">

**Author:** ![B-Mod](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.yarbo.com/b-mod/32/292_2.png) [@B-Mod](https://forum.yarbo.com/u/B-Mod)\
**Post date:** [April 12, 2026, 2:44pm UTC](https://forum.yarbo.com/t/upcoming-update-firmware-v3-13-0-app-v3-18-1/5763/27 "2026-04-12T14:44:41Z")

</div>

After is worse, can’t test till next year, and then if it sucks you are stuck with it all season, then the next fix comes after the season is done, put on repeat, nothing gets done timely.

If they did small changes and more frequently things would improve faster.

---

<div class="post-metadata">

**Author:** ![ken.w.gregory](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.yarbo.com/ken.w.gregory/32/922_2.png) [@ken.w.gregory](https://forum.yarbo.com/u/ken.w.gregory)\
**Post date:** [April 12, 2026, 3:12pm UTC](https://forum.yarbo.com/t/upcoming-update-firmware-v3-13-0-app-v3-18-1/5763/28 "2026-04-12T15:12:14Z")

</div>

Smaller changes more frequently is the way in my opinion.

---

<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:** [April 12, 2026, 4:04pm UTC](https://forum.yarbo.com/t/upcoming-update-firmware-v3-13-0-app-v3-18-1/5763/29 "2026-04-12T16:04:28Z")

</div>

Yes, constant iterative bug fixes and less frequent major releases. Bug fixes need to be decoupled from the major releases. I think they need a public beta test program too for things that roll out of closed beta testing to roll into next. Something as simple as Apple does it, toggle on the public beta if you want it and toggle it off if you don’t. Rolling updates wouldn’t be needed then IMHO. After 2 weeks of public beta without big issues, ship it to all. Those who have automatic updates enabled (this should be a toggle) it will auto install at the time and day specified by the end user. No unpredictable updates time/day. Otherwise it will inform the user there is an update available when they open the app and they can choose whether or not to install it. If they say no, they should be able to go back into the app and check for updates and install at any time. Not have to wait for the next update or contact support. The app needs to be fully backwards compatible through a couple of firmware versions.

---

<div class="post-metadata">

**Author:** ![s.moz](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.yarbo.com/s.moz/32/519_2.png) [@s.moz](https://forum.yarbo.com/u/s.moz)\
**Post date:** [April 12, 2026, 4:48pm UTC](https://forum.yarbo.com/t/upcoming-update-firmware-v3-13-0-app-v3-18-1/5763/30 "2026-04-12T16:48:42Z")

</div>

I’ve been a beta tester for Apple’s software for some time and can agree that it’s a good system. For me, I don’t mind the bugs in exchange for early access to new features, but others I know just want something simple that works every time, and have no interest in beta testing.

---

<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:** [April 12, 2026, 5:04pm UTC](https://forum.yarbo.com/t/upcoming-update-firmware-v3-13-0-app-v3-18-1/5763/31 "2026-04-12T17:04:19Z")

</div>

Agree, Agree, Agree, we can’t continue to wait an entire to season to get minor issues fixed. In many cases they’re items that were broken in a previous release. I can think several of from last year that still aren’t fixed - not new features, but bugs that have simply not been addressed.

---

<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:** [April 12, 2026, 5:13pm UTC](https://forum.yarbo.com/t/upcoming-update-firmware-v3-13-0-app-v3-18-1/5763/32 "2026-04-12T17:13:23Z")

</div>

Remembering how many times this was mentioned last year, I ran out of fingers.

---

<div class="post-metadata">

**Author:** ![rgloverii](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.yarbo.com/rgloverii/32/956_2.png) [@rgloverii](https://forum.yarbo.com/u/rgloverii)\
**Post date:** [April 12, 2026, 5:34pm UTC](https://forum.yarbo.com/t/upcoming-update-firmware-v3-13-0-app-v3-18-1/5763/33 "2026-04-12T17:34:35Z")

</div>

Agree with all of the above.

Yarbo needs two dev paths. One for major new feature releases, and another for quick bug fixes.

The current process of taking an entire season to release an update is harmful in that the update doesn’t appear until the season is almost over, and as a result, no one can test and provide feedback for the updates until the next year when the season begins again. If the update wasn’t ideal, it will then take another YEAR before another fix can be received by the end users. Dev cycle is simply too long.

---

<div class="post-metadata">

**Author:** ![JNS](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.yarbo.com/jns/32/3015_2.png) [@JNS](https://forum.yarbo.com/u/JNS)\
**Post date:** [April 12, 2026, 7:48pm UTC](https://forum.yarbo.com/t/upcoming-update-firmware-v3-13-0-app-v3-18-1/5763/34 "2026-04-12T19:48:05Z")

</div>

Agree with all of that. I would also recommend doing a roll back option for all updates.

---

<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:** [April 12, 2026, 7:52pm UTC](https://forum.yarbo.com/t/upcoming-update-firmware-v3-13-0-app-v3-18-1/5763/35 "2026-04-12T19:52:15Z")

</div>

> [@Bug Fix Updates and Feature Version Updates decoupled](https://forum.yarbo.com/t/bug-fix-updates-and-feature-version-updates-decoupled/5795):
>
> Bug fixes need to be decoupled from major version updates. There should be constant iterative bug fixes and less frequent major releases. This should apply to app and firmwares. These are the minor point release updates like App version 3.18.1 to 3.18.2 and firmware version 3.13.0 to 3.13.3. These would be “hot fix” releases and should be streamlined through the internal testing processes as there shouldn’t be any sweeping code changes, only targeted and specific bug fixes that are being add…

Everyone who agrees, please click the link above and vote on that feature request.

---

<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:** [April 12, 2026, 10:50pm UTC](https://forum.yarbo.com/t/upcoming-update-firmware-v3-13-0-app-v3-18-1/5763/36 "2026-04-12T22:50:41Z")

</div>

Can’t keep doing the same thing and expect different results.

---

<div class="post-metadata">

**Author:** ![jules](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.yarbo.com/jules/32/340_2.png) [@jules](https://forum.yarbo.com/u/jules)\
**Post date:** [April 13, 2026, 6:35am UTC](https://forum.yarbo.com/t/upcoming-update-firmware-v3-13-0-app-v3-18-1/5763/37 "2026-04-13T06:35:06Z")

</div>

I did all that - it’s working again!  
Thank you Bryan.

---

<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:** [April 13, 2026, 12:45pm UTC](https://forum.yarbo.com/t/upcoming-update-firmware-v3-13-0-app-v3-18-1/5763/38 "2026-04-13T12:45:26Z")

</div>

Awesome, glad to hear it!

---

<div class="post-metadata">

**Author:** ![abtaft](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.yarbo.com/abtaft/32/520_2.png) [@abtaft](https://forum.yarbo.com/u/abtaft)\
**Post date:** [April 14, 2026, 10:08am UTC](https://forum.yarbo.com/t/upcoming-update-firmware-v3-13-0-app-v3-18-1/5763/39 "2026-04-14T10:08:57Z")

</div>

I don’t see, in the new app, where the new pathway offset can be managed. Does this need the new firmware to show up?

---

<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:** [April 14, 2026, 10:17am UTC](https://forum.yarbo.com/t/upcoming-update-firmware-v3-13-0-app-v3-18-1/5763/40 "2026-04-14T10:17:21Z")

</div>

Welcome to the community. Yes. I think so.

[Previous page](https://forum.yarbo.com/t/upcoming-update-firmware-v3-13-0-app-v3-18-1/5763.md?page=1)

[Next page](https://forum.yarbo.com/t/upcoming-update-firmware-v3-13-0-app-v3-18-1/5763.md?page=3)
