8 hours ago, EricBarish said:

I went with home assistant last week. Connected my ecobee (by homekit) and roombas, garage control and other items in a few mintues. Really like the dash board on Home assistant. Figuring out the programing, AI helped a lot.

Using home assistant as an interface to devices missing in Eisy and Eisy for most programs and my smarthome, zwave and zigbee control.

Home assistant has an Eisy/ISY integration so I can pass data between the two systems using eisy variables.

With dashboard can quicky see what is going on with the systems.

Should have done this a while ago with the loss of the ecobee cloud connection and (Homekit ? on eisy) pushed me to make the jump.

Doesn't Ecobee work with Home Assistant without Homekit? Speaking of AI, I used it to write my own plugin. It isn't very polished and does not do as much as Jimbo's but it has gotten me by since it went down. I had my own developer key luckily. One thing I could never figure out (AI could not I mean :) ) was how to get the comfort setting names into the ISY. It just calls them SMART1, 2, etc... It also does not show the comfort setting in the program, you have to click the program line to see it. I do plan to go back to Jimbo's eventually. Just a lot of work to update all my programs.

11 minutes ago, btreinders said:

Doesn't Ecobee work with Home Assistant without Homekit?

Yes. There are several integrations for ecobee. Two are official:

1- An intergraiton when you already have your own dev key. It provides access to everything the Ecobee API offers, is cloud based and no Homekit needed. similar experience to Jimbo's Plugin.

2- A homekit device integration. You log your ecobee in on the same L2 lan as your HA server (L2 Bonjour based), the integraton sees it and the thermostat offers a pin to authenticate with. It offers some important features yet is also feature hampered by Homekit Accessory Protocol's (HAP) more limited definition of a thermostat. It however is completely local, cloud free and no apple products are required.

Yes, the Homekit method does have missing features which is a bummer, but being all local is nice since there is no polling delay. I was really hoping Ecobee would allow us to use the local method, and the cloud method for features missing with local but no luck. UDI is working with Ecobee on getting API access back but no promises yet, and sounds like the API is different so will require some development.

Trying to setup ecobee plugin from the beta store. I upgraded packages to get the latest software like was suggested. The configuration instructions are overwhelming:

1. Install and configure udi-poly-homekit first (PG3 store): pair your Ecobee(s), then enable the hub MQTT transport (mqtt_enable and broker settings in that plugin; see its PROTOCOL.md). MQTT is the preferred transport for new installs and is the default of hk_transport here — point both plugins at the same broker and matching *_hub_slug. WebSocket (ws_host / ws_port and optional ws_token) remains supported as a fallback when MQTT is not available. This nodeserver’s HomeKit mode talks to that hub only; it does not replace it.

2. Missing backend param: the plugin seeds a default once: homekit for a fresh NS (no OAuth, no api_key, no saved Ecobee tokens/PIN in customdata, no extra nodes yet); cloud if Polyglot OAuth is enabled for this NS, api_key is set, customdata has tokenData / pin_code, or the NS already has nodes besides the controller (legacy upgrade). If backend is already stored in PG3, it is never changed by seeding.

3. Ecobee cloud (REST API): Ecobee has cut off UDI / Polyglot Cloud access for this integration. Cloud mode only remains viable if you use your own Ecobee developer application key that you registered before Ecobee stopped honoring requests for the old shared keys, and you configure api_key / PIN flow as documented for local Polyglot. Do not rely on historical OAuth or UDI-provided keys for new setups.

can you give a simplified verbose example of what we should enter, especially in the homekit plugin? I do not have a personal API key for ecobee.

Thanks

Have to agree looked at these instructions and scatched my head. Decided to see what home assistant could do. Took a few seconds to connect my ecobees with homekit\home assistant and sent the data to easy needed for my control programs.

All defaults should work, just remember this is beta, I put in a lot of options for testing which should not be necessary once it is proven.