Honeywell / Resideo Thermostat v1.0

Bring your Honeywell Home / Resideo Wi-Fi thermostats into RTI — Lyric and the T-series (T5, T6, T9, T10) and Round. Mode, setpoints, fan, humidity and temperature, all on your RTI panel, with a setup that takes about two minutes in your web browser. Built for everything from a single thermostat to a whole mansion (up to 12).

What this driver is (and what it is not)

This driver talks to the official Resideo / Honeywell Home cloud API — the same modern API the Honeywell Home app and Home Assistant's lyric integration use. It is not the old Total Connect Comfort interface, and it is not a local connection.

It's a cloud driver. It reaches your thermostats over the internet through the Resideo cloud, so it needs a working internet connection and Resideo's cloud to be up. The upside: nothing to configure on your network, no port forwarding, and it works the same whether the thermostat is in the next room or another building.

Set it up

Everything happens in Integration Designer and your web browser. There's no app to install, no developer account to register, and no API keys to copy.

Quick version: Add the driver → click Connect to Honeywell → sign in → paste the pairing code → click Get Config from Honeywell to list your thermostats. Each thermostat is its own source — add it to a room and bind one reusable Climate page to each.

1. Add the driver

Add the Honeywell / Resideo Thermostat driver to your project.

2. Connect your Honeywell account (one click)

In the Driver Configuration panel (left side), you'll see two actions for this driver:

1. Click Connect to Honeywell. Your web browser opens automatically.

2. Sign in with your normal Honeywell Home account and approve access.

3. The page shows a short pairing code. Copy it and paste it into the driver's Pairing Code field (valid 60 minutes).

That's it for linking. The driver claims your secure Honeywell link once and keeps itself authorized automatically across reboots — you won't need to do this again unless you intentionally disconnect.

3. Import your thermostats

Click Get Config from Honeywell (the other action). The driver lists every thermostat on your account by its real name — "Master Bedroom", "Downstairs", "Living Room". The driver also fills these names in automatically once it connects, so they appear by themselves even if you skip this step.

4. Add each thermostat as a source and build one Climate page

Each thermostat is its own source (just like a separate AV zone), so you build one thermostat page and reuse it:

1. In Add Workspace Item, add a Thermostat source for each thermostat, into the room it belongs to.

2. Build a Climate control page once — drop on the tagged buttons (Heat / Cool / Auto / Off, fan, setpoint up/down) and the tagged variables (current temp, setpoints, mode). The tags do the wiring.

3. On each thermostat's page (or layer), set the Source to that thermostat. The same template now drives the right thermostat — set one layer's Source to "Master Bedroom," another to "Downstairs," and each binds to its own device.

The names you see update to the live names from your account once the driver connects, and you can also type names into the Thermostat Name fields yourself.

How updates work

Controlling a thermostat from RTI is instant. Press Heat, nudge a setpoint, or change the fan — the command goes out right away and the on-screen value updates immediately.

