Home Assistant Wall Tablet Setup That Stays Awake

Short Answer: Use a Kiosk Path, Not a Normal Browser

The reliable path is: make a simple dashboard, log in with a dedicated non-admin user, then run it in a kiosk app that is allowed to keep the screen awake. For many homes, the official Home Assistant Companion app is the cleanest place to start. On Android, the app can act as the home app launcher so the tablet opens Home Assistant instead of a normal Android home screen. On iPhone and iPad, Home Assistant's Companion docs now describe an iOS kiosk mode in Labs, with requirements tied to Home Assistant frontend 2025.2 or newer and the iOS app 2026.7.0 or newer.

If the wall tablet needs stronger display control, use Fully Kiosk Browser on Android. Home Assistant has an official Fully Kiosk integration that talks to Fully's local Remote Admin API, so Home Assistant can see tablet sensors and control display behavior over your LAN. That does not mean every tablet is good hardware. It means you get a better control path than a normal browser tab.

Matter, Thread, Zigbee, Z-Wave, and HomeKit are not the control path here. The tablet is a dashboard client. It talks to Home Assistant over Wi-Fi, and Home Assistant talks to the devices.

Why Wall Tablets Fail in Real Homes

Recent r/homeassistant and Home Assistant Community threads keep circling the same pain: wall dashboards get slow, cheap tablets sleep at the wrong time, Fully Kiosk behaves differently after updates, and households want one screen that guests can use without seeing the whole system. The problem is rarely one magic setting. It is usually the combination of an underpowered tablet, a heavy dashboard, OS battery rules, and a login that was never designed for a shared wall display.

Use plain language for the job. A dashboard is the Home Assistant page with lights, climate, locks, cameras, and room controls. Kiosk mode means the tablet hides normal browser or app chrome so the wall screen feels like a fixed control panel. Local control means the tablet is talking to Home Assistant inside the house instead of depending on a vendor cloud. A dedicated user is a separate Home Assistant login just for the tablet.

That last piece matters. A wall dashboard is physically public inside your home. It should not expose admin pages, backups, add-ons, logs, camera archives, alarm controls, or remote access settings to anyone who can tap the screen.

Choose the Right Wall Tablet Path

Build a Tablet Dashboard, Not an Admin Dashboard

Home Assistant dashboards are flexible enough to become too heavy. A dashboard that feels fine on a laptop can be miserable on a wall tablet because the tablet has less memory, a smaller processor, a smaller screen, and a browser engine that may stay open for weeks.

For a shared wall screen, make a separate dashboard with only the controls that make sense in that room:

• Kitchen: main lights, nearby climate, music, timers, presence status, front door glance, and one or two camera snapshots.
• Entry: locks, garage, exterior lights, alarm state if appropriate, weather, and arrival scenes.
• Bedroom: lights, shades, climate, sleep scene, white noise, and a simple morning view.
• Utility room: leak sensors, washer/dryer, energy, water shutoff status, and maintenance alerts.

Avoid the tempting version with every room, every camera, every history graph, and every custom card. Live camera streams, large graphs, animated cards, maps, browser popups, and complex custom cards are the first things to remove when a tablet becomes slow. A useful wall dashboard is usually dense but calm: a few big controls, clear status, and a path to more detail only when needed.

Create a Dedicated Dashboard User

Do not mount a tablet that is logged in as the same admin account you use for Home Assistant maintenance. Create a separate user for the wall tablet, then set that user's default dashboard to the room dashboard. If your household has kids, guests, cleaners, renters, or real estate showings, assume the wall screen can be touched by someone who should not manage your integrations.

The tablet user should usually be able to:

• Turn room lights and scenes on and off.
• Adjust climate within safe limits.
• See simple house status such as doors, water leaks, weather, and presence.
• Use media or routines that are safe for anyone in that room.

The tablet user should usually not be able to:

• Open Settings, backups, logs, add-ons, integrations, or developer tools.
• Change automations or helpers.
• View private camera history or microphones unless that is intentional.
• Unlock exterior doors or disarm alarms without an extra household decision.

If you put locks, garage doors, alarm panels, or cameras on a wall screen, add a family policy before you add the button. In many homes, "show state, require phone for action" is the better default for security devices.

Keep the Screen Awake Without Fighting the Operating System

The most common mistake is treating "screen off" as the same thing as "wall tablet is ready." On many tablets, true sleep can pause background activity, kill the browser, drop the WebSocket connection, or delay wake. The result is a black screen that looks energy-efficient but takes too long to become useful.

A more reliable pattern is:

1. Keep the wall app in the foreground. Use Android launcher mode, iOS kiosk mode, or Fully Kiosk so the tablet returns to the dashboard.
2. Use a dim or black screensaver overnight. That gives you a dark wall without depending on deep sleep.
3. Wake by motion or presence only if the device can do it reliably. Fully Kiosk is the stronger Android path for this.
4. Keep the local URL simple. The tablet should load the internal Home Assistant address while at home.
5. Disable aggressive battery optimization where the OS allows it. This is device-specific, especially on budget Android tablets.

Fully Kiosk's local controls are useful because Home Assistant can automate around real household context: dim at night, brighten in the morning, turn the screen on when the hallway is occupied, and keep it off during sleep hours. The official Fully Kiosk integration depends on the Remote Admin feature, so use a strong admin password and keep that endpoint on the local network only.

