Can't auth

[custa1200]

Hi I tried using the Dyson Cloud integration, I am asked for a locale which is Australia, and I enter .com.au email address.

I get and error and when I check the logs I see the following

File "/usr/local/lib/python3.10/site-packages/libdyson/cloud/account.py", line 122, in login_email_otp response = self.request( File "/usr/local/lib/python3.10/site-packages/libdyson/cloud/account.py", line 114, in request raise DysonInvalidAuth libdyson.exceptions.DysonInvalidAuth

[dotvezz]

Thanks for the report! This is one of the issues we inherited from the original repo - it does have a workaround that is known to work (I had to do it yesterday during testing):

The workaround:

Log out of your Dyson mobile app, then log back in. After that, you should be able to authenticate on Home Assistant. Of course, drop back in here if it doesn't work

Why the heck?

Your guess is as good as mine. After I get the Formaldehyde devices working I'm gonna try to dig in and see what the heck is going on with Dyson's login flow.

[custa1200]

It's not finding the device using discovery now when I get to the host screen. I am sure it previously just worked and after giving credentials everything was added to local without specific IP addresses required. 🤷‍♂️

[dotvezz]

Interesting. I don’t believe anything has changed in the auto-config logic. Are you running your hass in docker?

[custa1200]

No. Using in a VM currently (waiting for me Yellow/Amber) It seemed to autoconfig last time. Should I maybe delete and read everything Dyson from scratch?

[dotvezz]

Ah, a VM might have the same limitations as docker, since their networking situations can often be similar. If you like, can you share the following info about your setup?

1. What hypervisor are you using? VMWare, VirtualBox, KVM+qemu, etc?
2. Are you using a virtual NIC with bridge networking, or have you assigned a physical NIC from your host to the VM?
3. Is your VM on the same subnet as your Dyson device?
   • What's the IP Address of your Dyson device?
   • The IP Address of your HACS VM? (Visible on the page https://{your-hacs-here}/config/network)
4. In general, has anything changed with your networking setup?

For what it's worth, this project has used zeroconf for device discovery since early 2021. Before that, I don't think discovery was a feature.

[dotvezz]

Marking this as closed as the original issue was resolved. Feel free to open a new issue if you want to follow up on the network discovery. 🙂