Thread/Matter - Cannot Update Node Firmware (Eve Energy, Inovelli and others)

[tannerdsilva]

The problem

Hello.

I am trying to update my Thread/Matter nodes and I am noticing that HomeAssistant cannot do this nearly as well as Apple Home can. In fact, for me, HomeAssistant cant do this at all.

I have seen some documentation indicating that this is an issue with Apple Border routers (something about mDNS), unfortunately I am failing to find this documentation now. Perhaps it has been removed, I recall it being on the Thread page. Maybe I'm crazy.

I have some knowledge to contribute to this problem, because I hit this problem 100% of the time under current conditions.

1. I have an operational Thread network with ZERO Apple border routers.
2. My network is properly configured for IPv6 multicasting, MLD snooping, all that.
3. My network is FLAT, I do not have any more than one switch.

3 border routers, all of them are HomeAssistant with SkyConnect. You can see that here:

I have Eve Energy plugs and Inovelli switches on this thread/matter fabric. Unfortunately, I am getting the ol' "Failed to perform the action update/install. Error updating: Target node did not process the update file" error. You can see that here:

This happens 100% of the time I try to update anything. The network is perfectly functional and stable, but the updates simply do not work on Thread/Matter right now.

This is not a situation where I try until it works....no, this simply NEVER works.

What version of Home Assistant Core has the issue?

2025.5.2

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

Python Matter Server? OpenThread Border Router? unclear

Link to integration documentation on our website

No response

Diagnostics information

It's not immediately evident to me how to provide additional diagnostic data on this issue but I am happy to do so if anyone has ideas.

Example YAML snippet

Anything in the logs that might be useful for us?

Additional information

It's not immediately evident to me how to provide additional info on this issue but I am happy to do so if anyone has ideas.

[home-assistant]

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

Code owner commands

Code owners of thread 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 thread 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)}}

---

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

[tannerdsilva]

An additional piece of info that may be useful:

I got this error when the fabric had only a single node on it. So it doesn't necessarily matter how big or small the fabric is, I can easily demonstrate this error happening when the fabric only has one node, and equally when there are many nodes.