After updating the NSPanel Pro firmware to version 3.7.0, the problems started. The device occasionally hangs and stops responding. Randomly, the CUBE unexpectedly restarts. There are problems with Zigbee. NSPanel Pro loses connection to some or all end devices. Attempting to add Web Shortcut (this new feature) ends in an endless search attempt. With automatic search mode enabled, NSPanel Pro stops responding!
Temperature readings from Zigbee sensors are transmitted incorrectly. Instead of -0.7 it is 0. -7 (for example, on NSPanel). Descriptions and messages are truncated and not complete. It is difficult to understand the content. The responsiveness of the vertical slide has clearly worsened.
The screen saver generally does not start, regardless of the set time. Only sometimes does it start and it is not clear what this depends on.
@ward Version 3.7.0 is, in my opinion, the worst version published so far. Embarrassing.
Feedback for device 1001ea2549 has just been sent.
good morning, I have also noticed similar problems, the new update (3.7.0) is very unstable, sometimes it freezes during restart, sometimes the screen remains on even if the shutdown time is set, I also ask you to restore stable operation.
If you have a lot of Wi-Fi devices, especially a lot of matter devices, nspanel starts to work unstable. the device cannot process the information and hangs. if the device manages to diagnose the error, it will be able to restart. otherwise, only disconnecting the power helps.
Sonoff has been looking for a solution to the problem for several months, but it may not happen soon. Sonoff recommends setting the screen to sleep for 5 minutes. Frequent waking up of the screen causes a glitch.
I had the same issues and I’ve reported to the support team.
I decide to restore the device and after that the NS Panel pro automatically upgrade to 3.7.0 version. No more issues after this. It passes one week and so far so good.
U mnie dokładnie było tak samo niestabilna praca, gdy nagle NSpanel pokazał że jest nowa aktualizacja. Jest tylko jedno ale nr wersji zainstalowanej to 3.7.0 nr aktualizacji 3.7.0, ale włączyłem niech się zaktualizuje. Wynik jest taki że nadal trochę “wariuje” ale zdążą mu się to żadziej. Mam nadzieję że Sonoff coś z tym zrobi bo mimo tego ż problemy nie występują tak często to jednak są a to nie jest przyjemne.
As has been said, NSPanel Pro has stability issues (lock ups, unresponsive display, intermittent unresponsive black screen, random reboots, crashes) resulting in multiple issues with its sub devices, particularly on mesh networks with multiple Sonoff devices. Unfortunately in my experience, this has been present for some time, long before 3.7.0. In my case Sonoff were not able to fix this.
The workaround is to run the NSPanel Pros on a separate WiFi network from the other devices and also remove all sub devices and add them to zigbee bridge pros instead. The dedicated zigbee hubs are much more reliable as they don’t have to run the display functions of the NSPanel Pro. This fix has worked for 4 NSPanel Pros.
It can be expected that it will take some time to determine the causes and rectify the errors. Let’s hope it’s not quickly and under the influence of ‘ringing alarms’, as this will most likely only make things worse. A reasonable option would be to revert to the previous version, which had its faults but at least worked without random crashes. Only the dev team can prepare such an upgrade, which is in fact a downgrade. Undoubtedly, this step will heal the stalemate with 3.7.0.
I’m not sure if rollback is ok for NSPro, most models of SONOFF do not support firmware downgrade via OTA but I will talk to the team about such a possibility.
A note on the sidelines of the 3.7.0 release is that the dev team is once again releasing a firmware version with so many bugs that it should be deeply embarrassing. Are there no testers at your place? No one checks the software before release? This is hard to believe, but the facts strongly support such a perception.
This is not the first time this has happened. It’s time to rethink how to do an emergency downgrade via OTA or get on with robust testing of new versions. What’s the point of rushing the untested novelties? Who needs it?
(IRONY).