Home Assistant

Home Assistant stays in control.

OldPhoneKiosk is not a competing dashboard. It registers your displays as devices in Home Assistant and lets your existing automations decide what each screen shows.

One integration, real devices.

Every kiosk appears in the Home Assistant device registry, so it behaves like any other entity you can target from automations, scripts and the dashboard.

No cloud · your LAN

Core Home Assistant Source of truth

LAN Bridge LAN gateway

iPhone Hallway console

iPad Kitchen display

Kindle Bedroom e-ink

Integration

Installed via HACS

The custom integration adds a config flow and the OldPhoneKiosk services to your instance.

Device registry

Each screen is a device

Paired iPhones, iPads and Kindle displays register with a name, area and diagnostic state.

Services

Switch any screen

Call a service to change the active screen, wake or sleep a panel, or push a message.

Local network

No round-trip to a cloud

Displays talk to the Bridge on your LAN. Home Assistant remains the source of truth.

What Home Assistant can control and show

Because each display is a first-class device, anything you can automate in Home Assistant can drive the wall.

Active screen

Flip a panel between dashboard, calendar, photos or a camera view from any automation.

Wake & sleep

Send a panel into SLEEP — black UI, minimum brightness, muted media — while the app stays live in kiosk mode.

Room state

Surface climate, lights, locks and energy exactly as your dashboards already report them.

Messages & scenes

Push a short message or trigger a scene when someone arrives, leaves or rings the bell.

Setup flow

1
Add through HACS
Install the integration, restart Home Assistant and open the config flow.
2
Register displays
Pair iOS devices on the local network or create a Kindle web display.
3
Wire automations
Target each display device from your existing scripts, scenes and dashboards.

Call it like any other service

OldPhoneKiosk adds plain Home Assistant services. Pick one, read the call, and run a preview to see the response it returns.

Illustrative calls — service names and fields mirror the integration.

oldphonekiosk.set_screen

service: oldphonekiosk.set_screen
target:
  device_id: hallway_iphone
data:
  screen: camera.front_door
  duration: 30

oldphonekiosk.create_web_display

service: oldphonekiosk.create_web_display
data:
  name: Bedroom Kindle
  area: bedroom
  mode: read_only
# → returns display_url

oldphonekiosk.assign_area

service: oldphonekiosk.assign_area
target:
  device_id: kitchen_ipad
data:
  area: kitchen
  allow:
    - calendar
    - tasks

A quiet evening, automated

The same event fans out to the right surface. The hallway shows the camera; the kitchen keeps the calendar; the bedroom Kindle stays calm.

18:04
Doorbell rings
Hallway iPhone opens the camera and two-way intercom as an overlay.
18:05
Door unlocked
Home Assistant logs entry; the hallway panel returns to its dashboard.
21:30
Good-night scene
Lights dim, and the kitchen iPad switches to tomorrow's calendar.
23:00
Sleep window
All panels enter SLEEP; the bedroom Kindle shows a minimal read-only page.

Local-first, with clear boundaries

The kiosk is designed to reduce what leaves your network, not add to it.

Tokens stay server-side

Google and Home Assistant tokens live only on the Bridge or server — never in the iOS app.

No admin token on iOS

The iOS app talks to the Bridge, and a per-device secret is stored in the iOS Keychain.

Runs on your LAN

Displays and Bridge communicate locally; there is no OldPhoneKiosk cloud in the middle.

Switch a screen from an automation

service: oldphonekiosk.set_screen
target:
  device_id: hallway_iphone
data:
  screen: camera.front_door
  duration: 30

Put Home Assistant in charge

The integration is open source and installs through HACS.

Get the integration on GitHub