Been getting the following error when updating Onvis S4 Plugs:
(MainThread) ERROR [matter_server.server.client_handler] [547509452144] Error while handling: update_node (node 5): Target node did not process the update file
Unsure what else to try
Using a Home Assistant Connect ZBT-1.
Any ideas how to fix this?
If it is on firmware 1.1.0-315, then you might have to get an Apple Matter hub to do the update, because that firmware have a critical bug.
Other than that it is just keep trying.
I do not know if this helps. It is just guessing.
make sure you have plenty of mains powered devices. RF signals are not always straight between the transmitter and receiver. This I know to be true!
if you can use only one TBR. This is just a guess, but Multi-admin is pretty new and there have been issues with it.
remove the commisioning network, if it is still there. When commisioning with a mobile phone the phone will create a new network and then join the device to that network and after that then join that network to your choice of network. The commisioning network is still there then.
I can’t remember where I found it, but try the Matter integration, The web service of the Matter addon, the Thread integration and the web interface of the OTBR addon. It is there somewhere.
Thank you.
I will test with a Apple Matter hub.
Replying to your guesses:
I guess I’ll have to wait until the Apple Home Hub mini arrives tomorrow to give it a go on updating it from inside the walled garden.
People keep saying multiple TBR’s is a problem, but I have yet to read any good argument why. I have a ZBT-1 joined with the Google Nest thread network, 6 TBR’s all operating on the same Thread network. I have had this for at least a year, no problems because of that.
Anyone using Google products in their Tread network will find it is next to impossible to have only one TBR. So saying it is unusual is weird, as is implying that Google, who provided the base code for OTBR afaik would not support it very well.
Problems are foreseeable if you have multiple TBR’s on different networks. The commisioning on phones is confusing enough, let alone if it inclined to prefer Nest Thread network over the one HA has put up if they are different.
It is not the phone, but the Matter Thread device that have the commissioning network still stored.
As I said. I do not know if it helps or not.
I should probably have been clearer with the only one TBR and said only one brand of TBRs, because the TBRs usually have no issue with other TBRs of same brand.
It is when you start mixing the brands that it can go wrong, but it is not certain though, so it is still a vague argument. It is though still an option and when all else fails, then the small things might count also. 
As I said, I do have one SkyConnect too. I also used to have an esp based home brew, but firmware updates were too cumbersome and I figured advancements in the fields would require keeping up. So I decided to scrap it. But I must say HA did not inform me of much updates on the ZBT-1 either.
It is good to know what might contribute to problems, as is having stories of success. I always worry that people change three things and blame all three when it helps, or blame the wrong thing once they succeed.
I agree, but Matter is really hard to interpret, especially with all the warnings and errors in the Matter Server addon log, which seems to have no effect on the workings, so maybe many of the errors should have been warnings and many of the warnings should have been infos.