Home Assistant for Airbnb and Holiday Lets (UK Owner's Guide)

You run two cottages in Cornwall. Or four in the Lakes. Or one converted barn in Pembrokeshire that's booked forty weeks of the year. The booking calendar is on Airbnb, the heating is on a Tado app, the locks are on a Yale app, the leak sensor in the utility room came with its own hub and its own app, and the cleaner has a key safe code on a sticky note. Something is always slightly wrong, and you find out about it from a guest review or a £400 gas bill for an empty week.

This guide is about pulling that mess into one system. Home Assistant for Airbnb and holiday lets in the UK isn't a niche idea — it's already what serious hosts use to stop heating empty buildings, catch leaks before they become insurance claims, and run a portfolio of properties without three apps per cottage. Below, what it actually controls, what it costs to do badly, what to watch out for, and where a managed service fits if you don't want to become a part-time sysadmin.

The changeover problem nobody talks about

Hospitality runs on a clock. Check-out is 11am. Cleaner arrives by midday. Check-in opens at 4pm. In those five hours your property has to be cleaned, the linen turned around, the heating brought back up, the hot water tank topped up, the lock code rotated, and the place ready to receive a stranger who paid £180 a night and expects it warm on arrival.

Doing this manually across one property is annoying. Across four it's a part-time job. The standard failure modes are familiar to anyone who's hosted for more than a season:

• The heating stays on between guests because nobody remembered to drop it.
• The heating stays off between guests, then needs four hours to recover before the 4pm check-in, so the guest arrives to a cold house and leaves a three-star review.
• The cleaner's key safe code is the same one you used in 2023, and you've handed it to about sixty people.
• The Yale lock battery dies on a Friday night during a check-in.
• The dishwasher leaks for fourteen hours while the property is empty.
• The previous guest left the immersion heater on. You find out from your October bill.

Each of these is solvable individually. What Home Assistant does is solve them together, on one screen, across every property you run.

What a single system actually controls

Home Assistant is a small computer that sits on the property's broadband and talks to things. For a holiday let, the useful things are heating, locks, leaks, energy and a small amount of presence sensing. You don't need everything from day one — most hosts start with two or three of these and add the rest over a season.

Heating between guests

This is the biggest one financially. A typical UK two-bed cottage left at 18°C through an empty week in February burns through 80-120 kWh of gas it didn't need to. Multiply by however many empty days you average and a portfolio of four cottages quietly costs you a four-figure annual sum to heat nobody.

Home Assistant reads your booking calendar via an iCal feed. Airbnb, Vrbo and Booking.com all expose a per-listing iCal export natively — that's the easy path. Sykes and Cottages.com (Awaze) don't publish a native iCal feed for owners; if you book through them, you'll either route everything through a channel manager (e.g. SuperControl) that re-exports a unified iCal, or run a separate direct-booking platform alongside that does. Either way Home Assistant uses the resulting iCal as a trigger. The rule looks roughly like this in plain English: "If the property is unoccupied between bookings, hold heating at 12°C frost-protect. Three hours before next check-in, ramp to 20°C." That's it. The thermostat — Tado, Drayton Wiser, Hive or Nest, all of them work with Home Assistant — does the work; Home Assistant just decides when. A Tado smart thermostat starter kit is the most common starting point because the multi-zone TRVs let you also pull individual rooms back when nobody's in them.

The savings here pay for the entire system several times over on any property booked less than 90% of the time.

Smart locks and changeover codes

Yale Conexis (with the Yale Access module), Nuki and a handful of others integrate well today. Yale's newer Linus L2 has an official Home Assistant integration but real-world reports are mixed — some installs commission cleanly via Matter, others get stuck — so be cautious recommending it on a fleet until your install is proven. Conexis L2 with Bluetooth is the safer default if you want predictability. The pattern most professional hosts settle on:

• A permanent code for the cleaner that never changes.
• A guest code generated from the booking — last four digits of the phone number, or a random four-digit code emailed automatically.
• The guest code activates at 4pm on check-in day and deactivates at 11am on check-out day.
• An owner code, never shared, for emergencies.

Without Home Assistant, you do this in the Yale app, manually, per booking. With Home Assistant, the booking calendar drives it. New booking lands → code generated → code emailed to guest → code expires automatically. A Yale Conexis or Linus L2 smart lock on each property and one set of automation rules covers the lot.

A note on key safes: they're fine as a fallback, but the same physical code shared with sixty cleaners and guests over three seasons is a security posture you'd struggle to defend to your insurer if a property got turned over. Smart locks plus expiring codes is the modern equivalent and it's no longer expensive.

Leak detection — the insurance-claim category

This one is unglamorous and the most important thing on the list. A washing machine hose that fails on a Tuesday in an empty cottage is, at best, a ruined kitchen floor; at worst, a £15,000 insurance claim, weeks of remediation and a property off the booking grid through peak season.

Battery-powered Zigbee leak sensors sit under every sink, behind the washing machine, behind the dishwasher, in the airing cupboard near the hot water tank, and beside the boiler. Aqara water-leak sensors are the standard choice — about £15-20 each, batteries last roughly two years, no subscription. Aqara's marketing implies you need an Aqara hub; you don't. They pair directly to Home Assistant's own Zigbee coordinator (the ZBT-2 we ship with our kit, or any other), which is the route habbb uses on every install. When one trips, Home Assistant pushes a notification to your phone within seconds, and if you've fitted a motorised mains valve (Sure Stop, Surestop or a Shelly-driven actuator on a quarter-turn), it cuts the water automatically.

Several insurers now offer reduced premiums for properties with monitored leak detection. Worth a phone call to your broker — the kit pays for itself even before the first leak.

Energy oversight

A single Shelly EM clamp in the consumer unit gives you a live whole-property power reading. (For a single-phase domestic property the regular Shelly EM or Pro EM is the right fit; the Shelly Pro 3EM is a 3-phase meter and over-spec for most UK cottages.) That's enough to spot the things that quietly cost you money:

• The immersion heater the previous guest forgot about.
• The patio heater left on overnight.
• The fridge that's drawing twice what it should because the seal's gone.
• The hot tub heater stuck in a cycle because the cover blew off.

You don't need granular per-circuit monitoring at first. One whole-property reading, charted over a week, makes anomalies obvious.

Occupancy sensing — handle with care

Some hosts add motion or noise sensing to enforce no-party clauses or detect unauthorised pets. There are products for this — Minut is the best-known in the UK — and they have a place. They are also GDPR-sensitive: you must disclose monitoring in your booking listing, you should not record audio (Minut measures decibel level only, which is the legally clean way to do it), and you must not place sensors in bedrooms or bathrooms. Done right, this catches the parties of forty that occasionally happen in remote properties. Done badly, it's a complaint to the ICO.

Most hosts skip this until they've had at least one incident. That's a reasonable position.

The DIY trap: four cottages, sixteen apps

Holiday-let hosts who try to assemble this themselves usually end up at one of two endpoints.

The first is the vendor sprawl problem. Tado for heating, Yale for locks, Aqara for sensors, Shelly for power, the booking platform for the calendar, and a different account on each, per property. Four cottages at four vendors becomes sixteen logins, sixteen apps, and no single place where you can see what's happening. When something goes wrong at 9pm on a Friday, you're hunting through three apps to work out which property's leak sensor just fired.

The second is the DIY Home Assistant problem. You install it yourself, you spend three weekends getting it mostly working on one property, and you realise you now have to do it three more times, keep four installs updated, manage backups for four databases, fix four broken automations every time a vendor pushes an app update, and explain to the cleaner why the lock isn't responding tonight. The platform is genuinely capable. The ongoing maintenance is the part that bites.

This is roughly the same shape as the choice between servicing your own boiler and having a contract — you can do it, the parts aren't expensive, but you are now in the boiler business. For one property, fine. For a portfolio, the maintenance is the job, not the setup.

What habbb does for holiday-let hosts

habbb is a managed Home Assistant service for UK property owners. We handle the unglamorous half — provisioning the hardware, configuring remote access through a Cloudflare tunnel (no ports opened on the property's broadband, no static IP needed), running daily encrypted backups to S3, monitoring each instance 24/7, testing Home Assistant updates before pushing them to your fleet, and answering when something breaks at 9pm on a Friday.

What you get visually is a single dashboard per property and a fleet view across them. Each property's dashboard shows current temperature per room, who's checked in and when they leave, lock status, leak sensor status, current power draw, and the next booking's start time. The fleet view shows all your properties side by side, with red flags where something needs attention. It looks like a property-management tool, because that's what it is — Home Assistant is just the engine underneath.

Two ways to take it

With our hardware: £150 one-off for a pre-configured Raspberry Pi 5 with internal SSD, plus £30/month per property. The kit ships, you plug it in, we do everything else remotely. Best for properties that don't have Home Assistant yet.

Bring your own Home Assistant (BYOHA): £40/month per property if you already have a working Home Assistant install you want managed. The £10/month difference reflects the honest extra work — every existing install is a slightly different snowflake, with custom YAML, HACS components, integrations we didn't pick, and quirks we have to learn. We earn the difference by spending the time to learn yours.

Either way, the £30 or £40 monthly fee is a maintenance contract. It covers updates, backups, monitoring, remote access, and small fixes to existing automations — the equivalent of keeping the system you have working. New integrations, new properties added to the system, or larger reworks (e.g. wiring up a fresh booking platform, building a multi-property dashboard from scratch) are quoted as one-off projects. Simple automation work starts at £45; a new integration category from £75. We're upfront about the boundary because the alternative is the kind of contract that gradually eats both sides.

What we don't do

We don't fit hardware on-site. The kit ships and you plug it in, or your electrician does if there's wiring involved (a smart valve on the rising main, for instance). We don't replace your booking platform — Airbnb, Vrbo, Sykes, Cottages.com, direct bookings, all stay where they are. We don't do hospitality consulting. We make the technology layer reliable; the hosting is yours.

Pricing realities at multiple properties

Listed-price arithmetic gets uncomfortable past three or four cottages. £30 per property per month is right for a single home; eight properties at the same rate is £240 a month, and at that scale you'd reasonably ask whether it should look more like a portfolio plan than a stack of individual subscriptions.

Short answer: yes, and we price portfolios differently. The longer answer depends on how many properties, how similar they are (one Tado, one Hive and one Drayton across three cottages is more work than three Tados), whether you need a single fleet dashboard or per-property logins for cleaners and managers, and whether you want us to build the property-management automations or you've already got them.

Rather than publish a portfolio price we'd have to caveat into uselessness, we quote per portfolio. If you run more than two properties, get in touch through the form below and we'll work out what the right shape is — kit, BYOHA, or a mix.

If you're a letting agency or professional property management company rather than an owner-host, the conversation is different in shape — different software stack (Reapit, Arthur, Yardi rather than Airbnb/Vrbo), different tenant-privacy regime, different insurance angle. We've written that side up separately in the Home Assistant for UK Property Managers guide.

What to watch out for

A few things that bite holiday-let hosts specifically, that residential homeowners don't usually hit:

• Broadband at the property. Home Assistant needs working internet on-site. Most rural cottages have it now, but check before you order kit. 4G failover routers are cheap and worth fitting on isolated properties — a tunnel through 4G works fine.
• Cleaner access. Whatever you build has to survive the cleaner. If your "smart" system requires the cleaner to use an app, it's already broken. Codes on a keypad lock and the same physical entry routine they've always had is the right level. The smarts happen behind the scenes.
• Power cuts. A storm in November takes the power out, the Pi reboots, the broadband router takes ten minutes longer to come back than the Pi, the tunnel reconnects, and everything is fine. But test this once. A small UPS on the router and Pi (£60-£80) is sensible insurance for properties prone to outages.
• Battery devices. Every Zigbee sensor has a battery. Across a portfolio, one of them is always close to flat. Home Assistant tracks battery levels per device — set up a fleet-level alert at 20% so you can carry spares to the next changeover, rather than getting a 3am leak-sensor offline notification.
• Vendor lock changes. Yale, Tado and Hive all push firmware that occasionally breaks integrations for a week or two. This is the single biggest reason holiday-let hosts running their own Home Assistant give up — they don't have a free Saturday to debug it. Managed service exists precisely for this category of problem.

Frequently asked questions

Can I run all my properties from one Home Assistant install? Technically yes, practically no. A single Home Assistant talking to four properties over the internet is fragile — one broadband outage takes everything offline at once. The professional pattern is one Pi per property, all reporting up to a fleet view. That's how habbb does it.

Will it work with my booking platform? If your platform exposes an iCal feed, yes. Airbnb, Vrbo and Booking.com all do natively, as do most direct-booking systems. Sykes and Cottages.com (Awaze) do not — for those, you either run a channel manager that re-exports a combined iCal or pair them with a separate direct-booking platform that does. Home Assistant reads iCal natively.

What happens if the Pi fails? We replace it. Daily encrypted backups to S3 mean a replacement Pi can be flashed and shipped with your configuration intact. Typical turnaround is 48 hours from fault notification to the new unit landing.

Does this need a survey or installer visit? No. The kit ships pre-configured. You plug in ethernet and power, and we do the rest from our side over the tunnel. The only on-site work is if you want a smart mains water valve or hardwired sensors — that's an electrician job, separate from us.

What about GDPR for guest data? Guest data we touch is limited — an iCal feed entry is typically just dates and a guest name. We don't process payment data, ID verification, or anything you'd need a DPIA for. Standard data-processor terms cover the relationship; we'll send them with the contract.

Can my cleaner or property manager have their own login? Yes. Each Home Assistant supports multiple users with scoped permissions. A cleaner can have a dashboard that shows lock status and "next guest" without seeing the booking financials or the ability to change automations.

Is there a contract? No minimum term. Monthly subscription, cancel any time, kit is yours either way. We earn the renewal each month or we don't.

Where to start

If you've read this far, you almost certainly have at least one property where the heating costs more than it should and one near-miss leak story you'd rather not repeat. The realistic order is: start with one cottage, prove the heating-between-guests savings to your own satisfaction over a season, add the leak sensors and locks once you trust the system, then roll the same configuration to the rest of the portfolio.

If you'd rather not run any of it yourself — or you've already started and the second property has stalled — tell us about your properties and we'll come back with a portfolio quote. Two properties or twelve, the answer is usually shorter than you'd think.