After updating to 0.64.0, my ecobee thermostat stopped showing up and I was getting “Error connecting to ecobee. Possible connectivity outage.” errors in the log.
I deleted everything, created a new app in the ecobee developer site, and attempted to set things up again with a new API key. Once I did this, the logged error changed to “Error connecting to Ecobee. Possible connectivity outage. Could not request pin.”
I thought maybe for some reason my pi couldn’t contact the ecobee servers, but that doesn’t seem to be the case. I SSH’d into my RPi3 (running hass.io) and used cURL to manually send the http GET request to the ecobee server to get a PIN, then a POST to request tokens. I used this info to update the ecobee.conf file in the correct format (I looked at an old backup to confirm how the API key, authorization code, and tokens are stored).
I’m still getting the “Error connecting to ecobee. Possible connectivity outage.” error in the log on startup and there’s no climate component showing up on my states page. I’m pretty much out of ideas at this point.
My thermostat has been functioning normally and I’ve been able to access it remotely through the ecobee app the entire time.
Ron, I am getting a configuration error with my ecobee. I’ve tried multiple HA configurations and it keeps giving me a python error in the log file. Any ideas?
Yes I did. It just won’t bring up the pin box. When I check the log it references these errors:
Traceback (most recent call last):
File “/srv/homeassistant/lib/python3.5/site-packages/homeassistant/setup.py”, line 145, in _async_setup_component
component.setup, hass, processed_config)
File “/usr/lib/python3.5/asyncio/futures.py”, line 380, in iter
yield self # This tells Task to wait for completion.
File “/usr/lib/python3.5/asyncio/tasks.py”, line 304, in _wakeup
future.result()
File “/usr/lib/python3.5/asyncio/futures.py”, line 293, in result
raise self._exception
File “/usr/lib/python3.5/concurrent/futures/thread.py”, line 55, in run
result = self.fn(*self.args, **self.kwargs)
File “/srv/homeassistant/lib/python3.5/site-packages/homeassistant/components/ecobee.py”, line 120, in setup
NETWORK = EcobeeData(hass.config.path(ECOBEE_CONFIG_FILE))
File “/srv/homeassistant/lib/python3.5/site-packages/homeassistant/components/ecobee.py”, line 94, in init
self.ecobee = Ecobee(config_file)
File “/srv/homeassistant/lib/python3.5/site-packages/pyecobee/init.py”, line 72, in init
self.request_pin()
File “/srv/homeassistant/lib/python3.5/site-packages/pyecobee/init.py”, line 88, in request_pin
self.authorization_code = request.json()[‘code’]
KeyError: ‘code’
The PIN can be found from the Home Assistant portal on the Ecobee card or from the configurator.ecobee entity in states in the portal.
If you do not have an ecobee card, you may be using groups with default_view that don’t show the card. To get around this you can temporarily comment out the default_view section or add the configurator.ecobee component to your default_view and restart Home Assistant.
I vaguely recall having an issue when I first set ecobee up in HA. I don’t remember specifics because it seems every new item is a major pain in the butt to setup.
If you aren’t running into the default_view issue, you might try removing your 1st ecobee application on the ecobee developer site and stating over with a new application.
I’m having issues integrating my ecobee switch+ to HA. I’ve followed https://www.home-assistant.io/components/ecobee/ to the dot and nothing. Ive recreated DEV API several times without success… No errors on log file related to ecobee… any ideas???
Same deal here. I can find the card (which is empty, and does nothing), or I can fire request_tokens at configurator.ecobee, but it doesn’t go and get tokens, and just asks for app re-auth on next start. How do you actually get this to move past that step?
Got past that step - suddenly it started putting a notification in the bell menu, and from there I could hit the ‘authenticated’ button. Works now. Huh.