You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
I've been thinking about adding some sort of cache for the dyson API calls for quite some time now. It should be trivial to add and will prevent a lot of the issues. I'll have a go at it when I can find some free time.
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.
The text was updated successfully, but these errors were encountered: