Skip to content

Reboot not working for NSPanel Pro anymore (0.9.9-rc4) #181

Open
Open
Reboot not working for NSPanel Pro anymore (0.9.9-rc4)#181
Labels
bugSomething isn't workingquestionFurther information is requested

Description

@xionc666
xionc666
opened on Oct 4, 2026

ha-paneld version

0.9.9-rc4

Panel hardware

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

What happened?

In 0.9.9-rc4 the reboot button makes no effect (both in Panel Assistant as well as in web UI on 8888).

Steps to reproduce

No response

Diagnostic dump (/diag)

ha-paneld diagnostics — 0.9.9-rc4 (build 1095)
[captured] 2026-10-04T12:39:57.367+02:00 uptime=5m
[package] io.panelassistant.android

[panel]
ha-paneld=0.9.9-rc4 (build 1095)
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.4 GB free
Storage=7.8 GB eMMC · 2.9 GB free (data)
Display=480×480 px · logical 160 dpi · physical ≈172 ppi
System WebView=com.android.webview 138.0.7204.63
HA Companion=not installed
MQTT state=unreachable · TCP · last-ok never · last-auth never · auth-ok · family Automatic (next IPv4)
Security mode=Relaxed
Keep panel responsive=on · power locks held
Prevent idle dim=on · timeout never
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=716.0 KB used · 1.2 MB on disk · schema 14
Product version=NSPanel86P_1.1.7
Local-state sync=71s ago · screen →OFF (physical) · 244s ago · screen →ON (physical)
State convergence=36 channels · 23 dirty · 0 in-flight · 18 unknown · ack 0/147 · 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=false 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=rendered outcome=ok fault=none detail=none recovery=none transport=http address_family=automatic observed_age=4m process_age=4m package_updated=1h23m theme=light/light
[ha-network] state=idle measuring=false
[ha-path-probe] state=unowned
[camera] state=absent outcome=camera-unavailable fault=none detail=not_enumerated recovery=none clients=0 last_frame=never failures=0 indication=none stream_clients=0 stream_port=off encoder=none encode=none delivered=none requested_fps=none snapshot_exposure=none/0
[zigbee-health] state=unknown layout=vendor-native package=- joined=unknown role=- gateway_cpu=4 guard_cpu=0 restarts_10m=0 containment=none recursive_watchdog=true
[storage-health] state=healthy pressure_state=healthy usable_bytes=2864496640 total_bytes=3606081536 used_percent=20.564839940435554 database_bytes=663552 wal_bytes=524288 sidecar_bytes=32768 page_size_bytes=4096 page_count=162 freelist_count=0 schema_version=14 quick_check=ok auto_vacuum=incremental checked_at=1791110126110 failure=none failure_operation=none remediation=not_run
[power-safety] state=safe keep_awake=true wake_lock=true wifi_lock_required=true wifi_lock=true prevent_idle_dim=true screen_timeout_ms=2147483647 interactive=false power_source=ac plugged_mask=1 stay_on_mask=15 stay_on_effective=true device_idle=false doze_exempt=false screen_off=su_blpower screen_off_selected=unknown screen_off_reason="not yet exercised; no screen-off has occurred since this controller was constructed" reasons=doze_not_exempt
[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 cpufreq dmcfreq keychord ), cst226se (event1 cpufreq dmcfreq ), adc-keys (event2 cpufreq 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

Activity
  1. xionc666
    added 
    bugSomething isn't working
     on Oct 4, 2026
  2. maxlyth
    added 
    questionFurther information is requested
     on Oct 4, 2026
  3. maxlyth commented on Oct 4, 2026 
    @maxlyth
    maxlyth
    on Oct 4, 2026
    Collaborator
    Thanks for the report and the diagnostics. Could you check whether Reboot still does nothing on 0.9.9, the final release, from both Panel Assistant and the web interface? If it does, a fresh diagnostics dump taken right after pressing Reboot would help.
  4. xionc666 commented on Oct 4, 2026 
    @xionc666
    xionc666
    on Oct 4, 2026
    Author
    I will check next weekend.
  5. xionc666 commented on Oct 11, 2026 
    @xionc666
    xionc666
    on Oct 11, 2026
    Author
    Still the same in 0.9.11. The Panel Assistant interface shows this:
    
Image

    yet the panel is not restarted.
    

    When the interface reappeared, I took the dump:
    

    ha-paneld diagnostics — 0.9.11 (1202)
[captured] 2026-10-11T12:44:20.597+02:00 uptime=10m
[package] io.panelassistant.android

[panel]
ha-paneld=0.9.11 (1202)
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.4 GB free
Storage=7.8 GB eMMC · 2.8 GB free (data)
Display=480×480 px · logical 160 dpi · physical ≈172 ppi
System WebView=com.android.webview 138.0.7204.63
HA Companion=not installed
MQTT state=unreachable · TCP · last-ok never · last-auth never · auth-ok · family Automatic (next IPv4)
Security mode=Relaxed
Keep panel responsive=on · power locks held
Prevent idle dim=on · timeout never
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=728.0 KB used · 1.2 MB on disk · schema 14
Product version=NSPanel86P_1.1.7
Local-state sync=615s ago · screen →ON (physical)
State convergence=42 channels · 24 dirty · 0 in-flight · 18 unknown · ack 0/344 · 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=false 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=rendered outcome=ok fault=none detail=none recovery=none transport=http address_family=automatic observed_age=10m process_age=10m package_updated=11h36m theme=light/light
[ha-network] state=idle measuring=false
[ha-path-probe] state=unowned
[camera] state=absent outcome=camera-unavailable fault=none detail=not_enumerated recovery=none clients=0 last_frame=never failures=0 indication=none stream_clients=0 stream_port=off encoder=none encode=none delivered=none requested_fps=none snapshot_exposure=none/0
[zigbee-health] state=unknown layout=vendor-native 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=2833592320 total_bytes=3606081536 used_percent=21.421845520910594 database_bytes=671744 wal_bytes=515032 sidecar_bytes=32768 page_size_bytes=4096 page_count=164 freelist_count=0 schema_version=14 quick_check=ok auto_vacuum=incremental checked_at=1791714835055 failure=none failure_operation=none remediation=not_run
[power-safety] state=safe keep_awake=true wake_lock=true wifi_lock_required=true wifi_lock=true prevent_idle_dim=true screen_timeout_ms=2147483647 interactive=true power_source=ac plugged_mask=1 stay_on_mask=15 stay_on_effective=true device_idle=false doze_exempt=false screen_off=su_blpower screen_off_selected=su_blpower screen_off_reason="matches the declared route" reasons=doze_not_exempt
[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 cpufreq dmcfreq keychord ), cst226se (event1 cpufreq dmcfreq ), adc-keys (event2 cpufreq 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

  6. maxlyth commented on Oct 18, 2026 
    @maxlyth
    maxlyth
    on Oct 18, 2026
    Collaborator
    Thanks for retrying on 0.9.11 and for the dump. The dump says uptime=10m, so something restarted about ten minutes before you captured it. When you pressed Reboot, did the whole panel restart (screen goes black, boot logo, then the dashboard returns), or did only the app restart while Android stayed up? That tells me whether the reboot command itself is being ignored or only the screen is misleading.
  7. xionc666 commented on Oct 18, 2026 
    @xionc666
    xionc666
    on Oct 18, 2026
    Author
    10 min. ago I rebooted the device from terminal.
    

    Pressing reboot does really nothing - screen stays on, app stays on.
  8. maxlyth commented on Oct 19, 2026 
    @maxlyth
    maxlyth
    on Oct 19, 2026
    Collaborator
    That settles it, thanks: the reboot command is being ignored on your panel, and Panel Assistant was wrong to say it worked. With no helper service running, as on yours, the app hands the reboot to root and reports success as soon as the command starts, without checking whether the panel actually went down.
    

    I've changed that for 1.0. If the panel is still up a few seconds after the first command, the app tries svc power reboot and then setprop sys.powerctl reboot, and if it is still up after all three it reports the reboot as failed instead of done.
    

    On my 86P panels the plain reboot command does restart them, so something on yours differs. Which command did you use when you rebooted it from the terminal? That tells me which of the three will work for you.
  9. xionc666 commented on Oct 19, 2026 
    @xionc666
    xionc666
    on Oct 19, 2026
    Author
    I used “reboot” command.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Metadata
Metadata
Assignees
No one assigned
    Labels
    bugSomething isn't workingquestionFurther information is requested
    Type
    No type
    Projects
    No projects
      Milestone
      No milestone
      Relationships
      None yet
      Development
      No branches or pull requests
      Issue actions