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.

[mdzhigarov]

According to this page: https://www.zigbee2mqtt.io/devices/BRT-100-TRV.html the BRT-100-TRV device is supposed to support OTA updates.
However, I'm getting the following error:

Checking if update available for 'MasterBedroom TRV'
Failed to check if update available for 'MasterBedroom TRV' (No image available for imageType '5634')

The logs are showing:
2023-03-07 16:19:39MQTT publish: topic 'zigbee2mqtt/MasterBedroom TRV', payload '{"battery":88,"boost_heating":"OFF","boost_heating_countdown":0,"boost_heating_countdown_time_set":900,"child_lock":"UNLOCK","current_heating_setpoint":19,"eco_mode":"OFF","eco_temperature":20,"linkquality":92,"local_temperature":20,"local_temperature_calibration":-1,"max_temperature":25,"min_temperature":18,"position":25,"preset":"manual","programming_mode":"06:00/20°C 11:30/21°C 13:30/22°C 17:30/23°C 06:00/24°C 12:00/23°C 14:30/22°C 17:30/21°C 06:00/19°C 12:30/20°C 14:30/21°C 18:30/20°C","running_state":"idle","system_mode":"heat","update":{"installed_version":-1,"latest_version":-1,"state":"idle"},"update_available":null,"valve_state":"CLOSED","window":"CLOSED","window_detection":"ON"}'

Any suggestions?

[DarthWeber]

tried that on several TS011F Plugs, but one was interrupted by power loss. This one seems to be bricked, No reaction to button press or repeated OTA requests (not responding).

Is there any way to bring it back to life?

[titou4307]

Hello
I have the last update of Z2M 1.32.2 on my home assistant supervised (pure debian 12 on a Nuc)

Since this last update Z2M find 3 updates OTA for Legrand 412170 (DIN smart relay for light control (BTicino FC80RC ) (412170)
par Legrand )

I have succeed to pass one update on one matérial and the firmware passed to the version 0025 to the version 004e

But impossible to succeed to update the two other one....

Is there a solution to force this update process ?

Many thanks

titou43 (from France)

[pganansia]

I have exactly the same situation.
I found some posts saying that I may use the the Legrand App "Home + Control", but it means that I have to by and install a module control from Legrand.
Is there an explanation on this issue
Regards

[pganansia]

PS :
My configuration
Coordinator
20211217
Sonoff ZBDongle-P USB

Z2M
1.32.2 commit: 1ec1e57

[zen2]

@Koenkk: OTA documentation tell that update_available property is deprecated.
Is it possible to remove it since it is not in use at all ?

[felipejfc]

Is it possible to add support to DIY devices? I'm currently developing a custom device and I added the OTA cluster to it but Z2M doesn't recognize it as being OTA capable.

[pganansia]

Hi I manage to update my legrand device following this cookbook:
1- Deconnect frome Z2M and reset the device
2- Redo the connection to Z2M
3- Just after peering with Z2M, start update OTA.
Then the update start, go to the end.
Hope that will help.
Rgds

[Jizzay1]

Hi OTA issue with Sylvania (Osram) bulb. i've successfully used the OTA update on 5 of the total 6 bulbs i have. the final bulb is showing in the OTA tab with firmware that is the prior one. When i select "Check for new udpates" i get an error - "Failed to check if update available". i get the same error when checking for my other Sylvania bulbs that were previously update by OTA. what changed?

[K3vb3rt]

Hey,
yesterday I made the switch from ZHA to Zigbee2MQTT. Mostly flawless 👍🏼
Now there are several OTA updates available. For my ones devices everything went fine. But my two Philips devices won’t update. There is this log entry's with both devices:

2023-12-29 08:16:50Update of 'HuePlaybar' failed (self signed certificate in certificate chain)

Any advice on this? My coordinator is SONOFF Zigbee Gateway, ZBDongle-E 3.0 with Coordinator-Typ EZSP v12 Coordinator-Version 7.3.1.0 build 176. Running on HomeAssistant OS.

If you need any more details let me know. Thank you!

[stijn-dhondt]

Same issue here on Hue bulbs that have firmware updates ready, all on latest version.

