search

home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
72.69k stars 30.44k forks source link

Dyson integration stopped working with 2021.2 #46400

Closed afk11 closed 2 years ago

afk11 commented 3 years ago

The problem

I have been using the dyson integration with my hot/cold fan successfully for a while. I upgraded HA last night to 2021.2 and saw alerts that the integration couldn't initialize

What is version of Home Assistant Core has the issue?

2021.2

What was the last working version of Home Assistant Core?

2021.1

What type of installation are you running?

Home Assistant Core

Integration causing the issue

Dyson

Link to integration documentation on our website

https://www.home-assistant.io/integrations/dyson/

Example YAML snippet

dyson:
  username: EMAIL
  password: !secret SECRET
  language: GB
  devices:
    - device_id: DEVICE_ID
      device_ip: LAN_IP

Anything in the logs that might be useful for us?


# First Warning in logs

2021-02-11 03:17:41 ERROR (SyncWorker_2) [homeassistant.components.dyson] Not connected to Dyson account. Unable to add devices
2021-02-11 03:17:41 INFO (MainThread) [homeassistant.setup] Setup of domain dyson took 0.6 seconds
2021-02-11 03:17:41 ERROR (MainThread) [homeassistant.setup] Setup failed for dyson: Integration failed to initialize.
2021-02-11 03:17:41 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event call_service[L]: domain=persistent_notification, service=create, service_data=title=Invalid config, message=The following integrations and platforms could not be set up:
- dyson

# Later warning in logs. I'm not sure if this is actually from dyson or not. The IP looked weird, but when I googled it, it's some AWS thing. 

