Add 'for' duration to lovelace state visibility condition, and add 'not' lovelace visibility condition #26094
+160
−5
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
This is an alternative implementation of this PR: #25864.
In that PR, I added a new condition called 'Last Entity Change', which would allow the user to specify a 'within' and 'after' duration, which would show a card based on the last changed time of an entity (either 'within' a certain duration since a change; or 'after' some duration since a change).
Thanks to the comments of @karwosts , they suggested this could be implemented to more closely follow how the automation interface works.
To do this, this PR adds a 'For' duration to the State visibility condition, and adds a 'Not' condition. The 'Not' condition is required to replicate the behavior of the 'within' duration in the previous PR.
Type of change
Example configuration
Additional information
Demo:

Checklist
Some help with letting me know where to add tests would be much appreciated :)
If user exposed functionality or configuration variables are added/changed: