Home Assistant Vacation Rental Dashboard

You are at a wedding two states away when your phone buzzes. The cleaner texted: “Lockbox showing low battery, also the porch light wouldn’t turn off, did you fix it?” You open Home Assistant. There are forty-seven entities on the default Overview page. Three thermostats from a property you sold last year are still listed. The lock you actually care about is buried under a zigbee group called “sensor.front_door_lock_2_battery_level.” You spend six minutes scrolling. The bride is about to walk down the aisle. This is the exact pain a real home assistant vacation rental dashboard is supposed to solve. Done right, you should land on a single page and instantly see whether anything is wrong, who is at the property, and what the next 24 hours look like — without three taps and a deep breath.

Who this is for

This is for hosts running one to ten short-term rental properties on Home Assistant who have already paired their core devices — Schlage Encode or Yale Assure Lever locks, Ecobee Premium or Nest Learning Thermostat, a few Kasa KP125 smart plugs, maybe Aqara P1 motion and MCCGQ11LM contact sensors — and now want a control surface they can actually use from a phone screen. If you are still figuring out what occupancy means in a rental, build that model first using our occupancy automation walkthrough. The dashboard sits on top of working automations, not in place of them. New to the platform overall? Start with the Home Assistant short-term rental starter setup first.

What a good dashboard solves

Most hosts inherit a Home Assistant dashboard that was either auto-generated or copied from a Reddit post. Both are wrong for a rental. A useful operator view answers four questions in under three seconds.

Is anyone currently at the property, and if so, who — guest, cleaner, or me?
Is anything broken, low-battery, or offline right now?
What is the next event — checkout, cleaning, check-in — and when?
Can I do the one or two things I most often need to do (change a code, bump the thermostat, unlock briefly) without digging?

Everything else — battery levels, individual sensor states, automation YAML — belongs on a deeper page you only visit when something is wrong.

The three-dashboard pattern

One dashboard cannot serve everyone. Build three, with Home Assistant’s user role system controlling who sees which.

Owner dashboard — full visibility, everything you need to operate the property remotely. Status, alerts, calendar, quick actions, and a link to a deeper diagnostics view.
Cleaner dashboard — just the controls a turnover person needs. A “cleaning started” and “cleaning complete” button, the thermostat for that day, the front door lock with their personal code visible, and a supply note field. Pair this with a cleaner notification flow so they get a text when a turnover starts.
Guest dashboard — thermostat, a few light scenes (movie, all on, all off), maybe doorbell snapshot. No occupancy state, no calendar, no admin anything. The guest mode profile covers exactly which entities to whitelist.

For multi-property hosts, the owner dashboard becomes a grid of property cards, each one summarizing one home. Tap a card to drill into that property’s detail view.

Step-by-step setup

Here is the build order that will keep you sane. Do the structure first, then the prettifying.

Create a new dashboard in Settings > Dashboards. Name it “Owner.” Do not use Overview — leave that one alone.
Add three views: Status, Properties, and Diagnostics. The Status view is the one you will land on; it must answer the four questions above.
On Status, build a markdown card at top that uses templates to spell out occupancy in English: “Cabin: vacant, next check-in Thursday 4 p.m.” Hosts read English faster than they read icons.
Add an alert section: any battery under 20%, any device offline more than 30 minutes, any leak sensor wet. Use a conditional card so the section disappears when nothing is wrong — an empty alerts area is itself information.
Add a quick-actions row: Ecobee setpoint, Schlage Encode lock toggle, “reset to vacant” script button. Limit to four buttons.
Add a calendar card showing the next 7 days of bookings and turnovers, fed from the same iCal feed as your checkout automation.
Build the Cleaner dashboard separately. Create a Home Assistant user with limited entity access. Pin it to a Fire HD 8 tablet on the wall or share a URL via the cleaner’s home screen.
Build the Guest dashboard last, with even fewer entities. If you are not sure whether to expose something, do not expose it.

Privacy and guest experience

