Ensure that should_update only triggers in minutes 1-5 and 31-35 past the hour #366
Conversation
This file contains 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
Ensure that should_update only triggers in minutes 1-5 and 31-35 past the hour
Update sensor.py
dgibbs64
added a commit
to dgibbs64/ha-hildebrandglow-dcc
that referenced
this pull request
Apr 4, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Changed should_update trigger to only trigger twice an hour
Motivation and Context
The current code allows triggers twice in six minutes if the sequence is 0,5,10,15...55 at 0,5,30, & 35 minutes past the hour
Fixes issue #361
How Has This Been Tested?
Change the code on my running system and restarted exactly on the hour. Before the change, four runs an hour, afterwards two runs an hour
Checked by reviewing the logs
Types of changes