home-assistant / home-assistant/developers.home-assistant
Force update clarification on attributes
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 483
- Forks
- 1.2k
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 44
Description
I’m not completely sure what “each update” means here.
For example:
I have an entity that updates its state at regular intervals (say, once per hour).
This entity also has attributes that may update independently of the main state.
So If I enable force_update:
- Every scheduled state update generates a new state change event, even when the new state value is the same as the old one. This is clear, but
- If an attribute changes between two state updates, does the attribute change also trigger a state change event because of force_update, or is "force update" only tied to the state value itself?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read docs/core/entity.md at the referenced line and review the wording around “each update” and force_update. Clarify whether attribute-only changes trigger a state change event, and consider the work done when the documentation answers that case explicitly.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100