Home Assistant for Property Managers (US Portfolio Guide, 2026)

It's 11 p.m. on a Tuesday. A tenant in unit 14 calls because the heat won't come on, and the thermostat is showing a code she doesn't recognize. You're in bed. You don't own unit 14 — the owner lives in another state and pays you eight percent of gross to make this her problem and not theirs. So you get up, open four apps to figure out which thermostat is in unit 14, can't remember which Wi-Fi network it's on, and end up calling the on-call HVAC tech because it's faster than diagnosing it yourself. That's $180 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 twenty-three doors. This is the operational reality every small-to-mid US property manager hits, and it's the reason Home Assistant for property managers is becoming a serious procurement conversation rather than a hobbyist one.

If you're running a UK portfolio rather than a US one, the same playbook with UK-shaped insurance carriers, HHSRS heating obligations, GDPR rather than state-by-state privacy regimes, and Reapit/Arthur/Yardi rather than Buildium/AppFolio lives at Home Assistant for UK Property Managers.

What changes when 23 doors are on one fleet

The pattern with smart devices in a portfolio is almost always the same. The first owner to hand you a property put a Nest in it. The second owner installed Schlage Encodes on a recommendation from her brother-in-law. A third bought Ecobees because they were on sale at Costco. Each owner thought they were doing you a favor. The result is a manager 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 unit 14's thermostat is offline, unit 7's leak sensor under the kitchen sink is reporting moisture, and the lock on the side door of the duplex on Maple needs a battery this week. The phone call from the tenant in unit 14 is now a thirty-second triage instead of a forty-minute scavenger hunt.

Bulk operations. When daylight saving time changes, every thermostat schedule shifts in one operation. When you sign a new cleaning company, every cleaner code on every lock rotates in one operation. When the owner of three properties asks for vacation-mode setpoints across all three while she travels, 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 an owner asks why the unit 9 heat ran at 75°F 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. Insurance carriers and disputing tenants both 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 — Hostfully, Guesty, Hostaway, Buildium, AppFolio, or whichever you've standardized on — handles the things only software with access to your booking data and your accounting can handle. Bookings, calendars, listings sync, owner statements, rent collection, tenant screening, lease management, work-order ticketing, marketing automation. That's the business layer.

Home Assistant handles the device layer. The thermostats, locks, leak sensors, energy clamps, occupancy sensors, smart plugs, water valves, garage door controllers, and whatever else physically exists inside the property. Home Assistant doesn't know about leases. It doesn't run rent. It doesn't issue 1099s. 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; 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 your PMS 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 iCal feeds.

Heating across a portfolio

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

The pattern is straightforward. Each unit has a known set of states: occupied long-term lease, occupied short-term booking, vacant between tenants, vacant for owner-stay, vacant for renovation, vacant for the season. Each state implies a different thermostat behavior. A long-term tenant gets full thermostat control within sane min/max bounds — landlord-tenant law in most states means you can't lock the tenant out of their own heating. A short-term booking inherits per-booking setpoints from the iCal feed. A vacant unit drops to a holding value — typically 50°F frost-protect in winter, 85°F humidity-cap in summer, neither of which is comfortable but both of which prevent damage.

The thermostat brand matters less than the integration quality. Ecobee has the most polished Home Assistant integration and is the safest default for a manager standardizing across a portfolio. Honeywell T9 works well for forced-air HVAC and is widely deployed in newer construction. Nest (Learning, 3rd-gen, and the newer 4th-gen) is supported but the Google integration is more brittle on multi-property setups — when it works, it works; when it breaks, it breaks for everybody at once. Mysa is the right answer for the electric-baseboard units common across northern New England and older mountain rentals. Sensibo is the choice when the unit has ductless mini-splits, which is increasingly common in newer Florida and Southwest builds.

