IKEA OTA Firmware Update

smarties · November 2, 2021, 9:14pm

Hi,

i successfully configured IKEA OTA Updates within deCONZ. It works so far and almost all of my routers with permanent power are updated.

Now i notice that the battery devices are not updated. The status of SYMFONISK Sound Controller is for instance currently Idle. What does that mean?

I like to learn more about the rules and criterias how IKEA battery devices are updated? How long does it usually take until a battery devices is triggered? Is a docu or wiki available?

Is a certain battery percentage or treshhold neccessary in order that deCONZ start the update process?

I know that i am asking a lot questions but i find this topic very interesting and i really like that deCONZ offer OTA without the need of the original gateway!

Smanar · November 3, 2021, 4:35pm

I m not sure, but I think there are using the classic reporting, so if it’s that the frequency is a setting, you can see it on the GUI on the cluster “power configuration”.
Classic setting are

    rq.minInterval = 300;
    rq.maxInterval = 60 * 45;

Is a certain battery percentage or treshhold neccessary in order that deCONZ start the update process?

No, I don’t think.

The update have started I think now ?

Viking · November 3, 2021, 5:02pm

Can you explain step-by-step how you did this?

smarties · November 3, 2021, 5:31pm

If i open the Power Configuration for the Device i get the following entries
Bildschirmfoto 2021-11-03 um 18.28.37

But no entry for rq.minInterval or rq.maxInterval

What does this setting exactly do?

The devices connected to the electricity have already received the update! That works but not for the battery devices.

Smanar · November 3, 2021, 7:41pm

It seem the attribute 0x0020 don’t work so deconz use probably 0x0021
Double clic on it, then on the new windows “read config”, the previous copy/paste was from c++ code, they have better name on the GUI.
You probably need to wake up the device in same time you make the command.

Have you trie dto clic again on the “Update” button on the OTA panel ?
Can you show your OTA panel (with the device you want to update) ?

And if 21 mean 21 %, you can change the battery (almost for an update)

smarties · November 3, 2021, 9:10pm

Ok, i changed the battery and the new one has now 100% capacity.

If i click the update button again nothing happens. It looks like the device is stucking in “Idle” mode.

In Addition if i select the Basic Info Register of the device i see no values even if i hit the read button to force the device to update the register.

smarties · November 4, 2021, 9:10pm

The battery devices are still noch updated. Any other comments or ideas what can be the blocking point or how to get those devices motivated to update?

Smanar · November 5, 2021, 9:47pm

The device is sleeping, you need to wake it up.

I m searching someone that have already used it for remote. But ATM on deconz you can check logs, there is a flag just for ota.

smarties · November 5, 2021, 10:15pm

One of my two KADRILJ roller blinds is currently receiving the update. However, the transfer is very slow and takes a few hours and is not yet completed.

The log shows nothing else apart from the transmission of the data.

You said I have to wake up the battery devices. What’s the best way to do this so that they stay awake and receive the update?

Smanar · November 6, 2021, 9:33am

No it s just when you send one command, for exemple to start the update, you can just use it to wake it up.
One time it have started, better to don’t touch something.

discodogge · November 8, 2021, 6:08pm

Hi a bit late to the party but this is my experience updating several both powers and battery-powered devices.
Powers devices will handle updates by themselves, as you stated. And are quiet quick.
Battery devices will start quickly if you select firmware and press update several times while using the device for example pressing the button on a remote.
But you can only update one battery device at one time.
If the device have a fresh cr2032 battery 100% charge. it will lose roughly 30-40% power during a update.
On battery devices it goes a bit faster if you move it closer to the conbee device. But still slow. Fastest one I had was 2h but brand new installs next to Conner stick but the average is about 6h. There will be slowdowns in the network caused by all packets being transmitted and if that goes via other routers that will make other things feel slow.

smarties · November 9, 2021, 10:14pm

Thanks, this guide helped to get one SYMFONISK Controller updated. I see in deCONZ that the update is completed but the information about the new firmware version is now not displayed in Phoscon.

In general the readings of all SYMFONISK devices are not updated in deCONZ. I am running deCONZ 2.12.06

discodogge · November 10, 2021, 11:40am

Generaly i have never looked at the firmware in Phoscon as it have seemingly show a random numbber compard to deconz maby thats fixed by now. But i was ok so long its alright in deconz

Smanar · November 10, 2021, 5:12pm

Perhaps it s because the firmware number is not updated in the device JSON

smarties · November 10, 2021, 8:17pm

Ok, and what can i do to get the status?

Smanar · November 10, 2021, 10:04pm

You mean the correct firmware version ? If you have the GUI, you can just read it in the Basic cluster, it will update the JSON.

Note that after the firmware has upgraded, the deCONZ GUI (and the REST API) might still show the old values (notably the SW Build ID and Date Code). To refresh these, read the Basic cluster attributes, in the Cluster info panel in the GUI. Likewise, if the device exposes new or different endpoints and/or clusters (e.g. when upgrading from ZLL to ZigBee 3.0), refresh these by reading the Node Descriptor and Simple Descriptor(s) from the left drop-down menu on the node.

