ecobee
localProven against a real device on 2026-09-04by ALYT
The ecobee thermostat and its room sensors, paired on your own network. No ecobee account is involved.
What it adds to a house
Section titled “What it adds to a house”adds thermostats and sensors.
How a person connects it
Section titled “How a person connects it”Method: pair. Enable HomeKit on the thermostat first (Main menu, Settings, HomeKit) and stay at its screen: when ALYT starts the pairing the thermostat shows a fresh code, which is asked for next. The thermostat must not already be paired to Apple Home.
| Field | Kind | Required |
|---|---|---|
Address on your network (address) | text | yes |
What it can look for
Section titled “What it can look for”Yes: “Look for the thermostat”.
What stops working when it is disconnected
Section titled “What stops working when it is disconnected”The things it brought stop answering until it is connected again.
The descriptor
Section titled “The descriptor”The same object the console and the phone render from, served for a program at /connectors/ecobee.json.
{ "source": "built-in", "visibility": "public", "listed": true, "version": "1.0.0", "docsUrl": "https://developers.alyt.com/connectors/ecobee", "kind": "ECOBEE", "name": "ecobee", "icon": "thermometer-sun", "promise": "The ecobee thermostat and its room sensors, paired on your own network. No ecobee account is involved.", "connectivity": "local", "brings": [ "thermostat", "sensor" ], "connect": { "method": "pair", "help": "Enable HomeKit on the thermostat first (Main menu, Settings, HomeKit) and stay at its screen: when ALYT starts the pairing the thermostat shows a fresh code, which is asked for next. The thermostat must not already be paired to Apple Home.", "fields": [ { "key": "address", "label": "Address on your network", "kind": "text", "secret": false, "required": true, "placeholder": "192.168.1.224", "help": "The thermostat shows it under Settings, Wi-Fi. Needed because this network does not pass HomeKit's announcements to ALYT." } ] }, "discovery": { "verb": "Look for the thermostat" }, "disconnect": { "consequence": "{count} {things} stop answering until it is connected again." }, "author": { "kind": "alyt", "name": "ALYT", "url": "https://alyt.com" }, "verification": { "level": "proven", "at": "2026-09-04T00:04:00.000Z" }}The guide
Section titled “The guide”The ecobee connector pairs with an ecobee thermostat on your local network, not with an ecobee account. It brings the thermostat and its room sensors into ALYT over HomeKit on the LAN, so the house keeps working when the cloud is down. A household sees the thermostat itself and less than staff does: only the device data and controls exposed through the connector.
What you connect
Section titled “What you connect”This connector uses pair in two steps. First, you enter the thermostat’s network address. ALYT needs that because this network does not pass HomeKit announcements to it. Then ALYT starts pairing and the thermostat shows a fresh code on its screen. You type that code in the second step.
Before you start, enable HomeKit on the thermostat and leave it on the HomeKit screen. If the thermostat is already paired to Apple Home, remove it there first. An accessory already paired elsewhere refuses a new pairing.
What it exposes
Section titled “What it exposes”The connector brings two kinds of things:
| Kind | What ALYT shows |
|---|---|
thermostat | setpoint, mode, fan, hold |
sensor | temperature, occupancy |
The thermostat appears as the main device endpoint. Its room sensors appear as separate sensor endpoints.
What you can do
Section titled “What you can do”You can read the thermostat’s state and write the controls ALYT exposes for it. The thermostat state includes its setpoint, mode, and fan state, and the room sensors report temperature and occupancy. The connector also reports battery where the accessory provides it.
Write operations are limited to the controls HomeKit exposes here. If the thermostat is in auto mode, ALYT keeps the two thresholds around the target setpoint. Reads come back in Celsius.
What it cannot do
Section titled “What it cannot do”This connector does not use ecobee’s cloud API and does not need api.ecobee.com. It does not rely on an ecobee account or ecobee developer keys.
hold is not available through HomeKit here, so ALYT refuses it. The thermostat’s own schedule ends changes on its own terms.
Discovery
Section titled “Discovery”Discovery is “Look for the thermostat”. ALYT looks for the accessory again at the address where it was paired. If the thermostat moves on your network, discovery reads it again at the new location.
When pairing fails
Section titled “When pairing fails”Check these first:
- HomeKit is enabled on the thermostat.
- The thermostat is still on the HomeKit screen while you pair.
- The
addressis correct. - The thermostat is not already paired to Apple Home.
- You typed the fresh code shown after ALYT started pairing, not an older one.
If the code is wrong, the pairing is rejected and the thermostat shows a new code for the next try. If pairing has already been claimed by another controller, the thermostat rejects it as already paired.
Disconnect
Section titled “Disconnect”If you disconnect it, {count} {things} stop answering until it is connected again. In a household, that means the thermostat and its room sensors stop reporting through ALYT until you pair again.
DEV and LIVE keys
Section titled “DEV and LIVE keys”A DEV key acts in a sandbox. A LIVE key only works for its own connector. The house still keeps working when the cloud is down, but this connector itself is local and pairs to the thermostat on the home network.