[K3vb3rt]

Should be the same issue: #20423

[rori1977]

Hello, sorry, I am a newbie asking newbie questions here, please forgive my lack of knowledge:

The situation:
I have paired three devices, all three showing up nicely:

However, under the "OTA"-tab only two (out of three) appear... So I wonder why the 3rd device is not there?

This I find even more strange, because if I navigate to the device properties I can see the "firmware build dates" (which are not appearing in the OTA tab (see the empty column in the screenshot above)

Is this a bug or a misunderstanding on my end? Any hints appreciated. :-)

[mdworton]

Hi
I have just installed some of the Aqara H1M(ZNQBKG24LM- 1 gang, ZNQBKG25LM - 2 gang, ZNQBKG26LM- 3 gang). Previously used H1 with neutral and OTA updates working fine. With the H1M it tells me there is an update:

and also shows there is a new firmware version:

I checked the Z2M threads and the devices say they support firmware updates, and it looks like it does but when i trigger the update in about 4-5 seconds it tells me it is at 100% with remaining time always showing as N/A from start to finish. Once the device completes it says
it was updated from null to null.

I'm not sure if this is due to the devices not showing their firmware in the main screen of the OTA, or something else, but if i check the device to see if there is a new firmware again it shows on the firmware before the update and that it needs to be updated again.
Happy to help where i can to fault find this, but would need a little guidance on best steps.
Here is the log entry for the last update i tried and displaying in red:

[mdworton]

I also tried doing it from the settings screen and then returning to the OTA web screen as someone has suggested previously but still the same. Also have noticed that no firmware version showing in OTA screen for H1 or H1M devices

[zen2]

Since it is a battery powered end device. I suppose that device need to be awake in order to launch OTA update.
So the device needs probably to be actioned to be awake to be able to start OTA update.

[mdworton]

Hi Zen. These are mains devices. All have live and neutral and assume they would be awake as they are classed as routers.

[zen2]

I didn't understood correctly. I assumed H1 was neutral ones and H1M not. Sorry for the noise.

[Krewwell]

Hi everyone :)
Does anyone have problems with OTA Bticino k4003C and K4027C? When I try to start the update an error message appears "ota: timeout, device did not request any image blocks". Often the update does not start or when it does it reaches 99% and then the error message still appears.
Some advice?

[r0bb10]

works for me, see here #19509 (comment)

[NigelVanHattum]

Hi All,

During the weekend I got fed up that I was unable to update my Aqara wall switches without the Aqara hub so I thought. Why not just send a message to Aqara and ask them to open up their firmware access, looking at the amount of people within the Homey and Hass eco systems.

Here is the reply I got:

Thank you for sharing your feedback and insights with us regarding firmware updates for Aqara devices outside of our hubs.

We understand the importance of providing flexibility and compatibility with various smart home platforms, and we appreciate your >suggestion to enable firmware updates for devices used with other Zigbee platforms. Your input is invaluable as we strive to enhance >our products and meet the evolving needs of our customers.

We will certainly take your suggestion into consideration and discuss it internally to explore potential options for enabling firmware >updates outside of Aqara hubs. While we cannot guarantee immediate implementation, please rest assured that your feedback will >inform our decision-making process moving forward.

Thank you once again for taking the time to reach out to us and for your continued support of Aqara. If you have any further >questions or suggestions, please feel free to contact us.

Best regards,

Sincerely,
Caleb

[ncodee]

Anyone one know where I can find the latest changelog for the 'LYWSD03MMC' Xiaomi Thermostat? I updated to the latest version: 3001-0120 (build date: 20240211).

[Nardol]

I converted a LYWSD03MMC thermometer to Zigbee but it looks like checking for update for it fails every time because My log is full of:

warn  21/02/2024 11:09:59: OTA: Images currently unavailable for device 'LYWSD03MMC', hardwareVersion '14', manufacturerName Xiaomi, {"fieldControl":0,"manufacturerCode":56085,"imageType":515,"fileVersion":285224961}'

Should I open an issue? Or switch to dev branch?
I use Zigbee2MQTT 1.35.3.

[segaura]

Which firmware and procedure did you use?

[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.