Sonoff nspanel pro - cannot turn off the screen

[xionc666]

ha-paneld version

0.9.7-rc2

Panel hardware

Sonoff NSPanel Pro (86P / 120P, PX30 / rk3326)

What happened?

I could not install 0.9.6 (failing with pm discovery if ha-paneld is installed), so I just installed 0.9.7-rc2. Downgrade from UI to 0.9.6 is not working btw.

Anyway, I cannot make the screen to turn off automatically. I do not need anything fancy - just after 1 or 2 minutes of inactivity to turn off.

When I turn on this settings:

it never learns anything.

When I turn off this setting:

and enable auto screen off in android settings, it only dims. Never turns off.

I also set "keep_awake" to false via API, but it did not change anything.

Is the app not capable of disabling the screen completely? Do I need nspanel_pro_tools_apk for that?

Steps to reproduce

No response

Diagnostic dump (/diag)

ha-paneld diagnostics — 0.9.7-rc2 (build 613)
[captured] 2026-08-29T00:44:03.184+02:00 uptime=2h1m

[panel]
ha-paneld=0.9.7-rc2 (build 613)
Android=8.1.0 (API 27)
Firmware=1.5.6
Device=rockchip px30_evb (px30_evb)
CPU=4 cores · arm64-v8a · rk30board
RAM=1.9 GB total · 1.3 GB free
Storage=7.8 GB eMMC · 2.9 GB free (data)
Display=480×480 px · logical 160 dpi
System WebView=com.android.webview 138.0.7204.63
HA Companion=not installed
MQTT state=connected · TCP/IPv4 · last-ok 20s ago · last-auth 6198s ago · auth-ok · family Automatic (next IPv4)
Security mode=Relaxed
Keep panel responsive=on · power locks held
Prevent idle dim=off · timeout 60s
Android dashboard lock=off
LED=none
Nav actions (a11y)=yes
Navbar=Off
Zigbee=vendor-native · running
Relays=none
Network ADB=active (5555) · external — not persisted by ha-paneld
Audio playback=idle
App database=740.0 KB used · 1.2 MB on disk · schema 14
Product version=NSPanel86P_1.1.7
Local-state sync=20s ago · brightness 2→117 · 81s ago · backlight →2 (firmware dim) · 501s ago · brightness 110→117 · 621s ago · brightness 116→110 · 801s ago · brightness 255→116 · 861s ago · backlight →255 (firmware dim) · 921s ago · brightness 255→116 · 981s ago · backlight →255 (firmware dim)
State convergence=38 channels · 0 dirty · 0 in-flight · 12 unknown · ack 656/0 · pending none

