HVAC AI Agents home

Private beta · Home Assistant

Bring every HVAC brand into Home Assistant.

An MCP-style bridge that runs on your edge box. 20+ HVAC brands appear as HA entities. Local-first — no cloud signup required. Optional Claude / ChatGPT layer on top.

Join the waitlist →

20+

HVAC brands as HA entities

Daikin, Mitsubishi, Carrier, LG, Samsung…

local-first

no cloud signup

runs on your Pi / NUC / edge box

optional LLM

Claude / ChatGPT layer

ride on top of HA entities via MCP

Three modes — MCP leads here

Primary for this page

Bridge runs locally

Drop the bridge on your HA box. Every supported HVAC brand surfaces as HA entities with setpoint + telemetry under HA control.

Optional LLM copilot

Bring Claude or ChatGPT in via MCP — ask about your house in plain English when HA's UI isn't enough.

Automations + agents

Existing HA automations keep working. New: let an agent run a scenario for you.

Home Assistant integration

Home Assistant bridge — Daikin, Mitsubishi, Fujitsu, and more as native HA climate entities.

HVAC AI Agents' HA bridge surfaces brand-cloud mini-splits and VRF systems as native Home Assistant climate, sensor, and switch entities — event-driven where the brand supports push, polling only as a fallback — running on your LAN with no persistent cloud dependency.

The problem with most HVAC integrations in Home Assistant is that they're built on polling. Every 30 seconds, the integration calls the brand cloud, waits for a response, and updates the entity state. If the cloud is slow, state is stale. If the cloud is down, the entity is unavailable. And if you change the temperature at the physical remote, Home Assistant doesn't know for up to 30 seconds. For mini-splits in a living space or a managed rental, that lag is perceptible — and the cloud dependency is a privacy concern.

The bridge solves this by connecting to brand clouds over their native push APIs where available. Daikin and Mitsubishi Electric both offer websocket or server-sent-event channels for state changes; the bridge subscribes at startup and propagates state updates to Home Assistant within one to two seconds of a physical remote change. For brands that have no push channel — some Fujitsu General models, older Honeywell Home thermostats — the bridge falls back to adaptive polling, shortening the interval when activity is detected and backing off during idle periods.

The bridge runs as a Home Assistant add-on or a standalone Docker container on your LAN. Brand cloud credentials are stored locally; the cloud is only contacted for authentication and for brands with no local API. Daikin's local BRP072 gateway is supported for fully local operation with no cloud dependency at all. When the brand cloud is unreachable, the last known state persists in Home Assistant and the bridge retries silently — your automations continue running against cached setpoints rather than throwing unavailable errors.

Multi-property mode lets a single bridge instance manage multiple physical locations — each with its own brand cloud account — under one Home Assistant install. This is designed for short-term rental managers and residential service companies who maintain a single HA server for a portfolio of properties. Each property appears as a separate area in HA with properly scoped entities, and the bridge enforces that automations in one property area cannot address entities in another.

Who uses the bridge

Four scenarios where the HA bridge replaced a broken or missing integration.

Prosumers, integrators, and property managers — what they needed and what they got.

Prosumer with a Daikin VRV at home

Daikin VRV system had no reliable HA integration. Available community integrations polled every 60 seconds, missed state changes from the physical remote, and went unavailable whenever the Daikin cloud had an outage — which broke temperature-triggered automations nightly.

→ Bridge connected via Daikin's native push channel. Physical remote changes appear in HA in under two seconds. Cloud outage tolerance means automations run against cached state rather than failing. No integration restarts needed.

Sub-2-second state sync from physical remote

Smart-home integrator for a 12-unit luxury condo

Each unit had Mitsubishi Electric mini-splits. Twelve separate cloud accounts, twelve separate polling integrations, a HA instance that took 10 minutes to load, and residents complaining that the app showed the wrong temperature.

→ Single bridge instance manages all 12 units, each as a scoped area in HA. Push-based state sync keeps displayed temperatures accurate. HA startup time dropped from 10 minutes to under 90 seconds.

12 units, one bridge, accurate state

Multi-property Airbnb host with 8 listings

Eight properties across three HVAC brands — Daikin, Ecobee, and Honeywell Home. Three separate apps, no unified view, no way to set arrival pre-conditioning across the portfolio from a single automation.

→ Bridge normalizes all three brands into HA climate entities in one instance. A single Airbnb webhook triggers pre-conditioning across the right property 90 minutes before guest check-in, regardless of which brand is installed.

