Added note about updates for Hass.io users. #3348
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Hass.io users end up on this page when an update is available, but then can't see what they have to do. This is because of the the updater component and the inevitable delay in updates getting into the hass.io build. This update informs users about an updates transition from HA into Hass.io, how to install it, and suggests disabling the updater component to alleviate 'notification stress'.
|
@mikegchambers, thanks for your PR! By analyzing the history of the files in this pull request, we identified @fabaff, @yasinS and @Joeboyc2 to be potential reviewers. |
fabaff
requested changes
Sep 11, 2017
| @@ -14,6 +14,10 @@ redirect_from: /getting-started/updating/ | |||
| The upgrade process differs depending on the installation you have, so please review the documentation that is specific to your install [HASSbian](/docs/hassbian/common-tasks/#update-home-assistant), [Raspberry Pi All-In-One Installer](/docs/installation/raspberry-pi-all-in-one/#upgrading), [Vagrant](/docs/installation/vagrant/), or [Virtualenv](/docs/installation/virtualenv/#upgrading-home-assistant). | |||
| </p> | |||
|
|
|||
| <p class='note warning'> | |||
| Hass.io users can update Home Assistant via the ‘Hass.io' page in the UI. However please note that Home Assistant updates take time to roll into the Hass.io builds. Therefore there is often a slight delay between the availability of a Home Assistant update and an update being available in Hass.io, be patient. When a Hass.io update is available it will be shown as available on the ‘Hass.io' page in your UI. If you would prefer not to be notified of the general updates in the UI you can disable the ‘updater’ component in your configuration. | |||
| </p> | |||
There was a problem hiding this comment.
A link in the above note to the Hass.io details is enough. With #3349 the same content is placed in three sections.
|
Closing this PR in favour of #3349 which serve the same purpose. However I think we need a link to Hassio at the top of this page. I will add a PR for that. Thanks. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description:
Hass.io users end up on this page when an update is available, but then can't see what they have to do. This is because of the the updater component and the inevitable delay in updates getting into the hass.io build.
This update informs users about an updates transition from HA into Hass.io, how to install it, and suggests disabling the updater component to alleviate 'notification stress'.