When doing a Matter update, the server starts a separate OTA Provider. It’s log are not reflected in the Matter Server logs, however, the add-on specific config directory has a an update directory with directories for each node.
I’ve tested the Eve Weather update here, and it seems that retransmission fails 4 times in a row, then the OTA Provider gives up.:
[1746303124.068037][454:454] CHIP:EM: >>> [E:27017r S:5728 M:209871542 (Ack:162649340)] (S) Msg RX from 1:00000000000000A9 [6DB7] --- Type 0002:10 (BDX:BlockQuery)
[1746303124.068074][454:454] CHIP:EM: Found matching exchange: 27017r, Delegate: 0x5555a64580
[1746303124.068088][454:454] CHIP:EM: Rxd Ack; Removing MessageCounter:162649340 from Retrans Table on exchange 27017r
[1746303124.068097][454:454] CHIP:BDX: OnMessageReceived: message 0x10 protocol (0, 2)
[1746303124.068102][454:454] CHIP:ATM: Handling received BDX Message
[1746303124.068106][454:454] CHIP:ATM: BlockQuery
[1746303124.068109][454:454] CHIP:ATM: Block Counter: 177
[1746303124.074194][454:454] CHIP:BDX: OutputEvent type: QueryReceived
[1746303124.074293][454:454] CHIP:ATM: Sending BDX Message
[1746303124.074298][454:454] CHIP:ATM: Block
[1746303124.074301][454:454] CHIP:ATM: Block Counter: 177
[1746303124.074303][454:454] CHIP:ATM: Data Length: 1024
[1746303124.124408][454:454] CHIP:BDX: OutputEvent type: MsgToSend
[1746303124.125530][454:454] CHIP:EM: <<< [E:27017r S:5728 M:162649341 (Ack:209871542)] (S) Msg TX to 1:00000000000000A9 [6DB7] [UDP:[fd82:4325:bafa:1:df62:9f24:7a1:383f]:5540] --- Type 0002:11 (BDX:Block)
[1746303125.604308][454:454] CHIP:EM: Retransmitting MessageCounter:162649341 on exchange 27017r Send Cnt 1
[1746303127.023572][454:454] CHIP:EM: Retransmitting MessageCounter:162649341 on exchange 27017r Send Cnt 2
[1746303129.239121][454:454] CHIP:EM: Retransmitting MessageCounter:162649341 on exchange 27017r Send Cnt 3
[1746303132.653976][454:454] CHIP:DIS: SRV record already actively processed.
This might be related to RF interference and/or potentially made worse the fact that this is a battery device connecting through Thread routers.
I was finally able to update my Eve Weather to version 3.5.0. Unfortunately, I was unable to do this in Home Assistant until the end - even with the solutions suggested here.
Of my 5 Eve Weather, I had to
delete all 5 from Home Assistant and update them via Apple HomeKit,
first reset 3 out of 5 devices and reintegrate them into HomeKit,
in 4 out of 5 cases, several attempts to download and install until it finally worked.
I’ve never had such a disastrously difficult update with any of my numerous smart home devices - and not even with Eve Weather. Hopefully this won’t happen again.
Yes it sounds like the “trick” is to get the firmware update successfully transmitted to the device, and for some reason this fails more often than not.
Well, if Eve Weather really does go to sleep during an OTA firmware upload/update this is completely illogical and therefore an undesirable behavior. However, devs are currently investigating the root cause - which is not a user error.
Why is it illogical.
Many servers support a continue download function and it would make sense to have it as part of the standard in a network that is not high bandwidth.
So I did some more investigation, and written previously, this doesn’t seem to be a Matter Server/OTA Provider problem. I was able to reproduce the problem in my production network as well, and started to investigate some more. My Thread network is quite heterogeneous, with device from Aqara, Eve, Google, Nanoleaf and ONVIS all on the same Thread network. Now since Eve Weather is an end device in the Thread network, the device relies on the parent router to transmit messages. I repeated the update at least 10 times, but never succeeded. Only when I took the routers the device was connected through (I used some ot-cli commands to determine that, but it is complicated and not very reliable to write it down here), and the Eve Weather was directly a child of the OTBR, the update worked. So: Taking all Thread routers temporarily offline and update the device might be a solution. Or setup a dedicated temporary Thread network for the update.
I am not entirly sure why many messages make it to the device, and suddenly a couple in a row don’t. It doesn’t seem RF related, I rather belive that the router or end device might just temporarily be busy and dropping messages.
Do you have updated your Onvis?
There is an important update for it, which will fix an issue that will make your device go unavailable and I can also cripple your Thread mesh network.
I’m only using the ZBT-1, so I have just one Thread border router. Even when I put the Eve Weather devices right next to the stick, the OTA updates still fail. I’ve tried everything, no chance … :/.
Wait for the Matter server update. Although it doesn’t seem to finally solve the problem (which seems to be with the older firmware of Eve Weather), some users had success with the beta of the new version of Matter server - and its updated OTA provider service. Fingers crossed.
Bummer. What have you already done to rule out signal interference besides putting the devices next to ZBT-1? If you have any other Thread hubs, try to put them next to a hub that is least likely to be close to a source of signal interference. Try to deactivate 2.4 GHz WiFi before starting the update. That’s what I have done. Additionally, you could change the Thread channel. I didn’t need to do that.
To add a data point, I am encountering the same update issue (10+) tries on an Eve Smart Plug going from firmware 3.2.1 to 3.5.0 (latest), using the native Apple HomeKit Thread-over-Matter integration, from inside the Apple Home app.
I have two of the same devices that I was able to successfully update back in April 2025, albeit with several tries over a few days.
Meanwhile the old firmware v3.2.1 has been identified as the main reason why updates fail. So there seems no other way than trying until you are lucky.
Chiming in here as I also had absolute major issues updating my two Eve Weather.
I finally updated successfully and here are the steps I took, for anyone else that might have the issue and read this thread like me.
Buy a SMlight SLZB07mg24 and a USB extension cable use that for my Thread Border Router instead of the Home Assistant Yellow circuit board I was using before.
This made absolutely no difference in my results. It may be part of the solution but was not definitively what made me succeed
Remove the Eve Weather from it’s location and putting it 1 meter (3 feet) away from the Thread Border router antenna. Also removing the battery and inserting it again to restart the Eve weather.
Neither this made any substantial difference, might be part of the solution but not what made a noticeable difference.
Disconnect all my Thread Routers, in my case an Eve Energy which I unplugged and Nanoleaf downlight I had to shut off by shutting of the fuse to the bathroom it was placed in.
After this final step, I finally succeeded in updating one of my Eve Weathers. It didn’t stop suddenly and slowly reached 100% on the first try and then implemented the new firmware and it is now on version 3.5.0 from the earlier 3.3.0
Regarding my 2nd Eve weather I tried updating that one without removing it from it’s place and putting it closer to the border router but that one failed and went offline. After putting it closer and trying again I reached 81% before the update failed.
So that device was not as simple and smooth. However on my second attempt it reached 100% and installed the new firmware.
CONCLUSION: What fixed the issue for me seem to be a combination of turning off all thread devices connected to power to avoid routing while updating and just getting the Eve Weather close to the Thread Border Router to directly connect it. Instead of updating and failing probably 50+ times it worked in three attempts after those adjustments.
If this helps one or more other people, I’m happy I could be of help and make someone a bit happier
Just got eve weather today and at first I was delighted the pairing process went smoothly with my otbr (ZBT-1), probably using an eve energy smart plug and two nanoleaf essential light bulbs as relays. So far so good. Then I was greeted by an update firmware for it message right in the HA Settings menu from 3.3.0 to 3.5.0. Amazing I thought, so happy I ordered three more eve energy smart plugs yesterday to support them instead of Onvis at half price.
Because Onvis is junk and the firmware update is near impossible and only possible on Apple Homekit and even then a nightmare (and future updates may or may not be questionable).
So I try the update and go for a shower. Came back 10 mins later, update failed. Okay, no biggie, I rebooted and watched at the screen this time as it went to 51%, became unavailable for a few secs and it was back to 3.3.0 again. So I googled it and found this thread. Someone suggested updating through the Matter Server sidebar instead of the Settings menu. So I tried that, watched it go to 36% and fail and it showed as offline for a few mins only to have it reappear at 3.3.0. So I moved on to the next suggested “fix” - bringing down my entire Thread network (thankfully in my case it was two nanoleafs connected to a dumb switch and a single eve energy plug). Making sure all my thread devices are offline, I rebooted HA to make sure eve weather would connect directly to the zbt-1 placing it one meter away from the dongle/obtr. Got to 75% and failed again!! And it takes its sweet time to realize it failed. So, back to twiddling my thumbs as I anticipate removing the battery to see if that is going to help anything. So I remove the battery, reboot ha, wait until its fully loaded and only then do I reinsert the battery. Once it was back online, I started the update process yet again (this time from the Matter sidepanel). Anticipatingly, I slowly watched it go all the way up to 91% this time. Convinced removing the battery and having everything turned off as suggested by other people would help. Nope. Stuck at 91%.
So as a Hail Mary I reboot HA once again, making sure everything but the eve weather is offline and eve weather is one meter away from the otbr. Stuck at 22%.
I am completely out of options at this point, stuck with a device that won’t update its firmware, even with all the recommended strategies provided here. I was going to order another one, but after this horrible, horrible experience I refuse to buy any more smart devices at all. I really, really hoped matter over thread would be the end-all-be-all now that it was out of beta, but this is complete and utter bs. Even if I manage to update the firmware somehow (I keep trying while chilling on the couch, got to 98% once, then stuck at 37… Seems completely random. I’m about to bring my other 3 devices online and keep trying just out of curiosity (it will still probably be connected straight to the skyconnect since its still 1m away from it (as is the closest eve energy plug so who knows).
This whole matter/thread shiznit better get fixed. Sooner rather than later at that. Firmware updates are a mess. I couldn’t even updgrade my Skyconnect to Thread after following the procedure to migrate to another dongle and disabling zha. It would start installing and just failed. Had to plug it into my pc, install the drivers and use the web flasher. This is just horrible though, both with eve and Onvis and what have you.
Okay, so a good night’s sleep solves everything right?
Woke up at 4:30 am after trying half a dozen times last night as I dozed off on the couch lol. Anyway, I woke up and tried moving the Skyconnect 5-10 inches away from eve weather. Hit update, stuck on 4% (with the other devices turned off. mind you). Made me lol.
So I tried a 2nd time. It may or not have gone through, I honestly don’t rembember. But if not on the 2nd, it worked on the 3rd attempt this time. Watched it go to 100%, status became unknown and I got a happy face.
Gave it a good half an hour to come back up but it was still reporting as firmware unavailable, so I hit back, checked the devices and saw the fw successfully upgraded to 3.5.0 this time around. So now I have Matter 1.3 support, yay.
Battery level dropped from 100% to 65% and the Voltage now reads as unavailable.
Good job eve.
Okay, an hour later the battery reads as 3V. Fine. Still at 65% though >.>
Also, why can’t it pull the altitude from the GPS location? -.-
Edit: Also, under Configuration it still says Firmware: Unknown instead of Up-to-date (but it displays as 3.5.0 at the top). I’ll give it 24 hrs before I try removing the battery again to see if that fixes it.
Edit 2: Okay my eve energy smart plug also says Firmware: Unkown in the Configuration window. Is this normal? I’ll report back with the battery % tomorrow.
Welcome to the club - we went through the same. AFAIK the reason for this „odyssey“ is a faulty Eve Weather 3.3.0 firmware.
The battery levels are a mystery. I experienced the same erratic values. Recently my battery „died“ with 30-40% capacity left. I replaced it and now it shows a stable 100%. Let‘s see how this plays out.
