Home Assistant for UK Property Managers (Portfolio Guide 2026)

Published 14 May 2026 · 21 min read

Some links in this guide are Amazon affiliate links — we earn a small commission if you buy, at no cost to you. We only recommend kit we'd put in our own homes.

It's 11pm on a Tuesday. A tenant in flat 14 of a Bristol block rings because the heating won't come on, and the thermostat is showing a code she doesn't recognise. You're in bed. You don't own flat 14 — the landlord lives in Edinburgh and pays you eight percent of gross rent to make this her problem and not theirs. The boiler service contract is with British Gas, but the smart thermostat was installed by the previous letting agent and is on a Tado app you've never logged into. You don't know which Wi-Fi network it's on. You don't know whose phone the original verification SMS went to. So you get up, open four apps to work out which thermostat belongs to flat 14, can't get into the one that matters, and end up dispatching the on-call gas engineer because it's faster than diagnosing it yourself. That's £140 you're either eating or passing on, and either way you've spent forty minutes of your evening on a problem that should have taken sixty seconds.

Multiply that by forty-seven doors. This is the operational reality every small-to-mid UK letting agency and property manager hits, and it's the reason Home Assistant for property managers is becoming a serious procurement conversation rather than a hobbyist one.

What changes when 47 doors are on one fleet

The pattern with smart devices in a UK portfolio is almost always the same. The first landlord to hand you a property put a Hive in it because British Gas were already servicing the boiler. The second landlord installed Yale Conexis locks on a recommendation from a builder. A third bought Tado X because it was on offer at John Lewis. A fourth has a Drayton Wiser system the developer fitted at handover. An HMO down the road has Aqara sensors a tech-minded tenant installed and left behind. Each landlord thought they were doing you a favour. The result is a managing agent logging into seven vendor apps, none of which know about each other, none of which know which doors belong to which property, and none of which expose anything that looks like a portfolio view.

A single Home Assistant fleet — one logical platform spanning every property under management — changes three things.

One dashboard. Every thermostat, every lock, every leak sensor, every energy clamp across the portfolio shows up in one view. You see at a glance that flat 14's thermostat is offline, flat 7's leak sensor under the kitchen sink is reporting moisture, and the lock on the side door of the HMO in Easton needs a battery this week. The phone call from the tenant in flat 14 is now a thirty-second triage instead of a forty-minute scavenger hunt.

Bulk operations. When the clocks change at the end of October, every heating schedule shifts in one operation. When you sign a new cleaning company for your serviced lettings, every cleaner code on every lock rotates in one operation. When a landlord with three properties asks for void-mode setpoints across all three while a refurb runs, that's one operation, not nine.

Audit trail. Every code use, every thermostat setpoint change, every door event, every leak alert is logged in one place with timestamps. When a landlord asks why flat 9's heating ran at 24°C for two days in March, you can answer the question. When a tenant claims the lock didn't work on move-in day, the log either backs them up or doesn't. Insurers, deposit-scheme adjudicators and disputing tenants all prefer answers over hand-waving, and one log file is the answer.

The PMS sits on top, Home Assistant sits underneath

This is the most important framing in this whole guide, because it determines whether habbb fits your business.

Your property-management software — Reapit, Arthur, Re-Leased, PayProp, Goodlord, Fixflo, HomeLet, or Yardi Voyager for build-to-rent — handles the things only software with access to your tenancy data and your client account can handle. Tenancy agreements, AST renewals, rent collection and reconciliation, tenant referencing, deposit registration with TDS/DPS/MyDeposits, repairs ticketing, EPC tracking, owner statements, marketing portal feeds to Rightmove and Zoopla. That's the business layer.

Home Assistant handles the device layer. The thermostats, locks, leak sensors, energy clamps, occupancy sensors, smart plugs, motorised water valves, communal-door controllers, and whatever else physically exists inside the property. Home Assistant doesn't know about tenancies. It doesn't run rent. It doesn't talk to HMRC. It runs the mechanical and electrical reality of the building.

