# Bridge Firmware v2.11.2: Increase/DecreaseSpeed Fix

**URL:** <https://forum.bondhome.io/t/bridge-firmware-v2-11-2-increase-decreasespeed-fix/1383>\
**Category:** BETA\
**Created:** [March 20, 2020, 6:50pm UTC](https://forum.bondhome.io/t/bridge-firmware-v2-11-2-increase-decreasespeed-fix/1383 "2020-03-20T18:50:52Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![jacob](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.bondhome.io/jacob/32/312_2.png) [@jacob](https://forum.bondhome.io/u/jacob)\
**Post date:** [March 20, 2020, 6:50pm UTC](https://forum.bondhome.io/t/bridge-firmware-v2-11-2-increase-decreasespeed-fix/1383/1 "2020-03-20T18:50:52Z")

</div>

Hey all, just released v2.11.2 to Beta for Bond Bridges.

This version has a fix for the Increase & Decrease Speed actions, which were broken in a recent update. As we go, we’re adding more and more firmware tests to ensure that these API breaks are caught before release.

---

<div class="post-metadata">

**Author:** ![kingwr](https://avatars.discourse-cdn.com/v4/letter/k/ecc23a/32.png) [@kingwr](https://forum.bondhome.io/u/kingwr)\
**Post date:** [March 21, 2020, 4:15pm UTC](https://forum.bondhome.io/t/bridge-firmware-v2-11-2-increase-decreasespeed-fix/1383/2 "2020-03-21T16:15:08Z")

</div>

So dumb question, but is the way to load beta firmware just through REST calls to the API?

---

<div class="post-metadata">

**Author:** ![jacob](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.bondhome.io/jacob/32/312_2.png) [@jacob](https://forum.bondhome.io/u/jacob)\
**Post date:** [March 21, 2020, 4:22pm UTC](https://forum.bondhome.io/t/bridge-firmware-v2-11-2-increase-decreasespeed-fix/1383/3 "2020-03-21T16:22:08Z")

</div>

There is, you need to know the URL of the beta firmware and some metadata about it for validation though. I can put together a request for you, but if you’ve got Python 3 on your machine I’ve got a quick solution for you:

`pip install bond-cli`  
`bond discover`  
`bond select {Bond ID}`  
`bond upgrade --release beta`

If you don’t already have Python (or maybe you have Python 2? I really should get it working for older versions), let me know and I’ll throw together a request for you.

---

<div class="post-metadata">

**Author:** ![kingwr](https://avatars.discourse-cdn.com/v4/letter/k/ecc23a/32.png) [@kingwr](https://forum.bondhome.io/u/kingwr)\
**Post date:** [March 21, 2020, 4:31pm UTC](https://forum.bondhome.io/t/bridge-firmware-v2-11-2-increase-decreasespeed-fix/1383/4 "2020-03-21T16:31:56Z")

</div>

Exactly what I need. However, I get this upon upgrade:

> f:\Python37\Scripts\>python bond upgrade --release beta  
> Connecting to BOND…  
> Detected Target: zermatt  
> Selected Branch: beta-zermatt  
> Current Version: v2.10.21  
> Installing Version: v2.11.2-beta  
> Are you sure? [N/y] y  
> Requesting upgrade…  
> Traceback (most recent call last):  
> File “bond”, line 7, in   
> app.run()  
> File “F:\Python37\lib\site-packages\bond\app.py”, line 22, in run  
> bond.cli.execute\_from\_command\_line(sys.argv)  
> File “F:\Python37\lib\site-packages\bond\cli\main.py”, line 28, in execute\_from\_command\_line  
> args.func(args)  
> File “F:\Python37\lib\site-packages\bond\commands\upgrade.py”, line 137, in run  
> do\_upgrade(bondid, version\_obj)  
> File “F:\Python37\lib\site-packages\bond\commands\upgrade.py”, line 45, in do\_upgrade  
> progress = rsp[“b”][“progress”]  
> TypeError: ‘NoneType’ object is not subscriptable`

---

<div class="post-metadata">

**Author:** ![jacob](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.bondhome.io/jacob/32/312_2.png) [@jacob](https://forum.bondhome.io/u/jacob)\
**Post date:** [March 21, 2020, 4:40pm UTC](https://forum.bondhome.io/t/bridge-firmware-v2-11-2-increase-decreasespeed-fix/1383/5 "2020-03-21T16:40:33Z")

</div>

Ouch, okay, I’ll put some more work into it. For now, the endpoint to hit is

`PUT /v2/sys/upgrade`

with the body

> {“path”: “/bond-updates/v2/zermatt/beta-zermatt/zermatt.v2.11.2-beta.app.bin”, “host”: “[s3.amazonaws.com](http://s3.amazonaws.com)”, “http\_port”: “80”, “version”: “v2.11.2-beta”, “sig”: “”, “info”: “b485b129f252fe3724b65385e0268f846f7f6ce4e00737c9c8590be96d8b6315:zermatt:v2.11.2-beta”, “port”: “443”, “reboot”: 1}

The last key/value will make the Bond reboot into the new firmware automatically.

(Documented [here](http://docs-local.appbond.com/#tag/Upgrade/paths/~1v2~1sys~1upgrade/put))

---

<div class="post-metadata">

**Author:** ![jacob](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.bondhome.io/jacob/32/312_2.png) [@jacob](https://forum.bondhome.io/u/jacob)\
**Post date:** [March 23, 2020, 7:44pm UTC](https://forum.bondhome.io/t/bridge-firmware-v2-11-2-increase-decreasespeed-fix/1383/6 "2020-03-23T19:44:39Z")

</div>

I found that the bond-cli problem is due to the token not being set! `bond select {id}` only gets the token if it’s unlocked (that is, shortly after a boot or after you unlock it via the API)

I’m going to make this clear in the output of `bond select`. There’s also a `bond token` command that lets you manually set the token.

---

<div class="post-metadata">

**Author:** ![kingwr](https://avatars.discourse-cdn.com/v4/letter/k/ecc23a/32.png) [@kingwr](https://forum.bondhome.io/u/kingwr)\
**Post date:** [March 23, 2020, 9:45pm UTC](https://forum.bondhome.io/t/bridge-firmware-v2-11-2-increase-decreasespeed-fix/1383/7 "2020-03-23T21:45:20Z")

</div>

Great! Thanks. I will bookmark this for future beta upgrades. The 2.11.2 is working well for my integration.