For a manager, the operational win isn't on any individual property — it's the per-vacancy mode across the portfolio. When a tenant moves out of unit 9 and the unit will sit empty for nineteen days while the painters work, that's nineteen days of "vacant for renovation" thermostat behavior, and the manager flips that switch once. When unit 14 is going on the market and needs to be presentable for showings, that's "vacant with showing buffer" — holding low, ramping to comfortable thirty minutes before each agent's scheduled walkthrough.

Smart locks at portfolio scale

The second universal pain point. At 23 doors, key handover stops being something you can do in person and becomes either a lockbox-and-pray approach or a smart-lock-and-codes approach. Most managers end up at smart locks within a year.

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 lease and rotated annually. A short-term guest gets a code derived from their reservation, 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 owner gets a code that's always valid because it's their building.

For a US portfolio the safe default is the Schlage Encode (the Wi-Fi-enabled Encode, not the older Connect Z-Wave). It's the most widely deployed STR and small-multifamily lock in the country, the integration via the SchlageHome cloud is reliable, and the hardware survives the cycle counts a portfolio puts on it. The Yale Assure 2 with the Wi-Fi module is the alternative when you've inherited deadbolt cutouts the Encode doesn't fit. August locks (now Yale-owned) trend more toward homeowner than commercial use and don't survive 50-door portfolios as well in the field. 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.

The audit trail matters more here than anywhere else. When a tenant claims the lock didn't work, when an owner asks who entered the property on a specific day, when an insurance carrier 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: water damage is the single most common and most expensive claim across small-multifamily and short-term rental portfolios. A slow leak in an unoccupied unit runs for days before anyone notices. A burst supply line on a vacant Tuesday in February will destroy the unit below it.

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 water heater, behind the toilet. 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. Moen Flo and Phyn Plus are the two whole-property valves with mature Home Assistant integrations. Both fit on the main supply line just past the meter, both expose flow, pressure, and temperature, and both can be closed remotely or automatically when a leak is detected.

The angle that matters for a property manager — and the one most managers don't push hard enough — is the insurance discount. Several major US carriers (State Farm, Travelers, Liberty Mutual, Chubb among them) offer premium discounts for properties with monitored leak detection or automatic shutoff. The discount is often 5–10% on the dwelling premium and varies by carrier and state. Two things matter for the discount: the device has to be installed by code, and the carrier usually wants documentation the system is monitored. A portfolio-wide deployment with a habbb-managed monitoring layer behind it is exactly the documentation the carrier will accept. Worth a phone call to your broker before the next renewal.

Energy reporting per door

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

Sense is the consumer-friendly choice — easy to install, decent device disaggregation, clean Home Assistant integration. Emporia Vue is the more transparent option with sixteen individual circuit clamps and raw data without disaggregation guesswork. Either is fine; pick one and standardize.

What you actually do with this data, as a manager:

• Per-door $/month report. Roll up energy consumption per property per month and put it in the owner statement. Owners who never look at their PG&E or Duke bill suddenly notice a $340 month on a vacant condo and ask why. That's a conversation that justifies a smart-home platform on its own.
• Heating-on-empty pattern detection. A heat pump drawing 4 kW at 2 a.m. on a Wednesday in a vacant unit is the most common automation failure and the one that costs the most. Energy data flags it within 24 hours instead of when the owner sees the bill.
• Cleaner and contractor visibility. A 90-minute dryer draw mid-afternoon means the cleaner ran a load. A six-hour heat-lamp draw on a vacant property's deck means somebody left it on. These show up in the data without any extra device.

Tenant privacy — state by state

There is no single federal privacy law that covers what a property manager can and can't deploy in a tenant's unit. California (CCPA), Virginia (VCDPA), Colorado (CPA), and a growing list of other states have their own data-protection regimes, and the pattern is widening every legislative session. The general principle is the same across them: tenants have a right to know what's collected, why, and to request deletion.

For a manager running smart-home devices across the portfolio, three rules cover most of the ground.

