First thanks a lot for sharing the detailed instruction! This is something I’ve been looking for for quite some time!
But, hmmm… I’m not sure how it works in real life… I followed your instructions to the point of pressing Query button and then nothing happens… I did wait for quite some time and no progress visible at all. Hovering mouse cursor over the Version field shows that update is available (version with higher number). Progress field shows No File message.
What is interesting to me is the Update button… while hovering the mouse over it I can see message Start update for selected node. File must be choosen first. No file is selected however in Otau file field. While clicking on file selection buton (…) I can see the list of files (seems somehow uploaded to Phoscon data folder), but naming convention for these is, well, unreadible… I’d not take the risk of selecting one of these for updating firmware.
So the question is what exactly should we expect to happen in step of Update? How long it might take in real life to start seing update (I waited ~30 minutes). What is your experience with this? Perhaps I’m facing some connectivity issues…
Also I have multiple devices of the same type (~25 GU10 bulbs from Ikea), should I repeat the same operation for each device to get it updated or will phoscon handle it?
I have the same questions and I also see the ‘No file’ message, but I’m trying it with Philips Hue bulbs and Xiaomi Aqara hardware. (Just wanted to see if that’s going to work )
Philips Hue devices are currently not supported as there are no firmware files available yet easily (on Github someone could extract the URL for one hue light but we couldn’t manage to get this working in a broad sense yet).
I have used that guide to successfully upgrade my Osram devices a few weeks ago.
When using Hassio you can use the steps below to upload the OTAU files to the Deconz add-on, so you can easily select the file in step 5b of the instruction:
Download the OTAU file as mentioned in step 4.
Copy the file to your Hassio share folder.
Use the SSH & Web Terminal add-on to SSH into Hassio.
Run this command to copy the OTAU file to the Deconz addon
Thanks for the post! This was great, and worked great for my Trådfri devices.
Does anybody know if INNR-plugs are upgradable? I got the “No file…” on that one.
Exactly the same here. Everything just says no file. Query does nothing. Some of my Tradfri devices are definitely out of date and the correct files are in the folder.
Strange. I can only repeat that for me it took also some time after clicking Query (several minutes). I had already given up and then for no obvious reason when I looked again I found that the update process had started.
Could it be that you have to restart your HA deCONZ add-on after activating the STD OTAU Plugin? The log of my add-on shows the following lines at a restart that indicate that some IKEA related code has been initialized:
[09:50:04] INFO: Running the deCONZ OTA updater...
[09:50:04] INFO: Running the IKEA OTA updater...
[09:50:04] INFO: deCONZ is set up and running!
@Jpsy, where do you get deCONZ log from? I see some similarily looking deCONZ entries in home-assistant.log, but no such info as you posted, only something about setting up different ZigBee components.
I restarted hassio few times in meantime, one thing I noticed is that after every restart I have to re-enable STD OTAU Plugin - it is not active anymore. I tried to find any option in preferences to have it done automaticaly, but found nothing. Perhaps this is the problem.
@Jpsy those lines appear in my log, but as with @mirekmal theres no OTAU plugin at launch - it needs to be readded. Do you by any chance have the ikea plugs at all? Can you confirm what firmware deconz (none vnc) shows? I see the following :
In the OTAU folder I see a file for 2.0.022 so it seems this is out of date, but perhaps deconz has in fact updated it and it shows as 1.4 anyway?
EDIT:
I see OTAU disabled in the bottom right of this window… does yours say enabled?
@Dan for me message changes from OTAU disabled to enabled when I click on Query button. It stays like that until next restart, then it needs to be re-enabled again.
Regarding ikea plug version - inconsistency of version representation is very annoing in Phoscon
Phoscon add-on in hassio shows current version 2.0.022
Plugin shows in version column 0x20022623
After hovering the mouse over I can see that latest available version is 2.0 build 140835
in data folder I can see 2.0.022 being available (10005777-4.1-TRADFRI-control-outlet-2.0.022.ota.ota.signed)
Thanks. One more quick request if I may (your help is very much appreciated). Does the OTAU section in the node menu look this this for you? (This screenshot shows my conbee and one of my ikea plugs). OTAU looks greyed out in the plug menu and Im curious if you see the same.
The log I am talking about is the dedicated log in the HA deCONZ plug-in. Go to the “Hass.io” menu item, choose the deCONZ plug-in and scroll all the way down to find it. You can restart the plug-in without restarting HA and that log will fill with information about the plug-in initialization process (you may have to hit the refresh button below the log).
Maybe I can post some screenshots of my VNC view tomorrow. What I can tell you right now is that the upgrade did NOT increase the version number of my IKEA GU10 bulbs, but only the build number. I do not own any IKEA plugs though.
Thanks @Jpsy for additional info!
Well, I looked at the log directly in deCONZ component in hass.io section, but looked quite different from what you posted. Here is sample of my one (with irrelevant info, unfortunatelly):
I tried your advise to restart deCONZ and check the log… It is updating too fast to spot something interesting, though at one point of time I’ve seen message starting with INFO: prefix (like your log entries). This made me wondering, if you have any specific setup for deCONZ log, that would allow to see for example only INFO entries? This would help to find relevant information…
If you see more than the above entries, it is possible, that you have switched into a higher debug output level. I have not set any debug output level. In fact, my deCONZ config only contains “device” and “vnc_password”. I also have NO entries for deCONZ in my configuration.yaml. It is all done through HA discovery and the integrations page of Hass.io - exactly as described in the setup instructions of the plug-in.
I just went into the VNC view again and tried the update process again. From the moment I clicked “Query” it took a full 10 minutes (!) until the Version column of the selected node changed from 0x00000000 to a meaningful hex address and the node info became available. I have no idea, what deCONZ does in the meantime.
Hmmm… Indeed I had all debug options enabled in deCONZ configuration, I hoped this will help to get OTAU related messages in the log. So I removed these and restarted plugin… not much change, perhaps less messages, but stil pleanty of these with no reference to OTAU
Regarding running query; it is starnge, I tested it on every single node and for all nodes that are permanently powered on (e.g. bulbs I have instant responce with updating version (e.g. change from 0x00000000 to 0x12214572… yet hovering mouse over this value hints newer version is available…
)