diff --git a/_config.yml b/_config.yml index 1bd28a1cfef..911082b60aa 100644 --- a/_config.yml +++ b/_config.yml @@ -101,8 +101,8 @@ social: # Home Assistant release details current_major_version: 0 current_minor_version: 112 -current_patch_version: 4 -date_released: 2020-07-08 +current_patch_version: 5 +date_released: 2020-07-13 # Either # or the anchor link to latest release notes in the blog post. # Must be prefixed with a # and have double quotes around it. diff --git a/source/_cookbook/configuration_yaml_by_klaasnicolaas.markdown b/source/_cookbook/configuration_yaml_by_klaasnicolaas.markdown index 8b2d621cbda..51517847973 100644 --- a/source/_cookbook/configuration_yaml_by_klaasnicolaas.markdown +++ b/source/_cookbook/configuration_yaml_by_klaasnicolaas.markdown @@ -2,5 +2,5 @@ title: "Configuration.yaml by klaasnicolaas" description: "" ha_category: Example configuration.yaml -ha_external_link: https://github.com/klaasnicolaas/Smarthome-homeassistant-config +ha_external_link: https://github.com/klaasnicolaas/Student-homeassistant-config --- diff --git a/source/_docs/authentication.markdown b/source/_docs/authentication.markdown index 81ae30d9e97..11007d29d9e 100644 --- a/source/_docs/authentication.markdown +++ b/source/_docs/authentication.markdown @@ -24,15 +24,13 @@ For the moment, other user accounts will have the same access as the owner accou ### Your Account Profile -Once you're logged in, you can see the details of your account at the _Profile_ page by clicking on the circular badge next to the Home Assistant title in the sidebar. +Once you're logged in, you can see the details of your account at the _Profile_ page by clicking on the circular at the very bottom of the sidebar. Screenshot of the profile page You can: -* Change the language you prefer Home Assistant to use. -* Change your password. -* Select the [theme](/integrations/frontend/#defining-themes) for the interface of Home Assistant. +* Change your password. * Enable or disable [multi-factor authentication](/docs/authentication/multi-factor-auth/). * Delete _Refresh Tokens_. These are created when you log in from a device. Delete them if you want to force the device to log out. * Create [Long Lived Access Tokens](https://developers.home-assistant.io/docs/en/auth_api.html#long-lived-access-token) so scripts can securely interact with Home Assistant. diff --git a/source/_docs/authentication/providers.markdown b/source/_docs/authentication/providers.markdown index 0e825b19cda..b5c87c35541 100644 --- a/source/_docs/authentication/providers.markdown +++ b/source/_docs/authentication/providers.markdown @@ -22,6 +22,8 @@ However, this feature is deprecated and will be removed in a future release so y Home Assistant automatically configures the standard auth providers so you don't need to specify `auth_providers` in your `configuration.yaml` file unless you are configuring more than one. Specifying `auth_providers` will disable all auth providers that are not listed, so you could reduce your security or create difficulties logging in if it is not configured correctly. +This means that if you decide to use `trusted_networks` as your `auth_provider` there won't be a way to authenticate for a device outside of your listed trusted network. To overcome this ensure you add the default `auth_provider``type: homeassistant` back in manually. This will then present you with the default auth login screen when trusted network authentication fails as expected from outside your LAN. + Authentication providers are configured in your `configuration.yaml` under the `homeassistant:` block. You can supply more than one, for example: diff --git a/source/_docs/tools/dev-tools.markdown b/source/_docs/tools/dev-tools.markdown index d4460c61676..0272cf0c820 100644 --- a/source/_docs/tools/dev-tools.markdown +++ b/source/_docs/tools/dev-tools.markdown @@ -84,9 +84,3 @@ It has two sections, code goes on the left hand side, and the output is shown on It is a good practice to test the template code in the template editor prior to putting it in automations and scripts. For more information about jinja2, visit [jinja2 documentation](http://jinja.pocoo.org/docs/dev/templates/), and also read templating document [here](/topics/templating/) - -## MQTT - -This section is only visible if the MQTT integration is configured. To configure MQTT, add `mqtt:` to the `configuration.yaml` file. For more information, refer to the [MQTT](/integrations/mqtt/) integration. - -Even though MQTT in general provides deeper functionality, the developer tools section of MQTT is limited to publishing messages to a given topic. It supports templates for the payload. To publish a message, simply specify the topic name and the payload and click “PUBLISH” button. diff --git a/source/_integrations/calendar.google.markdown b/source/_integrations/calendar.google.markdown index 68e8f3ac39b..0f2eccd32a7 100644 --- a/source/_integrations/calendar.google.markdown +++ b/source/_integrations/calendar.google.markdown @@ -39,6 +39,12 @@ Generate a Client ID and Client Secret on If you will later be adding more scopes than just the "Google Calendar API" to the OAuth for this application, you will need to delete your token file under your Home Assistant Profile. You will lose your refresh token due to the re-authenticating to add more API access. It's recommended to use different authorizations for different pieces of Google. +## Troubleshooting + +If you are trying to switch to a new Google account then you would run into the following error message. Make sure to delete the existing **.google.token** file from your `config` folder and restart Home Assistant to try again. + +'oauth2client.client.HttpAccessTokenRefreshError: deleted_client: The OAuth client was deleted' + ## Configuration To integrate Google Calendar in Home Assistant, diff --git a/source/_integrations/demo.markdown b/source/_integrations/demo.markdown index 86c86f09cd9..714074607ce 100644 --- a/source/_integrations/demo.markdown +++ b/source/_integrations/demo.markdown @@ -22,6 +22,7 @@ Available demo platforms: - [Cover](/integrations/cover/) (`cover`) - [Fan](/integrations/fan/) (`fan`) - [Geolocation](/integrations/geo_location/) (`geo_location`) +- [Humidifier](/integrations/humidifier/) (`humidifier`) - [Image Processing](/integrations/image_processing/) (`image_processing`) - [Light](/integrations/light/) (`light`) - [Lock](/integrations/lock/) (`lock`) diff --git a/source/_integrations/plum_lightpad.markdown b/source/_integrations/plum_lightpad.markdown index ae8ece3a7fe..8a211f47ebf 100644 --- a/source/_integrations/plum_lightpad.markdown +++ b/source/_integrations/plum_lightpad.markdown @@ -4,10 +4,12 @@ description: Instructions on setting up Plum Lightpads within Home Assistant. ha_category: - Switch ha_iot_class: Local Push +ha_config_flow: true ha_release: 0.85 ha_domain: plum_lightpad ha_codeowners: - '@ColinHarrington' + - '@prystupa' --- Configurable/Dimmable Wi-Fi Lightswitch @@ -20,7 +22,14 @@ Configurable/Dimmable Wi-Fi Lightswitch ## Configuration -To enable Plum Lightpad support, add the following lines to your `configuration.yaml` file: +To use Plum Lightpad devices in your installation, add your Plum account from the integrations page. + +Menu: **Configuration** -> **Integrations**. + +Click on the `+` sign to add an integration and click on **Plum Lightpad** (use typeahead if necessary). +After completing the configuration flow, the Plum Lightpad integration will be available. + +Alternatively, add the following lines to your `configuration.yaml` file: ```yaml # Example configuration.yaml entry diff --git a/source/_lovelace/humidifier.markdown b/source/_lovelace/humidifier.markdown new file mode 100644 index 00000000000..ce853fbfc8f --- /dev/null +++ b/source/_lovelace/humidifier.markdown @@ -0,0 +1,40 @@ +--- +title: "Humidifier Card" +sidebar_label: Humidifier +description: "The Humidifier card gives control of your humidifier entity, allowing you to change the target humidity and mode of the entity." +--- + +The Humidifier card lets you control and monitor humidifiers, dehumidifiers, and hygrostat devices. + +