Three rules. First, never expose lock codes, occupancy logs, or anyone’s personal calendar on the guest dashboard. If you can see who booked the property, you have leaked too much. Second, never expose camera feeds inside the home, period — doorbell cameras facing the front entry only, and even those should not show on a guest dashboard. Third, if you give the cleaner a tablet pinned to a wall, lock that tablet to one app, with a kiosk-mode setup, so a curious guest who walks past it cannot tap into the broader Home Assistant interface and discover that you have a motion sensor in the hallway. Disclosure on the listing covers the legal piece — our device disclosure guide has exact wording you can copy — but a guest who can see a sensor list and battery levels is going to feel surveilled even when they are not.

Common dashboard mistakes

Showing every entity. If you have 200 entities and 200 dashboard cards, you cannot find anything in an emergency. Start with five cards and add only when you discover an actual unmet need.
Using only icons. Icons are great when you know what they mean. At 11 p.m. on a Sunday, with a guest yelling on the phone, plain English wins.
Forgetting mobile. Your dashboard will be opened on a phone 90% of the time. Test every view on the actual phone you carry, not the desktop. Cards that look elegant on a 27-inch monitor turn into a swiping nightmare on iPhone.
Mixing properties on one view. Multi-property hosts must have one card per property as the entry point, not a single firehose. Otherwise you will eventually issue a thermostat command on the wrong cabin.

Generating dashboards with AI assistance

Lovelace YAML is verbose and easy to typo, which makes it perfect work to hand to Claude Code or Codex. Describe the layout you want in a sentence: “a status row at top with three chips for occupancy, alerts, and next event; below it a horizontal grid of three property cards.” Paste in your entity IDs and let the model write the YAML. Then paste it into the Raw configuration editor inside a test dashboard. Do not paste straight into your production dashboard — one bad indent breaks the whole view. Always preview, then keep. Treat the LLM as fast scaffolding, not as a replacement for actually understanding what the cards do. The Home Assistant Airbnb templates pack bundles known-good Lovelace snippets you can crib from instead of writing from scratch.

Host checklist

Three dashboards exist: Owner, Cleaner, Guest, with appropriate user roles.
Owner Status view loads on phone in under 2 seconds and answers occupancy, alerts, calendar, and offers quick actions.
Alerts section uses conditional cards so “all good” means an empty section.
Cleaner dashboard tested on the actual device they will use, locked into kiosk mode if it is a tablet.
Guest dashboard exposes thermostat plus light scenes only, no calendar, no diagnostics, no camera.
Diagnostics view exists but is not the default landing page.

Frequently asked questions

Should the guest dashboard be hosted in Home Assistant or in a separate guest app?

Either works, but a separate URL using a limited Home Assistant user is simpler than running a second system. Generate a long-lived QR code, print it on the welcome card. Make sure the user account you assign to that URL has access only to the entities on the guest dashboard. If a guest types the URL into a friend’s phone, the friend should hit the same restricted view, not your full admin.

How do I show multiple properties on one dashboard without it getting messy?

Use a vertical-stack pattern with one entities card per property: name, current occupancy, alert count, next event. Tap to drill in. The top-level view should fit on one phone screen for up to about six properties; beyond that, group by region or owner, otherwise scrolling becomes the bottleneck. Color a property card red when it has any active alert and gray when vacant and quiet.

Can I edit dashboards from my phone?

Technically yes, practically no. Lovelace YAML editing on a phone is painful and error-prone. Edit on a laptop, test on a phone. Keep your dashboard YAML in a version-controlled folder so you can roll back when you accidentally break the property cards on a Sunday night.

What about Echo Show or wall tablets for guests?

An Echo Show 8 works for voice-driven control of lights and thermostats but is not a great Home Assistant dashboard surface. A cheap Amazon Fire HD 8 or refurbished iPad on the wall, locked into the guest dashboard, works much better. Make sure the tablet auto-relocks after a few minutes so it does not become a way to expose your admin interface.

Where to go next

Once your dashboard is doing real work, keep adding signal to it from the automations linked above. Build slowly, test every view on the actual phone you will pull out at midnight, and resist the urge to fill empty space — a calm dashboard is the goal.