Updater component is always available and shows on/off depending on whether an update is available or not#25418
Conversation
|
Hi @Santobert, It seems you haven't yet signed a CLA. Please do so here. Once you do that we will be able to review and accept this pull request. Thanks! |
|
Hey there @home-assistant/core, mind taking a look at this pull request as its been labeled with a integration ( This is a automatic comment generated by codeowners-mention to help ensure issues and pull requests are seen by the right people. |
|
Please give me feedback if this change is acceptable. If so, I will update the documentation as soon as possible. |
|
Please don't hold off creating a documentation PR, it slows down all progress, since merging without docs is a no go to being with. Adding |
|
The documentation now is up to date: home-assistant/home-assistant.io#9957 |
|
The docs-missing label can be removed. I've added the docs here: home-assistant/home-assistant.io#9957 |
|
I guess there is something wrong with the CI? These errors are import errors and they have nothing to do with my changes. |
This reverts commit 3f896a4.
@MartinHjelmare I'm afraid we have to test the remove method since we miss the coverage target by 0.12% 😆 Can we call that method directly or do we have to trigger hass to remove the component? |
|
Thank you @MartinHjelmare for all your help. I wouldn't have been able to do this without you. Is it possible to merge this into the upcoming version 0.97.0 or do we have to wait for 0.97.1? |
|
I think we should wait until 0.98 since it's a new feature and a breaking change. |
|
Please update the breaking change paragraph in the PR description with what the user needs to do to cope with the breaking change. Ie how to handle the change of entity domain for the updater entity. |
Done |
|
@balloob ok to merge? |
Breaking Change:
The updater component is now a binary sensor that is always available. The entity ID is
binary_sensor.updater. The state is on/off depending on whether an update is available or not. The latest version as well as the release notes are attributes of this binary sensor.Automations that are listening for the existence of
updater.updatershould now trigger whenbinary_sensor.updaterchanges toon.This makes the component more transparent and understandable for the user. Additionally it is visible if there is an error or the source (https://updater.home-assistant.io/) is outdated.
Description:
See Breaking Change.
Furthermore the updater logs a warning if the current version is before the newest version. This is the case if the JSON from https://updater.home-assistant.io/ is outdated.
If you don't want the updater component to always be available, I suggest at least keeping the warning if the current version is greater than the newest version. Otherwise, people would wonder if the updater component is broken.
But personally, I think it would be more understandable if the updater component is always visible and displays the newest version. Automations can be triggered by the state and not by the existence of this component.
Related issue (if applicable): fixes #24385
Pull request with documentation for home-assistant.io (if applicable): home-assistant/home-assistant.io#9957
Example entry for
configuration.yaml(if applicable):No changes
Checklist:
tox. Your PR cannot be merged unless tests passIf user exposed functionality or configuration variables are added/changed:
If the code does not interact with devices: