Updating Eve Thermo (Matter) to 3.5.1 fails: Target node did not process the update file

[IngmarStein]

The problem

I've seen the other related issues #123086, #123568, #123401, but they are all closed, so I'm creating a new one:

When attempting to update an Eve Thermo from 3.5.0 via HA, I get the following error:

2024-11-29 21:17:08.002 (MainThread) INFO [matter_server.server.device_controller] <Node:19> New software update found: 3.5.1 on UpdateSource.MAIN_NET_DCL (current 3.5.0).
2024-11-29 21:17:09.825 (MainThread) INFO [matter_server.server.device_controller] <Node:19> Update to software version 9400
2024-11-29 21:17:10.005 (MainThread) INFO [matter_server.server.device_controller] <Node:19> New software update found: 3.5.1 on UpdateSource.MAIN_NET_DCL (current 3.5.0).
2024-11-29 21:17:10.006 (MainThread) INFO [matter_server.server.device_controller] <Node:19> Downloading update from 'https://eve-updates.evehome.com/matter/eve_thermo-3.5.1+9400-matter-benc-enc-C54F559B-F35F-4CB2-9609-C606407BF8C6.bin'
2024-11-29 21:17:10.280 (MainThread) INFO [matter_server.server.ota.provider] Update file 'eve_thermo-3.5.1+9400-matter-benc-enc-C54F559B-F35F-4CB2-9609-C606407BF8C6.bin' downloaded to '/config/updates/19'
2024-11-29 21:17:10.281 (MainThread) INFO [matter_server.server.device_controller] <Node:19> Starting update using OTA Provider.
2024-11-29 21:17:10.282 (MainThread) INFO [matter_server.server.ota.provider] Starting OTA Provider
[Detaching after vfork from child process 258]
2024-11-29 21:17:10.286 (MainThread) INFO [matter_server.server.ota.provider] Commission and initialize OTA Provider
2024-11-29 21:17:10.476 (Dummy-2) INFO [chip.ChipDeviceCtrl] Established secure session with Device
2024-11-29 21:17:10.936 (Dummy-2) INFO [chip.ChipDeviceCtrl] Commissioning complete
2024-11-29 21:17:10.937 (MainThread) INFO [matter_server.server.ota.provider] OTA Provider App commissioned with node id 990019.
2024-11-29 21:17:12.245 (MainThread) INFO [matter_server.server.ota.provider] Waiting for target node update state change
2024-11-29 21:17:12.480 (MainThread) INFO [matter_server.server.ota.provider] Update state changed from <UpdateStateEnum.kIdle: 1> to <UpdateStateEnum.kQuerying: 2>
2024-11-29 21:17:57.384 (MainThread) INFO [matter_server.server.ota.provider] Update state changed from <UpdateStateEnum.kQuerying: 2> to <UpdateStateEnum.kIdle: 1>
2024-11-29 21:17:57.384 (MainThread) INFO [matter_server.server.ota.provider] Cleaning up OTA provider
2024-11-29 21:17:57.384 (MainThread) INFO [matter_server.server.ota.provider] Terminating OTA Provider
2024-11-29 21:17:57.402 (MainThread) ERROR [matter_server.server.client_handler] [140737221540896] Error while handling: update_node (node 19): Target node did not process the update file

The device itself is available (and responsive) via HA and HomeKit. It is shown as online in the Matter Python Server UI.

The network has five border routers: 3 Apple TV, 1 Aqara M3, 1 SkyConnect.

I'm running the current beta, but only as I was hoping it might fix the issue which was already present in 2024.11.

What version of Home Assistant Core has the issue?

core-2024.12.0b2

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

matter

Link to integration documentation on our website

https://www.home-assistant.io/integrations/matter/

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant[bot]]

Hey there @home-assistant/matter, mind taking a look at this issue as it has been labeled with an integration (matter) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `matter` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign matter` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

matter documentation matter source _{^{(message by IssueLinks)}}

[marcelveldt]

Unfortunately this is out of our control when Apple border routers are used (we've created a ticket with them but no signs it will have any priority). As long as you use other BR's than Apple, the update feature will work correctly.

[IngmarStein]

Thanks, @marcelveldt. Does that mean the feature stops working for all devices as soon as there is at least one Apple border router on the network (there are two non-Apple ones present) or that it's not working for the devices connected through these border routers?

[marcelveldt]

Its not 100% clear but it looks like it fails when the traffic is routed through an Apple BR