Not sure if this is known so I wanted to throw this out there before I open an issue. Is anyone else seeing this? I am getting a traceback on boot and it’s happening pretty frequently now. Looks like the Alexa integration is failing on boot and causing the entire nabu cloud integration to crash.
2021-12-07 11:04:17 WARNING (MainThread) [hass_nabucasa.cloud_api] Fetched https://alexa-api.nabucasa.com/access_token (500)
2021-12-07 11:04:17 ERROR (MainThread) [homeassistant.setup] Error during setup of component cloud
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/setup.py", line 254, in _async_setup_component
result = await task
File "/usr/src/homeassistant/homeassistant/components/cloud/__init__.py", line 233, in async_setup
await cloud.initialize()
File "/usr/local/lib/python3.9/site-packages/hass_nabucasa/__init__.py", line 275, in initialize
await self._start()
File "/usr/local/lib/python3.9/site-packages/hass_nabucasa/__init__.py", line 279, in _start
await self.client.cloud_started()
File "/usr/src/homeassistant/homeassistant/components/cloud/client.py", line 151, in cloud_started
await asyncio.gather(*(task(None) for task in tasks))
File "/usr/src/homeassistant/homeassistant/components/cloud/client.py", line 119, in enable_alexa
await aconf.async_enable_proactive_mode()
File "/usr/src/homeassistant/homeassistant/components/alexa/config.py", line 60, in async_enable_proactive_mode
await self._unsub_proactive_report
File "/usr/src/homeassistant/homeassistant/components/alexa/state_report.py", line 31, in async_enable_proactive_mode
await smart_home_config.async_get_access_token()
File "/usr/src/homeassistant/homeassistant/components/cloud/alexa_config.py", line 179, in async_get_access_token
self._token = body["access_token"]
KeyError: 'access_token'
I had similar issues. Not knowing what was happening, I performed a Server restart and it took an inordinate amount of time to get to an operational state. Indications were that HA was making multiple attempts (25, I think) to load some configuration from the Cloud. When an operational state was finally achieved, the Cloud integration had disappeared entirely, leaving me guessing if my own network or misconfiguration was to blame.
I know AWS service interruptions are pretty rare, but the lack of cloud services shouldn’t result in ungraceful behavior, IMHO.