API error 401 since yesterday #166

AdeTheux · 2021-03-03T07:57:28Z

Seems 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.

The text was updated successfully, but these errors were encountered:

jsalva23 · 2021-03-03T14:21:43Z

I'm having the exact same issue

3/3/2021, 9:18:16 AM [DysonPureCoolPlatform] Error while signing in. Status Code: 401
3/3/2021, 9:18:16 AM [DysonPureCoolPlatform] API could not be reached. Retry is disabled.

I'm using HOOBS 3.3.3, the version of the Dyson firmware is the latest: 1.8.7 all installed on a Raspberry Pi

marhindev · 2021-03-03T15:25:10Z

They really seem to have changed something. The release information for the latest update of the Dyson iOS app say something about new interface for room climate devices (https://apps.apple.com/de/app/dyson-link/id993135524). It also states changes to authentification (2 step auth).

henkied · 2021-03-03T17:52:28Z

same here

[3/3/2021, 5:16:27 PM] [DysonPureCoolPlatform] Error while signing in. Status Code: 401
[3/3/2021, 5:16:27 PM] [DysonPureCoolPlatform] API could not be reached. Retry is disabled.

jakemauer · 2021-03-04T03:18:38Z

A workaround that just worked for me was to log out of the latest iOS app, log back in, then reboot homebridge.

AdeTheux · 2021-03-04T07:52:45Z

A workaround that just worked for me was to log out of the latest iOS app, log back in, then reboot homebridge.

Indeed, works here as well. Thanks.

marhindev · 2021-03-04T08:46:06Z

If I have the Dyson app running on multiple devices, I assume that most likely I have to do this in all of them. Do you only run it on one device?

…

Am 04.03.2021 um 04:18 schrieb Jake Mauer ***@***.***>: A workaround that just worked for me was to log out of the latest iOS app, log back in, then reboot homebridge. — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

bondskin · 2021-03-04T09:51:03Z

This is what I get since yesterday:
[04/03/2021, 10:42:50] [DysonPureCoolPlatform] Error while signing in. Status Code: 429
[04/03/2021, 10:42:50] [DysonPureCoolPlatform] API could not be reached. Trying again soon...

bondskin · 2021-03-04T10:01:55Z

A workaround that just worked for me was to log out of the latest iOS app, log back in, then reboot homebridge.

Hi @jakemauer, I tried that but no luck

EDIT: correction, logging out/in via iOS app, restarting Homebridge fixes it for me. It just takes a few minutes

jsalva23 · 2021-03-04T14:50:55Z

A workaround that just worked for me was to log out of the latest iOS app, log back in, then reboot homebridge.

Not working for me... anyone else still having issues?

bondskin · 2021-03-04T15:00:18Z

A workaround that just worked for me was to log out of the latest iOS app, log back in, then reboot homebridge.

Not working for me... anyone else still having issues?

did you wait a few minutes?

jakemauer · 2021-03-04T17:53:07Z

If I have the Dyson app running on multiple devices, I assume that most likely I have to do this in all of them. Do you only run it on one device?
…
Am 04.03.2021 um 04:18 schrieb Jake Mauer @.***>: A workaround that just worked for me was to log out of the latest iOS app, log back in, then reboot homebridge. — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

My assumption is logging in to one of the apps should do it. What happens when you try?

jakemauer · 2021-03-04T17:53:43Z

A workaround that just worked for me was to log out of the latest iOS app, log back in, then reboot homebridge.

Not working for me... anyone else still having issues?

Are you on the latest app version? I had to supply a two-factor code sent to my email before I could login to the iOS app, which is new behavior I think.

marhindev · 2021-03-04T19:05:52Z

Logout and login, there providing the additional auth. code sent by mail from Dyson and then a reboot of Homebridge did it for me as well! It was sufficient to do it on one iOS device.

…

Am 04.03.2021 um 18:53 schrieb Jake Mauer ***@***.***>: If I have the Dyson app running on multiple devices, I assume that most likely I have to do this in all of them. Do you only run it on one device? … Am 04.03.2021 um 04:18 schrieb Jake Mauer @.***>: A workaround that just worked for me was to log out of the latest iOS app, log back in, then reboot homebridge. — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe. My assumption is logging in to one of the apps should do it. What happens when you try? — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

AdeTheux · 2021-03-04T19:30:10Z

Looks like the main requirements is re-authenticating via the official app, and getting that code via email.
It's not really 2fa, but lols more like they're marking the email address as verified once this is done.

jsalva23 · 2021-03-04T21:58:36Z

A workaround that just worked for me was to log out of the latest iOS app, log back in, then reboot homebridge.

Not working for me... anyone else still having issues?

did you wait a few minutes?

At what point did you waited? after login off on the mobile app? before login back in at the app? before login in on the plugin? how long did you waited?

jsalva23 · 2021-03-04T21:59:23Z

A workaround that just worked for me was to log out of the latest iOS app, log back in, then reboot homebridge.

Not working for me... anyone else still having issues?

Are you on the latest app version? I had to supply a two-factor code sent to my email before I could login to the iOS app, which is new behavior I think.

yes, latest version, and yes I had to add the code sent to my email and yes that's new...

jsalva23 · 2021-03-04T22:37:42Z

I actually got it working, for some reason the region acronym didn't match my region, I don't think I changed that recently I believe it was like that since I installed the plug-in for the first time. Not sure if the API was actually validating that, but it seems it is now.

Anyways I changed to the right region and it's working now. Thank everyone for the help provided.

robertburron · 2021-03-05T05:22:41Z

I'm seeing the same thing. I've tried troubleshooting steps that others have recommended, but no luck.
[04/03/2021, 23:19:47] [DysonPureCoolPlatform] Signing in. [04/03/2021, 23:19:47] [DysonPureCoolPlatform] Error while signing in. Status Code: 429 [04/03/2021, 23:19:47] [DysonPureCoolPlatform] API could not be reached. Trying again soon... [04/03/2021, 23:20:47] [DysonPureCoolPlatform] Signing in. [04/03/2021, 23:20:47] [DysonPureCoolPlatform] Error while signing in. Status Code: 429 [04/03/2021, 23:20:47] [DysonPureCoolPlatform] API could not be reached. Trying again soon...

AdeTheux · 2021-03-05T08:10:24Z

Looks like the main requirements is re-authenticating via the official app, and getting that code via email.
It's not really 2fa, but lols more like they're marking the email address as verified once this is done.

Following the latest Dyson iOS app update from yesterday, this trick doesn't work anymore.

marhindev · 2021-03-05T09:28:08Z

So you are saying that it worked when you were on App version 5.0.21060, and after you installed 5.0.21061 it stopped working? I am on 5.0.21060 and it still works so far.

…

Am 05.03.2021 um 09:10 schrieb Arnaud de Theux ***@***.***>: Looks like the main requirements is re-authenticating via the official app, and getting that code via email. It's not really 2fa, but lols more like they're marking the email address as verified once this is done. Following the latest Dyson iOS app update from yesterday, this trick doesn't work anymore. — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

AdeTheux · 2021-03-05T10:02:29Z

So you are saying that it worked when you were on App version 5.0.21060, and after you installed 5.0.21061 it stopped working? I am on 5.0.21060 and it still works so far.
…

Not 100% sure but it was working fine until ~11pm yesterday. This morning the app was updated on my iPhone, and since then I got error 400 in HB again.

Chewwy420 · 2021-03-05T14:50:16Z

I had same issue. Logged out of app and back in with new code. started working again... Was doing work on my homebridge so multiple restarts and started doing it again... Logged out of app and back in with new code and it is working again.. Seems there is a timeout of sorts.

jsalva23 · 2021-03-05T15:36:41Z

Mine is working fine since yesterday, when I fixed the region code I was already in the latest version of the app

marhindev · 2021-03-05T16:38:58Z

I updated now and it still seems to be working.

…

Am 05.03.2021 um 11:02 schrieb Arnaud de Theux ***@***.***>: So you are saying that it worked when you were on App version 5.0.21060, and after you installed 5.0.21061 it stopped working? I am on 5.0.21060 and it still works so far. … Not 100% sure but it was working fine until ~11pm yesterday. This morning the app was updated on my iPhone, and since then I got error 400 in HB again. — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

philipamour · 2021-03-05T16:51:12Z

If you can't sign in or sign up, this is what I got from Dyson Support after spending hours on the phone and web chat:


If you’d like to place an order, we’d suggest checking out as a guest for the time being, alternatively you’re certainly welcome to create a new online Dyson account with a different email address.```

AdeTheux · 2021-03-05T16:54:33Z


If you’d like to place an order, we’d suggest checking out as a guest for the time being, alternatively you’re certainly welcome to create a new online Dyson account with a different email address.```

Not really related to this issue.

philipamour · 2021-03-05T16:56:41Z

Asked them if this is relevant to Dyson Link, they said yes.

…

On Mar 5, 2021, at 4:54 PM, Arnaud de Theux ***@***.***> wrote: If you’d like to place an order, we’d suggest checking out as a guest for the time being, alternatively you’re certainly welcome to create a new online Dyson account with a different email address.``` Not really related to this issue. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#166 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABDVUCLXIJEYMVWFLUSS4XTTCEEFTANCNFSM4YQXIEWQ>.

philipamour · 2021-03-05T17:09:59Z

I've had to log out of Dyson link, create a new account with a new email, re-pair the device and then I was able to use my new credentials in this plugin config. All works now.

rohrkemper · 2021-03-27T15:51:12Z

Whoops I already deleted all logs when I reinstalled. Other ideas?

…

On Sat, Mar 27, 2021 at 14:59 Mike ***@***.***> wrote: I found the credentials in the homebrige.log and used it in the Homebridge config, this made it work for me Can you explain where to find the credentials in the log file. I see some text saying that they will be upcoming in the log. But I don't see the actual credentials. @rohrkemper <https://github.com/rohrkemper> you need to go back in the log until the last time the plugin connected successfully, there it prints the credentials. if you cycle your logs or don't archive it, you will not see this information until you are able to login again It looks something like: "Credentials for device with serial number NN2-EU-YXZ are: eyJTZXJpYW..." — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#166 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADHVYSYOLRVLTZ4JNUCKDB3TFXQF7ANCNFSM4YQXIEWQ> .

sweetw0r · 2021-03-28T08:02:25Z

Decided to give it a go:
https://mega.nz/folder/ULwAzD6K#twtjwaSJWEF1AQrsdFM_sQ

There are a postman collection and Dyson.apk source.

Status
Get a code by EMAIL_PWD_2FA
Get credentials. It is incomplete. ~~See if you can figure this one out.~~

P.S. Look at C1545d.java

Update - April 7 2021: After @coraxx pointed out that this Postman collection works I went ahead and verified it. And indeed it started working now. You can get credentials manually in Postman and Dev can update the plugin.

P.S. It is better to store the credentials in the plugin settings (existing feature is off by default) so you don't have go thru this process every time unless credentials get compromised.

tkaudioservices · 2021-03-31T15:02:40Z

@sweetw0r Did you manage to get this to work? Is this a way of extracting your machines credentials, I didn't know mine before the 2FA .

siim911 · 2021-03-31T16:19:45Z

I USE TP06
and i have the same issue i tried to get the credentials but i failed. this is happened after the new sign in changes which require to enter a code sent to the email

[DysonPureCoolPlatform] Device credentials not stored, asking Dyson API. If you want to prevent communication with the Dyson API, copy the credentials for each device from the coming log entries to the config.json.
[3/31/2021, 7:07:16 PM] [DysonPureCoolPlatform] Checked user account.
[3/31/2021, 7:07:16 PM] [DysonPureCoolPlatform] Signing in.
[3/31/2021, 7:07:22 PM] [DysonPureCoolPlatform] Error while signing in. Status Code: 429

arkku · 2021-03-31T16:33:16Z

I got the same error, but finally managed to get it working like this:

stop Homebridge
log out of Dyson from their mobile app
type in the command to restart Homebridge but don't press enter
log in to Dyson from their mobile app (on the same network as your Homebridge) and complete the 2FA
immediately as you log in, press enter on the Homebridge restart command

tkaudioservices · 2021-04-01T07:27:37Z

Is there no other way to retrieve your credentials, tried time and time again to time to mobile app login and Homebridge restart; to no avail

Krillle · 2021-04-01T08:15:05Z

@tkaudioservices Make sure your phone and homebridge are in the same network, so presenting same outer IP to Dyson API. Like that (and only like that) it worked for me.
(I didn’t even need to hurry as @arkku suggests.)

arkku · 2021-04-01T08:52:30Z

Could be that it's simply unrealiable and not actually as time-sensitive as I thought, i.e., retry a few times, and also wait some time between retries since I think it blocks you for too many failed attempts.

sweetw0r · 2021-04-02T04:52:53Z

Still need to figure out that final call to receive credentials. I suspect it is to /v3/userregistration/email/verify where you are supposed to pass "otpCode" that gets sent to your email after calling the /v3/userregistration/mobile/auth.

Can somebody with Java knowledge look at this syntax to figure out the request scheme?

sources/p033c3/C1545d.java

public C1545d(C3632i iVar, C8058u uVar, String str, String str2, String str3, String str4, String str5) {
        C9482o.m34106c(iVar, "httpRequestFactory");
        C9482o.m34106c(uVar, "userManagementEndpointsConfig");
        C9482o.m34106c(str, "countryCode");
        C9482o.m34106c(str2, SessionInfoKeys.Email);
        C9482o.m34106c(str3, "password");
        C9482o.m34106c(str4, "challengeId");
        C9482o.m34106c(str5, "otpCode");
        this.f4706b = iVar;
        this.f4707c = uVar;
        this.f4708d = str;
        this.f4705a = C10600m.m38108e(C15455l0.m55355l(C14509u.m52266a(SessionInfoKeys.Email, str2), C14509u.m52266a("password", str3), C14509u.m52266a("challengeId", str4), C14509u.m52266a("otpCode", str5)));

jonathanswenson · 2021-04-06T07:01:19Z

Looks like the secret here is the wifipassword of the device printed on the manual / sticker on the front of the fan.

It is first hashed (SHA512) and then base64 encoded. that is the “password” that you can also fetch with the manifest API:

wifiPassword = "<wifiPassword>“
hash = crypto.createHash('sha512')
hash.update(wifiPassword)
buffer = hash.digest()
password =  buffer.toString("base64")

However, this alone is not sufficient as the value for the “credentials” field for the plugin.

Looking at the source it is the base64 encoded JSON stringified apiConfig (as fetched from the manifest endpoint) with the addition of a “password” field to represent the sha512 hashed / base 64 encoded json string.

see (here)[https://github.com/lukasroegner/homebridge-dyson-pure-cool/blob/7287ae32d1e947242ab5c7655a79d3adbe3a2bf6/src/dyson-pure-cool-platform.js#L240] and (here)[https://github.com/lukasroegner/homebridge-dyson-pure-cool/blob/7287ae32d1e947242ab5c7655a79d3adbe3a2bf6/src/dyson-pure-cool-platform.js#L268]

For me this was:

{"Serial":"<serial>”,"Name":"<device_name>“,"Version":"<device_version>“,"LocalCredentials":"<from_manifest>“,"AutoUpdate":true,"NewVersionAvailable":true,"ProductType":"475","ConnectionType":"wss", "password": "<hashed/base64encoded wifi password>”}

It is possible to log in using the new authentication flow (that requires the 2FA email). I followed this comment to figure out how to do that.

It looks like you can circumvent the authentication with dyson completely if you have the wifi password (and other information you can get mostly from dyson link). It appears that the plugin is only using part of the information it gets from the manifests API:

homebridge-dyson-pure-cool/src/dyson-pure-cool-platform.js

Line 323 in 7287ae3

    
           platform.devices.push(new DysonPureCoolDevice(platform, apiConfig.Name, apiConfig.Serial, apiConfig.ProductType, apiConfig.Version, apiConfig.password, config));

in particular the fields apiConfig.Name, apiConfig.Serial, apiConfig.ProductType, apiConfig.Version, apiConfig.password

I was able to do the following given that I know the serial (from sticker or dyson link), name (from dyson link), version (software version in dyson link), product type (from the front sticker final 3 digits of product SSID) and wifi password.

wifiPassword = "<wifiPassword>“
hash = crypto.createHash('sha512')
hash.update(wifiPassword)
buffer = hash.digest()
password =  buffer.toString("base64")

serial = "<Serial>“
name = "<Room Name>“
version = "<Software Version>“
productType = "<Device Type>“

json = {"Serial": serial, "Name": name,"Version": version,"ProductType": productType, "password": password}

credentials = Buffer.from(JSON.stringify(json)).toString('base64')
console.log(credentials)

Hopefully that helps someone who has been struggling to the re-auth flow to work.

coraxx · 2021-04-06T10:25:57Z

@sweetw0r I just quickly played around with the new API calls a bit (in python). This is how you could login with the 2FA and receive a token. Though I do not know how new API calls look like using this token.

If someone is interested, here some pseudo code (working but no logic combining them):

import requests

# This checks if the user/email exists
url = 'https://appapi.cp.dyson.com/v3/userregistration/email/userstatus'
params = {'country': 'DE'}
payload = {'Email': 'XYZ@domain.tld'}
headers = {'user-agent': 'android client'}
r = requests.post(url, params=params, headers=headers, json=payload, verify = False)
# returns something like:
# {"accountStatus":"ACTIVE","authenticationMethod":"EMAIL_PWD_2FA"}
print (r.text)


# This will trigger sending the email with 2FA code
url = 'https://appapi.cp.dyson.com/v3/userregistration/email/auth'
params = {'country': 'DE'}
payload = {'Email': 'XYZ@domain.tld', 'Password': 'SecretDysonAccountPassword'}
headers = {'user-agent': 'android client'}
r = requests.post(url, params=params, headers=headers, json=payload, verify = False)
# returns something like:
# {"challengeId":"xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"}
print (r.text)


# Get the challenge id from previous call and the 6 digit code from the 2FA email
url = 'https://appapi.cp.dyson.com/v3/userregistration/email/verify'
params = {'country': 'DE'}
payload = {'Email': 'XYZ@domain.tld', 'Password': 'SecretDysonAccountPassword', "challengeId":"result from previous call", 'otpCode': '6 digit code received via email'}
headers = {'user-agent': 'android client'}
r = requests.post(url, params=params, headers=headers, json=payload, verify = False)
# returns something like:
# {"account":"xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx","token":"xxxxx-xxxxxxxxxxxxx_xxxxxxxxxxxxxxxxxxxxxxx","tokenType":"Bearer"}
print (r.text)

coraxx · 2021-04-06T19:39:43Z

Small update: after getting the token, all old API calls work as expected. Authentication is changed from "Basic" to "Bearer":

url = 'https://appapi.cp.dyson.com/v2/provisioningservice/manifest'
params = {'country': 'DE'}
# token id which gets returned after sending the 2FA code in the form of xxxxx-xxxxxxxxxxxxx_xxxxxxxxxxxxxxxxxxxxxxx
headers = {'user-agent': 'android client', 'Authorization': 'Bearer xxxxx-xxxxxxxxxxxxx_xxxxxxxxxxxxxxxxxxxxxxx'}
r = requests.get(url, params=params, headers=headers, verify = False)
# returns all your dyson products
print (r.text)

tkaudioservices · 2021-04-06T19:48:24Z

Small update: after getting the token, all old API calls work as expected. Authentication is changed from "Basic" to "Bearer":

url = 'https://appapi.cp.dyson.com/v2/provisioningservice/manifest'
params = {'country': 'DE'}
# token id which gets returned after sending the 2FA code in the form of xxxxx-xxxxxxxxxxxxx_xxxxxxxxxxxxxxxxxxxxxxx
headers = {'user-agent': 'android client', 'Authorization': 'Bearer xxxxx-xxxxxxxxxxxxx_xxxxxxxxxxxxxxxxxxxxxxx'}
r = requests.get(url, params=params, headers=headers, verify = False)
# returns all your dyson products
print (r.text)

Has anyone successfully pieced this together to receive Credentials?

coraxx · 2021-04-06T19:56:28Z

Yeah, it's very much just a proof of concept though I successfully got my Dyson fan credentials.
It should be easy enough to update the plugin here regarding the authentication.
Biggest issue I see, is to make entering the 2FA code easy enough for the end user.

Sadly my JavaScript knowledge is very limited, otherwise I would offer a pull request.
If I have time tomorrow I will give it a try.

jonathanswenson · 2021-04-06T20:48:42Z

@tkaudioservices I have successfully gone though the new authorization flow (V3) using curl and used the final returned bearer token to fetch the “password”. That password can be generated without having to do the auth flow if you have your wifi password (as printed on the sticker on the front / in the manual).

Unfortunately, that is not sufficient to generate the “credentials” as required by the plugin though. You’ll have to encode that password (and a few other bits of information properly) to generate one of these.

sweetw0r · 2021-04-08T05:26:22Z

Thanks @coraxx Just updated my original #166 (comment)

Here is an example of response for v3/userregistration/email/verify request. Token is the credentials:

{
    "account":"72b2af5b-2ed0-4c41-b779-2cd1a7082788",
    "token":"1RyaUBeez-uLXQ71jckTcxWmc4TsQE5BPVc8I6F0cGw",
    "tokenType":"Bearer"
}

porowskid · 2021-04-08T09:49:04Z

I suspect there's something else going on as well. I've got credentials for my devices stored (to avoid the API) and even though the manifest localCredentials (gotten with the 2fa/token process above) still match the creds I had stored, they no longer seem to base64 decode as they did. I haven't dug too far in yet, though; I thought it was an issue of attaching the bearer token to the device comms as well as to the API, but the plugin is failing at what appears to be the config-credential decode step.

dampney · 2021-04-08T12:09:36Z

Signing into the Dyson app again and Homebridge at the same time didn't work.

I've sent a negative survey to Dyson over the new app.

Hopefully we can find a work around with this change Dyson did to break the API.

coraxx · 2021-04-08T13:39:49Z

I think I have a version ready #177 for the plugin. Only "problem" is, that it is not a nice user experience ^^

First you have to start the homebridge to retrieve the challengeID in the log. Copy that into the config, as well as the one time password code you get via email.
Then restart homebridge and get the token in the log, copy that into the plugin config aswell.

Then it should work fine from there on. I just tested it and I can still logout and log back in with 2FA on my smartphone, as well as restarting the homebridge after that.

Only problem is, when you have too many API calls in a short time. Dyson API has quite the hard API rate limiting.

wbsmith2 · 2021-04-09T02:15:32Z

A workaround that just worked for me was to log out of the latest iOS app, log back in, then reboot homebridge.

Hi @jakemauer, I tried that but no luck

EDIT: correction, logging out/in via iOS app, restarting Homebridge fixes it for me. It just takes a few minutes

This fix worked for me

raiubreaksthings · 2021-04-12T12:35:19Z

Workaround,

Log out of the app on the phone. Then restart homebridge. Let homebridge login. Then log back into the app. I am good to go now.

Soldiiier · 2021-04-13T00:22:52Z

I think the log out / log back in steps are overkill.
All you need to do is enter the Dyson app and then wait for the plugin to try its next login. mine was set to 30 minutes, so too long to have to wait. though this doest resolve the issue entirely. it still comes back about once a week.

I've now gone to the 'credentials' method.

sweetw0r · 2021-04-25T23:38:52Z

Update Dyson API.postman_collection.json with 03. Get Credentials requests to retrieve the credentials:

[
    {
        "Serial":"C4B-US-XXXXXXX",
        "Name":"Bedroom",
        "Version":"ECG2PF.46.00.007.0003",
        "LocalCredentials":"XXXXXXXXXXXXXXXXXXXXXXXXXXX/XXXXXXXXXXXXXXXXXXXXXXXXXXX/XXXXXXXXXXXXXXXXXXXXXXXXXXX",
        "AutoUpdate":false,
        "NewVersionAvailable":true,
        "ProductType":"358",
        "ConnectionType":"wss"
    }
]

lukasroegner · 2021-05-14T13:47:16Z

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.

iMonZ · 2021-08-02T12:48:25Z

None of these approaches helped.
When I visit the Authentication website on port 48000 I get directly these errors in the console:

[Error] TypeError: undefined is not an object (evaluating 'crypto.subtle.generateKey')
createKey (topee-content.js:4028)
TextCrypto (topee-content.js:3981)
(anonymous function) (topee-content.js:3869)
webpack_require (topee-content.js:20)
(anonymous function) (topee-content.js:3312)
webpack_require (topee-content.js:20)
(anonymous function) (topee-content.js:3292)
webpack_require (topee-content.js:20)
(anonymous function) (topee-content.js:3279)
webpack_require (topee-content.js:20)
(anonymous function) (topee-content.js:123)
(anonymous function) (topee-content.js:229)
webpack_require (topee-content.js:20)
(anonymous function) (topee-content.js:84)
Global Code (topee-content.js:85)
[Error] ReferenceError: Can't find variable: chrome
(anonymous function) (content.js:21826)
injectContent (content.js:21839)
injectContentOnce (content.js:21)
[Error] ReferenceError: Can't find variable: chrome
injectContent (styles.js:3253)
injectContentOnce (styles.js:3249)
[Error] ReferenceError: Can't find variable: chrome
injectContent (fonts.js:391)
injectContentOnce (fonts.js:387)
[Error] Unhandled Promise Rejection: null
promiseEmptyOnRejected
promiseReactionJob
[Error] Unhandled Promise Rejection: null
(anonymous function)
rejectPromise
promiseReactionJob

rextsou0623 · 2021-10-14T04:16:02Z

I got the same error, but finally managed to get it working like this:

stop Homebridge

log out of Dyson from their mobile app

type in the command to restart Homebridge but don't press enter

log in to Dyson from their mobile app (on the same network as your Homebridge) and complete the 2FA

immediately as you log in, press enter on the Homebridge restart command

I follow EXACTLY all steps and it worked!! Among the hundreds of methods to get the credential, only this one works!
Thank you!!!

markholland mentioned this issue Mar 5, 2021

Does not work anymore error 401 #159

Closed

AdeTheux changed the title ~~API error 400 since yesterday~~ API error 401 since yesterday Mar 5, 2021

lukasroegner mentioned this issue May 14, 2021

API 401 sign in issue #180

Closed

hendersj mentioned this issue Jul 30, 2021

401 error returned when logging in in config node pbrunier/node-red-contrib-dyson-purelink#34

Closed

lukasroegner closed this as completed Feb 12, 2022

lukasroegner mentioned this issue Feb 12, 2022

Error while receiving 2FA challenge ID. Status Code: 401 #205

Closed

API error 401 since yesterday #166

API error 401 since yesterday #166

Comments

AdeTheux commented Mar 3, 2021

jsalva23 commented Mar 3, 2021

marhindev commented Mar 3, 2021 • edited Loading

henkied commented Mar 3, 2021

jakemauer commented Mar 4, 2021

AdeTheux commented Mar 4, 2021

marhindev commented Mar 4, 2021 via email

bondskin commented Mar 4, 2021

bondskin commented Mar 4, 2021 • edited Loading

jsalva23 commented Mar 4, 2021

bondskin commented Mar 4, 2021

jakemauer commented Mar 4, 2021

jakemauer commented Mar 4, 2021

marhindev commented Mar 4, 2021 via email

AdeTheux commented Mar 4, 2021

jsalva23 commented Mar 4, 2021

jsalva23 commented Mar 4, 2021

jsalva23 commented Mar 4, 2021

robertburron commented Mar 5, 2021

AdeTheux commented Mar 5, 2021

marhindev commented Mar 5, 2021 via email

AdeTheux commented Mar 5, 2021

Chewwy420 commented Mar 5, 2021

jsalva23 commented Mar 5, 2021

marhindev commented Mar 5, 2021 via email

philipamour commented Mar 5, 2021

AdeTheux commented Mar 5, 2021

philipamour commented Mar 5, 2021 via email

philipamour commented Mar 5, 2021

rohrkemper commented Mar 27, 2021 via email

sweetw0r commented Mar 28, 2021 • edited Loading

tkaudioservices commented Mar 31, 2021

siim911 commented Mar 31, 2021

arkku commented Mar 31, 2021

tkaudioservices commented Apr 1, 2021

Krillle commented Apr 1, 2021

arkku commented Apr 1, 2021

sweetw0r commented Apr 2, 2021

jonathanswenson commented Apr 6, 2021 • edited Loading

coraxx commented Apr 6, 2021 • edited Loading

coraxx commented Apr 6, 2021

tkaudioservices commented Apr 6, 2021

coraxx commented Apr 6, 2021 • edited Loading

jonathanswenson commented Apr 6, 2021

sweetw0r commented Apr 8, 2021

porowskid commented Apr 8, 2021

dampney commented Apr 8, 2021

coraxx commented Apr 8, 2021 • edited Loading

wbsmith2 commented Apr 9, 2021

raiubreaksthings commented Apr 12, 2021

Soldiiier commented Apr 13, 2021

sweetw0r commented Apr 25, 2021

lukasroegner commented May 14, 2021

iMonZ commented Aug 2, 2021

rextsou0623 commented Oct 14, 2021

marhindev commented Mar 3, 2021 •

edited

Loading

bondskin commented Mar 4, 2021 •

edited

Loading

sweetw0r commented Mar 28, 2021 •

edited

Loading

jonathanswenson commented Apr 6, 2021 •

edited

Loading

coraxx commented Apr 6, 2021 •

edited

Loading

coraxx commented Apr 6, 2021 •

edited

Loading

coraxx commented Apr 8, 2021 •

edited

Loading