Ikea Matter firmware updates - Solved!

Greetings,
After quite the fight getting Matter/Thread to work (:rage:) I got my first Matter/Thread devices online ( :confetti_ball: ). I picked up an Ikea ALPSTUGA and KLIPPBOK.

Both are working as expected ( :confetti_ball: ) and now both are showing that there are firmware updates. Neither will actually update. After clicking on the update button and waiting for it to think for a long period of time I get this message in the web:
Failed to perform the action update/install. Error updating: Target node did not process the update file

And in the log files I get this:
2026-01-18 14:04:21.579 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140497095029792] Error during service call to update.install: Error updating: Target node did not process the update file

Of course, Ikea says to use all their cruft which I absolutely don’t want. And I found others saying this should work with Home Assistant and their Thread devices - but I’ve not found anyone reporting firmware updates on their Matter/Thread devices using Home Assistant.

Anyone else having issues or should this be working?
(the absolute pain it was to get Matter/Thread working makes me wonder if I’ve still got other issues to work out… but in theory I’ve done all the checks that say it’s working and clearly these devices are working really well now for days so… :man_shrugging: )

Thanks!

[Edit] - Updated to 8.2.2 - enabled Beta matter.js - All Ikea devices updated without issue! :confetti_ball:

1 Like

I have similar issues for a while now, with a Nanoleaf light as TBR, and Eve devices. The devices are working, so I decided so far not to worry too much; I’ll pay attention when the new matter.js server will become a part of HA.
But yeah, at the moment updating Matter (Thread?) devices seems hard.

1 Like

I got confirmation that Home Assistant updated these devices when someone was using Apple devices as the Thread Border Router. I’m using the ZBT-1 - so maybe there is something wrong still in my configuration. But not sure how to debug it.

Thoughts?

I have update mine (using OTBR/Skyconnect). They may be a little finicky. The Timmerflote I had to try a couple of times. I place mine near the OTBR when updating, and If I have a battery device, I try to wake the battery device up and then click to do the update.

I am also experimenting the same issue. I have an SLZB-06M flashed for Thread, using HA as OBTR, and all the devices are reporting fine, pairing fine and all. However, the update would just not push with the same error:
Failed to perform the action update/install. Error updating: Target node did not process the update file

Commenting to follow if anyone ever finds out why!

I got a couple of Alpstuga paired first with my Dirigera and then added to my HA which doesn’t have any Thread HW. Just after I got them visible on my HA I saw on the status that they were updating and that it successfully completed.

Thanks. In my case they are all in the same room about 10 feet from the ZBT-1. And I’m used to the ā€œwake them up before updatingā€ for the battery devices. I just attempted the ALPSTUGA (which is powered) three times in a row… all the same error… :man_shrugging:

I asked another generic-nerd-community I’m in. Someone else mentioned they also used the Dirigera w/ home assistant w/o issue updating and thinks my problem is that my HA install isn’t routing the Thread/Matter network out to the internet properly. Although I’m new enough to Thread/Matter that I’m not entirely sure how to do that because it’s my understanding that it’s a separate network from my primary lan or my IoT lan. Something for me to research I suppose :man_shrugging:

Though I’m not entirely sure I like the idea of my Thread/Matter network talking freely out to the internet… That’s part of why I have an isolated IoT network! :frowning_face: I would prefer it if the updates passed through HA itself (like the zigbee/z-wave/other devices I have). :man_shrugging:

Updates don’t work while Apple border routers are switched on:

:man_shrugging:
All I know is that his updates worked.

I don’t have an Apple border router - mine is the ZBT-1 as I mentioned, and it’s not working.

:man_shrugging:

I have both a ZBT-1 and a Google TV streamer as threads border routers, I’ve tried the update on the Alpstuga with both attached and with one or the other disconnected, no success.

I just updated to the 8.2.0 matter server, switched on the beta, so that the new matter.js server is being used - and I was able to install some updates for my Matter over Thread devices for (I think?) the first time.

Let’s hope I didn’t completely bork my system by moving over too soon, but it seems promising that the new matter server will likely work!

I tried the beta matter server (it’s set in the configuration settings under the matter server in the add-ons section, not the matter thing in integrations) and indeed, the update seemed to go fine, got an installation bar graph and the unit did a reset (be patient, takes a few minutes) and it seems to be updated and working fine. While I don’t have a lot of matter devices, in brief testing everything else seems to be working.

2 Likes

Old news and no longer true as of 2 or 3 iOS versions in the past. I update 30 or so inovelli Matter over thread multiple times via Home assistant and just recently several Ikea with only apple TBR in the thread network.

Thank you, that worked great!

Ah, good to hear. I don’t have a lot of Matter devices, so once I got that Eve Energy to update without my Apple TVs, there were no new firmware updates since.

WhooHooo! This seems to be the answer! Thank you!

Watching the progress bar go across right now. :confetti_ball:

Just to let you know, the new Matter Server (GitHub - matter-js/matterjs-server: Matter server based on Matter.js) works really well in a container environment.
You can just replace the container with the same configuration base and that’ll get the job done.

This fixed the update problem. Just so you’re aware, the web API has been updated.