Cameras inside leased private spaces are off the table. Any camera in a unit a tenant occupies is a problem under landlord-tenant law in essentially every state, regardless of disclosure. Don't deploy them. Exterior cameras in common areas of small-multifamily are usually fine when disclosed in the lease.

Decibel-only noise sensors must be disclosed in the lease. Devices like Minut and NoiseAware that report decibel levels without recording audio are a legitimate tool for catching parties in short-term rentals and noise complaints in long-term, but the tenant has to know they exist. The disclosure goes in the lease, not the welcome packet.

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 booking-data layer or the tenant-data layer. Your PMS holds the lease, the names, the credit references, the move-in dates. Home Assistant holds the device states. The two are deliberately separated, and that separation is part of how a property manager 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 US service is Bring-Your-Own-HA at $60/month per property plus state sales tax (added at checkout via Stripe Tax), no contract, cancel any time. We adopt your existing Home Assistant install — whatever hardware it's running on — and run the operational layer behind it. If a property doesn't have a Home Assistant hub yet, the cheapest reliable option is a Raspberry Pi 5 with an NVMe SSD, which runs around $130 to $180 in parts depending on where you buy.

That $60/property number is the published rate, and at three or five properties it's the right number. At twenty-three properties the math gets less obvious, and we're upfront about that: a portfolio rate is a conversation, not a published number. We're in beta and we'd rather work through your actual portfolio shape — number of properties, mix of long-term and short-term, what's already deployed — than commit to a rate card we'd want to revise. If you're managing more than five doors, email us 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 room to the system is a separate job.

The $60/property/month 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, manager-to-engineer.

What's quoted separately:

• New automations built from scratch — typically $60+ for something simple, $100+ for a new integration category (rolling out noise monitoring across the portfolio, for instance).
• One-off projects: new dashboards, multi-property reporting, owner-statement export, rebuilding a property whose smart-home stack grew organically and needs straightening out.
• Regulatory compliance is your responsibility, not ours. Lease disclosures, ADA, state-by-state landlord-tenant law, short-term rental ordinances, HOA approvals — 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, owners, current devices per property, current PMS, 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 standardize the dashboard, port over whatever automations exist, and tie the iCal/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 SLA behind it.

For a 23-property portfolio this is roughly a three-month onboarding. For a 50-property portfolio it's six months. The pace is deliberate — moving faster means missing edge cases per property that turn into 11 p.m. 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 prioritized. We don't currently publish an uptime SLA with credits attached because we're in beta — 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 the owner of property 9 cancels and walks, their data goes with them and the other 22 properties are untouched.

What happens when a property leaves the portfolio? You keep the hardware, the owner 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 managers prefer one consolidated monthly invoice with a per-door breakdown, so they can pass the line item through to owners on their statements. Some prefer separate invoices per property for accounting reasons — that works too.

Does habbb integrate directly with Hostfully, Guesty, Buildium, AppFolio? Indirectly. Home Assistant ingests the iCal feeds those PMS platforms expose for each property, and that's how check-in and checkout automations are triggered. For deeper integration — pulling tenant move-in dates from Buildium, syncing work orders from AppFolio — 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 50 doors? Talk to us. The shape of the service is the same up to a point, but past 50 doors there are real procurement and operational questions — dedicated support, priority response, owner-portal integration — that shift the conversation. We're not the right fit for a 500-door REIT yet, but we may be the right fit for the 75–150 door manager who's outgrown the spreadsheet-and-vendor-app approach.

Get in touch

The US service launched in beta on May 9, 2026. We're onboarding managers a wave at a time so we can do it right. For a single-pilot property to feel out the service, you can subscribe directly to a one-property starter plan. State sales tax is added at checkout.

Subscribe — $60/month + tax

For a real portfolio rollout — five to fifty doors, mix of long-term and short-term, 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.

The 11 p.m. phone call is never going away entirely. But it can be a thirty-second triage instead of a forty-minute scavenger hunt, and it can hit your pager before it hits the tenant's phone.