Hi, I faced the same issue with not able to locate the Dyaon.
I have copied all the files into a new ‘dyson’ directory… however, I’m not familiar with custom components setup, would you kindly advice what need to be changed at the configuration.yaml file in order to kick in the custom component ?
I have just encountered this problem. For 2 days now i can’t connect to my DYSON fan anymore. I used to just restart HA and it will connect after a few tries. Has anyone else encountered this? and does anyone have a fix?
I’ve tried doing the custom components as well but nothing works.
I have attached the dyson part of my config file and removed the USER and PASS
dyson:
username: USER
password: PASS
language: US
timeout: 5 # optional
retry: 1 # optional
devices: # Optional, only if discovery is not working
- device_id: “YN5-XG-KDA0077A”
device_ip: “172.16.247.48”
I came here looking to see if there was a problem as I have just recently got a new Dyson fan and was looking to get it working. I’m getting the same results:
2020-08-07 13:32:39 INFO (SyncWorker_2) [homeassistant.components.dyson] Creating new Dyson component
2020-08-07 13:32:39 DEBUG (SyncWorker_2) [libpurecool.dyson] Disabling insecure request warnings since dyson are using a self signed certificate.
2020-08-07 13:32:39 ERROR (SyncWorker_2) [homeassistant.components.dyson] Not connected to Dyson account. Unable to add devices
2020-08-07 13:32:41 INFO (MainThread) [homeassistant.setup] Setup of domain dyson took 2.1 seconds
2020-08-07 13:32:41 ERROR (MainThread) [homeassistant.setup] Setup failed for dyson: Integration failed to initialize.
I wonder if they have changed the address again like the previous error was. The dyson ios app is working fine.
I just replaced the original file in the python library with the updated one using the find command to see where it was for me. I’m guessing that’s not permanent as the Docker container will presumably get re written on the next update, but it helped prove what was wrong and that a fix exists.
Funny thing is, mine was working fine until i had to restart for something different. Seems like as long as you had a connection you were ok. Now just need to wait.