Eve Weather OTA update from 3.3.0 to 3.5.0 running into timeouts

phaze75 · April 29, 2025, 6:35am

Eve released firmware 3.5.0 for Eve Weather yesterday. HA is showing the update correctly. However, I tried more than 20 times to install the update via Matter’s OTA update procedure. The procedure is always timing out at different percentages. The closest I’ve gotten is 95%.

I have already

rebooted the Eve Weather device
turned the “Transmit Power” of Eve Weather to “High”
rebooted the HA instance
turned off 2,4GHz WIFI

but the OTA update procedure keeps timing out.

Here is the log of the Matter server addon:

2025-04-29 07:58:16.310 (MainThread) INFO [matter_server.server.device_controller] Node:10 New software update found: 3.5.0 on UpdateSource.MAIN_NET_DCL (current 3.3.0).

2025-04-29 07:58:16.362 (MainThread) INFO [matter_server.server.device_controller] Node:10 Re-Subscription succeeded

2025-04-29 07:58:26.284 (MainThread) INFO [matter_server.server.device_controller] Node:10 New software update found: 3.5.0 on UpdateSource.MAIN_NET_DCL (current 3.3.0).

2025-04-29 08:00:43.260 (MainThread) INFO [matter_server.server.device_controller] Node:10 Update to software version 9464

2025-04-29 08:00:43.435 (MainThread) INFO [matter_server.server.device_controller] Node:10 New software update found: 3.5.0 on UpdateSource.MAIN_NET_DCL (current 3.3.0).

2025-04-29 08:00:43.435 (MainThread) INFO [matter_server.server.device_controller] Node:10 Downloading update from ‘https://eve-updates.evehome.com/matter/eve_weather-r3.5.0+9464-matter-benc-enc-F6AD84FE-EDDE-4360-B2F6-42C471FD73D8.bin’

2025-04-29 08:00:43.569 (MainThread) INFO [matter_server.server.ota.provider] Update file ‘eve_weather-r3.5.0+9464-matter-benc-enc-F6AD84FE-EDDE-4360-B2F6-42C471FD73D8.bin’ downloaded to ‘/config/updates/10’

2025-04-29 08:00:43.569 (MainThread) INFO [matter_server.server.device_controller] Node:10 Starting update using OTA Provider.

2025-04-29 08:00:43.569 (MainThread) INFO [matter_server.server.ota.provider] Starting OTA Provider

2025-04-29 08:00:43.569 (MainThread) INFO [matter_server.server.ota.provider] Commission and initialize OTA Provider

2025-04-29 08:00:43.609 (Dummy-2) INFO [chip.ChipDeviceCtrl] Established secure session with Device

2025-04-29 08:00:43.867 (Dummy-2) INFO [chip.ChipDeviceCtrl] Commissioning complete

2025-04-29 08:00:43.867 (MainThread) INFO [matter_server.server.ota.provider] OTA Provider App commissioned with node id 990010.

2025-04-29 08:00:45.590 (MainThread) INFO [matter_server.server.ota.provider] Waiting for target node update state change

2025-04-29 08:00:45.754 (MainThread) INFO [matter_server.server.ota.provider] Update state changed from <UpdateStateEnum.kIdle: 1> to <UpdateStateEnum.kQuerying: 2>

2025-04-29 08:00:47.952 (MainThread) INFO [matter_server.server.ota.provider] Update state changed from <UpdateStateEnum.kQuerying: 2> to <UpdateStateEnum.kDownloading: 4>

2025-04-29 08:18:15.225 (Dummy-2) CHIP_ERROR [chip.native.DMG] Subscription Liveness timeout with SubscriptionID = 0x08ebb85d, Peer = 01:000000000000000A

2025-04-29 08:18:15.229 (MainThread) INFO [matter_server.server.device_controller] Node:10 Subscription failed with CHIP Error 0x00000032: Timeout, resubscription attempt 0

2025-04-29 08:18:22.449 (MainThread) INFO [matter_server.server.ota.provider] Update state changed from <UpdateStateEnum.kDownloading: 4> to <UpdateStateEnum.kIdle: 1>

2025-04-29 08:18:22.449 (MainThread) INFO [matter_server.server.ota.provider] Node 10 update state idle, assuming done.

