mc2147
commented
2 months ago We've identified an issue in our syncing logic that results in expired tokens being used when a previously-connected SmartThings account is connected again. We have a way to fix this manually for now and will work on fixing our syncing logic in the future
For some SmartThings accounts we're seeing an issue where even though the account logs in successfully, fetching devices fails due to an unauthorized response (implying an error with the account's access token). Refreshing the account's access token also fails and returns a 400 Bad Response error from the SmartThings refresh token endpoint
This has occurred with 2 accounts so far and we've contacted SmartThings about this both times. They have replied asking for more request information which we have provided, and we are currently waiting on a follow-up response from their team