When I reboot the Raspi-based hassio system, it seems to lose the SmartThings configuration:
Error setting up entry Exeter Place for smartthings
Traceback (most recent call last):
File “/usr/local/lib/python3.7/site-packages/homeassistant/config_entries.py”, line 283, in async_setup
result = await component.async_setup_entry(hass, self)
File “/usr/local/lib/python3.7/site-packages/homeassistant/components/smartthings/init.py”, line 113, in async_setup_entry
entry.data[CONF_REFRESH_TOKEN])
File “/usr/local/lib/python3.7/site-packages/pysmartthings/smartthings.py”, line 202, in generate_tokens
client_id, client_secret, refresh_token)
File “/usr/local/lib/python3.7/site-packages/pysmartthings/api.py”, line 417, in generate_tokens
raise APIInvalidGrant(data.get(‘error_description’))
pysmartthings.errors.APIInvalidGrant: Invalid refresh token: a0acfff2-0e65-442f-a60f-edd6449af051
I then have to go through a convoluted process to get the ST entities back on-line. Any ideas what’s going wrong on the restart/reboot?
Did you by chance upgrade to 0.89 without reading the release notes?
If so, you just need to setup SmartThings again from the Integration menu,. You just need your token, authorize in the app, and your things will get rediscovered.
They removed the configuration.yaml entries.
I have just begun running into this very same issue after the ST component working fine since release. I have reset the component many times now, but every reboot it runs into same issue. My log reads the exact same.
I thought I had found the answer when I found a duplicate location listed in my ST IDE. It had the same name as Home, but had no hubs or devices. After removing that location, everything seemed like it was OK, but just before I replied here I decided to test it, and it failed a reboot once again.
I don’t see any others reporting this, could it really be just the two of us?
I too am now having this problem…worked fine until 0.92.0. I believe it worked at first with 0.92.0, but after several reboots trying to fix another problem I now get the Invalid refresh token error.
