Add support for last_changed / last_updated in start_time and improved duration calculation#233
Open
studiobts wants to merge 1 commit intorianadon:mainfrom
Open
Conversation
…d calculation of duration with start_time and remain_time
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 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.
This PR introduces two new features:
Support for last_changed and last_updated properties
start_time can now be set to use the entity’s last_changed or last_updated directly.
Example:
Automatic duration calculation
When both start_time and remain_time are available, the card now computes the duration automatically.
The calculation has a margin of error of about one second due to approximation, but it is sufficient for most use cases.
Use case:
I manage several electric valves (switches) that expose only the remaining time before they close.
Thanks to this change, I no longer need to create helper entities. I can simply use the last_changed timestamp of the switch as the start_time, while relying on the existing remain_time attribute to infer the total duration.