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!
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?
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)
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.
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?
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.
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.
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.
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
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
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.
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
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.