-
-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
get_devices.py results in libdyson.exceptions.DysonInvalidAuth #15
Comments
I found that you need to sign out from the dyson app. Once you do that, it asks for a passport and then emails the verification code. |
Same problem here, logging out from the app didn't help. |
After reseting the machine and linking it to new mail account, now it retrieves the devices. |
Hello, I got the same issue as you I guess,
@christianfus what's machine did you reset ? could you give me more detail? Thank you ! |
I was trying to make it work with a Dyson Pure Cool, I reset the machine and then link it to a new account with the Dyson app. But that was the temporal solution, the final solution is to connect it via mqtt connection. |
Thanks @FireHelmet for pinging me here, so I figured out on another issue that this can be resolved by trying to disconnect your phone from Dyson Link right before running the get_devices script for some reason. It can take a few tries too, the auth flow is not consistent right now. |
@Kakise , thanks I will try, I keep you informed ! |
@Kakise , I tried twice and I got this error below: Could you help ? I will also try more times... Thank you ! |
@Kakise I tried multiple times in different days, by signing out or not from Dyson mobile app and the issue persist. Could take a look in the code ? Thank you ! |
I'm getting the same issue...I used Dyson Cloud to add my Dyson Pure Hot+Cool to Dyson Local. It stopped working so I deleted it from Dyson Local and tried to setup Dyson Cloud to add it again. No luck. I'm getting the same error that FireHelmet posted. Any help would be most appreciated! This integration has been rock solid since I set it up. Traceback (most recent call last): |
Dropping in to say that the logging out from the app worked for me to at least allow me to finish Dyson Cloud HASS integration setup, but once that was complete I was given another log and the integration was inoperable.
I tried to delete the integration setup to start over, just in case this was a glitch, but now I'm flat out being blocked from logging in there - no amount of logging out from the app seems to fix it. |
On my end just launching the companion app on my phone (with it connected to my Dyson fan) was enough to fix this, no need to log out or reset anything. Then getting the credentials works fine. If it's been a while since I launched the Dyson app, then I get |
+1 to this same issue, failing after asking for password and successfully receiving verification code. |
+1 |
+1 Still getting the Steps I’ve tried:
I’ve seen some people have had success by changing the user agent, is this still a viable workaround? Any other suggestions? |
Same issue here, I get that exception as soon as I enter my email, no password. |
I updated libdyson to v0.8.11, only change I made is changing the user agent used to connect to the api. It should fix further connection problems.
Please reinstall the app, login to your account and then log out, I was able to reproduce your issue by uninstalling the app before logout |
That does solve it, thanks ! |
I’m still getting the same error… I’ve updated Is there something I’m missing? 🤔
|
@kastrom , yes you missed to use libdyson with Dyson Local component. Please re-read https://github.com/shenxn/ha-dyson/#setup-manually When your credential is generated with libdyson, you need to use it in Dyson Local component from HA. |
Retry after waiting more time between the logout from Dyson app and the login into libdyson. I had same issue the first time and after it has worked |
@FireHelmet thank you, you're a genius — I’d all but given up at this point. And also thanks to @Kakise for the fix. |
Trying to get the credentials and getting this exception.
The text was updated successfully, but these errors were encountered: