feat(experimental): add force_update
as experimental setting in YAML conf
#85
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.
Related Issues
n/a
Proposed Changes:
This change introduces the concept of having experimental settings in the YAML configuration. YAML configurations are not meant to be used by integrations, which should use always the configuration flow.
In that case, we use a not suggested method to provide settings we don't want to expose easily to end users. In this way we can ship settings we can add/remove/break based on the need.
With this change you can force HA to update sensors data even if previous/actual states are the same.
Testing:
Update your
configuration.yaml
with the following code:Extra Notes (optional):
n/a
Checklist