HVAC AI Agents home

Private beta · Home

An AI agent for your home HVAC.

Ask Claude or ChatGPT why your AC tripped at 3 AM. Designed to cut home HVAC bills 15-25%. Works with your existing smart-home stack.

Join the waitlist →

15-25%

designed bill reduction

compared to plain smart thermostats

minutes

to a 3 AM diagnosis

in a chat with Claude or ChatGPT

BYO

your LLM, your data

no vendor lock-in, no cloud round-trip required

Three modes — copilot leads here

Primary for this page

Ask-anything copilot

Chat with Claude or ChatGPT about your HVAC. The agent reads telemetry, explains in plain English, suggests the next move.

Quiet autonomy

Adjusts setpoints based on occupancy + weather + utility rate. You stay in charge — every change is logged.

MCP for Home Assistant

Bring every HVAC brand into Home Assistant via a tiny edge bridge.

Local-first residential HVAC

Your HVAC, your data — local-first agent that works with Alexa, Siri, and Google Home without cloud lock-in.

HVAC AI Agents' local-first mode runs on a small home server and operates your HVAC system without requiring any cloud services. Voice control works through the assistants you already use. Your thermostat data never leaves your network unless you explicitly enable cloud features.

Standard smart thermostats are cloud-dependent by design. Every temperature reading, every schedule change, and every voice command transits a vendor's cloud before it reaches your equipment. If that cloud goes down — and they do — your automations break, your voice commands fail, and your historical data is inaccessible. For households with unreliable internet or strong privacy preferences, this architecture is a fundamental problem, not an inconvenience.

The local-first mode solves this by running the agent process entirely on your home network. A Raspberry Pi 4 or any always-on mini PC is sufficient. Brand cloud connections are optional and disabled by default — for thermostats with local API support (Daikin BRP072, Ecobee local API, Home Assistant-native devices), all control and monitoring happens over LAN. Thermostat data is stored in a local database on your hardware. No vendor has access to your usage patterns, schedules, or occupancy signals.

Voice control integrates with the assistants you already have. The agent exposes your HVAC zones as Home Assistant entities, which Alexa, Google Home, and Apple HomeKit can address natively through their existing HA integrations. You say 'Hey Siri, set the bedroom to 70' and the command goes: Siri → HomeKit → local HA → agent → thermostat, entirely within your home network. No new speaker, no proprietary cloud gateway, no HVAC-specific voice skill to install and maintain.

Vendor lock-in protection means the agent stores all settings and historical data in open, portable formats. If you switch thermostat brands, add a new HVAC system, or move to a different automation platform, your data comes with you. Integration adapters are open-source. The agent has no proprietary protocol — it reads brand APIs using their documented interfaces and stores results in standard schemas. This is the architectural opposite of thermostat ecosystems that silo your usage data behind a vendor login.

Who uses local-first mode

Four households where cloud dependency was the problem, not the solution.

Privacy-conscious owners, voice enthusiasts, and off-grid households — what drove them here and what they gained.

Privacy-conscious homeowner avoiding cloud thermostats

Smart thermostat cloud account was breached in a vendor data incident — occupancy patterns, daily schedule, and location data exposed. Homeowner wanted HVAC automation with zero cloud footprint but without giving up scheduling, zoning, or remote access when traveling.

→ Local-first mode runs entirely on a home NUC. All thermostat data is stored locally. Remote access when traveling is via a self-hosted VPN — no vendor cloud in the path. Occupancy and schedule data are never transmitted to any external server.

Zero vendor cloud touches for day-to-day HVAC operation

Voice-control enthusiast with deep Alexa and Siri integration

Existing HVAC voice control required separate Alexa skills for each thermostat brand, each with different command syntax, inconsistent response quality, and regular skill-breakage when vendors updated their APIs. Adding a new HVAC brand meant setting up another skill.

→ Agent exposes all zones as standard Home Assistant climate entities. Alexa and Siri address them through their native HA integrations with uniform command syntax. Adding a new brand means adding an HA adapter — no new skills, no new cloud accounts in the voice path.

One voice interface across all HVAC brands, zero skill maintenance

Off-grid household with unreliable internet

Rural property with a satellite internet connection that drops for hours during storms. Cloud-dependent thermostats went into manual mode during outages, breaking pre-set schedules and automated ventilation. Recovery after reconnect required manual resets.

→ Local-first mode treats internet availability as optional. All schedules, automations, and zone coordination run on-device. During internet outages the system operates identically to normal operation. Cloud sync resumes automatically on reconnect with no manual intervention.

