# Note.add "err" response

**URL:** <https://discuss.blues.com/t/note-add-err-response/948>\
**Category:** Notecard API\
**Created:** [August 23, 2022, 10:46pm UTC](https://discuss.blues.com/t/note-add-err-response/948 "2022-08-23T22:46:41Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Karl\_iWell](https://avatars.discourse-cdn.com/v4/letter/k/7feea3/32.png) [@Karl\_iWell](https://discuss.blues.com/u/Karl_iWell)\
**Post date:** [August 23, 2022, 10:46pm UTC](https://discuss.blues.com/t/note-add-err-response/948/1 "2022-08-23T22:46:41Z")

</div>

1. note.add generates an err, but this is no document in the on-line manual on an error response. Here is the JSON:

```auto
> {"req":"note.add","file":"sensors.qo","body":{"temp":23.6,"battery":195.6,"CL1":0.2,"CL2":-0.1,"CL3":0.1,"CL4":0 },"sync":true}
{"err":"notecard DFU in progress {dfu-in-progress}"}

```

Any documentation available on other err responses in note.add or any other undocumented responses?

---

<div class="post-metadata">

**Author:** ![RobLauer](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.blues.com/roblauer/32/1567_2.png) [@RobLauer](https://discuss.blues.com/u/RobLauer)\
**Post date:** [August 24, 2022, 12:53pm UTC](https://discuss.blues.com/t/note-add-err-response/948/2 "2022-08-24T12:53:25Z")

</div>

Hi @Karl_iWell,

It looks like your Notecard is in the process of performing a firmware upgrade. You can check on the status of the DFU process in Notehub on the **Devices → Notecard Firmware** tab. You can also use the [dfu.status](https://dev.blues.io/reference/notecard-api/dfu-requests/#dfu-status) API locally to check the status (e.g. “mode” should be “idle” in the response):

```auto
{
  "req": "dfu.status",
  "name": "card"
}

```

Once DFU is complete, your `note.add` request should work just fine.

Rob

---

<div class="post-metadata">

**Author:** ![Karl\_iWell](https://avatars.discourse-cdn.com/v4/letter/k/7feea3/32.png) [@Karl\_iWell](https://discuss.blues.com/u/Karl_iWell)\
**Post date:** [August 24, 2022, 8:31pm UTC](https://discuss.blues.com/t/note-add-err-response/948/3 "2022-08-24T20:31:19Z")

</div>

Thanks Rob,

I understood the cause of the err, I was more interested in why err was not documented as a response.

In general, is err an acceptable response to any notecard request or just to some requests.

I appreciate your prompt response to the original post.

Karl

---

<div class="post-metadata">

**Author:** ![Carl-Henderson](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.blues.com/carl-henderson/32/587_2.png) [@Carl-Henderson](https://discuss.blues.com/u/Carl-Henderson)\
**Post date:** [August 24, 2022, 11:46pm UTC](https://discuss.blues.com/t/note-add-err-response/948/4 "2022-08-24T23:46:16Z")

</div>

Karl,

You’re right, any notecard request might be met with a response with an `err` field. Some other general rules about our API can be found [here](https://dev.blues.io/notecard/notecard-walkthrough/notecard-requests-and-responses/). One of the most interesting things to know about the `err` responses is that if you want to programmatically detect a certain error you should look for the special codes that look like `{code}`. Here’s a [list of many of those codes](https://dev.blues.io/notecard/notecard-walkthrough/notecard-error-and-status-codes/) but this list is not exhaustive.

-Carl

---

<div class="post-metadata">

**Author:** ![Karl\_iWell](https://avatars.discourse-cdn.com/v4/letter/k/7feea3/32.png) [@Karl\_iWell](https://discuss.blues.com/u/Karl_iWell)\
**Post date:** [August 25, 2022, 5:38pm UTC](https://discuss.blues.com/t/note-add-err-response/948/5 "2022-08-25T17:38:33Z")

</div>

Thanks Carl, I appreciate it.

Karl