API error 401 since yesterday
See original GitHub issueSeems like authentication is failing again, I guess Dyson changed something again?
[3/3/2021, 8:55:16 AM] [DysonPureCoolPlatform] Checked user account.
[3/3/2021, 8:55:16 AM] [DysonPureCoolPlatform] Signing in.
[3/3/2021, 8:55:17 AM] [DysonPureCoolPlatform] Error while signing in. Status Code: 401
[3/3/2021, 8:55:17 AM] [DysonPureCoolPlatform] API could not be reached. Retry is disabled.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:6
- Comments:79 (6 by maintainers)
Top Results From Across the Web
401 Unauthorized - HTTP - MDN Web Docs
The HyperText Transfer Protocol (HTTP) 401 Unauthorized response status code indicates that the client request has not been completed ...
Read more >Getting a 401-Unauthorized Error on REST APi
I have a SSO with company managed account using a new email and always got 401 with my API token. After reading your...
Read more >REST API Integration with 3rd party - 401 Error - ServiceNow
A ' 401 Unauthorized Error' indicates that the requested resource is restricted and requires authentication, but the client failed to provide any such ......
Read more >How to get rid of 401 error while calling web api - MSDN
A 401 (Not authorized) means the request is not authorized. The community cannot determine why you are getting a 401 from the shared...
Read more >Error Code 401 while using Server Side Huawei Mobile ...
Error 401 usually means “unauthorized” or “request denied” because a request lacks valid credential. Although this error code is not listed ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
A workaround that just worked for me was to log out of the latest iOS app, log back in, then reboot homebridge.
I finally had some time to find a viable solution for 2FA. With the help of @sweetw0r and @coraxx I added a separate flow for retrieving the credentials for all your devices. The plugin now has a small website where you can retrieve the credentials by logging into the Dyson account. The plugin no longer directly communicated with the Dyson API. New version 2.0.0 is live on npm.
Let me know that you think. I haven’t tried the non-2FA flow, as my account has already been migrated to 2FA, however, the old flow is also implemented in the “website” for retrieving credentials.