The two layers are complementary, not competitive. The PMS knows when a tenant moves in; Home Assistant takes that signal and rotates the lock code. The PMS knows when a unit is vacant for refurbishment; Home Assistant takes that signal and drops the thermostat to a holding setpoint. The PMS books the cleaner; Home Assistant gives that cleaner a one-shot code that expires when they leave.

Anyone who tells you Home Assistant is going to replace Reapit or Arthur is either selling you something they don't understand or doesn't run a real portfolio. Anyone who tells you the PMS will manage your devices is selling you the integration their PMS happens to have, not the one your portfolio actually needs. The honest answer is both, in their own lanes, talking to each other through webhooks and the occasional iCal feed.

Heating across a portfolio

This is where the per-door pound savings show up first, and it's almost always the place a managing agent pilots.

The pattern is straightforward. Each unit has a known set of states: occupied long-term AST, vacant between tenancies, void for refurbishment, owner stay (for managed second-home lets), HMO room let separately. Each state implies a different heating behaviour. A long-term tenant gets full thermostat control within sane min/max bounds — any controls you deploy must respect the tenant's right to set their own comfort. The Homes (Fitness for Human Habitation) Act 2018 and the landlord's Section 11 repair obligations under the Landlord and Tenant Act 1985 mean you don't lock a tenant out of heating. HHSRS guidance (citing WHO standards) sets 18°C in occupied bedrooms and 21°C in living rooms as the minimum a heating system must be capable of maintaining at −1°C outside; an automation that prevents a tenant reaching those is potentially a Section 11 / FFHH hazard. Any min-cap lives somewhere the tenant can override — not below 18°C in occupied rooms. A void unit drops to a holding value — typically 8–10°C frost-protect during a refurb week — which prevents pipework damage without burning gas.

The thermostat brand matters less than the integration quality. Tado X (the post-2023 line with Matter support) has a polished Home Assistant integration and is the safest default for a managing agent standardising across a portfolio. Drayton Wiser has strong per-radiator zoning via its smart TRVs and is widely fitted by independent heating engineers across the south of England. Hive Active Heating is the default in any property where British Gas hold the boiler service contract — the integration is via the Hive cloud and is reliable, if less granular. Honeywell Evohome is the right answer for a larger property with eight or more heating zones and a landlord prepared to spend on the high end. Genius Hub is the strongest UK installer story for wet systems with per-room control and a managing agent who wants a single zone-by-zone view. Nest Learning is supported but less common in BTR; treat it as inherited rather than specified.

For a managing agent, the operational win isn't on any individual property — it's the per-void mode across the portfolio. When a tenant moves out of flat 9 and the unit will sit empty for nineteen days while the painters work, that's nineteen days of "void for refurbishment" heating behaviour, and the agent flips that switch once. When flat 14 is going on the market and needs to be presentable for viewings, that's "void with viewing buffer" — holding low, ramping to comfortable thirty minutes before each agent's scheduled viewing. The landlord-side gas bill during a void lands on the landlord, not the tenant, and a drift of a degree or two for three weeks costs them real money.

Smart locks at portfolio scale

The second universal pain point. At 47 doors, key handover stops being something you can do in person at the office and becomes either a key-safe-and-pray approach or a smart-lock-and-codes approach. Most agents end up at smart locks within a year of crossing 20 doors.

The Home Assistant pattern is one master per-property automation that issues fresh codes from the source of truth — your PMS. A long-term tenant gets a code that's valid for the duration of the AST and rotated annually. A short-let guest gets a code derived from their booking, valid from check-in to checkout. A cleaner gets a recurring code that's valid for the cleaning window and a buffer either side. A contractor gets a one-shot code valid for the work order's day. The landlord gets a code that's always valid because it's their building.