One automation triggers across 3 HVAC brands

HA enthusiast consolidating mixed brands

Nest thermostat on the main floor, Ecobee in the addition, and a Daikin mini-split in the garage — three separate integrations with different polling intervals, different entity schemas, and no shared energy dashboard.

→ Bridge provides a uniform climate entity schema across all three brands. Energy totals roll up into one Energy dashboard. A single Lovelace card shows current temp, setpoint, and mode for every zone in the house.

Uniform entity schema across 3 brands

FAQ

Home Assistant bridge — common questions.

  • Which HVAC brands does the bridge cover?

    Production integrations are available for Daikin (Onecta cloud and local BRP072 gateway), Mitsubishi Electric (MELCloud), Fujitsu General (Airstage), Ecobee (SmartThermostat and SmartSensor), Nest via Google Device Access API, and Honeywell Home (T6, T9, T10 series). Additional brands ship quarterly. Check /coverage for the current model-level support matrix, or contact us with your specific model numbers to confirm compatibility before purchasing.

  • How do I install the bridge in Home Assistant?

    The easiest path is the HA add-on: open the Add-on Store, add our repository URL, install the bridge add-on, and enter your brand cloud credentials in the add-on configuration UI. The bridge registers a custom integration that creates climate entities automatically. A standalone Docker container is also available for users who run HA Container or want to host the bridge separately. The full installation guide is in our documentation — request access from the form below and we'll send you the repo link.

  • Is it local-first or does it require a cloud connection?

    Local-first by design. The bridge runs on your LAN and only contacts brand clouds for authentication tokens and for brands that have no local API. Daikin BRP072 gateway users can operate fully offline — no cloud traffic at all. For brands that require cloud API calls (Ecobee, Nest, Mitsubishi MELCloud), the cloud is used as a relay, but the bridge caches last-known state locally. If the cloud is unreachable, your HA entities stay available with cached state rather than going unavailable.

  • Push vs. polling — how does it work per brand, and what's the actual latency?

    Daikin Onecta and Mitsubishi MELCloud support server-sent events or websocket push channels; the bridge subscribes at startup and state changes propagate to HA in one to two seconds. Ecobee uses a long-polling API that delivers updates within three to five seconds. Nest via Google Device Access supports pub/sub events — updates arrive in under two seconds. Fujitsu Airstage and Honeywell Home currently have no push channel; the bridge polls every 15 seconds with adaptive shortening when activity is detected.

  • Multi-property mode — how do scopes work?

    In multi-property mode you define a list of properties in the bridge configuration, each with its own name, set of brand cloud credentials, and optional area mapping. The bridge creates a separate HA area for each property and registers all entities under it. Automations referencing area A cannot address entities in area B — the bridge enforces this at the entity registration level. You manage all properties from one HA instance and one bridge configuration file. Multi-property mode is available in the Pro tier.

  • What happens if the brand cloud goes down?

    The bridge stores the last known state for every entity locally. If the brand cloud becomes unreachable, entities remain in their last known state — they do not go unavailable or throw errors in automations. The bridge logs the outage, retries the connection with exponential backoff, and resumes normal operation when the cloud recovers. Set-temperature commands issued during an outage are queued and replayed on reconnect. This behavior is configurable — you can choose to surface unavailability explicitly if you prefer.

  • Is the bridge free or paid?

    A single-property install with up to three devices is free indefinitely — no account required for the basic add-on. Multi-property mode, adaptive polling, outage queuing, and priority brand support are in the Pro tier, billed annually per bridge instance with unlimited devices and properties. A 30-day Pro trial is available without a credit card. Request the trial from the form below and we'll activate it on your instance same-day.

Speaks to your existing kit

Carrier, Trane, Daikin, Mitsubishi, LG, Lennox, York, Samsung — 20+ HVAC, home-automation, and BMS brands.

63 brands across 3 categories — HVAC (31), Home Automation (18), BMS (14). Protocols: BACnet, KNX, MQTT, Matter, Modbus, REST, WebSocket, Z-Wave, Zigbee.

See full coverage →

How it stays out of your way

Secure

Sealed data plane. Per-site auth. Audit log on every setpoint touch.

Runs on the edge

Deploys at the building edge — your data doesn't leave the site to be useful.

BYO LLM

Works with Claude, ChatGPT, and any MCP-compatible client. You pick the brain.

Private beta

Get the bridge early.

Designed for Home Assistant power users + smart-home tinkerers.