Power and Mounting Safety

A wall tablet is a permanently powered device with a lithium-ion battery. Treat it like installed electronics, not a framed picture. Use a quality charger and cable, keep the device ventilated, and leave a way to inspect or remove it. Do not bury a consumer tablet, charger, or swelling battery in a sealed wall cavity.

NFPA lithium-ion battery safety guidance says not to charge a battery when the charger or battery is damaged and not to store batteries in extreme hot or cold conditions. For a wall tablet, this means you should be able to see the device, feel if it is getting hot, and remove it without demolition. If a tablet battery swells, leaks, smells unusual, or overheats, stop using it and handle it as a safety problem, not a software problem.

If the mount requires in-wall power, low-voltage routing, or a recessed outlet, use hardware that is meant for that installation and bring in an electrician where your local code or comfort level calls for it. A clean Home Assistant dashboard is not worth unsafe power.

If the Dashboard Is Slow or Unreliable

Try the boring fixes in order before buying another screen.

1. Make a lighter dashboard. Remove live cameras, history graphs, maps, popups, animations, and custom cards from the wall-tablet view.
2. Test on the local URL. If the tablet is at home, it should not hairpin through remote access just to reach Home Assistant.
3. Update the tablet browser engine or app. Android WebView, the Companion app, Fully Kiosk, and Home Assistant frontend updates can all change behavior.
4. Check memory by rebooting once. If a reboot makes the tablet fast for a day and then slow again, reduce dashboard complexity and consider a scheduled maintenance reboot.
5. Check Wi-Fi at the wall. A tablet mounted in a weak spot may look like a dashboard problem when it is really a network problem.
6. Replace truly underpowered hardware last. If the tablet cannot keep a simple dashboard smooth, it is the wrong wall tablet.

Community reports around Home Assistant 2026.4 and 2026.5 show why this needs to be practical, not dogmatic: some users saw Fully Kiosk pages become slow after updates, while others found specific dashboard or app combinations that worked. Keep the wall dashboard simple enough that an update does not turn it into a science project.

Privacy and Local Control Boundaries

A wall tablet can be local-first, but it is still a screen on the wall. Keep the tablet on your home network, use the local Home Assistant URL, and do not expose Fully Kiosk Remote Admin or Home Assistant directly to the public internet. If you need remote access, use a supported path such as Home Assistant Cloud, a properly configured VPN, or a hardened tunnel. Tara has a separate guide on remote access without port forwarding.

If the tablet includes a camera or microphone, decide whether you actually need it. Motion wake by camera can be convenient, but it also means a device pointed into the room is watching for motion. Many homes can use a separate presence sensor instead, which keeps the dashboard responsive without adding a camera to the kitchen or bedroom.

Tara's Take

The best wall dashboard is useful enough that people use it, limited enough that it does not expose the whole system, and boring enough that it survives updates. Tara's default is a dedicated dashboard user, a room-specific interface, local network access, simple controls, and a mounting plan that can be serviced later.

For installed homes, the handoff matters as much as the screen. A homeowner should know what the wall tablet can control, what it cannot control, how to restart it, and what to do if the screen goes blank. That is the difference between a smart-home feature and another device someone has to babysit.

Related Tara Reading

Wall tablets sit between dashboard design, remote access, privacy, presence, and Home Assistant maintenance. These Tara guides are useful next.

• Home Assistant Person Stuck Home or Away? Fix It
• How to Access Home Assistant Remotely Without Port Forwarding
• Should Home Assistant Be on an IoT VLAN?
• How to Update Home Assistant Safely Without Breaking Your House

FAQ

What is the best app for a Home Assistant wall tablet?

Start with the official Home Assistant Companion app if Android launcher mode or iOS kiosk mode covers your needs. Use Fully Kiosk Browser on Android when you need stronger wall-display controls such as local screen control, motion wake, and Remote Admin integration with Home Assistant.

Can a Home Assistant wall tablet work without the cloud?

Yes. Use the local Home Assistant URL while the tablet is on your home network. The dashboard itself does not need a vendor cloud. Remote access from outside the house is a separate design choice.

Should I use Matter, Thread, or HomeKit for the tablet?

No. Those are device-control ecosystems and protocols, not the wall-tablet path. The tablet is a Wi-Fi dashboard client. Home Assistant is the system that talks to Matter, Thread, Zigbee, Z-Wave, HomeKit, and vendor integrations.

Should the wall tablet use my admin account?

No. Use a dedicated non-admin user and a room-specific dashboard. A shared wall screen should not expose Home Assistant settings, backups, add-ons, logs, camera archives, or security controls to anyone walking by.

Why does my wall dashboard get slow?

The common causes are old tablet hardware, too many live camera feeds, large charts, heavy custom cards, popups, memory growth, weak Wi-Fi, or a browser engine that needs an update. Make a lighter tablet-only dashboard first.

Is it safe to keep a tablet plugged in all the time?

It can be practical, but use a quality charger, keep the device ventilated, inspect it, and remove it if it gets hot or the battery swells. Do not bury a consumer tablet or charger in a sealed wall cavity.