Merge branch 'next' into rc

This commit is contained in:
Franck Nijhof 2020-10-21 21:16:43 +02:00
commit 8a5f870e4d
No known key found for this signature in database
GPG Key ID: D62583BA8AB11CA3
8 changed files with 93 additions and 52 deletions

View File

@ -7,7 +7,9 @@ ha_release: 0.74
ha_iot_class: Cloud Push ha_iot_class: Cloud Push
ha_codeowners: ha_codeowners:
- '@ludeeus' - '@ludeeus'
- '@ctalkington'
ha_domain: cloudflare ha_domain: cloudflare
ha_config_flow: true
--- ---
With the `cloudflare` integration, you can keep your Cloudflare records up to date. With the `cloudflare` integration, you can keep your Cloudflare records up to date.
@ -26,43 +28,25 @@ Due to a limitation in the Cloudflare API, you can not use this integration with
</div> </div>
## Setup ## Requirements
You can find your global API key in your Cloudflare account settings. <div class='note warning'>
On older versions of Home Assistant, this integration used the account email and Global API Key to authenticate.
As of Home Assistant 0.117, API Tokens are now used to authenticate.
</div>
Setup requires an API Token created with Zone:Zone:Read and Zone:DNS:Edit permissions for all zones in your account.
An easy way to create this is to start with the "Edit zone DNS" template then add Zone:Zone:Read to the permissions.
[Cloudflare API Tokens Guide](https://developers.cloudflare.com/api/tokens/create)
## Configuration ## Configuration
To use the integration in your installation, add the following to your `configuration.yaml` file: Go to the integrations page in your configuration and click on new integration -> Cloudflare.
```yaml
# Example configuration.yaml entry
cloudflare:
email: YOUR_EMAIL_ADDRESS
api_key: YOUR_GLOBAL_API_KEY
zone: EXAMPLE.COM
records:
- ha
- www
```
{% configuration cloudflare %}
email:
description: The email address for your Cloudflare account.
required: true
type: string
api_key:
description: The global API key for your Cloudflare account.
required: true
type: string
zone:
description: The DNS zone (domain) you want to update.
required: true
type: string
records:
description: A list of records (subdomains) you want to update.
required: true
type: list
{% endconfiguration %}
## Additional information ## Additional information
@ -70,10 +54,6 @@ records:
This platform uses the API from [ipify.org](https://www.ipify.org/) to set the public IP address. This platform uses the API from [ipify.org](https://www.ipify.org/) to set the public IP address.
### API Key
Please note that the `api_key` is the [global API key](https://support.cloudflare.com/hc/en-us/articles/200167836-Managing-API-Tokens-and-Keys#12345682) of your Cloudflare account (not the API Token).
### Home Assistant Companion App ### Home Assistant Companion App
If you would like to use [iOS App](https://companion.home-assistant.io/) via Cloudflare set **Minimum TLS version as 1.2**, in order to do that, do the following: If you would like to use [iOS App](https://companion.home-assistant.io/) via Cloudflare set **Minimum TLS version as 1.2**, in order to do that, do the following:
@ -89,20 +69,6 @@ Other settings should not cause any issues.
For SSH usage (according to [this](https://blog.cloudflare.com/cloudflare-now-supporting-more-ports/) source), you need to connect directly to your server (bypassing Cloudflare). To do that, create a `CNAME` DNS record, e.g., `ssh.example.com`, with proxy status as "DNS only" (to do that click on orange icon, it will change color to gray) and then connect to `ssh.example.com` using your server SSH port. For SSH usage (according to [this](https://blog.cloudflare.com/cloudflare-now-supporting-more-ports/) source), you need to connect directly to your server (bypassing Cloudflare). To do that, create a `CNAME` DNS record, e.g., `ssh.example.com`, with proxy status as "DNS only" (to do that click on orange icon, it will change color to gray) and then connect to `ssh.example.com` using your server SSH port.
### Using Cloudflare domain only for Home Assistant
If you want to update just a main domain, place in the records list only your domain, e.g., `example.com`. It will update your `A` DNS record with your IP every hour.
```yaml
# Example configuration.yaml entry for one domain
cloudflare:
email: YOUR_EMAIL_ADDRESS
api_key: YOUR_GLOBAL_API_KEY
zone: EXAMPLE.COM
records:
- EXAMPLE.COM
```
#### The minimum DNS record settings (if you have set up HTTPS already) #### The minimum DNS record settings (if you have set up HTTPS already)
To redirect from your domain to the IP address of your Home Assistant server set this DNS record: To redirect from your domain to the IP address of your Home Assistant server set this DNS record:

View File

@ -10,7 +10,7 @@ ha_codeowners:
ha_domain: nissan_leaf ha_domain: nissan_leaf
--- ---
The `nissan_leaf` integration offers integration with the [NissanConnect EV](https://youplus.nissan.co.uk/GB/en/YouPlus/ConnectedServices.html) cloud service. NissanConnect EV was previously known as Nissan Carwings. It offers: The `nissan_leaf` integration offers integration with the [NissanConnect EV](https://www.nissan.co.uk/dashboard.html) cloud service. NissanConnect EV was previously known as Nissan Carwings. It offers:
* sensors for the battery status, range and charging status * sensors for the battery status, range and charging status
* a switch to start and stop the climate control * a switch to start and stop the climate control

View File

@ -8,6 +8,7 @@ ha_quality_scale: internal
ha_codeowners: ha_codeowners:
- '@home-assistant/frontend' - '@home-assistant/frontend'
ha_domain: panel_custom ha_domain: panel_custom
ha_iot_class: ~
--- ---
The `panel_custom` support allows you to add additional panels to your Home Assistant frontend. The panels are listed in the sidebar if wished and can be highly customized. See the developer documentation on [instructions how to build your own panels](https://developers.home-assistant.io/docs/frontend/custom-ui/creating-custom-panels/). The `panel_custom` support allows you to add additional panels to your Home Assistant frontend. The panels are listed in the sidebar if wished and can be highly customized. See the developer documentation on [instructions how to build your own panels](https://developers.home-assistant.io/docs/frontend/custom-ui/creating-custom-panels/).

View File

@ -0,0 +1,74 @@
---
title: "Supervisor 249: Resolution center, Stability & Private container registries"
description: "Resolution center, Stability & Private container registries"
date: 2020-10-21 00:00:00
date_formatted: "October 21, 2020"
comments: true
author: Joakim Sørensen
author_twitter: ludeeus
categories: Release-Notes
og_image: /images/blog/2020-10-21-supervisor-249/social.png
---
_The Supervisor is shipped with our Home Assistant Operating System and controls all hardware and software on your device. Bringing an effortless experience in managing, upgrading, and maintaining your Home Assistant instance via the user interface. It is what allows you to focus on what really matters; automating your home._
The Supervisor generally does not have enough changes that we can fill a blogpost with each release, it also does not have a fixed release schedule. A new Supervisor update is released when it's needed, but that does not mean that there is nothing going on in this part of the ecosystem! One month ago, we put out the [The Supervisor joins the party][supervisor-joins-the-party] post that went over the highlights from the past year. Now its time for version 249, rolling out to everyone as we speak and its full of new goodies, enjoy!
## Resolution center
We are introducing a new resolution center. This new feature will be used to identify issues and provide context and suggestions on solving your installation issues. We have big plans for this one!
New in this release is that if the available free space on your device drops below 1 GB, auto-updates will be paused and you will be notified. This should give you time to clean it up.
To help you free up some space, we have added a [new page to our documentation][more-info_free-space] to help guide you through that.
If you run Home Assistant Supervised, the system can get marked as unsupported if the host system does not have all the [required services running][required_services]. It was hard to find the reason why a system is marked as unsupported. It is written to the logs during startup, but the logs that you find in the UI do not go back that far. To make it more accessible, the message that your system is unsupported will now allow you to open a new dialog.
![unsupported dialog](/images/blog/2020-10-21-supervisor-249/unsupported_dialog.png)
This dialog will list all the reasons why the system is marked as unsupported. Clicking on the links in that dialog will take you to a documentation page that describes the issue, and there will be a solution you can use to make your installation compliant with [ADR-0014] and [ADR-0015].
## Stability
Stability is something that is always in focus for new Supervisor releases. The Supervisor is the central part of your Home Assistant OS/Supervised installation. Almost every release has some form of stability improvement, and this is not an exception to that.
If Home Assistant fails to start, we will now rebuild the container. This will ensure that a new fresh container is started up if something inside the container has been corrupted. We have also added this feature to our newly added [observer plugin][supervisor-joins-the-party-observer].
All auto-updates will be automatically paused if your system is running low on free space. Manual updates are still allowed, but now we will not fill up that space automatically, which in some rare cases could lead to startup issues.
Weve also added a new check when adding add-on repositories to make sure that its actually an add-on repository. This should help avoid confusion.
## Landing page
Weve updated the landing page that you see when youre installing Home Assistant. We added logs to it, so you can follow along with what's happening while you are waiting.
And there is more! Our mobile apps are now able to discover the landing page. This means that you can discover a new installation while its initializing and already start onboarding in the mobile app.
![landingpage](/images/blog/2020-10-21-supervisor-249/landingpage.png)
## Private container registries
Thanks to [@skateman][skateman], you can now use private (password protected) container registries in the Supervisor. This allows you to use add-ons and other containers that require you to log in to a container registry to install it.
![private registry](/images/blog/2020-10-21-supervisor-249/private_registry.png)
You can find this in the store tab of the Supervisor panel, by clicking the three dots in the top right corner. This option is only available if advanced-mode is enabled.
## Stricter Network Manager check
With this version more checks have been added to ensure that Network Manager is not only enabled on the system but that it also manages at least one network interface. If you are running our Home Assistant OS, this does not apply to you.
This stricter check allows us to provide a stable way for the Supervisor and for add-on developers to get the IP Address of the host.
The system will be marked as unsupported if Network Manager does not manage at least one network interface on your system. Weve added a [new page in our documentation][unsupported_network_manager] that will help you get it fixed.
[ADR-0014]: https://github.com/home-assistant/architecture/blob/master/adr/0014-home-assistant-supervised.md
[ADR-0015]: https://github.com/home-assistant/architecture/blob/master/adr/0015-home-assistant-os.md
[go]: https://golang.org/
[more-info_free-space]: /more-info/free-space
[persistent_notification]: /integrations/persistent_notification/
[skateman]: https://github.com/skateman
[supervisor-joins-the-party-observer]: /blog/2020/09/16/supervisor-joins-the-party#observer-plugin
[supervisor-joins-the-party]: /blog/2020/09/16/supervisor-joins-the-party
[unsupported_network_manager]: /more-info/unsupported/network_manager
[required_services]: https://github.com/home-assistant/architecture/blob/master/adr/0014-home-assistant-supervised.md#supported-operating-system-system-dependencies-and-versions

Binary file not shown.

After

Width:  |  Height:  |  Size: 58 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 17 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 80 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 27 KiB