Changes made elsewhere appear on the next refresh. Resideo does not push thermostat changes, so the driver refreshes state on a schedule (about every 5 minutes — Resideo's rate limit). A change made at the wall, in the Honeywell Home app, or by the thermostat's own schedule shows up on your RTI panel within that cycle. After one of your own commands the driver also does a quick confirming re-check so the panel and the device agree.

The refresh is the source of truth. An on-screen value can never get stuck: whatever the next refresh reports always wins, so the panel self-corrects.

Honest expectation: external changes are not real-time — they reflect within the refresh interval, not within a second. Commands you send from RTI are instant; the ~5-minute cadence only affects how quickly outside changes catch up. (Real-time local updates would require a local connection, which this cloud driver doesn't use.)

What you can control

Each function picks the thermostat (the source), so the tagged buttons on a templated Climate page just work. Per thermostat:

Operating Mode — Off / Heat / Cool / Auto (or Toggle). The mode choices carry the official RTI tags (Stat Heat / Cool / Auto / Off), so a tagged one-press button drops straight onto a Climate page and drives the page's thermostat.

Adjust Setpoint — step the active setpoint up/down, or the heat or cool setpoint explicitly (tagged Setpoint / Heat / Cool Up & Down).

Set Heat Setpoint and Set Cool Setpoint — set a value directly. Values are clamped to the range the thermostat reports.

Fan Mode — Auto / On / Circulate (or Toggle), tagged for one-press buttons.

Hold — a one-time override for the current setpoints: Follow Schedule (clear the hold), Permanent Hold, or Hold Until Next Period.

Default Hold — the hold each thermostat applies whenever you change a setpoint. It lives on the panel (not in the driver's config) so you can flip it seasonally — Permanent for deep winter, Temporary in shoulder season — without re-deploying the driver. Pick Permanent or Temporary, or Toggle to flip it. Each thermostat keeps its own setting, and it survives processor reboots. The Default Hold variable shows the current choice, with Permanent / Temporary state variables for button highlighting.

Auto Changeover — on dual-setpoint thermostats, lets the thermostat switch between heating and cooling automatically.

(Setting a temperature applies a hold so your change isn't immediately overwritten by the schedule. Whether that hold is permanent or temporary is each thermostat's Default Hold setting above; the Hold function overrides it once, just for the current setpoints.)

Reads, per thermostat: current temperature, indoor humidity, outdoor temperature, outdoor humidity, current operating mode and operating state (heating / cooling / idle), heat / cool / current setpoint, fan mode, fan state (running / idle), hold status, default hold, emergency heat, auto-changeover, the allowed modes and setpoint min/max bounds, the thermostat model, and an Online flag — each with boolean state variables so tagged buttons highlight when active. Driver-wide: connection state, status text, last error, last poll time, and how many thermostats were discovered.

Automation events (trigger macros from your thermostats)

RTI variables show state, but only events can trigger a macro — so every thermostat raises its own events as things change, letting you drive automation from the heating system. For each thermostat you get: Mode Off / Heat / Cool / Auto, Heating Started / Cooling Started / Idle, Came Online / Went Offline, and Emergency Heat On. Bind any of them to a macro — for example, "when the Living Room thermostat starts cooling, close the shades," or "if any thermostat goes offline, send an alert." These fire from the cloud refresh (real device state), so they reflect what the thermostat actually did, whether the change came from RTI, the wall, the app, or the schedule.

Options

Poll Interval (seconds) — how often thermostat state is refreshed (120–1800s; default 300). Resideo's rate cap is about one poll every 5 minutes, so 300 is the safe default. The driver automatically backs off if Resideo ever rate-limits a busy account.

Startup Delay (seconds) — wait this long after the processor boots before the first cloud connection (default 0). Raise it on a busy processor so your other drivers finish booting first.

Display in Celsius — a display hint only (the API also reports each thermostat's own unit). Leave off for Fahrenheit.

Debug Level — logging verbosity in the processor System Log. Leave on Low unless you're troubleshooting.

(The per-thermostat Default Hold preference is no longer here — it's a panel function so you can change it seasonally without re-deploying. See What you can control above.)

A note on multiple thermostats

The driver pulls every thermostat at every location on your account, and one cloud call returns all of a location's thermostats at once — so adding more thermostats barely changes the refresh load. It imports up to 12 thermostats (mansion-scale). If you have more than 12, the driver tells you (the Discovered Count vs Thermostat Count variables, and a Thermostats Truncated event) so nothing is a silent surprise. One license covers the processor.

Is this safe? (your account stays private)

We built the connection to bank-level standards and designed it so your Honeywell login never touches our servers:

You sign in directly with Honeywell. When you click Connect, you log in on Resideo's own page — we never see your password.

The sensitive app secret stays on our server, never inside the driver. The driver file you download holds no account credentials, so it can't be pulled apart to reach anyone's account.

Your processor holds its own Honeywell key. After you link, the long-term credential lives on your processor. Our relay only adds the secret app key during the brief token refreshes and does not keep your tokens — during the one-time linking step your credential is encrypted (AES-256-GCM) and discarded as soon as your processor picks it up.

Everything travels encrypted. All traffic between your processor, our relay, and Resideo runs over secure HTTPS.

We don't keep your data. Thermostat readings pass through only long enough to reach your processor — we don't log them, mine them, or sell them.

License

The driver runs for 2 hours per processor as a free trial. To license it permanently, purchase a key at customcontroldrivers.com and paste it into License Key. The license is locked to that processor.

Support

Questions or issues: support@customcontroldrivers.com