2025-04-29 08:18:22.450 (MainThread) INFO [matter_server.server.ota.provider] OTA update finished successfully

2025-04-29 08:18:22.450 (MainThread) INFO [matter_server.server.ota.provider] Cleaning up OTA provider

2025-04-29 08:18:22.450 (MainThread) INFO [matter_server.server.ota.provider] Terminating OTA Provider

2025-04-29 08:18:22.674 (MainThread) INFO [matter_server.server.device_controller] Node:10 New software update found: 3.5.0 on UpdateSource.MAIN_NET_DCL (current 3.3.0).

2025-04-29 08:18:22.718 (MainThread) INFO [matter_server.server.device_controller] Node:10 Re-Subscription succeeded

WallyR · April 29, 2025, 7:29am

The update looks like it succeeded and you might just be impatient and restarting it over again.

phaze75 · April 29, 2025, 8:47am

Thanks for checking. Unfortunately, the update consistently failed to reach 100%—I monitored it closely each time.

In the meantime, I may have found a workaround. Instead of using the standard Home Assistant interface, I initiated the update directly from within the Matter Server add-on, using the update button in the node itself. This worked instantly, and the update completed successfully. The device now shows firmware version 3.5.0.

It’s possible this was just coincidence, but there may be an issue in how the HA interface interacts with the Matter Server add-on. That said, my understanding is that the HA interface simply triggers the Matter Server’s update process, so it’s unclear if and why this made a difference.

WallyR · April 29, 2025, 9:27am

The HA core just calls the same function as when you press the button in the Matter server.
The reason why it updated instantly was that it was already updated, but when you pressed the button the device reported back with the right version.
It would have happened eventually.

Matter, Zigbee and Z-wave networks do not have huge bandwidth and update downloads are even limited in the bandwidth they can use of the available on, so as not to interrupt normal operation. This means updates takes a lot of time and you need to have patience. Let it sit the night over next time.

phaze75 · April 29, 2025, 12:51pm

You might have misunderstood me. With “instantly” I meant that it worked on the first try. It still needed the full timespan (several minutes) while also slowly progressing from 1% to 100% during the firmware upload to the device. After that the device rebooted automatically which it had never done before.

Sorry, but no, this has not been an impatience issue.

phaze75 · April 29, 2025, 1:13pm

There is even proof in the log.

2025-04-29 08:58:30.513 (MainThread) INFO [matter_server.server.device_controller] Node:10 New software update found: 3.5.0 on UpdateSource.MAIN_NET_DCL (current 3.3.0).

2025-04-29 08:58:30.540 (MainThread) INFO [matter_server.server.device_controller] Node:10 Re-Subscription succeeded

2025-04-29 08:58:40.498 (MainThread) INFO [matter_server.server.device_controller] Node:10 New software update found: 3.5.0 on UpdateSource.MAIN_NET_DCL (current 3.3.0).

2025-04-29 09:04:06.545 (MainThread) INFO [matter_server.server.device_controller] Node:10 New software update found: 3.5.0 on UpdateSource.MAIN_NET_DCL (current 3.3.0).

2025-04-29 09:08:13.536 (MainThread) INFO [matter_server.server.device_controller] Node:10 New software update found: 3.5.0 on UpdateSource.MAIN_NET_DCL (current 3.3.0).

2025-04-29 09:08:15.341 (MainThread) INFO [matter_server.server.device_controller] Node:10 Update to software version 9464

2025-04-29 09:08:15.490 (MainThread) INFO [matter_server.server.device_controller] Node:10 New software update found: 3.5.0 on UpdateSource.MAIN_NET_DCL (current 3.3.0).

2025-04-29 09:08:15.491 (MainThread) INFO [matter_server.server.device_controller] Node:10 Downloading update from ‘https://eve-updates.evehome.com/matter/eve_weather-r3.5.0+9464-matter-benc-enc-F6AD84FE-EDDE-4360-B2F6-42C471FD73D8.bin’

2025-04-29 09:08:15.626 (MainThread) INFO [matter_server.server.ota.provider] Update file ‘eve_weather-r3.5.0+9464-matter-benc-enc-F6AD84FE-EDDE-4360-B2F6-42C471FD73D8.bin’ downloaded to ‘/config/updates/10’

2025-04-29 09:08:15.627 (MainThread) INFO [matter_server.server.device_controller] Node:10 Starting update using OTA Provider.

