# Bond local API error with Fanimation kute 44 fan

**URL:** <https://forum.bondhome.io/t/bond-local-api-error-with-fanimation-kute-44-fan/5035>\
**Category:** Devices\
**Created:** [October 26, 2024, 10:24pm UTC](https://forum.bondhome.io/t/bond-local-api-error-with-fanimation-kute-44-fan/5035 "2024-10-26T22:24:25Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![jeffwdoak](https://avatars.discourse-cdn.com/v4/letter/j/e274bd/32.png) [@jeffwdoak](https://forum.bondhome.io/u/jeffwdoak)\
**Post date:** [October 26, 2024, 10:24pm UTC](https://forum.bondhome.io/t/bond-local-api-error-with-fanimation-kute-44-fan/5035/1 "2024-10-26T22:24:26Z")

</div>

Hi there! I’m looking for some help with a bond bridge local API error.

I’ve set up a bond bridge to connect some fans to my home assistant. I’m able to turn lights on and off in bond bridge and home assistant. I’m able to adjust the brightness of lights in bond bridge but not in home assistant. Home Assistant gives a 500 error with message `BondScript Transmit Failed`. I’m able to reproduce that error using curl below. I’d appreciate any advice on how to further diagnose this issue. Please let me know if there’s any other info I should provide.

## API Error

```auto
❮ curl -v -H "BOND-Token: XXXXXXXXXXXXXXXX" -X PUT "http://192.168.Y.Z/v2/devices/aaaaaaaasaaaaaaa/actions/SetBrightness" -d "{\"argument\": 100}"
* Trying 192.168.Y.Z:80...
* Connected to 192.168.Y.Z (192.168.Y.Z) port 80
> PUT /v2/devices/aaaaaaaaaaaaaaaa/actions/SetBrightness HTTP/1.1
> Host: 192.168.Y.Z
> User-Agent: curl/8.4.0
> Accept: */*
> BOND-Token: XXXXXXXXXXXXXXXX
> Content-Length: 17
> Content-Type: application/x-www-form-urlencoded
>
< HTTP/1.1 500 Internal Server Error
< Connection: close
< BOND-Flags: 4
< Content-Length: 61
< Content-Type: application/json; charset=utf-8
<
{"_error_id":612,"_error_msg":"BondScript Transmit Failed"}
* Closing connection

```

## Fan info

- Fan: Fanimation kute 44
  - Reciever:
    - WFRCCD854700
    - Fccid: KUJCE10718

  - Remote:
    - TR205D
    - Fccid: KUJCE10711

  - bond bridge template: RCF94v2

- bridge info
  - model BD-1000
  - firmware v4.7.7

---

<div class="post-metadata">

**Author:** ![merck](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.bondhome.io/merck/32/1238_2.png) [@merck](https://forum.bondhome.io/u/merck)\
**Post date:** [October 27, 2024, 1:02am UTC](https://forum.bondhome.io/t/bond-local-api-error-with-fanimation-kute-44-fan/5035/2 "2024-10-27T01:02:21Z")

</div>

@jeffwdoak Nice find. This is a bug in the RCF94v2 template. I took a look here and was able to repro and fix the bug. I’ll get you a beta build shortly.

---

<div class="post-metadata">

**Author:** ![merck](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.bondhome.io/merck/32/1238_2.png) [@merck](https://forum.bondhome.io/u/merck)\
**Post date:** [October 27, 2024, 8:55pm UTC](https://forum.bondhome.io/t/bond-local-api-error-with-fanimation-kute-44-fan/5035/3 "2024-10-27T20:55:46Z")

</div>

OK @jeffwdoak, we’ve just pushed `v4.7.16-beta` firmware (update via the beta channel in the app) which should fix the error you reported. I say “should” because I don’t have the hardware in question and have therefore only tested in simulation. I would appreciate if you could confirm the fix on your end. Please scrutinize the behavior of the SetPosition on the API that it really achieves the specific % you request. You may also try using the Increase/Decrease dimming buttons on the app and see how it all works together.

Epicly clear bug report btw! Thank you for that.

---

<div class="post-metadata">

**Author:** ![jeffwdoak](https://avatars.discourse-cdn.com/v4/letter/j/e274bd/32.png) [@jeffwdoak](https://forum.bondhome.io/u/jeffwdoak)\
**Post date:** [October 30, 2024, 11:13am UTC](https://forum.bondhome.io/t/bond-local-api-error-with-fanimation-kute-44-fan/5035/4 "2024-10-30T11:13:21Z")

</div>

Thank you very much! The v4.7.16-beta build solves this issue for me. The setBrightness seems to give correct brightness percentages.

Thanks again for the quick fix!