[build] fingerprint=rockchip/px30_evb/px30_evb:8.1.0/OPM8.190605.003/100509:userdebug/test-keys
board=rk30sdk product=px30_evb hardware=rk30board abis=arm64-v8a,armeabi-v7a,armeabi
[boot-security] verified=green flash=locked vbmeta=unknown build=userdebug debuggable=yes
[env] selinux=0 su=true write_settings=true a11y=true daemon=true shizuku=manager_missing evdev=stopped/none ledjni=false
[display-sizing] android_base_logical_dpi=160 current_logical_dpi=160 override_dpi=none font_scale=1.0 profile_recommended_dpi=160 profile_recommended_font_scale=1.0
[renderer] mode=builtin state=checking outcome=unobserved fault=none detail=none recovery=none transport=http address_family=automatic observed_age=1h42m
[zigbee-health] state=unknown layout=unknown package=- joined=unknown role=- gateway_cpu=3 guard_cpu=0 restarts_10m=0 containment=none recursive_watchdog=true
[storage-health] state=healthy pressure_state=healthy usable_bytes=2923180032 total_bytes=3606081536 used_percent=18.937494817643525 database_bytes=151552 wal_bytes=0 sidecar_bytes=32768 page_size_bytes=4096 page_count=37 freelist_count=0 schema_version=14 quick_check=ok checked_at=1787949756433 failure=none
[power-safety] state=safe keep_awake=true wake_lock=true wifi_lock_required=true wifi_lock=true prevent_idle_dim=false screen_timeout_ms=60000 interactive=true power_source=ac plugged_mask=1 stay_on_mask=15 stay_on_effective=true device_idle=false doze_exempt=true screen_off=su_blpower reasons=prevent_idle_dim_disabled,native_screen_timeout_finite
[sysfs] leds=[] backlight=[backlight] devfreq=[dmc, ff400000.gpu]
[labels] ls: /sys/class/leds/*/: No such file or directory ls: /dev/ledjni: No such file or directory u:object_r:sysfs:s0 /sys/class/backlight/backlight/
[hardware]
  inputs=[rk8xx_pwrkey (event0 dmcfreq keychord ), cst226se (event1 dmcfreq ), adc-keys (event2 dmcfreq keychord ), lightsensor-level (event3 ), proximity (event4 )]
  i2c=[0-0020:rk809, 1-001a:CST226, 1-005a:CST226SE, 2-003c:tp, 2-0047:ls_stk3x3x, 2-0047-1:ps_stk3x3x, i2c-0:rk3x-i2c, i2c-1:rk3x-i2c, i2c-2:rk3x-i2c]
  iio=[]
  thermal=[cooling_device0:thermal-cpufreq-0, cooling_device1:thermal-devfreq-0, cooling_device2:thermal-devfreq-1, thermal_zone0:soc-thermal, thermal_zone1:gpu-thermal]
  relays=[]
[packages] android=not installed minimal=not installed
[vendor-tame] known=7 installed=1 active=1 disabled=0
[capabilities] Root (su)=ok | Verified app update / screenshot / display=ok | Screen brightness=ok | Screen on/off=ok | Reboot / reload / launcher=ok

Home Assistant version

No response

Relevant logs

[maxlyth]

The Android screen timeout is the misleading part here. On the Sonoff firmware it applies the vendor's very dim backlight level, but it does not physically switch the display off. ha-paneld can use the NSPanel Pro's backlight power control directly, so NSPanel Pro Tools should not be required.

Automatic sleep is driven by activity in the panel's Home Assistant Area rather than being a simple countdown from the last touch. Could you attach the JSON from http://<panel-ip>:8888/api/v1/auto-sleep/status and say whether Browser sign-in shows as connected and the panel has an Area? That should show why it has not learned an activity source or sleep interval.

Please also try the panel's Screen entity in Home Assistant once. It should use the direct screen-off route and fully extinguish the backlight. If it only dims, that is a separate fault from automatic sleep and I will trace it separately.

[xionc666]

Thanks for picking this up. I downgraded to 0.9.6 to be on stable.

Sonoff is indeed only dimming. The Screen entity is shutting down screen completely. Dimming is not great because the screen remains active and touching it you can activate something by mistake.

Regarding automatic sleep driven by area activity, it is too fancy for me. I want the screen to wake when someone stands in front of it and/or touches it.

/api/v1/auto-sleep/:

{
  "available": false,
  "enabled": false,
  "phase": "disabled",
  "reason": "disabled",
  "learned_lease_ms": null,
  "source_count": 0,
  "discovered_source_count": 0,
  "area_name": "",
  "manual_suppression": false,
  "detail": ""
}

Also the proxitimity waiving is not working. I tried to teach it multiple times and despite successful learning process, it never wakes the screen when I repeat the motion later.

Taking both the issues (no auto screen off, no proximity waking), I installed back nspanel_pro_tools_apk. It is perfect now.

I will keep eye on the release notes.

ps. The software is awesome. With Fully Kiosk the panel was laggy, now it is very useful.

[maxlyth]

The direct Screen entity confirms that ha-paneld can switch this panel fully off. What is missing here is a simple idle timeout plus reliable proximity wake. The current automatic sleep path depends on Home Assistant Area activity instead.

This is work I had already started rather than a new feature I have only just put on the list. I began rewriting the proximity handling around a wizard guided, trainable wake-on-wave implementation, but had to stop the interactive testing while I was away from my panels and then got distracted by other release work. I still very much intend to finish it so watch this space, should be in rc4 or 0.9.8.

NSPanel Pro Tools is a sensible workaround for now, so there is no reason to disturb the working setup for more diagnostics. I will keep this open and return to the rewrite when I can test it properly on real panels again.

[maxlyth]

Coming back to this, since I said it would land in rc4 or 0.9.8. The proximity rework went into 0.9.7, and 0.9.8 is out now. The Presence & wake card on the Configure page starts a short setup that runs on the panel itself and learns presence and a hand wave separately. Once presence is set up, Auto sleep can use the panel's own proximity sensor as its source instead of Home Assistant Area activity, and a hand approach wakes the screen.

I have to admit that while the feature is in 0.9.8, I did not have a lot of time to test it as I was focussed on the migration to Panel Assistant. I'd love to hear your feedback as I tried to make it user friendly but my 10 minutes of real world testing is far short of what it deserves to I am happy to come back to it in a future release.

NSPanel Pro Tools is still a fine choice if you are happy with it. If you do try this, tell me how it goes. I will close this for now; reopen it if it does not work on your panel.

[xionc666]

Thanks. I noticed it was available in 0.9.7. I even tried to go through the learning process, but it was exiting/disappearing twice I tried. Probably the watchdog was bringing the dashboard to the front. I was not trying more as I still need nspanel pro tools to not only wake on wave, but also to fully turn off my screen after 30s of inactivity. And actually this issue is more about this: lack of ability to fully turn off (not only dim) the screen after defined time of inactivity (lack of presence in front of the screen can probably also work, but the screen must go fully off).

[maxlyth]

Thanks for trying the setup again. In 0.9.9-rc1, out now as a test release, I found that the dashboard watchdog could bring the dashboard forward during presence and wave setup, and fixed that. Auto sleep also has a Touch inactivity option with a delay you choose in seconds, including 30 seconds. It uses the same full-off route as the Screen control and needs neither proximity setup nor a Home Assistant Area. Could you try both on your panel and let me know whether the setup stays visible and the screen switches fully off?

[xionc666]

Perfect, I will test it tomorrow and let you know the results.

[xionc666]

0.9.9-rc3. I still had some issues with teaching the presence sensor - it cancelled by itself twice (browser disconnected error). Eventually third time was successful. I even repeated the process to teach the wave a bit further away. Anyway, waking by waving works as expected. Display backlight full shuts down after defined number of seconds. There are some issues, though:

• when screen is off and I touch it, it only wakes up, but the touch activates the thing I touched. It does not work that way with nspanel pro tools - touching only wakes the screen.
• the screen does not power off by lack of presence when I switch to that option, or it needs few minutes by default. I have small difference in reading between clear position (220) and occupied (240). Maybe that's the reason.