Refresh now() templates on second=0#42225
Conversation
bdraco
left a comment
There was a problem hiding this comment.
Tested and working as expected. Thanks 👍
I'll get a frontend PR going since the phrasing will need to be updated.
|
Updated documentation: home-assistant/home-assistant.io#15360 |
Nice. I forgot to actually put in the PR 🤦 when updating #41147. I'll check my local branch that is still useful and see if there is anything as soon as I have a free moment. |
|
I updated the breaking change section in #41147 |
|
The 0.117 release blogpost claims,
But there are no recommendations or links on how to do that. ☹ |
This comment has been minimized.
This comment has been minimized.
|
@acshef We don't know what to recommend because we have no examples where this would be needed. It will in any case depend on the template, there is no recipe. As it is really a support question please ask in the forum – but feel free to tag me and I will have a look. |
Breaking change
Proposed change
Beta feedback on #41147 is that it would be better if
now()causes templates to refresh when the minute changes. This will be more useful for example for comparisons with input_datetime and it is also easier to debug things when you know when to expect the change.Type of change
Example entry for
configuration.yaml:# Example configuration.yamlAdditional information
Checklist
black --fast 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..coveragerc.The integration reached or maintains the following Integration Quality Scale:
To help with the load of incoming pull requests: