Throttle Decora wifi updates#156994
Merged
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull Request Overview
This PR adds throttling to the Leviton Decora WiFi integration's update method to reduce excessive API requests to Leviton's servers. The implementation uses the @Throttle decorator with a 30-second minimum interval between update calls, serving as a temporary fix until the integration can be modernized with a config flow and push-based updates.
- Adds 30-second throttle to
update()method to prevent excessive server requests - Imports required
timedeltaandThrottleutilities
| except ValueError: | ||
| _LOGGER.error("Failed to turn off myLeviton switch") | ||
|
|
||
| @Throttle(timedelta(seconds=30)) |
There was a problem hiding this comment.
[nitpick] Consider defining the throttle interval as a module-level constant for better maintainability and consistency with other integrations. This makes the interval easier to find and adjust if needed.
MIN_TIME_BETWEEN_UPDATES = timedelta(seconds=30)
# Then use it in the decorator:
@Throttle(MIN_TIME_BETWEEN_UPDATES)
def update(self) -> None:This pattern is used by most other integrations using the @Throttle decorator (e.g., arest, bbox, dovado, etc.).
edenhaus
approved these changes
Nov 21, 2025
frenck
pushed a commit
that referenced
this pull request
Nov 21, 2025
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Proposed change
Throttle Leviton updates
So Leviton reached out and apparently there are several users who request the Leviton servers way too much. So let's throttle the update method. There are features available for Leviton so it could become a push based integration, but as it's a YAML only integration today and config flows take time, we can use this as a temporary fix to at least decrease the load.
As this is community maintained, I'd love to support people who want to migrate this and make this integration better.
Type of change
Additional information
Checklist
ruff format homeassistant tests)If user exposed functionality or configuration variables are added/changed:
If the code communicates with devices, web services, or third-party tools:
Updated and included derived files by running:
python3 -m script.hassfest.requirements_all.txt.Updated by running
python3 -m script.gen_requirements_all.To help with the load of incoming pull requests: