# Dfu.status missing body containing length **URL:** \ **Category:** Uncategorized\ **Created:** [January 21, 2025, 10:11am UTC](https://discuss.blues.com/t/dfu-status-missing-body-containing-length/2748 "2025-01-21T10:11:36Z")\ **Posts on this page:** 14\ **Page:** 1
**Author:** ![Thareeq](https://avatars.discourse-cdn.com/v4/letter/t/f19dbf/32.png) [@Thareeq](https://discuss.blues.com/u/Thareeq)\ **Post date:** [January 21, 2025, 10:11am UTC](https://discuss.blues.com/t/dfu-status-missing-body-containing-length/2748/1 "2025-01-21T10:11:36Z")
Hi, I am working on a host device firmware update. To download the firmware to the host, I have been using the “length” keyword in the body, and it was working well. However, after experimenting with outbound firmware updates or related settings, I no longer receive the body of the message when I use “dfu.status”. On the other hand, “dfu.get” still returns the host firmware as the payload. How can I resolve this issue or reset my device to restore its previous functionality? ---
**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:** [February 6, 2025, 9:11pm UTC](https://discuss.blues.com/t/dfu-status-missing-body-containing-length/2748/2 "2025-02-06T21:11:12Z")
Hi @Thareeq and sorry for the delay in getting back to you. If the `length` argument is absent, that means the `length` is likely `0`. Are you seeing anything else in the response (like a `crc` value for instance)? ---
**Author:** ![gomario2](https://avatars.discourse-cdn.com/v4/letter/g/dfb087/32.png) [@gomario2](https://discuss.blues.com/u/gomario2)\ **Post date:** [January 10, 2026, 11:20pm UTC](https://discuss.blues.com/t/dfu-status-missing-body-containing-length/2748/3 "2026-01-10T23:20:01Z")
Hi Rob - Might be related… last week, e.g. 1/7/2026 my dfu started failing ( esp32s3 ). I figured I broke it while doing some code cleanup but after going back to my know good code dfu was still not happening. Then about 1/9 things seemed to start working again. I’m still pouring through my logs and notes but what stood out was that the notehub got to ready state , which implies the code is now on the notecard. Looking at the host mcu side esp32s3 I saw that the length was 0 and thus no download. Notecard fw: 9.2.3.17324 Thoughts ? ---
**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:** [January 15, 2026, 2:43pm UTC](https://discuss.blues.com/t/dfu-status-missing-body-containing-length/2748/4 "2026-01-15T14:43:19Z")
Hi @gomario2, Are you seeing anything else in the `body` element of the `dfu.status` request? Rob ---
**Author:** ![Renato](https://avatars.discourse-cdn.com/v4/letter/r/858c86/32.png) [@Renato](https://discuss.blues.com/u/Renato)\ **Post date:** [March 18, 2026, 2:52pm UTC](https://discuss.blues.com/t/dfu-status-missing-body-containing-length/2748/5 "2026-03-18T14:52:32Z")
Hi @RobLauer, I had a similar issue on one of my devices where after triggering DFU from notehub the `dfu.status` just switched from `{"status":"successful firmware update","mode":"completed","on":true}` to `{"status":"successfully downloaded","mode":"ready","on":true}` but as you can see the `body` field is missing and I am not sure what would be the reason. I am working with Notecard WBEXN with FW version `11.1.1.17494`. Renato ---
**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:** [March 18, 2026, 4:21pm UTC](https://discuss.blues.com/t/dfu-status-missing-body-containing-length/2748/6 "2026-03-18T16:21:00Z")
Hi @Renato, I’m curious if you supplied any version, notes, and/or metadata for this host firmware update in Notehub? Either way, is the DFU able to complete successfully for this device? Rob ---
**Author:** ![Renato](https://avatars.discourse-cdn.com/v4/letter/r/858c86/32.png) [@Renato](https://discuss.blues.com/u/Renato)\ **Post date:** [March 18, 2026, 4:28pm UTC](https://discuss.blues.com/t/dfu-status-missing-body-containing-length/2748/7 "2026-03-18T16:28:32Z")
Thank you for the quick response @RobLauer, The FW image that was triggered to be applied during DFU has all the necessary fields filled out: - Source - Notes - Metadata - MD5 Checksum - Version The DFU was already successfully applied to the device with the same FW version and then on second apply it failed with the issue I described. So the DFU was not continued from the host firmware because it didn’t get the valid `body` field in the `dfu.status` response. Because the next step is to read the image with `dfu.get`, but without image length the end size to read is unknown. I tried to replicate this issue on a different device with the same HW and FW versions, but I wasn’t able to and everything seemed to work fine. Renato ---
**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:** [March 18, 2026, 4:53pm UTC](https://discuss.blues.com/t/dfu-status-missing-body-containing-length/2748/8 "2026-03-18T16:53:30Z")
Thanks @Renato. Did the Notecard reboot (power cycle, reset, etc.) between the first successful host DFU and the second attempt? ---
**Author:** ![Renato](https://avatars.discourse-cdn.com/v4/letter/r/858c86/32.png) [@Renato](https://discuss.blues.com/u/Renato)\ **Post date:** [March 19, 2026, 9:40am UTC](https://discuss.blues.com/t/dfu-status-missing-body-containing-length/2748/9 "2026-03-19T09:40:51Z")
@RobLauer Yes, at least 2 days passed and Notecard was rebooted multiple times between the first successful host DFU and the second attempt. I tested again with Notecard power-cycle after successful update and I was able to replicate the error. If I am using Notecard incorrectly, what is your suggested way to handle this issue? Renato ---
**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:** [March 19, 2026, 4:47pm UTC](https://discuss.blues.com/t/dfu-status-missing-body-containing-length/2748/10 "2026-03-19T16:47:29Z")
Hi @Renato, Thanks for the additional info. It looks like neither of us are seeing things and this may indeed be a bug in the Notecard firmware. Our firmware engineers are looking into this now. Rob ---
**Author:** ![sidwar](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.blues.com/sidwar/32/1854_2.png) [@sidwar](https://discuss.blues.com/u/sidwar)\ **Post date:** [March 19, 2026, 9:19pm UTC](https://discuss.blues.com/t/dfu-status-missing-body-containing-length/2748/11 "2026-03-19T21:19:20Z")
Just want to +1 this issue. I am running notecard-9.3.1.17434 and I get the same response. No body or length info. I’m using the Note Carrier F v1.3 with an Adafruit ESP32 Huzzah board attached. ```auto > {"req":"dfu.status"} { "status": "successfully downloaded", "mode": "ready", "on": true } ``` ---
**Author:** ![Renato](https://avatars.discourse-cdn.com/v4/letter/r/858c86/32.png) [@Renato](https://discuss.blues.com/u/Renato)\ **Post date:** [March 31, 2026, 1:00pm UTC](https://discuss.blues.com/t/dfu-status-missing-body-containing-length/2748/12 "2026-03-31T13:00:52Z")
Hi @RobLauer , Any progress on this, or additional information for a workaround? Renato ---
**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:** [March 31, 2026, 1:14pm UTC](https://discuss.blues.com/t/dfu-status-missing-body-containing-length/2748/13 "2026-03-31T13:14:29Z")
Hi All - Sorry for the delay in my reply. It does appear this is a bug in the Notecard firmware and will be addressed in the next Developer Release. Unfortunately I don’t have a timeframe for that yet as we just released v11.2.1 a few weeks ago, but just know that is in the works. Rob ---
**Author:** ![antun](https://avatars.discourse-cdn.com/v4/letter/a/8e8cbc/32.png) [@antun](https://discuss.blues.com/u/antun)\ **Post date:** [April 7, 2026, 12:00pm UTC](https://discuss.blues.com/t/dfu-status-missing-body-containing-length/2748/14 "2026-04-07T12:00:47Z")
Hi @RobLauer , Just to confirm one more case of this issue. I had Notecard 11.1.1.17494 running and tried DFU from Notehub: ![image](https://us1.discourse-cdn.com/flex020/uploads/blues/original/2X/5/511df462947fb97f1d80064cdb9a7ab4d007a8bf.png) It stayed like above. I was investigating what blocked the process, and saw unusual response to dfu.status request: `{“status”:“successfully downloaded”,“mode”:“ready”,“on”:true}` I updated to newer Notecard firmware 11.2.1.17592, this time I get some additional error field: `notecard> {“req”:“dfu.status”}` `[09:18:43] → sending 21 bytes …` `[09:18:44] {` ` “err”: “file stat error: not found”,` ` “status”: “successfully downloaded”,` ` “mode”: “ready”,` ` “on”: true` `}` I tried to stop DFU process to see what happens, and it just switched state to completed. `notecard> {“req”:“dfu.status”,“stop”:true}` `[09:18:53] → sending 33 bytes …` `[09:18:54] {` ` “err”: “file stat error: not found”,` ` “status”: “successfully downloaded”,` ` “mode”: “ready”,` ` “on”: true` `}` `notecard> {“req”:“dfu.status”}` `[09:19:02] → sending 21 bytes …` `[09:19:02] {` ` “status”: “successful firmware update”,` ` “mode”: “completed”,` ` “pending”: true,` ` “on”: true` `}` `notecard> {“req”:“dfu.status”}` `[09:19:08] → sending 21 bytes …` `[09:19:08] {` ` “status”: “successful firmware update”,` ` “mode”: “completed”,` ` “on”: true` `}` Anyway, I did not see any body field, that would show real firmware is ready to be fetched with `dfu.get` Keep me posted for next development release. Thanks, Antun