boldie · December 27, 2021, 2:18pm

I don’t get the correct firmware version even after refresh the basic cluster of my Traderfi Signal Repeater and Fyrtur roller blind. (permanent and battery power)

The OTA Upgrades were run successfully with 100% with the actual firmware build and no error appear But the old versions are still appear

I think I´m not on the new firmware. Am I ?
running latest deconz version 2.13.4 in docker

Has anybody a tip ?

Smanar · December 27, 2021, 4:57pm

You mean you still have the old one, on the GUI or in the API after updating using the GUI ?

boldie · December 27, 2021, 7:35pm

Yes in the GUI and via API (Hue Essential API Explorer)

duffbeer2000 · January 3, 2022, 3:53pm

Device: TRADFRI signal repeater
Actual Firmware: 2.3.070
Update Version: 2.3.086

I enabled the OTA Debug log, I see that at 16:38:51:871 the upload of the ota file to the devices finished and a upgrade end req is sent. At 16:41:10:734 it says that the end end request is invalide and restarts the upload. After that the same happens again and it restarts the upload…
The same behavior with the firmware upgrade I have with mit Ikea FYRTUR blinds.

16:38:51:711 Img block req fwVersion:0x23086631, offset: 0x000303A4, maxsize: 63
16:38:51:711 otau send img block rsp offset: 0x000303A4 dataSize 24 0x000D6FFFFE2FE74C
16:38:51:871 otau upgrade end req: status: 0x00, fwVersion:0x23086631, imgType: 0x1102

16:38:58:624 DeviceAnnce of LightNode: 0x000d6ffffe2fe74c Permit Join: 0

16:41:03:502 Bind response success for 0x000d6ffffe2fe74c ep: 0x01 cluster: 0x0000
16:41:03:614 ZCL configure reporting rsp seq: 221 0x000D6FFFFE2FE74C for ep: 0x01 cluster: 0x0000 attr: 0x4000 status: 0x00
16:41:10:734 otau invalide update end request for node 0x000d6ffffe2fe74c
16:41:10:735 otau query next img req: 0x000d6ffffe2fe74c mfCode: 0x117C, img type: 0x1102, sw version: 0x23070631

16:41:10:737 Match otau version 0x23086631 image type 0x1102

16:41:10:738 OTAU: /home/deconz/otau/117C-1102-23086631.zigbee: 198020 bytes
16:41:10:738 OTAU: offset 456: ota header (56 bytes)
16:41:10:757 OTAU: offset 512: tag 0x0000, length 0x0002D590 (185750 bytes)
16:41:10:757 OTAU: offset 186262: tag 0xFFBF, length 0x00000040 (70 bytes)
16:41:10:758 OTAU: offset 186332: tag 0xFFBE, length 0x00002BA2 (11176 bytes)
16:41:10:759 OTAU: offset 197508: tag 0x7035, length 0xA2DB5322 (512 bytes)
16:41:10:759 Found update file /home/deconz/otau/117C-1102-23086631.zigbee
16:41:10:761 Match otau version 0x23086631 image type 0x1102

16:41:10:762 OTAU: /opt/deCONZ/otau/117C-1102-23086631.zigbee: 198020 bytes
16:41:10:762 OTAU: offset 456: ota header (56 bytes)
16:41:10:780 OTAU: offset 512: tag 0x0000, length 0x0002D590 (185750 bytes)
16:41:10:781 OTAU: offset 186262: tag 0xFFBF, length 0x00000040 (70 bytes)
16:41:10:782 OTAU: offset 186332: tag 0xFFBE, length 0x00002BA2 (11176 bytes)
16:41:10:782 OTAU: offset 197508: tag 0x7035, length 0xA2DB5322 (512 bytes)
16:41:10:783 Found update file /opt/deCONZ/otau/117C-1102-23086631.zigbee
16:41:10:783 OTAU: /opt/deCONZ/otau/117C-1102-23086631.zigbee: 197564 bytes
16:41:10:783 OTAU: ota header (56 bytes)
16:41:10:784 OTAU: tag 0x0000, length 0x0002D590 (185750 bytes)
16:41:10:793 OTAU: tag 0xFFBF, length 0x00000040 (70 bytes)
16:41:10:794 OTAU: tag 0xFFBE, length 0x00002BA2 (11176 bytes)
16:41:10:794 OTAU: tag 0x7035, length 0xA2DB5322 (512 bytes)
16:41:10:795 OTAU: packed 1405696824 bytes

16:41:19:169 Img block req fwVersion:0x23086631, offset: 0x00000000, maxsize: 63
16:41:19:169 otau send img block rsp offset: 0x00000000 dataSize 28 0x000D6FFFFE2FE74C
16:41:19:328 Img block req fwVersion:0x23086631, offset: 0x0000001C, maxsize: 63
16:41:19:329 otau send img block rsp offset: 0x0000001C dataSize 28 0x000D6FFFFE2FE74C
16:41:19:504 Img block req fwVersion:0x23086631, offset: 0x00000038, maxsize: 63
16:41:19:504 otau send img block rsp offset: 0x00000038 dataSize 28 0x000D6FFFFE2FE74C