Closed homekitter closed 4 years ago
I think dyson may have changed the name of their api server…
Tried resolving api.cp.dyson.com elsewhere without success.
Took a look at my pi-hole instance after opening the app and saw an entry for a1u2wvl3e2lrc4-ats.iot.eu-west-1.amazonaws.com
Dyson app on my phone updated on Sept 3. They may have decommissioned old api server?
It seems that 'api.cp.dyson.com' is back…
Am now getting new errors…
Our Cli: $ hassio help ➜ ~ cd config ➜ config grep -i dyson home-assistant.log 2019-09-15 09:21:52 INFO (MainThread) [homeassistant.setup] Setting up dyson 2019-09-15 09:21:52 INFO (SyncWorker_3) [homeassistant.components.dyson] Creating new Dyson component 2019-09-15 09:21:53 ERROR (SyncWorker_3) [homeassistant.components.dyson] Not connected to Dyson account. Unable to add devices 2019-09-15 09:21:54 INFO (MainThread) [homeassistant.setup] Setup of domain dyson took 1.6 seconds. 2019-09-15 09:21:54 ERROR (MainThread) [homeassistant.setup] Setup failed for dyson: Integration failed to initialize. ➜ config
Same issue here. It is still working in the app though.
I checked within the libpurecool
code and when I'm issuing the same request as here, it returns with the proper message:
curl -X POST -H "Content-Type: application/json" -k \
'https://api.cp.dyson.com/v1/userregistration/authenticate?country=FR' \
-d '{"Email": "xxx@zzz.com", "Password": "SuperPassword"}'
Returns:
{"Account":"xxxxxx","Password":"yyyyyyy"}
Don't quite understand what is happening...
I tried multiple times with a wrong request and now I'm receiving 503 Service Unavailable
(My public IP seems banned... Hopefully it's only temporary). With a new IP it works again.
Also some kind of rate limiting seems to be in place (don't know if it was the case before or not)
Seemingly self corrected a moment ago.
I think actually their service is crashing in the backend as it randomly works/doesn't work anymore using curl
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
Home Assistant release with the issue: Home Assistant 0.98.5
Last working Home Assistant release (if known): Home Assistant 0.98.5 (Unchanged)
Operating environment (Hass.io/Docker/Windows/etc.): Hass.io
Component/platform: Dyson
Description of problem: Error during setup of component dyson
Problem-relevant
configuration.yaml
entries and (fill out even if it seems unimportant): From: configuration.yamlFrom: dyson.yaml
From: secrets.yaml
Traceback (if applicable):
Additional information: