Closed sb37 closed 3 months ago
According to JohNan/homeassistant-wellbeing#99 logins made using the "old" API are rejected.
(The plugin has been working for a year now. Great!)
I'm in the process of making an update to work with the new API. I'm just stuck because I was stupid and disabled my API Key, but can't enable it nor I can create a new one. Waiting for support...
Either way, I'm trying a way so we can still use the username/password rather than providing an api-key and refresh token, because I don't think it will be stable over the long run. A refresh token can only be used once, so if you add it to the hardware section, it's invalid as soon as you use it.
Massive update using the new APIs. I've put some effort in keeping the normal username/password which is a lot more convenient then needing to create an api key and refresh token yourself. I think this would be more stable as a refresh token is expired as soon as it's used, so storing it in the hardware field makes no sense
Works like a charm. I had some funny errors in the log. I deleted all the "old" devices started again. No more errors. Everything works.
According to https://github.com/JohNan/homeassistant-wellbeing/issues/99 logins made using the "old" API are rejected.
(The plugin has been working for a year now. Great!)