Climate devices are some of the most useful things to automate. A thermostat can react when nobody is home, and a purifier can follow your schedule. Which integration you use depends on the brand, and on whether you want local control or a cloud connection.
Does ecobee connect to Home Assistant?
Yes, through two routes. For new setups, the most dependable option is the HomeKit Device integration, which talks to the thermostat on your local network. The official ecobee integration needs a developer API key. ecobee stopped issuing new developer API keys in 2024, so that route may not work for a new setup. Check the current status before you start.
Climate basics in Home Assistant
Climate entities have a few concepts that new users often mix up:
- HVAC modes include
off,heat,cool,heat_cool,auto,dryandfan_only. Which ones appear depends on the device. heat_coolandautoare different.heat_cooluses two setpoints (target_temp_lowandtarget_temp_high) that you set.autolets the device or its own schedule decide.- Common actions include
climate.set_temperature,climate.set_hvac_mode,climate.set_preset_modeandclimate.set_fan_mode.
Ecobee: HomeKit Device (local)
- On the ecobee, open the menu and enable HomeKit pairing. If the thermostat is still paired with Apple Home, remove it from Apple Home first. An ecobee that remains paired there won’t join through HomeKit Device.
- In Home Assistant, go to Settings > Devices & services > Add integration and choose HomeKit Device.
- Enter the pairing code shown on the thermostat’s screen.
- Assign the thermostat and any exposed sensors to rooms.
Community members generally report that this works well for new setups. Custom comfort settings aren’t exposed directly, so you may need to rebuild them as Home Assistant automations.
Ecobee: official integration (existing API keys only)
If you already have an ecobee developer API key, you can add the ecobee integration from the same Add integration menu. Enter your API key, then authorize the PIN in the ecobee portal. Without an existing key, use the HomeKit route above.
Google Nest: Smart Device Management setup
The Google Nest integration uses Google’s Smart Device Management (SDM) API. It covers Nest thermostats, cameras and doorbells, but not Nest Protect smoke and CO alarms. Setup has several steps:
- Register for Device Access in Google’s Device Access Console. The registration has a one-time US$5 fee, not a subscription.
- In Google Cloud, create a project and enable the Smart Device Management API and the Cloud Pub/Sub API.
- Configure the OAuth consent screen and create OAuth credentials. Use Home Assistant’s redirect URI,
https://my.home-assistant.io/redirect/oauth. - Set up the Pub/Sub topic that Home Assistant uses to receive device events.
- Add the Google Nest integration in Home Assistant, enter your project details and credentials, and then switch on your devices in the Google Partner Connections prompt.
If the device list is empty, check that your devices are switched on in Google Partner Connections and that your Google account belongs to the Nest home. If you see an already_in_progress error, community opinion is split on whether recreating the Cloud and Device Access projects helps.
Some Nest thermostat models also support Matter, with fewer features. Check your model before you choose that route.
Community integrations for older Nest APIs can cover devices the official integration doesn’t, such as some Nest Protect models. Their status depends on Google’s API changes, so check before you rely on one.
Carrier: no official integration
Carrier Infinity and Bryant Evolution systems don’t have a core Home Assistant integration. Community options include:
- Infinitude, a local proxy that the thermostat communicates with. It’s a more involved setup, and it depends on how your system connects.
- HACS Carrier Infinity, a cloud-based integration.
Carrier mini-splits built by Midea may work with community Midea integrations from HACS, depending on the model. Check each project’s list of supported models before you buy or set up anything.
Dreo fans, heaters and air purifiers
Dreo doesn’t have a core integration, but several HACS options exist:
- hass-dreoverse is published by Dreo’s engineering team. It uses cloud polling and covers fans, air conditioners, heaters, humidifiers and purifiers.
- hass-dreo is a community project. It uses a cloud connection with real-time WebSocket updates, and it exposes more sensors and controls.
- Matter is available on some newer Dreo models, which lets you connect them without a cloud integration. Check your model.
- ESPHome firmware has been used on a few fan models. It’s an advanced, unofficial route.
Check each project’s device list to see which one covers your model.
Generic Thermostat helper
If your heating or cooling isn’t a supported smart thermostat, Home Assistant’s Generic Thermostat helper can control a switch using a temperature sensor. You set the cold and hot tolerances. The default for both is 0.3 degrees.
Safety
- Smart thermostats are usually low-voltage devices. Never wire one to a 120 V or 240 V baseboard heater.
- Turn off HVAC power at the breaker before you rewire a thermostat.
For how devices, integrations and entities fit together, see adding and managing devices in Home Assistant.