Hi,
I have legacy Smart thermostat, and apparently, Ecobee will eventually migrate all users with a Smart legacy (original Ecobee model from 2006-2009) thermostat to their Smartbuilding portal, which is targetted for the EMS thermostat.
I currently use 5 ecobee Smart in my house. I wanted to check ahead if this would still allow Home Assistant integration to work, so I suscribed one spare Smart thermostat I had on the smartbuilding portal, and asked for developper access. But it seems that the API behave differently on Smartbuilding than on the residential portal.
On Smartbuilding, you do not get an “API Key” when you get developper access, but you get a json file which contains a “client_id” and a “client_secret” with which you can generate a JWT token.
I tried to use the “client_id” as the API key in the Ecobee integration, but it generates “Unknown error occurred”.
Should I conclude that thermostats on Smartbuilding are not supported under the current Ecobee integration?
Ecobee technical support would not tell me when they will move the legacy thermostat to Smartbuildings, but this could mean that all those thermostats will loose Home Assistant integration.
Does someone know if there is a way to get Smartbuilding to work with the current Ecobee integration?