Thank you.
Sorry for the occasionally sharp criticism — perhaps a bit too sharp at times. It’s not my intention to offend anyone; I genuinely appreciate and notice the work you’re doing. That said, I don’t think there’s much point in sugar‑coating things or putting on artificial smiles. It doesn’t really help solve problems. And after all, I care about fixing them just as much as you do 
Again?
Haha..
, That was the first thing I tried. It doesn’t recognize 4.2.0. Too bad, I’ll wait to see if Matter 2 supports clustered shades. I’m eagerly awaiting more supported devices. 
After restarting it’s ok. It just doesn’t see the next version 4.2.0 
, a manual attempt to check for updates doesn’t work. Only “checked” message.
Hi,You can join the whitelist via the Beta tool to access the latest version. : NSPanel Pro Beta Testing Program
If you have already joined but still haven’t received it, could you please share your device ID with me separately so I can investigate the cause?
Hi,
According to the logs, your NSPanelPro is experiencing frequent disconnections and reconnections (averaging about once per minute). Have there been any recent changes to your network? We recommend checking your WiFi settings and improving the wireless signal strength for the NSPanelPro to see if that resolves the issue.
Also, thank you for your feedback. In theory, frequent device disconnections should not cause a crash. This has been identified as a bug. We will optimize the issue of NSPanelPro crashes caused by frequent connection changes in the upcoming version 4.3.0.
I’ve just reviewed the router logs. The average signal strength is –52 dBm for NSPanel Pro. In the WiFi section, the only entry related to any interruption or signal loss is the one from December 12: “5‑GHz band cannot be used for 1 min. on the selected channel 36–64 (5.180–5.320 GHz) because of check for higher‑priority users (e.g. radar).” I also checked the Dongle‑M log, which connects to the same router and is located about 1 meter vertically from the NSPanel Pro. No communication interruptions were recorded in recent days.
Moreover, the described issue started immediately after updating the firmware to version 4.2.0. It had never occurred before. Other users have reported similar or identical events, but they never affected my panel — until now. That’s why I have reason to believe there is a bug in the firmware.
Based on the log analysis, your NSPanelPro experienced frequent network changes between 07:00 and 08:00 on the morning of the 14th. (If you need the specific offline timestamps, I can privately share the detailed times or a screenshot from the logs.)
Regarding the issue you reported as occurring only in version 4.2.0, I have confirmed with our development team that this is coincidental. The problem has actually existed for some time. It is a probabilistic issue that occurs when the device receives frequent long-connection message reports. As mentioned, because the issue is triggered probabilistically, it may not have manifested in previous versions.
Thank you for the clarification. I’d like to add one more important point.
Other devices connected to the same router do not experience any disconnections. There are no symptoms that would suggest any instability on the network side — and if such instability really were the cause, I would have noticed it sooner or later, for example while listening to internet radio. A stream player would eventually exhaust its buffer or drop the connection, but this has never happened.
From what you wrote, it’s clear that the team is already aware of this issue and that it’s related to the device‑side handling of long‑connection message reports. That’s not a network‑side symptom — it’s behavior coming from the device or firmware.
Given this, and considering that the issue appeared immediately after updating to firmware 4.2.0, it still seems likely that the update increased the probability of the problem or changed the conditions under which it occurs. I’d really appreciate if the team could take another look at whether something in 4.2.0 might be contributing to this behavior. I’m happy to provide more logs or run additional tests if needed.
Understood. I have received this important information and will relay it to my colleagues immediately. Once the new version that resolves this issue is ready, I will promptly notify you to upgrade to the latest version for verification.
Thank you. There’s no rush, so take your time to exercise it deeply. It’s perfectly possible to live with this, but it would be lovely to finally get rid of that bug
A moment ago, the panel system restarted. I immediately sent the log and checked in detail how the situation looked for other devices. The router did not record any interference in its logs, and the Dongle‑M shows no communication interruptions (it connects via WiFi) with ZHA. As you surely know, any — even very short — interruptions in Dongle‑M ↔ HA communication cause cascading errors in ZHA and fill the HA logs with entries. There is nothing that would cast even the slightest shadow of doubt on the stability of the WiFi connection.
What you’re seeing on the panel is Touch Debug / Touch Overlay enabled at the firmware level, not in the Android system.
Fully Kiosk: Settings → Advanced → Show Touches → OFF
WallPanel: Settings → Touch → Show Touches → OFF
HA Companion (Android): Developer Options → Show taps → OFF Developer Options → Pointer location → OFF
It should work now. And seriously — stop poking those settings before something explodes 
Thank you very much. It helped. I actually managed to turn it on somehow through an open application in the background when I looked at the multitasking window that was open in the background.
I had big problem after update to 4.2.0 and opened a ticket 3days aqo, no response yet. After Upgrade OTA prompt in Ewelink app to version 4.2.0. I always got screen: NSPANEL pro stopped. Start the app again ?. The panel restarts every couple of minutes and then the same error notification is shown and I couldn’t do anything on nspanel . Eventually i made 5 times power off/on sequence and it reset to factory FW version, I then updated to higher version, the last offered was version 4.0.13 that I installed and when I selected additional update to higher version nspanel loaded 4.2.0, that now I do not want to install, I was hopping to get back to 4.1.X. but don’t get offered that version. I am afraid to install 4.2.0 again.
I’m sorry to hear you’re experiencing this issue. Could you please confirm if you have already submitted the NSPanelPro logs (via: Screen Pull-down > Settings > About > Feedback)? If so, would you mind sending me your NSPanelPro Device ID separately? With this information, we can efficiently pinpoint the cause.
Hi , I sent you private mesage with my Device ID and I just submmitted the logs over NSPANEL. But this feedback is now from fresh install to version 4.0.13, don’t know if problematic logs before reset are also kept and sent?
Thanks for help.
Sorry for the trouble.
We have identified the issue and will release a bugfix version within this week.
Hi great that you identified the problem and will solve it. I just could not do anything on NSPANEL as it was constantly rebooting and I could not go to settings to get logs out. thanks
