As Dyson's somewhat unreliable API servers are queried whenever this library is loaded (eg. at Home Assistant startup), their availability is effectively on the critical path of a successful server restart. (They aren't working for me right now: Cloudflare says the backend servers are currently unavailable. I am going to try again later but it got me thinking about how to ameliorate this situation.)
#14 (comment) mentioned that a list of devices is downloaded via the Dyson API, then the library subsequently connects to devices locally via MQTT. Would it be possible to cache/save that list of devices locally, to be used when the Dyson API is not available? It would greatly reduce the need for Dyson's API servers to be available at library startup.
As Dyson's somewhat unreliable API servers are queried whenever this library is loaded (eg. at Home Assistant startup), their availability is effectively on the critical path of a successful server restart. (They aren't working for me right now: Cloudflare says the backend servers are currently unavailable. I am going to try again later but it got me thinking about how to ameliorate this situation.)
#14 (comment) mentioned that a list of devices is downloaded via the Dyson API, then the library subsequently connects to devices locally via MQTT. Would it be possible to cache/save that list of devices locally, to be used when the Dyson API is not available? It would greatly reduce the need for Dyson's API servers to be available at library startup.