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.
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?
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.
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?
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 
Perhaps it s because the firmware number is not updated in the device JSON
Ok, and what can i do to get the status?
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
Has anybody a tip ?
You mean you still have the old one, on the GUI or in the API after updating using the GUI ?
Yes in the GUI and via API (Hue Essential API Explorer)
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
Same two devices I cannot update
18:49:27:797 otau upgrade end req: status: 0x00, fwVersion:0x23086631, imgType: 0x1102
18:51:45:631 0x54EF441000195801 error APSDE-DATA.confirm: 0xE1 on task
18:51:46:559 ZCL attribute report 0x001788010219D567 for cluster: 0x0001, ep: 0x02, frame control: 0x08, mfcode: 0x0000
18:51:46:635 otau invalide update end request for node 0xcc86ecfffe9fc011
18:51:46:636 otau query next img req: 0xcc86ecfffe9fc011 mfCode: 0x117C, img type: 0x1102, sw version: 0x23070631
18:51:46:639 Match otau version 0x23086631 image type 0x1102
Any updates for ikea reapter update problem?
I have also the problem, the update is in a loop.
I haven’t been able to resolve this. In the sniffer the update looks fine, but for some reason the device doesn’t pick up the new version after rebooting.
Could anybody make a test with an older version of deCONZ like v2.13.4?
Other Ikea devices seem to update fine so far in my setup.
I just downgraded to 2.13.4 (HA plug-in version 6.11.1) per @manup 's request and the behavior is the same as in 2.14.1 - it just keeps going in circles.
I just realized I originally reported the issue using 2.13.4 btw, the relevant log extract can be found here: https://github.com/dresden-elektronik/deconz-ota-plugin/issues/37
anything else I can do to help resolve this issue?