Hi, please include me in the beta testing program.
Id ns panel pro: 10026d2343
Hi, please include me in the beta testing program.
Id ns panel pro: 10026d2343
Thank you very much for your interest in NSPanel Pro Beta Testing Program. Please follow the instructions below:
Please let me know if you encounter any issue. We are here to help.
Hello, I just installed beta version 4.2.2 which is very good and significantly improves Home Assistant.
However, my screen doesnât go to sleep when Home Assistant is running by default ![]()
NSPanel has just been updated to firmware 4.3.0 and it should allow, among other things, putting the screen to sleep even with Home Assistant; I just need to figure out how ![]()
The problem with software 4.3.0 is that it doesnât allow you to turn the light on and off directly from the main screen. You have to go to the sub-panel first, and then itâs possible. Itâs a good thing I didnât update my main panel, because my wife would already be making me install a regular switch.
After upgrading to version 4.3.0, the screen-off settings under Settings â Display will automatically apply to all pages and take effect globally without any additional steps. If your current settings are not working, please send me a screenshot of your current configuration.
Is your switch a multi-channel device? If it is a single-channel switch, version 4.3.0 allows you to control the device on/off by clicking the device icon on the card.
Panel 86 pro. Until now, you could turn on the light by touching the area on the main screen. Now, touching this area takes me to the next screen, where I can only turn the light on or off.
Even if itâs a single-channel device, having to aim for a tiny icon instead of the whole button is a huge step backward. It requires too much precision and makes the process very slow. The previous version allowed me to tap anywhere on the button to toggle the device. This new design is impractical and makes the NSPanel Pro 120 feel useless for quick daily control.
Please refer to this post for enabling Sleep and Screen saver: NSPanel F-Droid auto start HA - #4 by MichaelLearnsToCode
If you encounter any issue, please let me know.
Hi there, @jackon
Thank you for your honest feedback. We understand that the new interaction in version 4.3.0 might be confusing, especially if you were used to the previous way of controlling your devices. Weâre sorry for the frustration this has caused.
To clarify, you can still turn your lights on and off directly from the main screen. Please try tapping specifically on the deviceâs icon (in the top-left corner of the card).Tapping anywhere else on the card will open the details page.
We made this change to allow faster access to both device control and details with a single tap. We realize this requires a slight adjustment. Your experience is very important to us, and weâve shared your feedback directly with our product team for review in future updates.
So in fact, after many tries, it still doesnât work, well it does, but only half.
So already if Iâm not on home assistant it works perfectly.
Then on the first launch of HA it works, however if I press on the screen to redisplay HA it no longer works, a little, as if the function was no longer reloading (equivalent in home assistant of single / restart). I should point out that in HA, I did not activate âKeep screen onâ.
If necessary, yes, I can send my config.
I just sent a log on your NSPanel Pro device.
Hi, @serkandemir1989
Thank you for your detailed feedback. We understand your concern about the need for precise tapping. This change was designed to better separate quick control from device details, but we understand your frustration.
Your experience is very valuable to us, and we will carefully consider your feedback.
For now, you can still control the device by tapping the icon in the corner of the card. We sincerely apologize for any inconvenience this adjustment may cause.
Thank you for your response, but I must emphasize that having to aim for a tiny icon is not a practical solution for a wall-mounted control panel.
This isnât just a matter of a âlearning curveâ for the primary user. Think about guests, children, or elderly family members who do not use the device every day. They expect the entire button to work, and they wonât know they have to hit a specific small icon. This change makes the device confusing and difficult to use for anyone visiting my home.
My suggestion is simple: Please make this a selectable option in the settings. Let the users decide if they want the entire button to act as a âDirect Toggleâ or to âOpen Detailsâ.
Smart home technology should adapt to the userâs needs, not force the user to adapt to an inefficient design. Without this choice, the NSPanel Pro 120 loses its primary value as a quick and accessible controller. I look forward to seeing this customization in the next update.
Hello. I prefer the new light cards as previously, in my situation, tapping the card wouldnât do anything. I had to long press the card to get to the details page, where I could toggle the light. So Iâm happy with it as it is, but Itâd also be OK if a quick tap on the card toggled the light, and a long press opened the details page.
All of my lights are synced from a Hue bridge via matter. Currently, the two lights at the top say âALL OFFâ or âALL ONâ, but there is only one bulb in each location. Do you know why this is? Is it possible to set up a group of lights? That would be very useful to me. Also, tapping the icon doesnât work for those two lights, I have to go to the details page to toggle them.
Iâm continuing my tests: If I set up an automation in the eWeLink app that turns off the screen when the front door sensor closes, then the nspanel will go into standby mode with the clock displayed, as configured on the device. But if I manually wake the nspanel from standby mode, it wonât go back into standby. However, if I open the door again and close it, it will go back into standby mode with the clock displayedâŚ
Another bug Iâve detected is that when I enable the locking feature in the nspanel settings, all my connected devices are no longer recognized as soon as the nspanel locks. I donât think this is normal.
I set the screen to stay on all the time, but it still turns off after a while. Why? Is there a way to go back to version 4.2.2 of the software?
Hi, could you check the settings in these two locations:
Hi, @Stophammer
Thank you for your detailed feedback! We sincerely apologize for the inconvenience this has caused you.
To better locate the issue, please help confirm:
Scenario A : After tapping the card icon, there is no response on the UI (e.g., state does not switch), but does the actual light turn on/off successfully?
Scenario B : After tapping, the light device does not respond at all, and there is also no change on the UI?
To further analyze the problem, please assist in providing logs from your NSPanel Pro device :
Top drop-down menu -> Settings -> About -> Feedback -> Submit .