Emporia has asked me to reduce the number of API requests this integration uses since this and other uses of their unofficial API are causing noticeable strain on their database. See this issue within PyEmVue for specific details magico13/PyEmVue#19. In short, they've asked that the number of API requests be reduced to 2000 requests a day.
To accomplish this the following changes have been made:
- The 1 Second sensor has been completely removed. This was an estimated 80,000+ requests a day and there's no way to keep it under 2k.
- The 1 Minute sensor is unchanged (1440 requests/day)
- The 1 Day and 1 Month sensors now only update hourly instead of each minute (24 requests/day each instead of 1440 each)
- Outlets update every 5 minutes in the background, rather than every 15 seconds (288 requests/day instead of 5760). Outlets will still update status immediately if toggled via Home Assistant.
These changes reduce the number of requests from a worst-case scenario of about 100,000 requests per day to 1,776, leaving just over 200 requests free for toggling of switches and otherwise providing a buffer.
While you can avoid updating for now to keep the older settings, changes to the backing API being deployed by Emporia soon will likely result in older versions of this integration quickly hitting a rate limit and no longer functioning. Additionally, we would like to remain on their good side since they could opt to shut down the API access completely if we keep using excessive resources.
I apologize for any inconvenience this causes or if it results in any automations breaking. These rate and functionality changes will likely be reassessed at a later point, especially if/when Emporia releases a public API with proper documentation and limits. For now we've been asked to keep it under 2k requests per day and this is the best setup I could figure to do that.