Local control of the Honeywell (Resideo) Lyric T6 / T6R thermostat in SmartThings. The hub talks to the thermostat directly over HomeKit on your own network: no Resideo cloud, no Honeywell account, no Apple device, no bridge computer.
Why: the Honeywell Home / Resideo cloud integration runs on the older Lyric platform and regularly loses its login while the Resideo app keeps working. Over HomeKit the hub does not depend on that.
The complete HomeKit controller (SRP pair setup, Ed25519, X25519, ChaCha20 Poly1305, encrypted sessions and events) is written in pure Lua and runs on the hub. It is the same controller as in my VELUX ACTIVE (HomeKit local) driver.
What you get
- Temperature (the thermostat’s own sensor)
- Heating setpoint: read and set (0.5 °C steps)
- Mode: off, heat, auto
- Operating state: heating or idle, so routines can see whether the thermostat itself calls for heat
- Live updates (the thermostat pushes every change) plus a safety poll every 5 minutes
- Connection status (Connected / Offline) and Last drop, for offline notifications in routines
- Automatic reconnect
Install
- Enroll your hub in the channel: SmartThings. Add a little smartness to your things. (Stoeckie Edge Drivers) and install Honeywell T6 (HomeKit local).
- On the thermostat: advanced menu, RESET, HomeKit (only resets HomeKit, not your installer settings). HomeKit then stays active for a limited time.
- SmartThings app: Add device, Scan nearby. A “Honeywell T6” device appears.
- The hub starts pairing by itself and the thermostat shows an 8 digit code on its display. Type that code in the device settings (HomeKit code) within 5 minutes. Pairing then takes 1 to 2 minutes on the hub.
Important: the T6 makes a new code for every pairing attempt. The code on the sticker does not work, and a code from an earlier attempt does not work either. With a wrong code the hub starts a new attempt after 10 seconds and the display shows a new code.
The thermostat must not be paired with Apple Home or another HomeKit controller (HomeKit accepts one owner). The Resideo app keeps working next to this driver.
Offline notification
SmartThings has no routine trigger for “device offline”. Make a routine: if Honeywell T6, Connection is Offline, send a notification. Connection only turns Offline after 2 minutes without a connection.
Code, tests and troubleshooting: GitHub - Stoeckie/smartthings-honeywell-t6-homekit-local: SmartThings Edge driver: Honeywell (Resideo) Lyric T6 thermostat over HomeKit, locally from the hub · GitHub
Not affiliated with Honeywell or Resideo. Feedback welcome, especially from T6R and T5 owners.
Update (build 2026-11-05d): heat demand per room
For setups where the T6 is the only thermostat that talks to the boiler and the rooms have their own radiator or floor heating thermostats in SmartThings.
The device now has a capability Heat Demand with the command setRoom(room, "on"/"off"). A rule sends per room on when its temperature is below its setpoint and off otherwise. With N rooms asking for heat the driver sets the T6 to its own temperature (rounded up to 0.5 °C) plus 0.5 °C per room, and keeps following the T6 temperature. When no room asks any more, the setpoint goes back to 19 °C. Both values are device settings. The device shows which rooms ask for heat.
The more rooms need heat, the bigger the gap between temperature and setpoint, so the boiler gets asked for more. A rule example is in the README: GitHub - Stoeckie/smartthings-honeywell-t6-homekit-local: SmartThings Edge driver: Honeywell (Resideo) Lyric T6 thermostat over HomeKit, locally from the hub · GitHub
Update (build 2026-11-05e)
- Heat demand is now off until a rule sends its first
setRoom. If you only use the driver as a thermostat, nothing changes for you: the driver never touches your setpoint on its own.
- When the last room stops asking for heat, the setpoint goes back to the idle value once; a manual setpoint after that is left alone.
- New:
tools/heat-demand-rule.ps1 (Windows, needs the SmartThings CLI). It lists every device with a temperature and a heating setpoint, you type the numbers of the rooms that count, and it creates or updates the rule. Run it again to change the rooms.
Details: GitHub - Stoeckie/smartthings-honeywell-t6-homekit-local: SmartThings Edge driver: Honeywell (Resideo) Lyric T6 thermostat over HomeKit, locally from the hub · GitHub
Update (build 2026-11-05g)
- Fix: builds 05e and 05f could restart in a loop as soon as a heat demand rule sent
setRoom (a stored value that did not exist yet). If you use heat demand, update to 05g. Errors in the heat demand part can no longer stop the driver.
- A stored room list now also keeps heat demand active right after a driver update.
- Tip: besides the Offline routine (Connection is Offline), duplicate it with Connection is Connected to get a “back online” notification.
All code, the rule script and the README: https://github.com/Stoeckie/smartthings-honeywell-t6-homekit-local
Example heat demand rule
The rule I use myself is now on GitHub, with placeholder IDs and generic room names, plus the logic step by step: https://github.com/Stoeckie/smartthings-honeywell-t6-homekit-local/tree/main/examples
In short, per room thermostat: if its temperature is below its own setpoint, send setRoom(name, "on") to the T6, otherwise "off". The rule runs on every temperature or setpoint change of that room (per the Rules API docs a plain condition is evaluated on every event), the driver ignores repeats, keeps the list and sets the T6 to its own temperature plus 0.5 °C per room asking. Replace the placeholders and create it with smartthings rules:create, or let tools/heat-demand-rule.ps1 build it for you.
Update (build 2026-11-05i), please update
- Fix: the connection could hang without anyone noticing. After a request got no answer the session was closed, but the reader kept waiting forever (on the hub, closing a socket does not wake a coroutine that is blocked reading it). Result: no updates, no heat demand and still “Connected”. The reader now checks every 20 s and reconnects.
- Heat demand: the T6 reports its temperature in 0.5 °C steps and often flips between two of them every 20 s. The setpoint now follows the temperature upwards only and goes down only when fewer rooms ask for heat, so it no longer flips along.
- Note: the T6 closes its HomeKit session roughly every 20 minutes; the driver reconnects within seconds and this does not count as Offline.
- Tip for more than one T6: the HomeKit ID changes with every HomeKit reset, so Scan nearby can add a second device for the same thermostat. Delete the one without values.
Update (build 2026-11-06a)
The short drops (about 18 s, “session closed”) every 15 to 45 minutes came from the driver itself: on two thermostats they fell exactly on the 5 minute poll, at the same second. The T6 often closes its HomeKit session after a poll request. It pushes every change anyway, so the driver now only polls after 15 minutes without any message from the thermostat, and the first reconnect comes after 3 s instead of 10 s. Last night one of those reconnects took 2 minutes and triggered an Offline notification; that should be gone now.
Update (build 2026-11-07a): heat demand fix
If you use the heat demand control (a rule that sends setRoom per room): when the last room stopped asking for heat at the same moment the T6 closed its HomeKit session (it does that every 20 minutes or so), the write back to the idle setpoint failed and the driver still counted that change as done. The T6 then kept its high setpoint and the boiler kept heating with no room asking, until something else changed the setpoint.
Now the driver only counts the change once the setpoint is written, so the next try after the reconnect (a few seconds later) still goes back to the idle setpoint. Install the new build from the channel; nothing else to change.
Update build 2026-11-08a: no more “not all status information updated yet”
The SmartThings app shows that message when an attribute has no value. On a device that never had a connection drop, Last drop was still empty. It now starts with “No drops yet”.
Code: GitHub - Stoeckie/smartthings-honeywell-t6-homekit-local: SmartThings Edge driver: Honeywell (Resideo) Lyric T6 thermostat over HomeKit, locally from the hub · GitHub
Update build 2026-11-08b: no Offline notification for a short network outage
New setting Offline after (minutes), default 5. Connection only turns Offline after that many minutes without contact. Before it was 2 minutes, so a router or network update at night (a few minutes without network) gave an Offline notification even though nothing was wrong. A real outage still gives one.
Also for US users: a setpoint in °F (the app sends °F for a Fahrenheit location) is now converted to °C for the thermostat. Before, 68 °F was sent as 68 °C and ended at the maximum. The idle setpoint setting also accepts °F (a value above 40 is read as °F).
Code: GitHub - Stoeckie/smartthings-honeywell-t6-homekit-local: SmartThings Edge driver: Honeywell (Resideo) Lyric T6 thermostat over HomeKit, locally from the hub · GitHub