Full HVAC automation maintained through multi-hour internet outages

Anti-vendor-lock-in tinkerer switching thermostat brands

Three years of Ecobee schedule history, occupancy data, and comfort preferences were locked inside the Ecobee cloud account. Wanted to switch to a Daikin system but couldn't migrate the historical data — would start from scratch with zero baseline for the new system.

→ Agent stores all historical data in a local time-series database in a documented open schema. When the switch to Daikin was made, historical baselines migrated without loss. The new system's auto-schedule seeded from three years of prior occupancy patterns from day one.

Three years of thermal history preserved through brand switch

FAQ

Local-first residential HVAC — common questions.

  • Is this really local-first or does it just say that?

    Genuinely local-first. The agent process runs on hardware you own. Brand cloud connections are disabled by default and only enabled if you explicitly turn them on for a specific brand that has no local API. For thermostats with local API support — Daikin BRP072 gateway, Ecobee local API, any Home Assistant-native device — every command, every temperature read, and every schedule update stays on your LAN. We publish the full traffic manifest in the documentation so you can verify with a packet capture what, if anything, leaves your network.

  • Which voice assistants are supported?

    Alexa, Siri Shortcuts, and Google Home routines are all supported via the agent's Home Assistant integration. The agent exposes HVAC zones as standard HA climate entities; each assistant's existing HA integration handles the voice layer. No HVAC-specific skill, action, or shortcut is required. Command syntax is whatever you'd use to control any HA climate entity: 'set bedroom to 70 degrees', 'turn off the office AC', 'what's the temperature in the living room'. Adding a new thermostat brand adds an entity — the voice layer requires no changes.

  • What happens when the internet is down?

    Nothing changes for HVAC operation. All schedules, zone coordination, automations, and fault monitoring run on the local agent process. The internet connection is only used for optional cloud sync, remote access, and brands that have no local API. For fully local thermostats the system is completely internet-independent. For brands that require cloud API calls — Nest, some Ecobee configurations — those specific devices fall back to last-known setpoints during outages; local automations continue running. When connectivity restores, cloud sync resumes automatically.

  • Can I move my data if I switch thermostat brands or automation platforms?

    Yes — this is a core design principle. The agent stores all historical data in a local time-series database using an open, documented schema. Export is available in JSON and CSV formats at any time. If you switch from Ecobee to Daikin, your schedule history, occupancy patterns, and energy baselines migrate with you. If you move from Home Assistant to a different platform, the data export gives you everything you need to seed the new system. No data is held hostage behind a vendor account — it's on your hardware and in your formats.

  • How does this differ from the standard residential page?

    The standard /home residential agent is cloud-connected by default and optimized for prosumers with mixed-brand setups who want fast setup, multi-zone coordination, and energy cost visibility over their existing thermostats. This page describes the local-first mode, which trades cloud convenience for privacy, offline resilience, and no vendor lock-in. Both modes share the same core agent — the difference is where data is stored and which brand connections are cloud-relayed versus LAN-direct. You can also run both modes simultaneously on the same agent instance.

  • What hardware do I need?

    A Raspberry Pi 4 with 4 GB RAM is sufficient for up to 8 zones. For larger installs or if you want the agent to co-host with Home Assistant, an Intel NUC or equivalent mini PC with 8 GB RAM is recommended. The agent runs as a Docker container or a Home Assistant add-on. An always-on connection to your home LAN is required — wireless is fine for the agent host, but a wired connection is recommended for reliability. Storage needs are modest: a 32 GB SD card or SSD holds multiple years of thermal history for a typical home.

  • Is it free or paid?

    Local-first mode with up to three zones is free indefinitely — no cloud account required, no credit card, and the agent software is self-hosted on your hardware. Multi-zone coordination, voice-assistant integration helpers, and the open data export API are in the Pro tier, billed annually per home instance. A 30-day Pro trial is available without a credit card. The trial activates on your local instance — no data ever leaves your network to validate the trial. Request access from the form below.

  • Does local-first mode work without Home Assistant?

    Yes — Home Assistant is optional, not required. The agent has its own local web UI for monitoring, scheduling, and zone management that runs on your home server. Home Assistant integration is additive: if you already run HA, the agent registers entities there automatically and your existing automations can address them. If you don't run HA, the agent's native UI and API provide the same capabilities. Voice control without HA is available via Siri Shortcuts and direct Alexa custom device integration, though HA integration gives the most seamless voice experience.

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

Try it on your house.

Early access is free for the first 500 homes.