+ Screenshot of the humidifier card + Screenshot of the humidifier card. +

+ +{% configuration %} +type: + required: true + description: humidifier + type: string +entity: + required: true + description: Entity id of `humidifier` domain + type: string +name: + required: false + description: Name of Entity + type: string + default: Entity Name +theme: + required: false + description: Set to any theme within `themes.yaml` + type: string +{% endconfiguration %} + +## Example + +```yaml +- type: humidifier + entity: humidifier.bedroom + name: Bedroom Humidifier +``` diff --git a/source/_posts/2020-07-01-release-112.markdown b/source/_posts/2020-07-01-release-112.markdown index 9111768edb9..8911de6ef74 100644 --- a/source/_posts/2020-07-01-release-112.markdown +++ b/source/_posts/2020-07-01-release-112.markdown @@ -765,6 +765,44 @@ The integrations below have been removed: [wake_on_lan docs]: /integrations/wake_on_lan/ [withings docs]: /integrations/withings/ +## Release 0.112.5 - July 14 + +- Smappee dependency update ([@bsmappee] - [#37680]) ([smappee docs]) +- Properly set update_interval during Speedtest setup ([@engrbm87] - [#37708]) ([speedtestdotnet docs]) +- Support multiple MQTT availability topics ([@emontnemery] - [#37418]) ([mqtt docs]) +- Tweak MQTT availability ([@emontnemery] - [#37719]) ([mqtt docs]) +- Fix MQTT availability startup race ([@emontnemery] - [#37718]) ([mqtt docs]) +- Fix homekit_controller discovery via zeroconf ([@bdraco] - [#37725]) ([zeroconf docs]) +- Add support for the DataUpdateCoordinator to not automatically update ([@rohankapoorcom] - [#37734]) +- Bump blinkpy version to fix connection errors ([@fronzbot] - [#37755]) ([blink docs]) +- UniFi - Handle session expiration ([@Kane610] - [#37782]) ([unifi docs]) +- deCONZ - don't let light "attr" events update group data ([@Kane610] - [#37797]) ([deconz docs]) + +[#37418]: https://github.com/home-assistant/core/pull/37418 +[#37680]: https://github.com/home-assistant/core/pull/37680 +[#37708]: https://github.com/home-assistant/core/pull/37708 +[#37718]: https://github.com/home-assistant/core/pull/37718 +[#37719]: https://github.com/home-assistant/core/pull/37719 +[#37725]: https://github.com/home-assistant/core/pull/37725 +[#37734]: https://github.com/home-assistant/core/pull/37734 +[#37755]: https://github.com/home-assistant/core/pull/37755 +[#37782]: https://github.com/home-assistant/core/pull/37782 +[#37797]: https://github.com/home-assistant/core/pull/37797 +[@Kane610]: https://github.com/Kane610 +[@bdraco]: https://github.com/bdraco +[@bsmappee]: https://github.com/bsmappee +[@emontnemery]: https://github.com/emontnemery +[@engrbm87]: https://github.com/engrbm87 +[@fronzbot]: https://github.com/fronzbot +[@rohankapoorcom]: https://github.com/rohankapoorcom +[blink docs]: /integrations/blink/ +[deconz docs]: /integrations/deconz/ +[mqtt docs]: /integrations/mqtt/ +[smappee docs]: /integrations/smappee/ +[speedtestdotnet docs]: /integrations/speedtestdotnet/ +[unifi docs]: /integrations/unifi/ +[zeroconf docs]: /integrations/zeroconf/ + ## All changes
diff --git a/source/getting-started/presence-detection.markdown b/source/getting-started/presence-detection.markdown index 21eb5c2502c..24243b20192 100644 --- a/source/getting-started/presence-detection.markdown +++ b/source/getting-started/presence-detection.markdown @@ -26,7 +26,7 @@ During the setup of Home Assistant Companion on your mobile device, the app will -Zones allow you to name areas on a map. These areas can then be used to name the location a tracked user is, or use entering/leaving a zone as an automation [trigger] or [condition]. Zones can be set up from the integration page in the configurations screen. +Zones allow you to name areas on a map. These areas can then be used to name the location a tracked user is, or use entering/leaving a zone as an automation [trigger] or [condition]. Zones can be set up from configuration screen.
The map view will hide all devices that are home. diff --git a/source/help/reporting_issues.markdown b/source/help/reporting_issues.markdown index 893ea9db372..9c2aa22eb1b 100644 --- a/source/help/reporting_issues.markdown +++ b/source/help/reporting_issues.markdown @@ -8,7 +8,7 @@ If you have an installation, a setup or a configuration issue please use our [Fo If you found a bug then please report it in one of our [trackers](/help/#bugs-feature-requests-and-alike). To help you and our developers to identify the issue quickly, please fill out the provided template. The "weird" content you will see is there to render your entry in a nice format after submitting. It's just [markdown](https://guides.github.com/features/mastering-markdown/). -Please refer to the **Info** page, which is accessible in the **Developer tools** in the Home Assistant frontend. +Please refer to the **Info** page, which is accessible inside the **Configuration** panel in the Home Assistant frontend. ## First Home Assistant release with the issue diff --git a/source/images/docs/authentication/profile.png b/source/images/docs/authentication/profile.png index 10a445c8a6f..a6b88e17cbc 100644 Binary files a/source/images/docs/authentication/profile.png and b/source/images/docs/authentication/profile.png differ diff --git a/source/images/lovelace/lovelace_humidifier_card.png b/source/images/lovelace/lovelace_humidifier_card.png new file mode 100644 index 00000000000..0e04a2acea7 Binary files /dev/null and b/source/images/lovelace/lovelace_humidifier_card.png differ diff --git a/source/lovelace/index.markdown b/source/lovelace/index.markdown index 43981cc24cb..cc62afd0879 100644 --- a/source/lovelace/index.markdown +++ b/source/lovelace/index.markdown @@ -7,7 +7,7 @@ redirect_from: Lovelace is the Home Assistant user interface. It's a fast, customizable and powerful way for users to manage their homes, working on mobile or desktop. -- 25 different cards to place and configure as you like. +- 26 different cards to place and configure as you like. - UI Editor. A configuration UI to manage your Lovelace UI including live preview when editing cards. - Fast. Using a static configuration allows us to build up the UI once. - Customizable.