OTA updates discussion

[Koenkk]

This feature allows to OTA update your devices, documentation is available here: https://github.com/Koenkk/zigbee2mqtt.io/blob/develop/docs/information/ota_updates.md

• Requires latest zigbee2mqtt dev branch.
• Currently it's only available for IKEA TRADFRI devices, don't ask if device X can also be supported but rather search for the firmware files (if available). If they are available it could be implemented.
• No guarantees, but I don't think it's possible to brick your devices with this. The device will only start upgrading once the image is valid. So don't worry if an update fails or is interrupted.

[sjorge]

Are results only logged or is there a mqtt message also? Will update once I get home.

Also sources for other manufacturers

• Ubisys https://www.ubisys.de/en/support/firmware/
• osram/ledadvance https://update.ledvance.com/firmware-overview?submit=all https://portal.update.ledvance.com/docs/services/firmware-rest-api/operations/5d8e482edb442c3151c64fae
• Salus https://eu.salusconnect.io/demo/default/status/firmware?timestamp=0

These are all that I know of, Hue doesn’t post them and encrypt there API, Innr responded that they will not publish firmware either.

[tim-devel]

Successfully updated a tradfri bulb! 🎉🎉

Having to watch the logs on info level is a pain though. Can you add an mqtt message that confirms if an update is available or not and a couple of messages that say updated started and then update successful/unsuccessful please.

[atxbyea]

So I just upgraded to the latest dev branch to check on the tradfri ota feature, however I don't see anything in the logs when I try, running Starting zigbee2mqtt version 1.10.0-dev (commit #5e152f2) and trying to push the following to mosquitto mosquitto_pub -h 192.168.1.40 -u user -P password -t "zigbee2mqtt/bridge/ota_update/check" -m "Stue Stuebord"

[Koenkk]

There is currently a problem with the docker builds, so they don't support OTA yet.

[Koenkk]

Fixed, OTA is available on latest-dev docker now.

[copystring]

I'm currently doing an OTA. Yeah. It is really slow but ok. But waiting for it to finish I think it does make sense to log a message with the current state in % of the update lets say every 60 seconds regardless of progress.
That way I know for sure if the OTA is still running or already finished. Helps a lot when there is a lot going on like in my network with 60+ devices sending a lot of messages.

[pedrolamas]

Fixed, OTA is available on latest-dev docker now.

Fantastic!! WIll update my local docker instance and report back in a bit once it updates the 2 smart plugs I have! 😄

Salus https://eu.salusconnect.io/demo/default/status/firmware?timestamp=0

If no one does the Salus integration before, I can take a look... I have a Salus SP600 that I'm not using and will be willing to "sacrifice" it!

[way2many]

I'm trying to update a Ikea dimmer ICTC-G-1 but it fails:

info  2020-02-08 21:00:26: Checking if update available for 'Dimmer: Salon'
info  2020-02-08 21:00:27: Update available for 'Dimmer: Salon'
info  2020-02-08 21:00:27: Starting update of 'Dimmer: Salon'
info  2020-02-08 21:00:29: Update of 'Dimmer: Salon' at 0%
error 2020-02-08 21:00:38: Failed to call 'OTAUpdate' 'onMQTTMessage' (Error: Update failed with code '149'
    at fulfilled (/app/node_modules/zigbee-herdsman-converters/ota/common.js:126:24))

Device is awake. What is error code 149?

[pedrolamas]

I'm having the same issue as @way2many while trying to update my IKEA Tradfri E1603/E1702 smart plugs

Correction, it's actually a timeout error.

zigbee2mqtt:info  2020-02-08 21:04:15: Checking if update available for 'SmartPlug1'
zigbee2mqtt:error 2020-02-08 21:04:25: Failed to call 'OTAUpdate' 'onMQTTMessage' (Error: Timeout - 65430 - 1 - null - 25 - 1 after 10000ms
    at Timeout._onTimeout (/app/node_modules/zigbee-herdsman/dist/utils/waitress.js:44:24)
    at listOnTimeout (internal/timers.js:531:17)
    at processTimers (internal/timers.js:475:7))

[Koenkk]

