It’s great that 02DR2 finally made it.
And behold: –3.4°C shining proudly on the display.
Wow, it’s really cold outside. Keep warm and happy new year! 
1 Like
At this time of year it used to get much colder. Usually it hovers around –5°C, but among the more “memorable surprises” I still recall a brief –25°C 
Anyway, a light frost is still better than that eternal dance around zero, when everything keeps thawing and freezing like it can’t make up its mind. But for someone from the subtropical zone (yes, I mean you) this probably counts as an exotic natural phenomenon. That’s probably where the LL.L error came from 
Don’t worry though - once summer hits, we’ll catch up with Hong Kong standards and settle into those long, 35‑degree heatwaves. That’s just our climate saying hello.
Thanks for the New Year wishes - and the same to you! Although for the Chinese ones I’ll have to wait until February. And the Year of the Fire Horse might get interesting… if the zodiac tradition is to be believed.
1 Like
Now all we need to do is create a larger font or some clearer dot separation. 
1 Like
Hi, this issue has been resolved by SONOFF. The upgrade function for the 02DR2 device is now working normally. Please try upgrading again. If you encounter any issues, feel free to contact me again.
1 Like
Looks like you need to reconnect 02DR2 to have a successful upgrade. At least as far as NSPanel Pro is concerned. Otherwise, the issue is finally resolved by Sonoff, after the numerous attempts.
Regards
And now you can undestand, why are some of us furious about Thermostat and Central Heating.
It is snowing outside right now and temperatures between 0 to -5 st. C. are considered common here (Central Europe).
Happy New Year and thank you for ongoing support. Appreciate it.
1 Like
also @p.silhan
Yes, I think you are totally right. It’s 17°C outside at 9:44 p.m. in Longgang, Shenzhen, China. And that’s why we at eWeLink and SONOFF should talk more to our dear users to get better understanding of real use cases 
4 Likes
OTA update for SNZB-01M device not working on IHOST
Got it. We’ll update the progress at topic SNZB-01M_v1.0.5.ota [ Ihost Cube 2.8.1 OTA update error ]
The SNZB-02DR2 manual told me to install the latest firmware (1.1.0), so I clicked Update and updated to version V1.0.3, although the pop-up is now asking me to upgrade to V1.0.2 (see attached image).
I want to use the Windows interface for eWelink ( eWeLink Web ) and am a bit disappointed that the SNZB-02DR2 is still showing as “Not supported now”. (see image below).
The latest firmware version of SNZB-02DR2 is indeed v1.0.3, not v1.1.0. v1.1.0 must be a typo.
Regarding SNZB-02DR2 on eWeLink Web, I have checked with my colleague, she confirms that eWeLink Web will support SNZB-02DR2 in early Feburary.
Sorry for the inconvenience we caused.
Could you please confirm the firmware version shown for this device in the eWeLink app?
It is good to know that we can expect the eWeLink Web to support SNZB-02DR2 devices in early Feburary. Thank you.
Yes of course. The firmware version of the ZBBridge-U is 1.17.2, and the firmware version of the SNZB-02DR2 is V1.0.3.
There is no indication of the SNZB-02DR2 firmware in the eWelink web ( https://web.ewelink.cc/#/home ) as it simply says " Not supported now". The firmware version is shown in the Zigbee devices list shown when I log into the ZBBridge-U and also in the eWelink phone app, where the firmware version is also showing as v1.0.3 with a Plug-in version showing as 0.0.95.
When I first completed the online update to v1.0.3, I was getting a pop-up inviting me to upgrade from 1.0.3 to 1.0.2 . That message has now gone away.
Thank you for following this up. I quite understand that it takes time and work to get all these devices to work on different platforms.
A very difficult 4+ hours to install a SNZB 02DR2 on the NS Panel Pro
I have Ewelink v5.22
NSpanel V4.3
And (Finally) device firmware 1.0.3
So many things dont work correctly, and I see bug fixes are due shortly.
Sadly my view is that the level of testing prior to release is inadequate.
I think it would be better to set expectations of higher quality rather than faster delivery for software drips, since frustration runs high when you just run into the next function bug.
Im sure this will ultimately manifest itself by users avoiding early versions and delay purchase until bugs are ironed out and product is more robust and reliable.
Ive put my installation on ice for a month hoping that users less frustrated than me help clean up the code so that I can be a user instead of a tester.
Sorry for the issue. Are these bugs related to eWeLink App, or NSPanel Pro, or SNZB-02DR2 itself?
Hi
All three interact, I can’t see inside the code, so it’s diificult to be sure where the problem might be.
Difficulty updating software. This could be nspanel/zigbee implementation or device
On setup
- install device on nspanel by adding to Zigbee gateway.
- Device is added but fails repeatedly to update firmware (1.0.2 > 1.0.3).
- Delete device on Zigbee bridge
- add device to Ewelink directly
- Device is added
-
- update commences but reports failure three to four times, but if you persist and restart process it eventually works. This could be a sleep timer on device or server timeout or ??
- Once software is uploaded successfully. Delete device in app and re-instal via zigbee gateway.
- Device connects.
Misreported values. The expected graph for temp and hum performance does not appear
No data over following days but now appears to have been reporting for four days, likely due to nspanel reboot. I was attempting ( still unsuccessfully) to configure the nspanel screensaver screen and rebooted 2 or 3 times to attempt to read in a new config.
Nspanel connection
Need to re-enable the sync function between the nspanel and home assistant.
- Nspanel/home assistant/ sync zigbee subdevices
There are three model 02D thermostat and 1 model 02DR2.
The 02D devices seem to hold their sync status, the 02DR2 does not. I cannot replicate or cause this issue but will try again - or maybe wait for a couple of software drops and see if it gets ironed out.
1 Like
According to your feedback, I see that your device has been upgraded to version 1.0.3. Has this been completed successfully? If the issue occurred within the last two days, you can submit the NSPanel Pro logs. I will do my best to extract useful information from the logs.
Milk
Yes. device is currently 1.0.3
This was completed 17 Jan so outside your timescale. I can send logs if you wish but update has completed and they may not be useful now.
Regards
I’ve experienced the same issue. The device was added correctly, but the firmware update from 1.0.2 to 1.0.3 kept failing several times before it finally went through. So it’s not an isolated case.
It’s worth noting that battery‑powered devices often struggle with OTA updates, and this applies not only to this model but to many BLE/Matter/Zigbee devices in general. During an update they need to:
- stay awake much longer than usual,
- maintain a stable radio connection,
- avoid going into sleep mode,
- and operate on very limited power reserves.
If the battery is not close to full, or if the device aggressively manages sleep cycles, the update process can easily time out or fail mid‑transfer. That’s why multiple attempts are sometimes needed before the firmware finally installs.
So the behaviour is frustrating, but unfortunately quite typical for low‑power devices relying on short‑range wireless protocols.
1 Like