Foolproof pairing
The primary screen guides pairing over local Wi‑Fi discovery, with a 10-digit Home Assistant backup code when discovery is not enough.
iPhone & iPad
The mobile app is more than a web page in a frame. It is a native kiosk surface with Wi‑Fi pairing, Keychain device secrets, HA-driven screens, bottom navigation, sleep/dim policy, camera/intercom picture-in-picture, tasks, calendar, photos and dashboard views.
The iOS code already treats the device like a household appliance: configured by Home Assistant, but polished for a wall-mounted phone or kitchen iPad.
The primary screen guides pairing over local Wi‑Fi discovery, with a 10-digit Home Assistant backup code when discovery is not enough.
The app hides system chrome, keeps the screen awake when appropriate, shows a bottom menu, handles swipes and dims or sleeps itself after inactivity.
Home Assistant can feed native tasks, calendar, photos and dashboard screens instead of leaving the old device as a generic browser tab.
Pairing is intentionally local and recoverable. The app first asks for Local Network permission, advertises itself for a limited Wi‑Fi pairing window, and falls back to a one-time 10-digit code from Home Assistant.
The app checks iOS Local Network permission before pretending it is discoverable.
Home Assistant can claim the device during the Wi‑Fi broadcast; the backup path is a typed 10-digit code.
The device talks to the Bridge with a per-device secret stored in Keychain — no HA admin token on the iPhone or iPad.
Home Assistant switches the surface; the app renders each mode natively and keeps the kiosk context instead of throwing the user into a full-screen detour.
Live tiles for climate, lights, locks and energy, tuned for glanceability across a room.
A camera opens as a picture-in-picture overlay — the current screen is never lost behind it.
Answer the door hands-free. Home Assistant can hang up and return the panel to its dashboard.
Black UI, minimum brightness and muted media — the app stays locked in kiosk mode, ready to wake.
Coming soon
The Android app is planned as an Android-native surface for old tablets and phones, not a separate cloud product. Expect the same Home Assistant-owned model as iPad: local pairing, per-device secrets, room screens and kiosk policy — adapted to Android hardware.
A kitchen tablet or hallway phone should receive HA-driven dashboard, tasks, calendar, photos and sleep/dim commands in the same product language.
The goal is a proper kiosk shell with local storage, screen policy and device controls, instead of asking every Android device to run a heavy browser tab.
iOS and Kindle are the active surfaces today. Android is on the roadmap, so the site sets expectations without pretending the app is available.
Camera and intercom only run on iOS devices that can handle them — never on a Kindle. Here is how the surfaces compare.
| Capability | iPhone / iPad | Kindle |
|---|---|---|
| Native kiosk shell | Yes — hidden system chrome, bottom menu, swipe navigation | No |
| Pairing | Wi‑Fi discovery or 10-digit code | Just a URL |
| Secrets | Per-device secret in Keychain | None on device |
| Camera view | Top-right PIP overlay | No |
| Two-way intercom | WebRTC audio overlay | No |
| Tasks / calendar / photos | Native screens | Server page; existing tasks can be marked Done |
The iOS app is distributed through the App Store. Any subscription is handled by Apple, and we keep the boundaries honest.
Get the iOS app and the Home Assistant integration.