Yesterday, a firmware update for TRVZB was released. Since not long ago the update process in eWeLink Web (3.20.0) for M5-1C-86W went surprisingly smoothly and was completed successfully, I decided to see how it would look with a Zigbee device connected to NSPanel Pro (fw 4.1.1). The update started, but after some time I saw this on the screen:
At the same time, messages about failure and ongoing update were displayed.
Clicking Retry led to the same situation repeating. Clicking Cancel caused the update to freeze the Zigbee controller in NSPanel Pro. All Zigbee devices went offline, both in eWeLink Web and in the eWeLink App. Using the Reboot option in NSPanel Pro (since everything except Zigbee was working normally) did not improve the situation. Only toggling the power restored the Zigbee controller’s operation in NSPanel Pro. This time I launched the update in the App. It started and after several minutes finished successfully. Meanwhile, eWeLink Web was showing messages inconsistent with the actual progress. The conclusion is that eWeLink Web still suffers from problems with updating device firmware. Since no WiFi device update was available at that time, it cannot be determined whether the described situation is limited to Zigbee. I sent feedback from the panel. Please check whether this was an unfortunate coincidence or if there is indeed a bug in the software.
“By the way, take a look at why clickingShare your ideasin eWeLink Web opens this:
Personally, I haven’t experienced any problems updating via the web so far, but I don’t have many devices like you probably do. So, perhaps these are device-specific issues + the web, hmm…
My devices refused to update if they didn’t have internet access on port 8088. One also requests port 8080, and all of them, of course, require 443… TCP.
When I started using eWeLink Web, I hoped that with the addition of the Firmware Update function I would finally be able to update without draining my phone’s battery. Unfortunately, while displaying the currently installed and available versions works very well, the updates themselves are sluggish. Sometimes they succeed, sometimes they don’t. This is especially true for Zigbee. Recently, I updated temperature sensors. One went flawlessly, but the other failed, and I had to use my phone.
However, the latest situation surprised me, because I didn’t expect the Zigbee subsystem in NSPanel Pro to crash after an initially smooth process. It’s probably not related to ports, since the update wouldn’t have worked in the App either. In my opinion, this may be a matter of time limits. Perhaps you know what, if anything, differentiates the way updates are handled in Web versus App?
From what I remember, I haven’t had any problems with updates lately, and I’ve been doing everything through the web, not the app. I don’t think there’s a technical difference, though I don’t know. You’d have to ask eWeLink.
You clearly have a problem, but how can diagnose it… Hmm.
It might be related to the ZigBee device that supports the sensors. I don’t have NSP, so maybe that’s the difference…
Have you tried a different browser? Maybe something’s being blocked, an add-on, or DNS filtering. Although the likelihood is low.
My 02WDs are currently on version 1.1.0, and I don’t see anything newer. I’ll be more careful with future updates to see if any errors appear.
The only thing I remember is that when I first started using the web version, I had a few problems with updates. It would start and run, and after a while, an error would pop up. But if I remember correctly, after allowing communication on port 8088, it seemed to work fine. At least I don’t recall any problems in recent months.
But if the NSP is crashing, something is wrong deep within the Sonoff/ewelink ecosystem and the updates are not working correctly.
