Why doesnt Home Assistant register a deveoper account with Ecobee for a consistent API Key?

1

Not sure if this has been addressed before and being curious, why somebody at Home assistant hasnt created an “official Home Assistant application” api key?

Currently each user has to create their own ecobee ecosystem unique application name (mine was HOMEASSISTANT-MYADDRESS) and somebody out there seems to have HOMEASSISTANT registered. (Is that the reason???)

TBH, I would recommend somebody create Homeassistant-Official or something, get the api key registered, and integrate that api key into the integration (ideally in a secure way) and include the part with Home assistant generating an ID as part of the registration process.

My brother-in-law JC connell created an integration and I’m a C# developer so maybe I could work this? (Although first I might need an “official” home assistant dude to do it and get an official api key)

2

Isn’t there a limit on the number of API calls?

3

Hmm, I dont know if there is an API limit… I guess that could be the limiting factor.

If that’s the case, maybe we should open up a dialog with ecobee engineers to discuss a better way to handle that… IE, an api limit on calls per IP address

4

An API key inside an open-source project means no API key, really.
The whole world could use the HA one.

1 Like