How to put a Home Assistant dashboard on a wall display without a login screen

Step 1: create a dedicated wall user

Never trust a screen as your own account. A wall user sees only what you give it and can be deleted in one click if the screen is ever moved or stolen.

1. Add the user. Settings → People → Users → Add user. Display name Kitchen wall, username wall-kitchen, a long random password you will never type.
2. Lock it down. Leave Administrator off and turn on Can only log in from the local network. Save.
3. Copy the user ID. With the browser on /config/users, select the user; the dialog shows its ID, a 32-character string. You need it in step 2.

Step 2: trust the screen's address and skip the login page

Trusted networks compares the address a connection comes from with a list you configure. Give the screen a fixed address first, then add it. On DisplayOps the display's current IP is shown on its page in the portal; reserve that address in your router's DHCP settings so it never changes.

1. Edit configuration.yaml (File editor or Studio Code Server add-on, or SSH). Add the trusted networks provider before the default one and keep the default one so you can still log in with a password from everywhere else:

homeassistant:
  auth_providers:
    - type: trusted_networks
      trusted_networks:
        - 192.168.1.40        # the kitchen wall display
        - 192.168.1.41        # the hallway display
      trusted_users:
        192.168.1.40: 8c0f2a4d1e5b4f0c9a7d3b2e6f1a5c4d   # wall-kitchen user ID
        192.168.1.41: 2b7e9c1a3d5f4e6b8a0c2d4e6f8a1b3c   # wall-hall user ID
      allow_bypass_login: true
    - type: homeassistant

2. Check the configuration (Developer tools → YAML → Check configuration) and restart Home Assistant.
3. Test from the screen's address. Open http://192.168.1.20:8123/ from a device that has the trusted address (or temporarily add your laptop's address). You should land on the default dashboard with no login page. From any other address the normal login still appears.

Step 3: build a dashboard for the wall

Your phone dashboard is the wrong shape for a 55-inch TV two metres away. Make one for the wall, keep it non-admin, and make it the wall user's default.

1. Create it. Settings → Dashboards → Add dashboard → New dashboard from scratch. Title Wall, an icon, Show in sidebar on, Admin only off. The URL becomes /dashboard-wall.
2. Lay it out for distance. Use the Sections layout with a few large cards, or a single Panel view for one big card such as a floor plan, camera or energy graph. Big text, few colours, no more than what someone reads in five seconds.
3. Hide what the wall should not show. Open your other dashboards' settings and turn on Admin only where possible. The wall user then sees only the wall dashboard.
4. Make it the default for the wall user. Log in as that user once from a trusted address and, on the Profile → General tab, choose it under Dashboard. Simpler still: give the screen the dashboard's full URL, which is what DisplayOps does anyway, and skip this step.

Step 4: hide the header and sidebar with Kiosk Mode

Home Assistant does not ship a fullscreen dashboard mode. The community Kiosk Mode plugin (installed through HACS) removes the header, the sidebar and the menu button, either for a dashboard or through URL parameters, and it is what nearly every wall-display setup uses.

1. Install it. In HACS search for Kiosk Mode, download it, and add the resource it tells you to under Settings → Dashboards → Resources (HACS usually does this for you). Kiosk Mode 7 needs Home Assistant 2025.5 or newer; older cores need an older plugin release.
2. Turn it on for the wall dashboard. Open the dashboard, Edit → Raw configuration editor, and add a root-level block:

kiosk_mode:
  non_admin_settings:
    kiosk: true          # hide header and sidebar for the wall user
  admin_settings:
    kiosk: false         # admins keep the header so they can edit

3. Or use the URL. Append ?kiosk to the dashboard URL to hide everything, or ?hide_header / ?hide_sidebar for one of them. The URL form is convenient with DisplayOps because the parameter lives in the content item, not in the dashboard.
4. Keep an exit. Kiosk Mode only works on dashboards you created, not on the auto-generated Overview, which is another reason to use your own; and ?disable_km brings the chrome back when you need to edit from the screen's address.

Screens that are not on the home network

Trusted networks needs to see the screen's own address. Through the Nabu Casa remote URL or any reverse proxy the screen connects to, the connection arrives from the cloud or the proxy, so the bypass cannot apply and Home Assistant shows the login page. Two setups work for a screen in another building:

• A VPN such as Tailscale or WireGuard. Put Home Assistant and the screen on the VPN and trust the screen's VPN address (for Tailscale, the device's 100.x.y.z address). The screen talks to Home Assistant's VPN address directly, so trusted networks sees the right source.
• A site-to-site tunnel between the two networks (most business routers can do this). The screen then has a normal private address that Home Assistant can trust.

URL options worth knowing