Generate OTA file

RE: Generate OTA file

Nagajans — Fri, 14 Nov 2025 08:30:22 GMT

its working now. issue was myindex.json syntax error. Thank you very much for your support.

RE: Generate OTA file

Huong Nguyen — Fri, 14 Nov 2025 06:34:32 GMT

Did you read this post https://smarthomescene.com/guides/how-to-setup-zigbee2mqtt-local-ota-index/ ?

RE: Generate OTA file

Nagajans — Fri, 14 Nov 2025 05:44:08 GMT

I was able to get the update button and set force to true, but when I click the update button, I receive the following error message.

configuration.yaml

mqtt:
base_topic: zigbee2mqtt
server: mqtt://localhost:1883
ota:
update_check_interval: 1440
disable_automatic_update_check: false
image_block_response_delay: 250
default_maximum_data_size: 50
ota_base_url: http://localhost:8081/
zigbee_ota_override_index_location: my_index.json
zigbee_ota: true

external converter
[
{
"url": "http://localhost:8081/127F-0141-02000000-Dimable_Light_v01.zigbee",
"force": true
}
]

RE: Generate OTA file

Huong Nguyen — Fri, 14 Nov 2025 00:57:31 GMT

You must check the version of the .zigbee again

RE: Generate OTA file

Nagajans — Thu, 13 Nov 2025 15:01:28 GMT

When I perform a “Check for update” action, I receive an “OK” response, but the “Firmware Update” button does not appear. Please help me resolve this issue.

RE: Generate OTA file

Huong Nguyen — Thu, 13 Nov 2025 11:08:58 GMT

The file within .zigbee is ok. But the model ID in zboss must match the model in z2m

For example: 127F-0141-02000000-Dimable_Light_v01.zigbee

RE: Generate OTA file

Nagajans — Thu, 13 Nov 2025 10:07:57 GMT

Thanks for the information. I can now see the device listed under the OTA tab, but when I try to trigger an update through MQTT Explorer, I get the following error:

I’ve placed the file 127F-0141-02000000-light_bulb.zigbee in my MQTT local server directory. Do I need to use a .ota file instead, or is the .zigbee format acceptable?

RE: Generate OTA file

Huong Nguyen — Thu, 13 Nov 2025 07:19:39 GMT

You should add this code into the external converter

    ota: {
        ota: true,
        isUpdateAvailable: async (device, logger, data) => {
            return ota.isUpdateAvailable(device, logger, data, 'your_ota_index.json');
        },
        updateDevice: async (device, logger, data, onProgress) => {
            logger.info(`Starting FOTA update for ${device.ieeeAddr}...`);
            return ota.updateToLatest(device, logger, data, onProgress, 'your_ota_index.json');
        },
    },

RE: Generate OTA file

Nagajans — Thu, 13 Nov 2025 07:10:40 GMT

I’ve been experimenting with Zigbee2MQTT and the nRF52840 board to perform OTA updates, but I haven’t been successful so far. I created a custom external converter for the nRF52840, added it as a supported device, and generated the my_index.json file — however, the OTA update still doesn’t work. I’ve attached all the necessary details. I created 127F-0141-02000000-light_bulb.zigbee file but this file is not visible in Zigbee2Mqtt OTA firmware update page. please help me troubleshoot this issue.

External converter

import * as m from 'zigbee-herdsman-converters/lib/modernExtend';

console.log(">>> Loading external converter for Dimable_Light_v01");

export default {
zigbeeModel: ["Dimable_Light_v01"],
model: "Dimable_Light_v01",
vendor: "Nordic",
description: "Automatically generated definition",
extend: [m.deviceEndpoints({"endpoints":{"5":5,"10":10}}), m.light()],
meta: {"multiEndpoint":true},
};

my_index.json
[
{
"url": "/ota/127F-0141-02000000-light_bulb.zigbee",
"imageType": 321,
"manufactureCode": 4735,
"fileVersion": 16777216,
"force": true
}
]

