First device I bought is IKEA Alpstuga qir quality sensor. Straight after onboarding (well maybe after few minutes) the Firmware entity changed to Update available and I attempted to update frpm, 1.0.13 to 1.0.15. Failed and retried few times, rebooting the sensor along the way too.
Attempts failed with:
Error updating: Target node did not process the update file
At some point after these attempts the Firmware entity state changed to ‘unknown’ and it stays that way. The Firmware entity attributes show 1.0.13 as current firmware:
An IKEA tech support issue? Your logs are too short, and there may be other clues hidden in there.
[Please format </> when posting your log for readability]
Was the firmware update pulled? Can you wget it for troubleshooting purposes? Corrupted during transfer to you? Format changed by vendor in intermediate .14 version?
Hello @IOT7712 mind that - for the time being - my issue is not that it fails to update, but that it doesn’t even show update status in firmware entity anymore. That’s why I’m afraid that I broke something - as before, even between failing update, the firmware state never was `unknown’.
I’ve seen people updating them successfully - there are some known issues in the environments with Apple devices as routers, but I don’t have any in my network.
The firmware was pulled and an install attempt was made - we got to the ‘installing’ phase. The error in this case (Target node did not process the update file) allegedly means that the device refused the update.
I don’t have any meaningful logs from the failed updates, I realized some time later that firmware got ‘unknown’. And that is my main issue - that while attributes look all right (I think) so the device/integration ‘knows’ what firmware it has, the Matter server knows what firmware it detected upstream for upgrade, still the status of the firmware entity is unknown.
The only log I have, I’m afraid wont be helpful, is below:
2026-01-26 11:25:22.188 INFO ClientInteraction Subscription successful « @1:3•a13c⇵e996 id: b5b3cb04 interval: 10m timeout: 10m 32s
2026-01-26 11:29:07.856 INFO DclOtaUpdateService Update available in Prod-DCL new: 16777231 vid: 4476 pid: 12289 prod: true current: 16777229
2026-01-26 11:29:07.860 INFO DclOtaUpdateService Downloading OTA image from https://ota.matter.ikea.com/files/4476_12289_16777231_57dc5bcf-8c27-4db6-ba37-fc3aa976be0f.ota vid: 4476 pid: 12289 v: 16777231 (1.0.15) prod: true
2026-01-26 11:29:08.230 INFO SoftwareUp~teManager OTA update available for vendorId: 4476 productId: 12289 softwareVersion: 16777229 file: ota/ota/117c.3001.prod peers: peer2
2026-01-26 11:29:08.232 INFO Controller~ndHandler Update available for node 6: { vendorId: 4476, productId: 12289, softwareVersion: 16777231, softwareVersionString: "1.0.15", releaseNotesUrl: "", specificationVersion: 0, source: "dcl-prod" }
2026-01-26 11:30:02.663 INFO Controller~ndHandler Node 6: Discovering addresses via mDNS (3s timeout)
2026-01-26 11:30:02.674 INFO Controller~ndHandler Node 6: Discovering addresses via mDNS (3s timeout)
2026-01-26 11:30:02.678 INFO Controller~ndHandler Node 6: mDNS discovered 1 addresses: fd85:6e45:48cb:1:6ddc:bb92:a520:a849
2026-01-26 11:32:08.533 INFO ClientSubs~onHandler Ignoring data report for unknown subscription ID e53c4146
2026-01-26 11:32:08.641 INFO ClientSubs~onHandler Ignoring data report for unknown subscription ID 0cad2f31
2026-01-26 11:32:08.731 INFO ClientSubs~onHandler Ignoring data report for unknown subscription ID de829a53
2026-01-26 11:32:10.164 INFO ClientEventEmitter Received event timeSynchronization.dstTableEmpty on server.@1:6 undefined
2026-01-26 11:32:13.252 INFO ClientEventEmitter Received event timeSynchronization.dstTableEmpty on server.@1:6 undefined
2026-01-26 11:33:36.468 INFO Controller~ndHandler Node 6: Discovering addresses via mDNS (3s timeout)
2026-01-26 11:33:36.469 INFO Controller~ndHandler Node 6: mDNS discovered 1 addresses: fd85:6e45:48cb:1:6ddc:bb92:a520:a849
2026-01-26 11:33:36.471 INFO Controller~ndHandler Node 6: Discovering addresses via mDNS (3s timeout)
2026-01-26 11:33:36.472 INFO Controller~ndHandler Node 6: mDNS discovered 1 addresses: fd85:6e45:48cb:1:6ddc:bb92:a520:a849
2026-01-26 11:34:29.384 INFO ClientSubscription Subscription 274047434 timed out after 2m 16s
2026-01-26 11:34:29.387 INFO PairedNode @1:6 Subscription timed out ... trying to re-establish ...
2026-01-26 11:34:29.389 INFO PairedNode @1:6 Reconnecting now ...
2026-01-26 11:34:29.869 INFO ClientInteraction Subscribe » @1:6•a13b⇵e99b min: 1s max: 1m attributes: events: eventFilters: undefined=16
2026-01-26 11:34:30.068 INFO ClientInteraction Subscription successful « @1:6•a13b⇵e99b id: aa841a9f interval: 1m timeout: 2m 16s
2026-01-26 11:34:55.700 INFO Controller~ndHandler Node 6: Discovering addresses via mDNS (3s timeout)
2026-01-26 11:34:55.703 INFO Controller~ndHandler Node 6: mDNS discovered 1 addresses: fd85:6e45:48cb:1:6ddc:bb92:a520:a849
2026-01-26 11:34:55.705 INFO Controller~ndHandler Node 6: Discovering addresses via mDNS (3s timeout)
2026-01-26 11:34:55.706 INFO Controller~ndHandler Node 6: mDNS discovered 1 addresses: fd85:6e45:48cb:1:6ddc:bb92:a520:a849
2026-01-26 11:34:29.869 INFO ClientInteraction Subscribe » @1:6•a13b⇵e99b min: 1s max: 1m attributes: events: eventFilters: undefined=16
2026-01-26 11:34:30.068 INFO ClientInteraction Subscription successful « @1:6•a13b⇵e99b id: aa841a9f interval: 1m timeout: 2m 16s
2026-01-26 11:34:55.700 INFO Controller~ndHandler Node 6: Discovering addresses via mDNS (3s timeout)
2026-01-26 11:34:55.703 INFO Controller~ndHandler Node 6: mDNS discovered 1 addresses: fd85:6e45:48cb:1:6ddc:bb92:a520:a849
2026-01-26 11:34:55.705 INFO Controller~ndHandler Node 6: Discovering addresses via mDNS (3s timeout)
2026-01-26 11:34:55.706 INFO Controller~ndHandler Node 6: mDNS discovered 1 addresses: fd85:6e45:48cb:1:6ddc:bb92:a520:a849
2026-01-26 11:42:32.723 INFO ClientSubs~onHandler Ignoring data report for unknown subscription ID 1055a1ca
2026-01-26 11:42:34.033 INFO ClientEventEmitter Received event timeSynchronization.dstTableEmpty on server.@1:6 undefined
2026-01-26 11:42:37.237 INFO ClientEventEmitter Received event timeSynchronization.dstTableEmpty on server.@1:6 undefined
2026-01-26 11:47:37.831 INFO Controller~ndHandler Node 6: Discovering addresses via mDNS (3s timeout)
2026-01-26 11:47:37.834 INFO Controller~ndHandler Node 6: Discovering addresses via mDNS (3s timeout)
2026-01-26 11:47:40.837 INFO Controller~ndHandler Node 6: mDNS discovery found no addresses
2026-01-26 11:47:40.840 INFO Controller~ndHandler Node 6: mDNS discovery returned no addresses, using commissioning addresses { type: "udp", ip: "fd85:6e45:48cb:1:6ddc:bb92:a520:a849", port: 554
Wondering what will happen when the next firmware release is issued? Will the ‘unknown’ condition clear? Automagically?
As an aside: Curious what role mDNS has for IPv6 addresses?
Is your network reliable and configured correctly? Seeing a few timeout issues that seem to be for routine network sessions, including firmware file downloads.
Yes, others have successfully upgraded Alpstuga, others not.
I’m not familiar with the newer Matter Server js logs, so I’m not quite sure but it not have made contact with node 6. Can you like use HA UI to turn the Alpstuga display on/off?
But since you are running the Beta Matter Server js, may be a good opportunity to write up an issue and see what they say.
I can also tell something is strange. I got the same Alpstuga sensor added today. After a successful intergration I got the firmware update available.
And I was able to update the firmware to 1.0.15.
After the update is said it was on the latest firmware.
Restarted my Matter Server and Openthread border router.
And now it shows also firmware unavailable on all my matter devices.
2x Alpstuga, 1x Klippbok
