Message “NSPanelPro is not responding” shown again, aprox. 20 hours after last reboot. I have choosen “Close app”, it restarted. Feedback submitted.
(Device ID: 10022022ca)
“NSPanelPro is not responding” again, after aprox. 6h of usage. Feedback submitted again.
@Milk: Zigbee seems ok as my nsp pro will still get the temperature on its screen but wifi seems working somehow, but in HA nothing is visible (neither temp sensor nor the panel itself), after a reboot all seems ok for about 1-2 days. I sent you logs again unfortunatley after the reboot.
best
clem
@Milk The drops in connection are getting worse, but the WIFI and Zigbee on the panel itself seem to be ok. A restart of the NSPro will restore everything instantly. I just found this posting here(NSPanel Pro 4.3.0: Zigbee stack becomes unstable, devices randomly go offline and MQTT bridge stops working); the problem I described here for 4.4 seems to be old and not yet resolved.
best
clem
I’ve reviewed the logs. The unresponsiveness is caused by network instability, which leads to occasional timeouts when requesting device data. In such cases, you can click “close” or “wait.” If the network is stable, it won’t affect the use of other functions. Additionally, we will optimize this issue in the version scheduled for April 8th.
We have identified the issue, which seems to be related to your MQTT network. We are currently trying to reproduce it. If we can successfully reproduce it, we will send you a version with the fix.
@Milk thanks for your reply, I seem not to be the only one to have this problems… I hope there is a fix for that in the near future….. if there is anything i could try please let me know.
best
clem
Hi, we’ve identified the cause of this issue — it’s due to network changes that cause your MQTT connection to drop and fail to automatically reconnect. We’ll optimize this in the next version.
@Milk: thank you very much. Can you provide me a test version as soon as the optimization is ready?
Thanks
clem
1 Like
Thank you! Looking forward next release.
Btw, I recently added Scene Swich R5. After first install, it reported last press repeateadly, even through night when nobody pressed any button. Quite scary, if lights go on/off. After NSPP restart it seems to be OK now (I am not on site), will investigate more in next days. Hope it was some mess after first configuration.
@Milk, any news on when the optimization will be available to test? The Zigbee drops are unfortunately continuing 
thanks
clem
New bugfix should be available today, if I remember correctly…
Also looking forward to fix terrible device disconnections and fix for Scene R5, which does not work (fantom/random presses). Had to delete the device from NSPP.
@clem_z Yes, this version is expected to be released today.
I recall that you mentioned suspecting an error in the initial configuration. If there’s no indication of a configuration error, could you please let me know the specific time the issue occurred and share the NSPanel Pro logs?
@Milk thanks for your answer, is it a normal “beta” update or pushed especially to the customers with the zigbee problem for initial testing? For the moment, I got no notification/possibility to update.
Thanks
Clem
@clem_z Just checked now, and updating while i write this post. You have to re-enroll to the beta updates on NSPanel Pro Beta Testing Program
Sw 4.4.6 installed. Problems with zigbee are persisting. Really clear amateurism.
I’ve created a dedicated feedback topic for 4.4.6 version, can you please share your feedback there? So we can track and report issues in one place.
1 Like
May I ask — after upgrading to version 4.4.6, are your sub-devices still offline and unable to come back online? Does restarting the NSPanel Pro bring them online? Please provide your feedback and logs as soon as possible, and also send me the NSPanel Pro device ID separately.
Problem continued even after restart, so I had to delete R5 from the NSPP. As I am on v.4.3.0, I plan to upgrade do 4.4.6 and will give it a try - pair it again and see how does it work.
Sure, after you give it a try, please let me know the results along with the corresponding log timestamps.