configuration.yaml
version: 4
mqtt:
base_topic: zigbee2mqtt
server: mqtt://localhost:1883
serial:
port: COM18
adapter: zboss
baudrate: 115200
rtscts: false
external_converters:
- >-
C:/Users/nagarajan.m/Downloads/zigbee2mqtt-master/zigbee2mqtt-master/data/external_converters/Dimable_Light_v01.mjs
advanced:
log_level: info
channel: 16
network_key:
- 192
- 99
- 61
- 57
- 226
- 129
- 254
- 190
- 202
- 191
- 105
- 202
- 14
- 55
- 40
- 50
pan_id: 23150
ext_pan_id:
- 71
- 227
- 191
- 250
- 103
- 23
- 180
- 99
frontend:
enabled: true
port: 8080
homeassistant:
enabled: false
ota:
update_check_interval: 1440
disable_automatic_update_check: false
image_block_response_delay: 250
default_maximum_data_size: 50
ota_base_url: http://localhost:8081/
zigbee_ota_override_index_location: data/my_index.json
zigbee_ota: true
devices:
'0xf4ce366c68e5776c':
friendly_name: Nordic_Light_Bulb

RE: Generate OTA file

Huong Nguyen — Thu, 13 Nov 2025 04:39:52 GMT

What is your problem?

RE: Generate OTA file

Nagajans — Fri, 07 Nov 2025 09:48:00 GMT

Hi alyssiarosewhite,
I've been experimenting with Zigbee2MQTT but haven’t had any success with OTA updates. Could you please share what changes you made to get OTA working on your Nordic board?

RE: Generate OTA file

Edvin — Wed, 05 Jun 2024 09:17:14 GMT

Hello,

Wow, that,s actually really cool! I guess the DFU protocol for Zigbee is standardized, so it kind of makes sense, but I wouldn't expect it to work so easily out of the box.

Thanks for sharing!

Best regards,

Edvin

RE: Generate OTA file

alyssiarosewhite — Tue, 04 Jun 2024 12:41:35 GMT

Hi Edvin,

I've been playing around today and it looks like Z2M does successfully update my board. I found that building my project also gave me a *.zigbee image which I uploaded to Home Assistant and I was able to successfully update my board from the Z2M add-on.

Thank you very much for your help.

RE: Generate OTA file

Edvin — Mon, 03 Jun 2024 13:28:23 GMT

I see. Z2M is not something that we support directly, but I believe we have other users (perhaps you, included), who has tried before. Not sure of the outcome, though. Also, not sure if anyone have (successfully) tried FOTA using Z2M.

The app_update.bin is at least the binary format of the application. You should also find something like merged.hex in there, which is the .hex representation. What I am not sure of, however, is how the transport would work in Z2M. By default it is expected to use it's own Zigbee cluster for transporting the new image, when you are using MCUBOOT. Not sure how this is done in Z2M.

Best regards,

Edvin

RE: Generate OTA file

alyssiarosewhite — Mon, 03 Jun 2024 08:25:21 GMT

Hi Edvin,

I'm using MCUBoot and v2.5.2 of the SDK.

I found app_update.bin Thursday evening after submitting this ticket and was wondering if that would be it.

Yes, ZigBee2MQTT is a Home Assistant thing. I've been pulling my hair out trying to figure out how to do both the NRF side of things and the Z2M side of things.

I'll give this all another read with fresh Monday eyes and report back.

Thank you

RE: Generate OTA file

Edvin — Fri, 31 May 2024 12:38:48 GMT

Hello,

What kind of bootloader do you have? And what SDK version are you using? Based on your other tickets, it looks like you are using NCS. So if you have added a bootloader to your application, then your build folder should include the ota file.

The file is located in build\zephyr\dfu_update.zip, and is called app_update.bin.

However, this bootloader is not tailored for Zigbee, so where you would typically use something called mcumgr for performing the FOTA via bluetooth or serial, mcumgr doesn't do zigbee. As you can see here, we are currently using a tool called nrfutil to generate the ota image.

What I am not sure of, however, is how to transfer this file over ZigBee2MQTT (Z2M). Is this some sort of Home Assistance thing, by chance? In our guides, we use nrfutil with an additional DK to transfer the image to the OTA target, but I am not sure whether this will work with Z2M. You will have to test that.

Best regards,

Edvin