You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now, installing ha-paneld assumes a computer with adb on the same LAN (the curl … | bash one-liner), or a USB cable. Once the agent is running, configuration is already phone-friendly — you point your phone's browser at the panel's own config page, or scan its QR, and set panel id / MQTT there. So the open question is the install and first-run, with no computer to hand.
Before building for this, I want to gauge whether it's a real need: do panel installers always have a laptop nearby, or is "I only have my phone" a genuine blocker for you?
What actually needs a computer today — and why it isn't trivial on a phone:
Granting permissions. ha-paneld needs Modify system settings + an accessibility service (and root, for true screen-off and sysfs LEDs). Over adb that's automatic; without it you're hand-toggling Settings on a small touchscreen (the app's setup screen already walks you through this), and root can't be granted at all without adb or an already-rooted panel.
Updating the system WebView. Almost every panel ships a WebView far too old to render a current HA dashboard, and the clean fix for that is currently adb-only. For a phone-only install this is arguably the harder blocker than the app itself.
Approaches we're weighing:
Polish the on-device, no-adb path — sideload the APK on the panel, have the setup screen deep-link you straight to the exact toggles, and walk the WebView update on-device; configure from your phone's browser / QR. Limits: locked-down panels with no browser or file manager, no root path, and the WebView step may need a workaround.
Phone-as-adb-host (Termux) — run adb from the phone itself (Termux + android-tools) and use the normal one-liner over the LAN: full automation, WebView update included, no PC. More technical; we could ship a Termux-tailored script.
Wireless ADB pairing — adb pair with the code shown on the panel. Clean, but Android 11+ only; most panels are 8.1, so it only helps the newer ones.
(stretch) a phone-side provisioner — a small PWA/app that does the network provisioning end-to-end. Heaviest to build; only worth it if there's real demand.
What I'd like to hear: Is phone-only setup a real need for you, or a niche? Which of these would you actually use? And if you've set a panel up with no computer to hand — especially the WebView update — how did you do it?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Right now, installing ha-paneld assumes a computer with
adbon the same LAN (thecurl … | bashone-liner), or a USB cable. Once the agent is running, configuration is already phone-friendly — you point your phone's browser at the panel's own config page, or scan its QR, and set panel id / MQTT there. So the open question is the install and first-run, with no computer to hand.Before building for this, I want to gauge whether it's a real need: do panel installers always have a laptop nearby, or is "I only have my phone" a genuine blocker for you?
What actually needs a computer today — and why it isn't trivial on a phone:
Approaches we're weighing:
adbfrom the phone itself (Termux + android-tools) and use the normal one-liner over the LAN: full automation, WebView update included, no PC. More technical; we could ship a Termux-tailored script.adb pairwith the code shown on the panel. Clean, but Android 11+ only; most panels are 8.1, so it only helps the newer ones.What I'd like to hear: Is phone-only setup a real need for you, or a niche? Which of these would you actually use? And if you've set a panel up with no computer to hand — especially the WebView update — how did you do it?
All reactions