2025-04-29 09:08:15.627 (MainThread) INFO [matter_server.server.ota.provider] Starting OTA Provider

2025-04-29 09:08:15.627 (MainThread) INFO [matter_server.server.ota.provider] Commission and initialize OTA Provider

2025-04-29 09:08:15.667 (Dummy-2) INFO [chip.ChipDeviceCtrl] Established secure session with Device

2025-04-29 09:08:15.921 (Dummy-2) INFO [chip.ChipDeviceCtrl] Commissioning complete

2025-04-29 09:08:15.921 (MainThread) INFO [matter_server.server.ota.provider] OTA Provider App commissioned with node id 990010.

2025-04-29 09:08:18.560 (MainThread) INFO [matter_server.server.ota.provider] Waiting for target node update state change

2025-04-29 09:08:18.709 (MainThread) INFO [matter_server.server.ota.provider] Update state changed from <UpdateStateEnum.kIdle: 1> to <UpdateStateEnum.kQuerying: 2>

2025-04-29 09:08:20.738 (MainThread) INFO [matter_server.server.ota.provider] Update state changed from <UpdateStateEnum.kQuerying: 2> to <UpdateStateEnum.kDownloading: 4>

2025-04-29 09:17:28.489 (MainThread) INFO [matter_server.server.ota.provider] Update state changed from <UpdateStateEnum.kDownloading: 4> to <UpdateStateEnum.kApplying: 5>

2025-04-29 09:17:29.837 (MainThread) INFO [matter_server.server.device_controller] Node:10 Marked node as unavailable

2025-04-29 09:17:29.837 (MainThread) INFO [matter_server.server.device_controller] Node:10 Forcing subscription timeout in 5s

2025-04-29 09:17:34.838 (Dummy-2) CHIP_ERROR [chip.native.DMG] Subscription Liveness timeout with SubscriptionID = 0x6355f8ba, Peer = 01:000000000000000A

2025-04-29 09:17:34.843 (MainThread) INFO [matter_server.server.device_controller] Node:10 Subscription failed with CHIP Error 0x00000032: Timeout, resubscription attempt 0

2025-04-29 09:17:35.838 (MainThread) INFO [matter_server.server.device_controller] Node:10 Subscription failed with CHIP Error 0x00000003: Incorrect state, resubscription attempt 1

2025-04-29 09:17:43.473 (Dummy-2) CHIP_ERROR [chip.native.EM] <<5 [E:7639r with Node: <000000000000000A, 1> S:47435 M:112111371] (S) Msg Retransmission to 1:000000000000000A failure (max retries:4)

2025-04-29 09:18:16.780 (Dummy-2) CHIP_ERROR [chip.native.EM] <<5 [E:25102i with Node: <0000000000000000, 0> S:0 M:152573919] (U) Msg Retransmission to 0:0000000000000000 failure (max retries:4)

2025-04-29 09:18:27.784 (Dummy-2) CHIP_ERROR [chip.native.SC] CASESession timed out while waiting for a response from peer <000000000000000A, 1>. Current state was 4

2025-04-29 09:19:09.966 (MainThread) INFO [matter_server.server.device_controller] Interviewing node: 10

2025-04-29 09:19:10.092 (MainThread) INFO [matter_server.server.device_controller] Node:10 Re-Subscription succeeded

2025-04-29 09:19:50.616 (MainThread) INFO [matter_server.server.ota.provider] Update state changed from <UpdateStateEnum.kApplying: 5> to <UpdateStateEnum.kIdle: 1>

2025-04-29 09:19:50.616 (MainThread) INFO [matter_server.server.ota.provider] Node 10 update state idle, assuming done.

2025-04-29 09:19:50.616 (MainThread) INFO [matter_server.server.ota.provider] OTA update finished successfully

2025-04-29 09:19:50.616 (MainThread) INFO [matter_server.server.ota.provider] Cleaning up OTA provider

2025-04-29 09:19:50.616 (MainThread) INFO [matter_server.server.ota.provider] Terminating OTA Provider

Check out the bold formatted lines in the log. When timing out it had never reached <UpdateStateEnum.kApplying: 5> because it had never finished the upload to the device.

iChris · April 29, 2025, 7:41pm

