You mean the download progress seems OK, but the actual firmware was not updated?
Where did you update 02DR2 from? eWeLink App or Home Assistant ZHA or Zigbee2MQTT?
I still only see 1.0.2 as the latest. eWeLink 5.22.0 Android.
Yest, this is the case.
eWeLink app.
also @morgan
Sorry for the issue. Let me check with SONOFF staff and my colleague tomorrow (Monday).
2 Likes
Sure thing! Itâs not the end of the world 
BTW: No firmware update is visible in HA.
A new version 1.0.3 is available on github
I can confirm that the git pull request for 02DR2 v1.0.3 firmware is wrong. SONOFF staff is fixing it right now. It shouldnât take long.
Without unnecessary snark, it looks like the Sonoff staff isnât paying much attention to code correctness (a bug with displaying negative temperatures) or to preparing OTA updates. Theyâre stumbling from one mistake to another.
A shot in the foot, because this is a newly launched product and the first impression is what counts. I write this without any satisfaction 
1 Like
A bitter reflection, while weâre at it â Sonoff still doesnât provide any public OTA repository for its Zigbee devices. Itâs 2025, and the manufacturer still isnât publishing firmware in the standard Zigbee OTA format, with proper metadata, headers, and structure as defined by the specification, unlike most vendors who respect the open ecosystem. The Zigbee community has the tools, the infrastructure, and full support in ZHA and Z2M â the only thing missing is an official firmware source. Without it, Sonoff devices are effectively unmaintainable, because thereâs no way to update them in a standard, interoperable manner. For a manufacturer that benefits so heavily from Zigbeeâs popularity, thatâs a pretty poor standard.
1 Like
Actually, SONOFF does provide public OTA repository:
- For Zigbee2MQTT, SONOFF staff submits pull requests to GitHub - Koenkk/zigbee-OTA: A collection of Zigbee OTA files from time to time.
- For ZHA of Home Assistant, the URL is https://zigbee-ota.sonoff.tech/releases/upgrade.json
I am discussing with SONOFF staff to see if itâs OK for my team to take the responsibility of releasing Zigbee firmwares to Zigbee2MQTT and ZHA. Afterall, we at eWeLink will always have these firmwares because eWeLink users need to update SONOFF Zigbee devices from eWeLink App/Cloud.
2 Likes
Thanks for the clarification. Itâs great news that eWeLink is considering taking responsibility for publishing official Zigbee OTA firmware - that would really help clean up the situation and benefit the entire Zigbee community.
Just to explain where the complaints from ZHA users come from: even though OTA files technically exist, ZHA often canât match them correctly. Some devices donât have complete metadata, some firmware isnât published consistently, and ZHA ends up showing things like âFirmware: Unknownâ or no updates available at all. Thatâs why users get the impression that âthere is no OTAâ, even if some files are out there.
Thatâs why the idea of eWeLink officially and systematically releasing full OTA packages for both ZHA and Zigbee2MQTT is such a good direction â the community would really benefit from it.
1 Like
The update returned, proudly pretending to fix things⌠and somehow managed to make everything worse. It keeps flashing âavailabilityâ like itâs doing something important, something spins as if progress is happening, but absolutely nothing of value comes out of it. Just an endless loop of circles turning into squares and back again, a perfect little exercise in futility. And thatâs all we got from the soâcalled improvements 
Could you please take the trouble to take several photos of the issue you just described? So we could better understand the situation.
No problemo, I took a video.
The new firmware finally appeared and I was able to update both of my devices to 1.0.3.
My 02DR2s are connected to a ZBBridge-P (2.8.0) and Iâm using eWeLink 5.22.0 Android.
Once the app managed to see the new firmware, I clicked to update, which the app also announced. And then a long silence and a long something beganâŚ
Nothing else happens on the app side except for a constant message about the update process. On the bridge side, after a long period of inactivity, thereâs a lot of ZigBee activity, which looks different from typical traffic, which I suspect is the new firmware being uploaded.
But the entire process, from startup to completion, took about 20+ minutes. I donât know if itâs because of my weak signal or if the firmware is so largeâŚ
I had the eWeLink app running the entire time, though Iâm not sure if that matters.
Iâm currently running 1.0.3, and the devices are working and displaying the temperature correctly.
And after a long wait, in a galaxy far, far away⌠absolutely nothing happened. On my end it just snaps back to âUpdate Now,â as if thatâs the only trick it knows 
1 Like
@jam3
See if this helps resolve your update issue.
Turn on your phoneâs Wi-Fi and turn off mobile data, then launch the eWeLink app.
Nada 
The pull request for Zigbee-OTA (the one Zigbee2MQTT relies on) is just merged 1 hour ago. So it should work now. Otherwise, I would suggest you wait for a few hours. Let the cache expire before trying OTA again.
I finally managed to convince my SNZBâ02D R2 to download the new firmware - and honestly, it felt a bit like negotiating with a stubborn guest who refuses to join the party. In the end, the winning combo was: remove it from Zigbee, reset it, and pair it again with the NSPanel Pro. Only then did it graciously acknowledge that an update was available.
After manually searching for the update and confirming it, the process began⌠at the classic, glacial pace of a batteryâpowered peripheral that clearly has no intention of rushing on New Yearâs Eve. But it made it. It updated. It survived.
And since itâs below freezing outside, I could immediately check what appears instead of the mysterious âLL.Lâ. And behold: â3.4°C shining proudly on the display. Finally working exactly as intended.
So yes: new year, new firmware, new hope. Cheers to that!
2 Likes