149 = 0x95, not sure why it happens try removing power from the device for a minute and try again.

[sjorge]

I tried both my currently paired trådfri bulbs and repeated, some have no update (but have old firmware AFAIK) and some throw

zigbee2mqtt:info  2020-02-08 21:08:48: MQTT publish: topic 'zigbee2mqtt/masterbedroom/repeater', payload '{"linkquality":34}'
zigbee2mqtt:info  2020-02-08 21:09:04: Checking if update available for 'masterbedroom/repeater'
zigbee2mqtt:error 2020-02-08 21:09:14: Failed to call 'OTAUpdate' 'onMQTTMessage' (Error: Timeout - 47816 - 1 - null - 25 - 1 after 10000ms
    at Timeout.object.timer.setTimeout [as _onTimeout] (/opt/zigbee2mqtt/node_modules/zigbee-herdsman/dist/utils/waitress.js:44:24)
    at ontimeout (timers.js:425:11)
    at tryOnTimeout (timers.js:289:5)
    at listOnTimeout (timers.js:252:5)
    at Timer.processTimers (timers.js:212:10))

That error I get for my repeater and for my remotes.

[pedrolamas]

I've corrected my comment above as my error actually matches what @sjorge is getting (timeout).

I'm using pihole and a bunch of other stuff, I wonder if this is related... here's my docker configuration just in case (the volume mappings for zigbee-herdsman-converters and homeassistant-extension are currently disabled, I just haven't pushed the changes yet): https://github.com/PedroLamas/nanopineo2-docker-config/blob/master/docker-compose.yml

[sjorge]

@pedrolamas I'm not sure, I can download the json file from the url in ota/tradfri.js just fine.
And for my bulbs it reports no update.

[Koenkk]

It seems it doesn't work well for the battery powered devices yet, only for bulbs ATM.

[sjorge]

It seems it doesn't work well for the battery powered devices yet, only for bulbs ATM.

Repeater is mains power though, and I am 100% sure that one should have an update.

[jessereynolds]

Does anyone know what to do when zigbee2mqtt exits part way through a device OTA update? Is there a way to trigger it to resume?

I was updating one of my Tuya smart plugs - https://www.zigbee2mqtt.io/devices/TS011F_plug_1.html - and zigbee2mqtt exited about 10 mins into the update, the last update progress message in log:

info  2024-09-09 12:19:51: MQTT publish: topic 'zigbee2mqtt/Power Switch 2', payload '{"child_lock":"UNLOCK","current":0,"energy":169.89,"indicator_mode":"off/on","last_seen":"2024-09-09T02:19:51.615Z","linkquality":148,"power":0,"power_outage_memory":"off","state":"ON","update":{"installed_version":77,"latest_version":192,"progress":64.64,"remaining":614,"state":"updating"},"update_available":null,"voltage":232}'

and then it shuts itself down, for no apparent reason (other than the zigbee adaptor disconnected - did it crash? there was no physical disconnection):

error 2024-09-09 12:19:52: Adapter disconnected, stopping
info  2024-09-09 12:19:52: MQTT publish: topic 'zigbee2mqtt/bridge/state', payload '{"state":"offline"}'
info  2024-09-09 12:19:52: Disconnecting from MQTT server
info  2024-09-09 12:19:52: Stopping zigbee-herdsman...
error 2024-09-09 12:19:52: Failed to stop Zigbee2MQTT

docker-compose then starts it up again just fine, after which it is showing the update in progress, but it's not actually resumed the update.

Running under docker-compose on a raspberry pi model 2 B with a SkyConnect v1.0 adapter.

info  2024-09-09 12:20:27: Logging to console and directory: '/app/data/log/2024-09-09.12-20-25' filename: log.txt
info  2024-09-09 12:20:28: Starting Zigbee2MQTT version 1.35.2-dev (commit #da1d0d8)
info  2024-09-09 12:20:28: Starting zigbee-herdsman (0.33.5)
info  2024-09-09 12:20:34: zigbee-herdsman started (resumed)
info  2024-09-09 12:20:34: Coordinator firmware version: '{"meta":{"maintrel":"1 ","majorrel":"7","minorrel":"1","product":9,"revision":"7.1.1.0 build 273"},"type":"EZSP v9"}'
info  2024-09-09 12:20:34: Currently 7 devices are joined:

[jessereynolds]

Got it to resume the update after upgrading to 1.40.1 (via tag bump in docker-compose.yml) - UI then provided button to start the update, but looking at the progress it resumed at the ~64% mark. That's nice. It's now showing at latest version, 192.

[miekeandtim]

Hi

I am having the same issue but with all my Hue devices. I am using zigbee2mqtt as an addon in Home assistant.
The OTA updates are stuck for a week now. I cannot find any zigbee2mqtt updates at the moment.
Does anyone have any suggestions how to solve this?

[K3vb3rt]

For me it helped to restart Z2M Addon within HomeAssistant.

[miekeandtim]

Thank you so much! That worked.

[Aogu181]

what happend?
z2m: Update of '007P' failed (Cannot destructure property 'data' of '(intermediate value)' as it is undefined.)

[RogerSero]

Hi, I recently purchased the Sonoff SWV valve. When I added it to Z2M, an OTA update appeared. When I tried to update it, it failed. Can these types of devices be updated? Does Sonoff allow it?

Thank you.

[ikarisan]

It seems that after one of the last OTA update for my POPP 701721 the local temperature control is broken. First I thought that the rotation encoder is broken. But after replacing it I am still not able to change the target temperature locally. When rotating the knob the display lids on but the temperature does not change. Is there a way to FORCE an OTA update?

[fa4600]

Hi, there are no devices when trying to update the OTA. A clean sheet. I can't figure out what the problem might be.

[cariad61]

I have a couple of Innr SP-242 Smart Plugs on firmware version 1.6.24, and know there is OTA update available to 1.7.23.

I do have SONOFF devices listed in the OTA webpage, but the Innr SP 242's are not listed. I have no external converters.

I am running zigbee2mqtt using IOTstack and which uses docker. It reports the version as: koenkk/zigbee2mqtt:latest

Ive tried updating via the Innr app, but have no hub so this is not an option.

I initially posted this in Innr SP-242 Smart Plug not reporting status automatically #6747, but was gently adivsed that was only about the reporting issue, which is my issue but I understand this upgrade may help. Hence why I am asking here.

Before I investigate doing this manually, has anyone got any tips on how I might get these devices to show up on the OTA Z2M webpage, noting I already have two of the SONOFF temp / humidity sensors showing.

[chris-1243]

Which version of Z2M do you have ?

According to zigbee-herdsmann-converters, your device should support OTA

zigbeeModel: ['SP 242'],
model: 'SP 242',
vendor: 'Innr',
description: 'Smart plug',
extend: [
            m.onOff(),
            m.electricityMeter({current: {divisor: 1000}, voltage: {divisor: 1}, power: {divisor: 1}, energy: {divisor: 100}}),
            // Device looses reporting config on power cycle
            // https://github.com/Koenkk/zigbee-herdsman-converters/issues/6747
            m.reconfigureReportingsOnDeviceAnnounce(),
        ],
ota: true,

In order to use latest converters, you need to run latest version of Z2M. I would update Z2M then check again if OTA is available for your device. I have a bunch of INNR lights and OTA is perfectly working

[cariad61]

Where do I find which version of Z2M is installed? I have checked the log files and cant find a message.

In the install yaml file the only info I have is that above i.e.: koenkk/zigbee2mqtt:latest

Z2M is installed in a docker container via IOT stack.

I will go back and check the IOT stack documentation to see if there is info there on how to report the Z2M version.

[chris-1243]

In the frontend --> settings --> about.

As you run Z2M via docker, I suppose you are running 2.0.0 which is the latest stable version

[cariad61]

Apparently I was using version 1, whilst I still do not know how to report which version of Z2M is installed, I found out about these commands on the sensorsIOT website https://sensorsiot.github.io/IOTstack/Containers/Zigbee2MQTT/

• cd ~IOTstack

• docker-compose pull zigbee2mqtt

• docker-compose up -d zigbee2mqtt

• docker system prune

This upgraded me to version 2, latest I presume. The upgrade broke my yaml configuration, but the same site explained how to fix.

My SP242 are updating as I type is comment. Strangely my SONOFF sensors disappeared off the OTA page, but I have achieved my aim of updating the SP -242.

I would still be keen to know how to report which version. I tried without success:

• docker exec -it zigbee2mqtt ash

• /app # zigbee2mqtt --version

• ash: zigbee2mqtt: not found

[chris-1243]

As I told you, open your frontend. Go to settings and then about...

For your Sonoff devices, it seems OTA is not available for this brand in latest version of Z2M. Unless you need a firmware upgrade to solve an issue, keep in mind, those firmwares are not made for Z2M. It is better to keep working firmwares versions (even if a bit old) instead of always updating...

[cariad61]

Thank you, sorry I missed the 'settings' and 'about', all noted and understood now.

[andreivicol]

Hello. I've been developing a temperature sensor using Ti's CC2652RB MCU and testing it using Z2M. I've been working on and off for about a year on this implementation, but lately I've encountered an issue that I had resolved a long time ago. To be more specific, it seems that none of the devices I'm testing appear to support OTA updates. I find this very weird, as last year around this time I could do a 200KB ota update in about 30-40 minutes. Not only did I manage to do an update, I was doing updates reliably at speeds faster than most off the shelf devices. I've delved deeper and found some weird things, but can't seem to find a solution.

Firstly, my devices implement ota and Z2M sees the OTA cluster:

When I publish to zigbee2mqtt/bridge/request/device/ota_update/check, the response I get is:
{"data":{},"error":"Device 'ABC04S23' does not support OTA updates","status":"error"}

Z2M keeps sending this error:
z2m: EventBus error 'OTAUpdate/deviceMessage': CommandResponse 0x00124b0031e5cb7e/8 genOta.queryNextImageResponse({"status":152}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":1,"reservedBits":0,"writeUndiv":false}) failed (Data request failed with error: 'No network route' (205))

I thought that I may have broken ota through the changes I made to the firmware during the past year, but I took a firmware dated 22-04-2024 (a firmware from the commit stating fully functional ota) and flashed a device with it. The behavior is identical to my latest build.

My device has two endpoints, but ota is only implemented in one of the endpoints. Could this be an issue? There were no problems in the past it updates were working fine with only one endpoints containing the ota cluster.

Have there been any major changes concerning ota sometimes in the past year? I cannot seem to find a guide that gives a comprehensive requirements list for functional OTA updates.

Thank you.

[andreivicol]

Can anyone share some thoughts on this issue? @Koenkk

[danielbrunt57]

Data request failed with error: 'No network route' (205) would seem to be the issue and while I know a thing or two about that in an IP network, I've no idea what the issue might be in a zigbee network in relation to ota updating and whether implementing ota in only one endpoint is the cause, but It very well might be.

[andreivicol]

Hello @danielbrunt57
Thank for your reply. I've implemented OTA for the seconds endpoint as well, but there is no change. Using the UI to check all devices does not work(no devices appear in the list) and manually checking for OTA using MQTT returns the same error message that the device does not support OTA updates.

I'm still curious what might lie at the core of this problem. Have there been any changes to the way OTA updates work from Z2M's perspective? The official documentation (or, at least, the one I found) does not mention any changes made to the procedure. Would really appreciate some feedback so I can go forward with my development.

[danielbrunt57]

Sorry, I'm just not knowledgeable in this stuff

[garry0garry]

How to collect data so that Zigbee2MQTT knows firmware details?
#25124

[Bagunda]

What to do? How to roll back?
After updating the firmware of the Ikea roller blind, the device stopped working.
The buttons on the blind stopped working. The blind stopped being controlled from Z2M.
If you take out the battery and then insert it, the blind goes up to the end.
Nothing else works.
I tried to restart pairing without removing the device from Z2M. It didn't help. Although the LED blinks adequately.
I charged the battery.

The device was identified as https://www.zigbee2mqtt.io/devices/E1926.html#ikea-e1926
Zigbee manufacturer: IKEA of Sweden
Zigbee model: KADRILJ roller blind
Firmware build date: 20190311
Firmware version: 24.4.13

[I-Would-Like-To-Report-A-Bug-Please]

I'm trying to update my Aquara curtain driver firmware via OTA, however, it fails after a moment, found this in the logs:

[2025-07-17 08:44:57] info:     z2m: Updating 'SmartCurtain_Bedroom' to latest firmware
[2025-07-17 08:44:58] info:     z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/SmartCurtain_Bedroom', payload '{"battery":88,"charging":false,"device_temperature":26,"hand_open":true,"hooks_lock":"LOCK","hooks_state":"locked","illuminance":100,"last_seen":"2025-07-17T07:44:58.151Z","limits_calibration":null,"linkquality":127,"motor_state":"closing","position":56,"power_outage_count":3,"power_source":"battery","running":true,"state":"OPEN","target_position":56,"update":{"installed_version":27,"latest_version":6168,"state":"available"},"voltage":3000}'
[2025-07-17 08:44:59] info:     z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/SmartCurtain_Bedroom', payload '{"battery":88,"charging":false,"device_temperature":26,"hand_open":true,"hooks_lock":"LOCK","hooks_state":"locked","illuminance":100,"last_seen":"2025-07-17T07:44:59.140Z","limits_calibration":null,"linkquality":123,"motor_state":"closing","position":56,"power_outage_count":3,"power_source":"battery","running":true,"state":"OPEN","target_position":56,"update":{"installed_version":27,"latest_version":6168,"state":"available"},"voltage":3000}'
[2025-07-17 08:44:59] info:     zhc:ota: [0x54ef44100060dc3e | lumi.curtain.agl001] Getting latest image, meta: {"fileName":"20220506181329_lumi.curtain.agl001_Multi_JN5189_FMSH_0.0.0_2424_20220422_1aa302.ota","fileVersion":6168,"fileSize":288213,"url":"https://raw.githubusercontent.com/Koenkk/zigbee-OTA/master/images/Lumi/20220506181329_lumi.curtain.agl001_Multi_JN5189_FMSH_0.0.0_2424_20220422_1aa302.ota","imageType":4105,"manufacturerCode":4447,"sha512":"0d1bae25759420898d381b98e97858d2e47f48cd3495abd8754661d0e1957eb5b570a2ae7435acc435d5a18665409e07148abae6f1f4a190c9af786d94ec725d","otaHeaderString":"CURTAIN-OCC-JN5189---ENCRYPTED00","modelId":"lumi.curtain.agl001"}
[2025-07-17 08:46:31] info:     z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/SmartCurtain_Bedroom', payload '{"battery":88,"charging":false,"device_temperature":27,"hand_open":true,"hooks_lock":"LOCK","hooks_state":"locked","illuminance":100,"last_seen":"2025-07-17T07:46:31.958Z","limits_calibration":null,"linkquality":123,"motor_state":"closing","position":56,"power_outage_count":3,"power_source":"battery","running":true,"state":"OPEN","target_position":56,"update":{"installed_version":27,"latest_version":6168,"state":"available"},"voltage":3000}'
[2025-07-17 08:47:29] info:     z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/SmartCurtain_Bedroom', payload '{"battery":88,"charging":false,"device_temperature":27,"hand_open":true,"hooks_lock":"LOCK","hooks_state":"locked","illuminance":100,"last_seen":"2025-07-17T07:46:31.958Z","limits_calibration":null,"linkquality":123,"motor_state":"closing","position":56,"power_outage_count":3,"power_source":"battery","running":true,"state":"OPEN","target_position":56,"update":{"installed_version":27,"latest_version":6168,"state":"available"},"voltage":3000}'
[2025-07-17 08:47:29] info:     z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/bridge/response/device/ota_update/update', payload '{"data":{},"error":"Update of 'SmartCurtain_Bedroom' failed ([0x54ef44100060dc3e | lumi.curtain.agl001] Timeout. Device did not start/finish firmware download after being notified. (Timeout - 40468 - 1 - undefined - 25 - 3 after 150000ms))","status":"error","transaction":"litcl-3"}'
[2025-07-17 08:47:29] error:    z2m: Update of 'SmartCurtain_Bedroom' failed ([0x54ef44100060dc3e | lumi.curtain.agl001] Timeout. Device did not start/finish firmware download after being notified. (Timeout - 40468 - 1 - undefined - 25 - 3 after 150000ms))
[2025-07-17 08:49:25] info:     z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/bridge/health', payload '{"response_time":1752738565516,"os":{"load_average":[0.04,0.07,0.01],"memory_used_mb":323.92,"memory_percent":64.256},"process":{"uptime_sec":240014,"memory_used_mb":135.64,"memory_percent":14.9681},"mqtt":{"connected":true,"queued":0,"published":374829,"received":367},"devices":{"0xa4c1389c47f0d978":{"messages":166693,"messages_per_sec":0.6945,"leave_count":0,"network_address_changes":0},"0xa4c138210afc39b4":{"messages":1365,"messages_per_sec":0.0057,"leave_count":0,"network_address_changes":0},"0x001e5e09025a0566":{"messages":947,"messages_per_sec":0.0039,"leave_count":0,"network_address_changes":0},"0xa4c138627b4b277f":{"messages":1299,"messages_per_sec":0.0054,"leave_count":0,"network_address_changes":0},"0x001e5e09024def76":{"messages":4804,"messages_per_sec":0.02,"leave_count":0,"network_address_changes":0},"0x001e5e09024d5e39":{"messages":4487,"messages_per_sec":0.0187,"leave_count":0,"network_address_changes":0},"0x54ef44100060dc3e":{"messages":936,"messages_per_sec":0.0039,"leave_count":0,"network_address_changes":0},"0xa4c1381b865af2c3":{"messages":1397,"messages_per_sec":0.0058,"leave_count":0,"network_address_changes":0},"0xa4c13817d795923f":{"messages":284,"messages_per_sec":0.0012,"leave_count":0,"network_address_changes":0},"0xa4c13832fbbc5011":{"messages":433,"messages_per_sec":0.0018,"leave_count":0,"network_address_changes":0},"0x54ef44100060d293":{"messages":824,"messages_per_sec":0.0034,"leave_count":0,"network_address_changes":0},"0xa4c138da23087eb7":{"messages":278,"messages_per_sec":0.0012,"leave_count":0,"network_address_changes":0},"0xa4c138a4c6823d30":{"messages":301,"messages_per_sec":0.0013,"leave_count":0,"network_address_changes":0},"0x00158d000373c812":{"messages":73,"messages_per_sec":0.0003,"leave_count":0,"network_address_changes":0},"0xa4c1387de64cc6d1":{"messages":30,"messages_per_sec":0.0001,"leave_count":0,"network_address_changes":0},"0x00158d000359b015":{"messages":68,"messages_per_sec":0.0003,"leave_count":0,"network_address_changes":0},"0xa4c1381172b05e7c":{"messages":302,"messages_per_sec":0.0013,"leave_count":0,"network_address_changes":0},"0x00158d000407e81a":{"messages":76,"messages_per_sec":0.0003,"leave_count":0,"network_address_changes":0},"0x00158d0003961158":{"messages":69,"messages_per_sec":0.0003,"leave_count":0,"network_address_changes":0},"0xa4c13876a7e6a626":{"messages":159,"messages_per_sec":0.0007,"leave_count":0,"network_address_changes":0},"0xa4c13837428a1ebc":{"messages":18,"messages_per_sec":0.0001,"leave_count":0,"network_address_changes":0},"0x00158d000a836dd2":{"messages":430,"messages_per_sec":0.0018,"leave_count":0,"network_address_changes":0},"0xa4c13841bc0fbb79":{"messages":316,"messages_per_sec":0.0013,"leave_count":0,"network_address_changes":0},"0xa4c138dc5c0a67c2":{"messages":32,"messages_per_sec":0.0001,"leave_count":0,"network_address_changes":0},"0xa4c138d6a82a2186":{"messages":33,"messages_per_sec":0.0001,"leave_count":0,"network_address_changes":0},"0xa4c1385e6b9a96fb":{"messages":25,"messages_per_sec":0.0001,"leave_count":0,"network_address_changes":0},"0xa4c138b226ce65ff":{"messages":240,"messages_per_sec":0.0019,"leave_count":0,"network_address_changes":0}}}'
[2025-07-17 08:52:58] info:     z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/SmartCurtain_Bedroom', payload '{"battery":88,"charging":false,"device_temperature":27,"hand_open":true,"hooks_lock":"LOCK","hooks_state":"locked","illuminance":100,"last_seen":"2025-07-17T07:52:58.095Z","limits_calibration":null,"linkquality":123,"motor_state":"closing","position":56,"power_outage_count":3,"power_source":"battery","running":true,"state":"OPEN","target_position":56,"update":{"installed_version":27,"latest_version":6168,"state":"available"},"voltage":3000}'
[2025-07-17 08:59:18] info:     z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/SmartCurtain_Bedroom', payload '{"battery":88,"charging":false,"device_temperature":27,"hand_open":true,"hooks_lock":"LOCK","hooks_state":"locked","illuminance":100,"last_seen":"2025-07-17T07:59:18.218Z","limits_calibration":null,"linkquality":123,"motor_state":"closing","position":56,"power_outage_count":3,"power_source":"battery","running":true,"state":"OPEN","target_position":56,"update":{"installed_version":27,"latest_version":6168,"state":"available"},"voltage":3000}'
[2025-07-17 08:59:25] info:     z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/bridge/health', payload '{"response_time":1752739165520,"os":{"load_average":[0.01,0,0],"memory_used_mb":324.61,"memory_percent":64.1805},"process":{"uptime_sec":240614,"memory_used_mb":135.61,"memory_percent":14.9637},"mqtt":{"connected":true,"queued":0,"published":376101,"received":367},"devices":{"0xa4c1389c47f0d978":{"messages":167287,"messages_per_sec":0.6953,"leave_count":0,"network_address_changes":0},"0xa4c138210afc39b4":{"messages":1366,"messages_per_sec":0.0057,"leave_count":0,"network_address_changes":0},"0x001e5e09025a0566":{"messages":949,"messages_per_sec":0.0039,"leave_count":0,"network_address_changes":0},"0xa4c138627b4b277f":{"messages":1302,"messages_per_sec":0.0054,"leave_count":0,"network_address_changes":0},"0x001e5e09024def76":{"messages":4815,"messages_per_sec":0.02,"leave_count":0,"network_address_changes":0},"0x001e5e09024d5e39":{"messages":4499,"messages_per_sec":0.0187,"leave_count":0,"network_address_changes":0},"0x54ef44100060dc3e":{"messages":938,"messages_per_sec":0.0039,"leave_count":0,"network_address_changes":0},"0xa4c1381b865af2c3":{"messages":1400,"messages_per_sec":0.0058,"leave_count":0,"network_address_changes":0},"0xa4c13817d795923f":{"messages":284,"messages_per_sec":0.0012,"leave_count":0,"network_address_changes":0},"0xa4c13832fbbc5011":{"messages":433,"messages_per_sec":0.0018,"leave_count":0,"network_address_changes":0},"0x54ef44100060d293":{"messages":827,"messages_per_sec":0.0034,"leave_count":0,"network_address_changes":0},"0xa4c138da23087eb7":{"messages":278,"messages_per_sec":0.0012,"leave_count":0,"network_address_changes":0},"0xa4c138a4c6823d30":{"messages":301,"messages_per_sec":0.0013,"leave_count":0,"network_address_changes":0},"0x00158d000373c812":{"messages":74,"messages_per_sec":0.0003,"leave_count":0,"network_address_changes":0},"0xa4c1387de64cc6d1":{"messages":30,"messages_per_sec":0.0001,"leave_count":0,"network_address_changes":0},"0x00158d000359b015":{"messages":68,"messages_per_sec":0.0003,"leave_count":0,"network_address_changes":0},"0xa4c1381172b05e7c":{"messages":304,"messages_per_sec":0.0013,"leave_count":0,"network_address_changes":0},"0x00158d000407e81a":{"messages":76,"messages_per_sec":0.0003,"leave_count":0,"network_address_changes":0},"0x00158d0003961158":{"messages":69,"messages_per_sec":0.0003,"leave_count":0,"network_address_changes":0},"0xa4c13876a7e6a626":{"messages":159,"messages_per_sec":0.0007,"leave_count":0,"network_address_changes":0},"0xa4c13837428a1ebc":{"messages":18,"messages_per_sec":0.0001,"leave_count":0,"network_address_changes":0},"0x00158d000a836dd2":{"messages":430,"messages_per_sec":0.0018,"leave_count":0,"network_address_changes":0},"0xa4c13841bc0fbb79":{"messages":316,"messages_per_sec":0.0013,"leave_count":0,"network_address_changes":0},"0xa4c138dc5c0a67c2":{"messages":32,"messages_per_sec":0.0001,"leave_count":0,"network_address_changes":0},"0xa4c138d6a82a2186":{"messages":33,"messages_per_sec":0.0001,"leave_count":0,"network_address_changes":0},"0xa4c1385e6b9a96fb":{"messages":25,"messages_per_sec":0.0001,"leave_count":0,"network_address_changes":0},"0xa4c138b226ce65ff":{"messages":240,"messages_per_sec":0.0019,"leave_count":0,"network_address_changes":0}}}'
[2025-07-17 09:02:46] info:     z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/SmartCurtain_Bedroom', payload '{"battery":88,"charging":false,"device_temperature":27,"hand_open":true,"hooks_lock":"LOCK","hooks_state":"locked","illuminance":100,"last_seen":"2025-07-17T08:02:46.629Z","limits_calibration":null,"linkquality":116,"motor_state":"closing","position":56,"power_outage_count":3,"power_source":"battery","running":true,"state":"OPEN","target_position":56,"update":{"installed_version":27,"latest_version":6168,"state":"available"},"voltage":3000}'

Any idea what might be wrong? I've got two of them; however, they both behave the same way. Although one is 57% at battery, the other one is 88% (one where I took the logs for)

[benscammell]

Great work on Z2M. Thank you.

Is automatic OTA zigbee updates on the roadmap?

[Hedda]

FYI, Shelly developer hinted that they he received green light to implement native Zigbee OTA in firmware for Shelly's new Zigbee devices:

• Shelly devices custom Zigbee clusters? Does all of Shelly's Zigbee devices require support for custom Shelly clusters + non-Zigbee OTA and should all those new features be fully exposed in ZHA? zigpy/zha#470

More on that development here:

• Update for a device found but firmware was not fetched zigpy/zigpy#1713

[clscrzyc]

May I ask if the following link can be achieved using Zigbee 2mqtt for OTA in Home Assistant? For example, if the server sends the corresponding topic and payload to Zigbee 2mqtt through MQTT, will the URL in the payload be automatically downloaded from Zigbee 2mqtt? Then download the file to HA's file management and perform OTA upgrade on the Zigbee end device through the Zigbee network?

[Hedda]

Are you asking if you can use the same OTA collection repository as Zigbee2MQTT is using in Home Assistant’s built-in ZHA integration instead of Z2M? If so then the answer is yes, but the question is however off-topic here (as it has practically nothing so do with Zigbee2MQTT) and you should instead be asking questions about ZHA usage in the Home Assistant community forum instead, but FYI everything you should to achieve that is in this zigpy repo wiki here -> https://github.com/zigpy/zigpy/wiki/OTA-Device-Firmware-Updates

[clscrzyc]

Sorry，Perhaps my expression was not clear enough. What I want to know is how to use the functions based on this interface? Because it seems that I need to upload an OTA file first, and if the OTA file is recognized here, what will the interface display?

[ditheo]

I need help updating my Aqara WKS-EU03 and WKS-EU04 devices.
I have check that there is a new firmware avaiable for WKS-EU03 on the repository with file version 25 and date 25/07/2024 but my devices are on file version 2839 and date 11/10/2021. On the OTA section of z2m I can check for ota updates but it fails to show the new version. I don't how file version is checked but i think if this is check by the number (ver.2839 vs ver.25) maybe this is the reason.

Also I cannot see my WKS-EU04 devices on the OTA section although there is the same OTA update on the repository, (maybe there is no ota.update definition at the converters defitions for this device?)
Could help me?