2021-02-11 03:17:41 ERROR (SyncWorker_2) [homeassistant.components.dyson] Not connected to Dyson account. Unable to add devices
2021-02-11 03:17:41 INFO (MainThread) [homeassistant.setup] Setup of domain dyson took 0.6 seconds
2021-02-11 03:17:41 ERROR (MainThread) [homeassistant.setup] Setup failed for dyson: Integration failed to initialize.
2021-02-11 03:17:41 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event call_service[L]: domain=persistent_notification, service=create, service_data=title=Invalid config, message=The following integrations and platforms could not be set up:
- dyson
Please check your config and [logs](/config/logs)., notification_id=invalid_config>
2021-02-11 03:17:41 DEBUG (SyncWorker_0) [botocore.utils] Caught retryable HTTP exception while making metadata service request to http://169.254.169.254/latest/api/token: Connect timeout on endpoint URL: "http://169.254.169.254/latest/api/token"
Traceback (most recent call last):
File "/usr/local/lib/python3.8/site-packages/urllib3/connection.py", line 169, in _new_conn
conn = connection.create_connection(
File "/usr/local/lib/python3.8/site-packages/urllib3/util/connection.py", line 96, in create_connection
raise err
File "/usr/local/lib/python3.8/site-packages/urllib3/util/connection.py", line 86, in create_connection
sock.connect(sa)
socket.timeout: timed out
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/lib/python3.8/site-packages/botocore/httpsession.py", line 311, in send
urllib_response = conn.urlopen(
File "/usr/local/lib/python3.8/site-packages/urllib3/connectionpool.py", line 755, in urlopen
retries = retries.increment(
File "/usr/local/lib/python3.8/site-packages/urllib3/util/retry.py", line 506, in increment
raise six.reraise(type(error), error, _stacktrace)
File "/usr/local/lib/python3.8/site-packages/urllib3/packages/six.py", line 735, in reraise
raise value
File "/usr/local/lib/python3.8/site-packages/urllib3/connectionpool.py", line 699, in urlopen
httplib_response = self._make_request(
File "/usr/local/lib/python3.8/site-packages/urllib3/connectionpool.py", line 394, in _make_request
conn.request(method, url, **httplib_request_kw)
File "/usr/local/lib/python3.8/site-packages/urllib3/connection.py", line 234, in request
super(HTTPConnection, self).request(method, url, body=body, headers=headers)
File "/usr/local/lib/python3.8/http/client.py", line 1255, in request
self._send_request(method, url, body, headers, encode_chunked)
File "/usr/local/lib/python3.8/site-packages/botocore/awsrequest.py", line 92, in _send_request
rval = super(AWSConnection, self)._send_request(
File "/usr/local/lib/python3.8/http/client.py", line 1301, in _send_request
self.endheaders(body, encode_chunked=encode_chunked)
File "/usr/local/lib/python3.8/http/client.py", line 1250, in endheaders
self._send_output(message_body, encode_chunked=encode_chunked)
File "/usr/local/lib/python3.8/site-packages/botocore/awsrequest.py", line 120, in _send_output
self.send(msg)
File "/usr/local/lib/python3.8/site-packages/botocore/awsrequest.py", line 204, in send
return super(AWSConnection, self).send(str)
File "/usr/local/lib/python3.8/http/client.py", line 950, in send
self.connect()
File "/usr/local/lib/python3.8/site-packages/urllib3/connection.py", line 200, in connect
conn = self._new_conn()
File "/usr/local/lib/python3.8/site-packages/urllib3/connection.py", line 174, in _new_conn
raise ConnectTimeoutError(
urllib3.exceptions.ConnectTimeoutError: (<botocore.awsrequest.AWSHTTPConnection object at 0x7f41143bd5e0>, 'Connection to 169.254.169.254 timed out. (connect timeout=1)')
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/lib/python3.8/site-packages/botocore/utils.py", line 377, in _fetch_metadata_token
response = self._session.send(request.prepare())
File "/usr/local/lib/python3.8/site-packages/botocore/httpsession.py", line 344, in send
raise ConnectTimeoutError(endpoint_url=request.url, error=e)
botocore.exceptions.ConnectTimeoutError: Connect timeout on endpoint URL: "http://169.254.169.254/latest/api/token"
2021-02-11 03:17:41 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=persistent_notification.invalid_config, old_state=None, new_state=<state persistent_notification.invalid_config=notifying; title=Invalid config, friendly_name=Invalid config, message=The following integrations and platforms could not be set up:
- dyson

I'm running the qcow2 image in KVM. Happy to muck about with suggested tweaks if it helps narrow down the issue.

bfayers commented 3 years ago

May I know where is the dyson.py location if I am using HA Supervised? I tried to search this file inside my Debian but I can’t locate it, thank you

Just run the docker command shown above.

ghost commented 3 years ago

May I know where is the dyson.py location if I am using HA Supervised? I tried to search this file inside my Debian but I can’t locate it, thank you

Just run the docker command shown above.

Thank you, didn’t realise this will work

shesmer commented 3 years ago

After applying the dyson.py fix I get further but still errors that it can't connect to my devices like this

2021-02-17 21:12:14 WARNING (SyncWorker_2) [homeassistant.components.dyson] Unable to connect to device DysonPureCool(...)
2021-02-17 21:12:19 WARNING (SyncWorker_2) [libpurecool.dyson_pure_cool_link] Unable to find device XXXXX, try 0
2021-02-17 21:12:28 WARNING (SyncWorker_2) [libpurecool.dyson_pure_cool_link] Unable to find device XXXXX, try 1
2021-02-17 21:12:36 WARNING (SyncWorker_2) [libpurecool.dyson_pure_cool_link] Unable to find device XXXXX, try 2
2021-02-17 21:12:45 WARNING (SyncWorker_2) [libpurecool.dyson_pure_cool_link] Unable to find device XXXXX, try 3
2021-02-17 21:12:53 WARNING (SyncWorker_2) [libpurecool.dyson_pure_cool_link] Unable to find device XXXXX, try 4
2021-02-17 21:13:02 WARNING (SyncWorker_2) [libpurecool.dyson_pure_cool_link] Unable to find device XXXXX, try 5
2021-02-17 21:13:10 WARNING (SyncWorker_2) [libpurecool.dyson_pure_cool_link] Unable to find device XXXXX, try 6
2021-02-17 21:13:19 WARNING (SyncWorker_2) [libpurecool.dyson_pure_cool_link] Unable to find device XXXXX, try 7
2021-02-17 21:13:27 WARNING (SyncWorker_2) [libpurecool.dyson_pure_cool_link] Unable to find device XXXXX, try 8
2021-02-17 21:13:36 WARNING (SyncWorker_2) [libpurecool.dyson_pure_cool_link] Unable to find device XXXXX, try 9
2021-02-17 21:13:39 ERROR (SyncWorker_2) [libpurecool.dyson_pure_cool_link] Unable to connect to device XXXXX

I turned on debug but this is all I get

2021-02-18 17:37:04 WARNING (SyncWorker_0) [libpurecool.dyson_pure_cool_link] Unable to find device XXXXX, try 7
2021-02-18 17:37:07 DEBUG (zeroconf-Engine-803) [zeroconf] Ignoring duplicate message received from '127.0.0.1':5353 (socket 9) (40 bytes) as [b'\x00\x00\x00\x00\x00\x01\x00\x00\x00\x00\x00\x00\x0b_dyson_mqtt\x04_tcp\x05local\x00\x00\x0c\x00\x01']
2021-02-18 17:37:07 DEBUG (zeroconf-Engine-803) [zeroconf] Ignoring duplicate message received from '172.17.0.4':5353 (socket 9) (40 bytes) as [b'\x00\x00\x00\x00\x00\x01\x00\x00\x00\x00\x00\x00\x0b_dyson_mqtt\x04_tcp\x05local\x00\x00\x0c\x00\x01']
2021-02-18 17:37:08 DEBUG (zeroconf-Engine-803) [zeroconf] Ignoring duplicate message received from '127.0.0.1':5353 (socket 9) (40 bytes) as [b'\x00\x00\x00\x00\x00\x01\x00\x00\x00\x00\x00\x00\x0b_dyson_mqtt\x04_tcp\x05local\x00\x00\x0c\x00\x01']
2021-02-18 17:37:08 DEBUG (zeroconf-Engine-803) [zeroconf] Ignoring duplicate message received from '172.17.0.4':5353 (socket 9) (40 bytes) as [b'\x00\x00\x00\x00\x00\x01\x00\x00\x00\x00\x00\x00\x0b_dyson_mqtt\x04_tcp\x05local\x00\x00\x0c\x00\x01']
2021-02-18 17:37:09 DEBUG (zeroconf-Engine-803) [zeroconf] Ignoring duplicate message received from '127.0.0.1':5353 (socket 9) (40 bytes) as [b'\x00\x00\x00\x00\x00\x01\x00\x00\x00\x00\x00\x00\x0b_dyson_mqtt\x04_tcp\x05local\x00\x00\x0c\x00\x01']
2021-02-18 17:37:09 DEBUG (zeroconf-Engine-803) [zeroconf] Ignoring duplicate message received from '172.17.0.4':5353 (socket 9) (40 bytes) as [b'\x00\x00\x00\x00\x00\x01\x00\x00\x00\x00\x00\x00\x0b_dyson_mqtt\x04_tcp\x05local\x00\x00\x0c\x00\x01']
2021-02-18 17:37:11 DEBUG (zeroconf-Engine-803) [zeroconf] Ignoring duplicate message received from '127.0.0.1':5353 (socket 9) (40 bytes) as [b'\x00\x00\x00\x00\x00\x01\x00\x00\x00\x00\x00\x00\x0b_dyson_mqtt\x04_tcp\x05local\x00\x00\x0c\x00\x01']
2021-02-18 17:37:11 DEBUG (zeroconf-Engine-803) [zeroconf] Ignoring duplicate message received from '172.17.0.4':5353 (socket 9) (40 bytes) as [b'\x00\x00\x00\x00\x00\x01\x00\x00\x00\x00\x00\x00\x0b_dyson_mqtt\x04_tcp\x05local\x00\x00\x0c\x00\x01']
2021-02-18 17:37:12 WARNING (SyncWorker_0) [libpurecool.dyson_pure_cool_link] Unable to find device XXXXX, try 8
emdimon commented 3 years ago

Any update on when this fix will be implemented ?

maxandersen commented 3 years ago

connect to the console for it and run docker exec -t homeassistant pip3 install --upgrade git+https://github.com/bfayers/libpurecool.git@fix_auth Then restart hass.

this made hass again able to see and change temperature but turn on/off does not seem to work.

repomanz commented 3 years ago

Hello everyone. Been missing my dyson automations since it broke. I'm running hassos supervised on the hassos vm image. I've logged into the console but I can't seem to find the correct commands to get to the point where I can add the updated dyson.py file for temporary fix. Any suggestion here?

Also, it looks from above comments there's an overhaul for this integration, any preview documentation on this yet as I'm hoping it addresses a few of the shortcomings in current integration.

kintaroju commented 3 years ago

Hello everyone. Been missing my dyson automations since it broke. I'm running hassos supervised on the hassos vm image. I've logged into the console but I can't seem to find the correct commands to get to the point where I can add the updated dyson.py file for temporary fix. Any suggestion here?

Also, it looks from above comments there's an overhaul for this integration, any preview documentation on this yet as I'm hoping it addresses a few of the shortcomings in current integration.

connect to the console for it and run docker exec -t homeassistant pip3 install --upgrade git+https://github.com/bfayers/libpurecool.git@fix_auth Then restart hass.

the above fix was suggested to me on my vm and works

kintaroju commented 3 years ago

@bfayers, haha you beat me to it mention your command that worked like hot cakes for me

aLTeReGo-SWI commented 3 years ago

I've tried both the Portainer console method

install Portainer Addon, disable protection mode, start addon and open web-ui. in Portainer settings remove core and homeassistant from the disabled devices now from the containr list select homeassistant, clic the console button and enter the three lines above one after the other: cd /usr/local/lib/python3.8/site-packages/libpurecool/ rm dyson.py curl -O https://raw.githubusercontent.com/bfayers/libpurecool/fix_auth/libpurecool/dyson.py Reboot core and Voilà !

as well as the pip3 method

connect to the console for it and run docker exec -t homeassistant pip3 install --upgrade git+https://github.com/bfayers/libpurecool.git@fix_auth Then restart hass.

Both executed and completed successfully, including restarting HA Core. Unfortunately, neither of these solutions has fixed the issue. My Dyson Hot+Cool was working perfectly in Home Assistant before February 11th, but hasn't worked since. I've made zero changes to the Dyson section of my configuration.yaml file. Any help would be much appreciated.

Invalid config The following integrations and platforms could not be set up:

dyson Please check your config and logs.

Logger: homeassistant.setup Source: setup.py:138 First occurred: 5:42:17 PM (1 occurrences) Last logged: 5:42:17 PM

Setup failed for dyson: Integration failed to initialize.

Logger: homeassistant.components.dyson Source: components/dyson/init.py:60 Integration: dyson (documentation, issues) First occurred: 5:42:17 PM (1 occurrences) Last logged: 5:42:17 PM

Not connected to Dyson account. Unable to add devices

repomanz commented 3 years ago

Hello everyone. Been missing my dyson automations since it broke. I'm running hassos supervised on the hassos vm image. I've logged into the console but I can't seem to find the correct commands to get to the point where I can add the updated dyson.py file for temporary fix. Any suggestion here? Also, it looks from above comments there's an overhaul for this integration, any preview documentation on this yet as I'm hoping it addresses a few of the shortcomings in current integration.

connect to the console for it and run docker exec -t homeassistant pip3 install --upgrade git+https://github.com/bfayers/libpurecool.git@fix_auth Then restart hass.

the above fix was suggested to me on my vm and works

I'm using the hassos image (not a native linux image). That command doesn't work

image

When I login to the console, I have very specific HA commands I have to use. image

https://www.home-assistant.io/blog/2018/07/11/hassio-images/

kintaroju commented 3 years ago

You need to type 'login' then that command afterwards

repomanz commented 3 years ago

You need to type 'login' then that command afterwards

+1 to you. I've been using this now for 2 years and up until now I didn't know I could get to the actual shell. Thanks a ton!

repomanz commented 3 years ago

You need to type 'login' then that command afterwards

Well I spoke too soon; looks like the integration is still failing after running the command. Is there yaml changes with this update that I need to consider? I've looked at the dyson page and my settings are correct (per the page)

Kernald commented 3 years ago

It still fails for me as well, with a plain Docker image and restarting it after upgrading libpurecool with the command listed above.

repomanz commented 3 years ago

I put my system in the beta channel for supervisor. That fixed it, dyson is now working but sadly, I can't get to the supervisor UI anymore. :)

zjph602xtc commented 3 years ago

Last week, the problem was solved by replacing dyson.py by: https://raw.githubusercontent.com/bfayers/libpurecool/auth_customdeps/libpurecool/dyson.py

It stops working today. No success with: pip3 install --upgrade git+https://github.com/bfayers/libpurecool.git@fix_auth

3mta3 commented 3 years ago

Broken (again) here also - tried both pip3 install and docker update solutions that worked previously, but no luck this time. I'm running HassOS fwiw. I also reinstalled HACS today - no luck restoring from previous backups, but wonder if there's a new conflict..

arifroni commented 3 years ago

something happened again. since a restart in the morning mine is also not working.

damiano75 commented 3 years ago

Hi, my Dyson is an HP02 and I migrated all my stuff to ha-dyson It is a local integration, it is not linked to my Dyson account and it works very well

arifroni commented 3 years ago

Hi, my Dyson is an HP02 and I migrated all my stuff to https://github.com/shenxn/ha-dyson. It is a local integration, it is not linked to my Dyson account and it works very well

I am trying to add my dyson to this integration. But it is asking for serial and credential, how did you get these values?

ripburger commented 3 years ago

Hi, my Dyson is an HP02 and I migrated all my stuff to https://github.com/shenxn/ha-dyson. It is a local integration, it is not linked to my Dyson account and it works very well

I am trying to add my dyson to this integration. But it is asking for serial and credential, how did you get these values?

Serial can be found on the device itself, but I am stuck on the credential part too... :(

GitPetri commented 3 years ago

something happened again. since a restart in the morning mine is also not working.

Ditto

damiano75 commented 3 years ago

When I installed this integration I actually had two integrations: image I first inserted my dyson account credential in Dyson Cloud: I think it is used just to know which devices I have. Then discovery found my device and just asked for host ip

lolongan commented 3 years ago

@damiano75 Where do you find discovery or how do you enable it ? TIA.

arifroni commented 3 years ago

at the moment dyson_cloud is not working either. saying invalid auth.

damiano75 commented 3 years ago

@damiano75 Where do you find discovery or how do you enable it ? TIA.

It is the HA discovery service: https://www.home-assistant.io/integrations/discovery/

damiano75 commented 3 years ago

at the moment dyson_cloud is not working either. saying invalid auth.

Maybe your device is not yet supported

lolongan commented 3 years ago

@damiano75 Where do you find discovery or how do you enable it ? TIA.

It is the HA discovery service: https://www.home-assistant.io/integrations/discovery/

I have this discovery added in my configuration.yaml discovery: but when I try to add the dyson_local integration, it still ask me credentials, serials, host and so on.

damiano75 commented 3 years ago

@damiano75 Where do you find discovery or how do you enable it ? TIA.

It is the HA discovery service: https://www.home-assistant.io/integrations/discovery/

I have this discovery added in my configuration.yaml discovery: but when I try to add the dyson_local integration, it still ask me credentials, serials, host and so on.

Your credentials should be the credentials of your Dyson account, the host should be the IP address of your device in your local lan

ripburger commented 3 years ago

k it is used just to know which devices I have. Then discovery found my device and just asked for host ip

Thx, but I'm getting an error when I try to login to Dyson Cloud.

arifroni commented 3 years ago

at the moment dyson_cloud is not working either. saying invalid auth.

Maybe your device is not yet supported

mine is TP04, which is listed as pure cool in dyson_local integration. so i assumed it is also supported in dyson_cloud.

damiano75 commented 3 years ago

at the moment dyson_cloud is not working either. saying invalid auth.

Maybe your device is not yet supported

mine is TP04, which is listed as pure cool in dyson_local integration. so i assumed it is also supported in dyson_cloud.

I had problem with dyson_local at the beginning: it saw my device but it didn't accept ip address. In this case my device was not supported yet

image

damiano75 commented 3 years ago

Now all sensors and scripts work weel

image

aLTeReGo-SWI commented 3 years ago

@damiano75, what exactly did you do to get working again?

3mta3 commented 3 years ago

Now all sensors and scripts work weel

@damiano75 are you using shenxn's ha-dyson service, or the native integration? It must be ha-dyson as native's still wonky on my side.

damiano75 commented 3 years ago

@damiano75, what exactly did you do to get working again?

I installed the integration by shenxn, at the beginning there were two integrations: Dyson Cloud and Dyson Local. I first installed Dyson Cloud and login with my Dyson credentials, then Dyson Local was able to discover my device and to create sensors and entities

ripburger commented 3 years ago

I guess that now that Dyson has changed something on their end, Dyson Cloud isn't able to login anymore (probably as of yesterday). Hope there's a way to solve this!

bfayers commented 3 years ago

I guess that now that Dyson has changed something on their end, Dyson Cloud isn't able to login anymore (probably as of yesterday). Hope there's a way to solve this!

For you, and anyone else in the thread trying to use shexn's integration (or the stock one with my library change)

Sign out of the Dyson App, then log into it again and then restart home assistant as soon as you've logged in on the app - should be fine after that.

damiano75 commented 3 years ago

Now all sensors and scripts work weel

@damiano75 are you using shenxn's ha-dyson service, or the native integration? It must be ha-dyson as native's still wonky on my side.

shenxn's one, because with native integration I have also another issue: every time I unplug my device from the power HA loses the connection with the device and I have to restart HA to re-establish the connection. With this local integration I don't have any connection issue

PsychoMnts commented 3 years ago

I have installed both dyson cloud and dyson local using HACS. Where do I enter my credentials? I only see Dyson Local as intergration listed.

ripburger commented 3 years ago

I guess that now that Dyson has changed something on their end, Dyson Cloud isn't able to login anymore (probably as of yesterday). Hope there's a way to solve this!

For you, and anyone else in the thread trying to use shexn's integration (or the stock one with my library change)

Sign out of the Dyson App, then log into it again and then restart home assistant as soon as you've logged in on the app - should be fine after that.

Thanks for the reply, but still not able to login unfortunately! :(

damiano75 commented 3 years ago

I have installed both dyson cloud and dyson local using HACS. Where do I enter my credentials? I only see Dyson Local as intergration listed.

Now I think shenxn changed the integration, it seems you have to enter your credentials and host IP in Dyson Local integration, but I don't know the details, 'cause I installed this integration at his early stage and thejn I just updated it

arifroni commented 3 years ago

I guess that now that Dyson has changed something on their end, Dyson Cloud isn't able to login anymore (probably as of yesterday). Hope there's a way to solve this!

For you, and anyone else in the thread trying to use shexn's integration (or the stock one with my library change)

Sign out of the Dyson App, then log into it again and then restart home assistant as soon as you've logged in on the app - should be fine after that.

thanks. it works with ha_dyson_cloud and leads to the discovery by ha_dyson.

arifroni commented 3 years ago

I guess that now that Dyson has changed something on their end, Dyson Cloud isn't able to login anymore (probably as of yesterday). Hope there's a way to solve this!

For you, and anyone else in the thread trying to use shexn's integration (or the stock one with my library change) Sign out of the Dyson App, then log into it again and then restart home assistant as soon as you've logged in on the app - should be fine after that.

Thanks for the reply, but still not able to login unfortunately! :(

works for me...what i did: ha_dyson and ha_dyson_cloud are installed but not configured. logged out from my mobile app. log in again after 1 min. then add ha_dyson_cloud and put my email and pass...works. right after this ha_dyson found my dyson.

GitPetri commented 3 years ago

Sign out of the Dyson App, then log into it again and then restart home assistant as soon as you've logged in on the app - should be fine after that.

Worked for me, thanks

arifroni commented 3 years ago

for those who are using ha_dyson, it doesn't support setting angle, right? i cant seem to find that option.

repomanz commented 3 years ago

for those who are using ha_dyson, it doesn't support setting angle, right? i cant seem to find that option.

correct, i could never get this to work or the rotation

3mta3 commented 3 years ago

Sign out of the Dyson App, then log into it again and then restart home assistant as soon as you've logged in on the app - should be fine after that.

@bfayers solid direction, native integration is working(ish) here - oddly, my (unsupported) HP06s are registering, but my HP04s are not - I'll troubleshoot this evening. FWIW this fix didn't initially work for me, although I have been updating various Hass components over the last 24 hours and likely needed to re-update the auth patch (did via docker command).

In any case, I also uninstalled / reinstalled both Hass and Dyson apps on mobile during the process - upon re-installing the Dyson app I had to provide a 2fa email token during initial login (can't remember if that was standard previously), and sure enough the app UI was quite updated. Not sure what version I was on prior, but now 5.0.21060. Thanks again!

aLTeReGo-SWI commented 3 years ago

I guess that now that Dyson has changed something on their end, Dyson Cloud isn't able to login anymore (probably as of yesterday). Hope there's a way to solve this!

For you, and anyone else in the thread trying to use shexn's integration (or the stock one with my library change)

Sign out of the Dyson App, then log into it again and then restart home assistant as soon as you've logged in on the app - should be fine after that.

That was the missing piece of the puzzle! Thank you for sharing. The native (and updated) integration is once again working. Appreciate the assist!

richlawson commented 3 years ago

Last week, the problem was solved by replacing dyson.py by: https://raw.githubusercontent.com/bfayers/libpurecool/auth_customdeps/libpurecool/dyson.py

It stops working today. No success with: pip3 install --upgrade git+https://github.com/bfayers/libpurecool.git@fix_auth

I'm in this same situation as of today when I upgraded to 2021.3.0. The command above worked for me previously.

Sign out of the Dyson App, then log into it again and then restart home assistant as soon as you've logged in on the app - should be fine after that.

I tried logging out of the app, logging back in, and restarting home assistant (twice) as well.

Edit: I'm using the native integration.