For a UK portfolio the safe default is the Yale Conexis L2 with the Yale Access module — it's the most widely deployed UK smart lock, the integration via the Yale cloud is reliable, and most UK locksmiths can fit one in an afternoon. The Nuki Smart Lock 4 Pro is the alternative when you want to keep the existing euro cylinder and motorise it from the inside; useful in flats where the building's communal door rules require an unmodified front-door barrel. Loqed Touch is widely specified in build-to-rent blocks where the developer has standardised on it across the scheme. Ultion Smart by Brisant is the right choice for properties where the existing key system is insurance-rated to TS007 3-star and the lock has to match — replacing a 3-star cylinder with something less secure can void the buildings policy. Igloohome is what you reach for when the property has unreliable internet, because it generates time-bounded PIN codes algorithmically without needing the lock to be online — useful for rural lettings and HMOs where shared Wi-Fi is unstable.

The audit trail matters more here than anywhere else. When a tenant claims the lock didn't work on move-in day, when a landlord asks who entered the property on a specific day, when an insurer asks how access was controlled after a break-in — the log is the answer. One log, all properties, queryable.

Leak detection and water shutoff

Insurance loss data is consistent year after year: escape of water is the single most common claim across UK residential portfolios. Aviva data shows escape of water accounted for ~24% of all home insurance claims in 2024, and the ABI reports the average property-insurance claim has risen to roughly £6,000 in 2025 (a ~15% year-on-year increase). A slow leak in an unoccupied flat above another can run for days before anyone notices. A burst supply line on a void Tuesday in February will destroy the flat below.

The minimum viable setup is a battery-powered Aqara Zigbee leak sensor under every fixture that can fail in every unit — every sink, the dishwasher, the washing machine, the boiler, behind the WC. They're cheap, they live for years on a CR2032, and they report instantly to Home Assistant.

The next step up is automatic shutoff at the rising main. The UK whole-property valve market is less mature than the US — there's no direct equivalent of the Moen Flo as a packaged consumer product. The practical UK approach is LeakSafe for new-build BTR specifications, Surestop (the manual quarter-turn version, retrofittable as a motorised assembly) for older stock, and a Shelly-driven motorised ball valve on the rising main where an installer is comfortable building it. Home Assistant ties leak detection to valve closure with the appropriate confirmation steps so a false positive doesn't dry out a tenant at 3am.

The angle worth pushing — and the one most managing agents don't push hard enough — is the insurance conversation. UK carriers don't publish a leak-detection discount the way some US ones do, but the mechanism exists at the broker level. Aviva has partnered with HomeServe Labs to deploy LeakBot (a smart-meter-clamp leak monitor) directly into customer policies since 2016, and Direct Line, NIG, AXA Commercial, Hiscox and Allianz all underwrite for landlord buildings cover with rate-setting flexibility your broker can use when a property has monitored leak detection and ideally an automatic shutoff valve fitted by an installer. The discount mechanic is broker-negotiated rather than published — a phone call with your broker before next renewal, with photographs of the deployed kit and a one-page note on the monitoring layer, is the right play. Carriers respond to the reduced claim frequency the monitoring evidences, not to a brand. Across a 25-door portfolio even a single-digit reduction on buildings premium pays the smart-shutoff hardware back in two to three years.

Energy reporting per door

A panel-level current clamp at every property gives you something the individual smart devices can't: a per-door pound number you can put in front of a landlord.

The Hildebrand Glow IHD is the right starting recommendation for the UK because it talks directly to the smart-meter HAN radio — no electrician, no consumer-unit work, no DNO conversation. Plug it in, pair it, and the property's half-hourly electricity (and gas, where the smart-meter pairing supports it) flows into Home Assistant. For a managing agent with a portfolio of properties that already have second-generation smart meters, this is the path of least resistance. The Shelly Pro 3EM is the more granular option — three CT clamps in the consumer unit, sub-circuit visibility, and the right answer when the landlord wants per-zone consumption or when the property doesn't yet have a smart meter. The Emporia Vue 3 is available via UK importers but the cost and PSU-conversion friction means most managing agents won't bother once Glow IHD is in.

What you actually do with this data, as a managing agent:

Per-door £/month report. Roll up energy consumption per property per month and put it in the landlord statement. Landlords who never look at their Octopus or British Gas bill suddenly notice a £180 month on a void flat and ask why. That's a conversation that justifies a smart-home platform on its own.
Heating-on-empty pattern detection. A boiler firing for six hours overnight in a void flat is the most common automation failure and the one that costs the most. Energy data flags it within 24 hours instead of when the landlord sees the bill. The £80–£120/yr drift in landlord-side heating costs during voids is a number worth quoting back at landlords on renewal.
Cleaner and contractor visibility. A 90-minute tumble-dryer draw mid-afternoon means the cleaner ran a load. A six-hour heat-lamp draw on a void flat's hallway means somebody left it on at the last viewing. These show up in the data without any extra device.

UK property managers have a simpler regulatory landscape than their US counterparts. There is one regime — UK GDPR plus the Data Protection Act 2018 — and the ICO publishes practical guidance for landlords and property managers on the use of smart devices in let property. You don't have a state-by-state patchwork to navigate; you have one set of principles (transparency, purpose limitation, data minimisation, lawful basis, data subject rights) and one regulator to answer to.

Three rules cover most of the ground.

Cameras inside leased private spaces are off the table. Any camera inside a flat or house let on an AST is a problem under UK GDPR and a likely breach of the tenant's Right to Quiet Enjoyment under common law and the Protection from Eviction Act 1977, regardless of disclosure. Don't deploy them. Exterior cameras covering communal areas of a block of flats are workable when there's a clear lawful basis (usually legitimate interests for building security), the cameras don't intrude on individual flats' windows, and there's signage and a published privacy notice — but that's a block-level decision the freeholder takes, not a managing-agent default.

Decibel-only noise sensors must be disclosed in the tenancy agreement. Devices like Minut that report decibel levels without recording audio are a legitimate tool for catching parties in serviced lets and persistent noise complaints in HMOs, but the tenant has to be told they exist before they sign. The disclosure goes in the AST, not the welcome pack handed over on move-in day.

habbb stores no tenant PII. This is worth being explicit about. We touch the device layer — thermostats, locks, sensors, energy clamps. We don't touch the tenancy-data layer. Your PMS holds the tenancy, the names, the references, the deposit ID, the move-in dates. Home Assistant holds the device states. The two are deliberately separated, and that separation is part of how a managing agent keeps tenant data exposure narrow when a smart-home platform sits in the building. We do not see tenant names, payment information, or anything that wouldn't be visible to whoever has physical access to the property.

Pricing at portfolio scale

habbb's UK service has two paths. The Kit path is £150 one-off hardware (a pre-configured Raspberry Pi 5 with internal NVMe SSD, shipped within the UK) plus £30/month per property subscription, inc. VAT — the right choice for a property that doesn't yet have a Home Assistant hub. The BYOHA path is £40/month per property inc. VAT with no hardware, which is the right choice when you've inherited a Home Assistant install (or want to commission one on a Pi or Yellow you already own) and you want us to take over the operational layer.

Both are no-contract, cancel any time.

Those numbers are the published rates, and at three or five properties they're the right numbers. At forty-seven properties the maths gets less obvious, and we're upfront about that: a portfolio rate is a conversation, not a published number. We'd rather work through your actual portfolio shape — number of doors, mix of long-term AST and serviced lets, HMO count, what's already deployed — than commit to a rate card we'd want to revise. If you're managing more than five doors, drop us an email and we'll work it through with you.

What's out of scope

The boiler-service analogy is the clearest framing we have. We maintain what's there. Adding a new radiator to the system is a separate job.

The per-property monthly subscription covers:

Secure remote access to each property's Home Assistant via Cloudflare tunnel.
Daily encrypted off-site backups.
Tested Home Assistant updates — we validate before we upgrade your fleet.
24/7 health monitoring across the portfolio with alerts to us, not you.
Fixes and tweaks to the automations already running.
Hands-on email support, agent-to-engineer.

What's quoted separately:

New automations built from scratch — from £45 for something simple, from £75 for a new integration category (rolling out noise monitoring across the portfolio, for instance).
One-off projects: new dashboards, multi-property reporting, landlord-statement export, rebuilding a property whose smart-home stack grew organically and needs straightening out.
Regulatory compliance is your responsibility, not ours. HMO licensing, BTR ESG reporting, MEES / EPC requirements for lettings, How to Rent guide distribution, Right to Rent checks, deposit protection deadlines, gas safety certificates — none of those are things a smart-home platform can absolve you of. We give you the device layer; you run the business.

We scope each project before starting. Nothing happens until you've agreed.

Onboarding flow

A portfolio doesn't get onboarded in a weekend, and any vendor who tells you it does has either never done it or is going to leave you with a mess. Our practical timeline:

Week 1. Discovery call. We walk through the portfolio with you — properties, landlords, current devices per property, current PMS (Reapit, Arthur, whatever), the two or three operational pains you most want addressed first. We come back with a written scope and pricing.

Week 2–3. First wave: roughly five properties. We adopt the existing Home Assistant install at each one, or stand one up if there isn't one. We standardise the dashboard, port over whatever automations exist, and tie any iCal or PMS feeds in. By the end of the wave, those five properties are fully on the managed platform.

Week 4 onward. Subsequent waves of about five properties at a time, two to three weeks per wave. Each wave gets the same treatment as the first. By the time you're done, the whole portfolio is under one dashboard, with one set of automations, and one operational standard behind it.

For a 47-door portfolio this is roughly a three-month onboarding. For a 100-door portfolio it's six months. The pace is deliberate — moving faster means missing edge cases per property that turn into 11pm phone calls later.

FAQs

What's the SLA on the managed service? We monitor every property's Home Assistant 24/7 and respond to detected outages within an hour during business hours and within four hours overnight. Tenant-impacting issues (heating offline in winter, lock offline at a check-in) get prioritised. We don't currently publish an uptime SLA with credits attached because we're a young service — that's a conversation we'd rather have with your specific portfolio than commit to before we know it.

How is data isolated between properties? Each property runs its own Home Assistant instance on its own hardware. There is no shared database. The portfolio dashboard is a logical aggregation across the per-property instances, not a single instance pretending to be many. When a landlord pulls a property out of management, their data goes with them and the other 46 properties are untouched.

What happens when a property leaves the portfolio? You keep the hardware, the landlord keeps the Home Assistant install, and we hand back the tunnel configuration if they want to keep running it themselves. We remove our admin user, stop billing, and the property comes off your dashboard cleanly. No exit fee, no contract.

Do you bill per door or per portfolio? Either, your choice. Most agents prefer one consolidated monthly invoice with a per-door breakdown, so they can pass the line item through to landlords on their statements as a management ancillary. Some prefer separate invoices per property for client-account reasons — that works too.

Does habbb integrate directly with Reapit, Arthur, Yardi Voyager, Fixflo, PayProp? Indirectly out of the box. Where the PMS exposes iCal feeds — usually for serviced lets — Home Assistant ingests those and that's how check-in and checkout automations are triggered. For deeper integration — pulling tenancy start dates from Arthur, syncing work orders from Fixflo, posting energy readings to a landlord statement in Reapit — we use the PMS's webhook or API on a per-customer basis as part of a scoped project. That's typically a one-off setup quoted alongside onboarding, not part of the base subscription.

What if my portfolio is bigger than 100 doors? Talk to us. The shape of the service is the same up to a point, but past 100 doors there are real procurement and operational questions — dedicated support, priority response, integration with your landlord portal — that shift the conversation. We're not the right fit for a 1,000-door institutional BTR landlord yet, but we may be the right fit for the 150–300 door regional letting agency or the build-to-rent operator commissioning a single 80-flat block.

Get in touch

For a real portfolio rollout — twenty to a hundred doors, mix of AST and serviced lets, no appetite for becoming a Home Assistant administrator — drop us an email with your portfolio size, your PMS, and what's currently breaking. We'll come back within a working day with a portfolio rate before you sign anything.

If you're a build-to-rent operator commissioning a new block of thirty-plus flats and choosing between the developer's bundled smart-home package, a DIY Home Assistant build, and a managed service — we'd particularly like to hear from you at scoping stage, not after the kit is fitted.