Key Takeaways
- Look for Zigbee, Z-Wave, or Matter protocol support, or a documented local API
- "Home Assistant integration" doesn't always mean local — some route through the manufacturer's cloud even when integrated
- Confirmed local picks (checked 2026-07-16): Sinopé Zigbee (~$80), Aqara Thermostat Hub W200 (Matter, $159.99), 2GIG-STZ-1 (Z-Wave Plus, ~$124)
- A locally-controlled thermostat is what lets AI automations (see that guide) adjust climate without a cloud dependency
Local vs Cloud-Relayed Integration
A thermostat's Home Assistant integration can be genuinely local (Zigbee/Z-Wave/Matter, or a local API) or cloud-relayed (the integration works, but every command still round-trips through the manufacturer's servers) — check which type before assuming full local control.
- Genuinely local: the thermostat communicates directly with your Home Assistant instance over your local network, continuing to work during an internet outage. Sinopé's Zigbee thermostats (~$80, via ZHA or Zigbee2MQTT), Aqara's Thermostat Hub W200 ($159.99, Matter), and the 2GIG-STZ-1 (~$124, Z-Wave Plus) all confirm this.
- Cloud-relayed: Home Assistant talks to the manufacturer's cloud API, which then talks to the thermostat — this stops working if your internet or the manufacturer's service is down, even though it looks integrated day-to-day. Ecobee is the clearest current example: Home Assistant's own integration page lists its IoT class as "Cloud Polling," confirmed as of this writing.
- Check Home Assistant's own integration documentation for the specific model's IoT class (local push, local polling, or cloud polling) — this is stated explicitly on each integration's page and is more reliable than a manufacturer's marketing claims.
What to Verify Before Buying
Check Home Assistant's own integration documentation for the specific thermostat model to see whether it's listed as local push/local polling versus cloud-dependent, before relying on general marketing claims.
- Home Assistant's integration listings typically specify the connection type (local push, local polling, or cloud) for each supported device — this is the most reliable source, more so than the thermostat manufacturer's own marketing.
- Check for discontinuations before buying based on an older recommendation: the once-common GoControl GC-TBZ48 Z-Wave thermostat is discontinued, replaced by the 2GIG-STZ-1 — the same model name doesn't always stay purchasable, so confirm current availability at a retailer, not just a product's existence.
- If a local LLM automation adjusting climate settings matters to you specifically, prioritize confirmed local push/polling support over other features when comparing models.
Frequently Asked Questions
Does "works with Home Assistant" mean a thermostat is local?
Not always — some integrations relay through the manufacturer's cloud even when Home Assistant support exists. Check whether the specific integration is documented as local push/polling or cloud-dependent.
Are Zigbee or Z-Wave thermostats always local?
Generally yes, since those protocols communicate directly with a local coordinator rather than a manufacturer cloud service — this is one of the more reliable signals of genuine local control.
Can a local LLM adjust my thermostat directly?
Yes, if the thermostat is exposed as a standard Home Assistant entity via local integration — see the AI automations and home-assistant-ollama-integration guides for how this connects.
What happens to a cloud-relayed thermostat during an internet outage?
It typically stops responding to Home Assistant commands until connectivity is restored, since the command has to round-trip through the manufacturer's servers.
Does this affect energy-dashboard integration too?
If the thermostat reports usage/state locally, yes, it can feed into the Energy dashboard the same way — see that setup guide for details.