# Allow blade height (and probably blower height) to be reflective of button taps

**URL:** <https://forum.yarbo.com/t/allow-blade-height-and-probably-blower-height-to-be-reflective-of-button-taps/6765>\
**Category:** Suggestion and Feature Requests\
**Created:** [June 30, 2026, 11:10pm UTC](https://forum.yarbo.com/t/allow-blade-height-and-probably-blower-height-to-be-reflective-of-button-taps/6765 "2026-06-30T23:10:54Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![marriott001](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.yarbo.com/marriott001/32/991_2.png) [@marriott001](https://forum.yarbo.com/u/marriott001)\
**Post date:** [June 30, 2026, 11:10pm UTC](https://forum.yarbo.com/t/allow-blade-height-and-probably-blower-height-to-be-reflective-of-button-taps/6765/1 "2026-06-30T23:10:54Z")

</div>

Noticed when you try to lower the mower height in the app, if you try to tap the button and get the value where you want it from 4 inches, it will reset after a second to reflect the current mower height. It feels a little counter intuitive this way where I think you would expect the value on the height to be reflective of each press of the button then move the deck until it reaches that value (or has an error). I’m not sure if the snow blower is the same but I would think the same logic would apply there as well.

---

<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:** [June 30, 2026, 11:40pm UTC](https://forum.yarbo.com/t/allow-blade-height-and-probably-blower-height-to-be-reflective-of-button-taps/6765/2 "2026-06-30T23:40:40Z")

</div>

I think this was a recent change. Didn’t used to behave this way.

---

<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:** [July 1, 2026, 12:09am UTC](https://forum.yarbo.com/t/allow-blade-height-and-probably-blower-height-to-be-reflective-of-button-taps/6765/3 "2026-07-01T00:09:19Z")

</div>

That’s correct and I really hope they figure something else out because it’s a bad UI experience.

---

<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:** [July 1, 2026, 12:17am UTC](https://forum.yarbo.com/t/allow-blade-height-and-probably-blower-height-to-be-reflective-of-button-taps/6765/4 "2026-07-01T00:17:19Z")

</div>

It is very frustrating when you are manually trying to move the blades up and down, it is like yarbo is fighting you.

---

<div class="post-metadata">

**Author:** ![ben.karrow](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.yarbo.com/ben.karrow/32/3989_2.png) [@ben.karrow](https://forum.yarbo.com/u/ben.karrow)\
**Post date:** [July 1, 2026, 3:04am UTC](https://forum.yarbo.com/t/allow-blade-height-and-probably-blower-height-to-be-reflective-of-button-taps/6765/5 "2026-07-01T03:04:36Z")

</div>

I just noticed that today with my testing. Bunk.

---

<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:** [July 1, 2026, 6:29am UTC](https://forum.yarbo.com/t/allow-blade-height-and-probably-blower-height-to-be-reflective-of-button-taps/6765/6 "2026-07-01T06:29:09Z")

</div>

Thanks for sharing your feedback! I’ll pass it along to our product team for consideration.

---

<div class="post-metadata">

**Author:** ![hmkb74](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.yarbo.com/hmkb74/32/3254_2.png) [@hmkb74](https://forum.yarbo.com/u/hmkb74)\
**Post date:** [July 6, 2026, 3:36am UTC](https://forum.yarbo.com/t/allow-blade-height-and-probably-blower-height-to-be-reflective-of-button-taps/6765/7 "2026-07-06T03:36:39Z")

</div>

I have noticed the same but was just happy it was working.
