All right, I have directed version 4.3.2 to one of your devices. You can try upgrading it now.
Thank you! Installed and now is everything working smoothly ![]()
So far, the update hasn’t reached me...
Hello,
First feedback from me. After installing version 4.3.2, my Zigbee devices were still offline, so I sent the log from my nspanel (10026d20b6).
Secondly, I wanted to know if there was a way to disable notifications every time a sensor is detected? This turns my screen saver back on every time and/or prevents it from turning off.
@Milk , here is the video of the issue. It basically appears on all my NSPanel Pro panels.
Device ID 1001f4546d , please refresh this device to obtain the latest version 4.3.2.
May I ask which device ID is experiencing this issue? Could you please submit logs from that device? I will work on identifying the problem ASAP.
This particular one was 100181f412.
Sorry, I am using version 4.3.2, but I cannot find the device details page on my nspanel.
I paired my devices in ewelink and not on the nspanel. Could that be the reason ?
Perfect, I found it. My problem was that yesterday I deleted the devices from this page, leaving only my connected socket, so it was no longer displayed. But I found it, fixed it, and it’s perfect. Thank you very much.
Have same issue here. My zigbee devices connected to NSPPro goes off-line for some time (from a minute to few hours). I am on 4.3.2.
Sorry for the issue. We thought v4.3.2 should fix the bug. Would you please submit a log on your NSPanel Pro device through Top drop-down menu -> Settings -> About -> Feedback -> Submit.
Any idea why this is happening? All my 7 NSPanel Pro panels are suffering from it. Sometimes it causes the Zigbee hub on the NSPanel Pro to turn off which put all the connected Zigbee devices to offline state → which turns into the malfunction of the thermostat of course.
It just happened now at around 8:43 am CET on 100181f40e (feedback submitted).
Sorry about the issue. Please submit logs on your NSPanel Pro device via Top drop-down menu -> Settings -> About -> Feedback -> Submit. We will identify the root cause as soon as possible.
That’s exactly what I did.
I apologize for this issue. I have reviewed the logs and identified the problem, which is currently being addressed. I will keep you updated as soon as there is any progress.