I am experiencing the same issues with several Eve weather integrated in HA.

phaze75 · April 29, 2025, 7:51pm

Even though it shouldn’t make a difference: have you tried to start the update directly within the node?

iChris · April 29, 2025, 8:05pm

Unfortunately, I don’t know what exactly you mean.

ryrun · April 29, 2025, 8:24pm

I’m having the same issue. The Eve Energy update to 3.5 went through without any problems though. Maybe there’s something wrong with the 3.5.0 update for the Eve Weather?

phaze75 · April 30, 2025, 6:09am

Try to start the firmware update with this button directly within the Eve Weather Node on HA’s Python Matter Server.

Before you do that check your “Transmit Power” setting for “Eve Weather” within your “Eve App”. It is usually set to “Default”. For the update I had set it to “High”.

Again, as I have mentioned before, technically this shouldn’t make any difference. However, after 20+ frustrating tries, starting the update directly in the node worked for me. It probably has been pure luck, but it is worth a try.

phaze75 · April 30, 2025, 6:14am

I don’t think there is an issue with the update. As soon as you manage to upload the firmware package to the device, everything is fine. The issue seems to be with the upload procedure itself. But this is only an educated guess.

PixelPW · April 30, 2025, 8:28am

This solved my problem. I started the update as described through the Matter Server. I have not changed the “Transmit Power” to “High”.

Good start for Eve works with Home Assistant

Turd.Ferguson · April 30, 2025, 6:58pm

I’ve been fighting with this for a few days. Update process kept getting stuck at different points and would not complete. I messed with a bunch of different things so I’m not sure what actually did it but here’s the sequence of events that got it working.

set transmit power to high on the sensor and bring it into the house near the the thread router
unplug all Apple thread border router devices on network (my primary thread border router is an open source device)
remove battery from eve weather
restart Matter Server (settings, add-ons, Matter Server, restart)
reinstall battery in Eve Weather (you can look at the “log” tab on Matter Server to see everything come up and rejoin the network)
start the upgrade. Doesn’t matter where you start it from it calls the same function.

Progress % should increment one about every 4-6 seconds if it stops for more than 10 seconds it’s probably stuck.

I had to do this several times - it would get stuck and crash out eventually. Last time it got stuck at 94% but when it refreshed after timing out the Eve Weather came up with the new firmware version.

Process is definitely janky and felt a bit like jiggling the flush handle until the toilet stopped making the noise….but it DID eventually work with a bit of coaxing.

Biggest things I see changed so far:

battery level WORKS now!
barometric pressure which was lost when I converted to Matter is now back and reporting air pressure!

Hofst01 · May 1, 2025, 2:55pm

Had the same problem. Tried many times from the standard HA interface. It also worked for me to use the update button in the node screen from the matter server addon. Thanks for the suggestion!

phaze75 · May 2, 2025, 6:04am

I am not sure the update fixed the battery levels. At least not for me. Since the update (red arrow) after which the battery level jumped to 100% and shortly after dropped back to 75%, the battery -running my device already for about 4-5 months- seems to be miraculously recovering. Today it reached 100% again, which -of course- cannot be true. See below:

The “miracle recovery” is also reflected in the voltage levels:

Does anybody else experience this “miracle”?

phaze75 · May 2, 2025, 6:52am

After taking out the battery for 5 minutes I still get the same voltage and percentage readings. Further, I assume that after updating to 3.5.0 the device is somehow smoothening the readings. The temperature drops during the night are not reflected in voltage readings anymore - which is wrong. With lower temperatures the battery voltage always drops. However, comparing my battery readings to the typical discharge curve of a CR2450 battery the actual values make more sense:

Nevertheless, I can’t believe that my battery is capacity wise still “almost new”.

Turd.Ferguson · May 2, 2025, 12:23pm

You may be right. I switched out a few batteries I had and the battery level behavior is weird. Maybe “fixed” was the wrong word. The behavior is certainly different but it may still not be accurate.

Hofst01 · May 3, 2025, 7:47am

I had the same “miracle”. After the update, the battery level was 80%, which could be logical. But now it is back to 100% what it was before too. Strange.

phaze75 · May 3, 2025, 10:09am

The percentage reading is one thing, but the fact that the voltage went up is very strange. So, either the reading has been wrong before or it is wrong now. I assume it is the second possibility.