Hi, where is this “Screen OFF” setting? It’s some HA add-on?
No, you can now set the screen off time directly in “Advanced Settings” on the NsPanel. For example, 5 minutes. Then the display will turn black after 5 minutes and a tap on the display will wake it up again. Surely something can be built that HA can control.
Oh, didn’t know about this “Advanced Settings”. Found it, thanks!
Indeed, I confirm the screensaving now works ![]()
In addition, the Home Assistant integration “Sonoff” can now also control the display on the 86 model. However, this only works if no other app is running on the NsPanel. In other words, Home Assistant can only turn the display on and off directly in the NsPanel app. If Home Assistant is running on the NsPanel, it no longer works. However, Android ScreenOFF still works.
Home Assistant, through the Sonoff LAN integration, does not lose the ability to control the display, and in fact this is not a bug but a natural limitation: either you use the original firmware with the Sonoff LAN integration, or you use F-Droid, where display control works differently. Adding Android ScreenOFF into this explanation is misleading, because it’s a completely separate mechanism and has nothing to do with the Sonoff LAN integration in HA. Besides, the ‘Screen’ option in Sonoff LAN does not actually turn the display on or off, but rather activates or deactivates the screensaver, which is not the same thing. Here, screensaver control takes effect immediately.
The 4.1.1 update, the 86 NsPanel - froze during install. Devices are in eWeLink seen as connected, so it communicates somehow, but after “install” I see just the rotating circle. It already lasts for few hours, so I will try to unplugg it from the power source. Hope it will not brick the device. ![]()
It happens occasionally. The reason is unknown, though there must be one. If you wait, a message usually appears about the application not responding or a prompt asking whether to close the eWeLink app.
It has happened a few times, and toggling the power helped without any consequences.
I’ve just updated to 4.1.1 and set the screen timeout to 5 minutes in advanced settings…. But screen is still showing the HA app after 15 minutes.
is there something else i need to do to have the screen turn off ?
steve
Please make sure you haven’t enable Keep screen on in Home Assistant companion app -> Settings -> Companion app -> Other settings.
If not, then please take several photos of the Advanced Settings of your NSPanel Pro, so we could look into it.
Thank you!
I had left ‘keep screen on’ checked
Unchecked it and the screen is now sleeping as it should ![]()
After many hours of waiting with no progress I upnlugged the panel and did upgrade again - successfully completed, everythink is OK now. As you sad… Thanks.
Looking forward for Termostat revamp.
You’re welcome ![]()
Just purchased the NSPanel 120 to use with home assistant. I love the possibility of having the homeassistant app on it, it works really well.
However I see 2 main issues for now. It seems eWeLink app connection is tied to the NS Launcher therefore when home assistant is configured as launcher the app see the device as offline.
Additionally when Home Assistant is open the screen doesn’t turn off. Is there a fix for the screen part?
Thanks
This is great! The screen timeout finally works — and we don’t even have to wait for 4.2.0
The only thing I’ve noticed is that we still can’t wake or sleep the screen from HA or eWeLink while HA is running.
It seems eWeLink app connection is tied to the NS Launcher therefore when home assistant is configured as launcher the app see the device as offline.
This issue will be solved in v4.2.0. Please refer to NSPanel Pro Roadmap and Co-Created Future
Additionally when Home Assistant is open the screen doesn’t turn off. Is there a fix for the screen part?
- Please update to
v4.1.2. - Then set
Sleepand/orScreen saverinTop drop-down menu -> Settings -> Advanced Settings -> Display - Make sure
Keep screen onis disabled inHome Assistant companion app -> Settings -> Companion app -> Other settings.
The only thing I’ve noticed is that we still can’t wake or sleep the screen from HA or eWeLink while HA is running.
I don’t quite understand it. Isn’t it the same as Home Assistant is open the screen doesn’t turn off?
Ok, so this is the case.. ![]()
With the NSPanelPro app in the foreground (the default UI):
-
Settings > Displayworks as intended.
-
Turning on and off the screen via
ScenesineWeLink appworks as intended.
-
Turning on and off the screen via
SonoffLANintegration inHome Assistantworks as intended. (Which I know is handled the same way as via eWeLink anyways).
With the Home Assistant app in the foreground:
-
None of the above works. The screen timeout doesn’t follow the
Settings > Displaysetting; and we have no way to control the screen viaScenesandAutomations. -
Advanced Settings > Display > Sleepdoes work, which is great! So now the screen turns off after the set timeout even with Home Assistant running. Controlling the screen viaScenesandAutomationsstill doesn’t work.
Hope this helps.
And while on this - may be an option to take a Screenshot of NSPanel’s screen via the eWeLink app? ![]()
Got it. Thank you very much for the detailed explanation.
The reason is:
- The
Auto-LockinSettings -> Displayof NSPanelPro (used asHomeApp) is totally different from theSleep/Screen saverinSettings -> Advanced Settings -> Display. Auto-Lockis an Application-level screensaver which only works when NSPanelPro App is at the frontend.Sleep/Screen saveris a System-level screensaver which always works, but can not be managed through eWeLink cloud or Open API.
We’ll see if we can merge above 2 into 1 which should be easlier to understand and use.
And while on this - may be an option to take a
Screenshotof NSPanel’s screen via the eWeLink app?
Yeah, I want this too. @JoJo our product manager of NSPanel Pro said that no one need this feature except me. Now I can say to her that I’m not alone ![]()
Of course, thank you very much for considering all of our feedback.
That’d be great indeed!
Yes, @JoJo, come on, WE need this!
Jokes aside, if not hard to implement, this would be a nice and useful feature especially now when we all test and troubleshoot these new and awesome features ![]()
It’s not about liking or not liking your comments. To be honest, I’ve usually grown the habit of ignoring your long and often out-of-context replies. What matters to me is that the dev team likes and considers my feedback.
What I genuinely don’t understand is why you keep responding to other users’ posts on behalf of the dev team; and in such a negative, ironic, and ultimately counter-productive way. Especially when, in most cases, the dev team (thankfully!) doesn’t even share your opinion.
We’re all here to offer feedback and ideas, and it’s great to see that the developers are actually listening closely. It would be much more helpful if we could keep the discussion constructive. And positive.





