diff --git a/_config.yml b/_config.yml index 19d9dad7a333..2aeb3a197bcd 100644 --- a/_config.yml +++ b/_config.yml @@ -101,8 +101,8 @@ social: # Home Assistant release details current_major_version: 0 current_minor_version: 107 -current_patch_version: 5 -date_released: 2020-03-21 +current_patch_version: 7 +date_released: 2020-03-25 # 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/package-lock.json b/package-lock.json index ede6616e59e3..51d398be2b12 100644 --- a/package-lock.json +++ b/package-lock.json @@ -1420,9 +1420,9 @@ } }, "mdast-comment-marker": { - "version": "1.1.1", - "resolved": "https://registry.npmjs.org/mdast-comment-marker/-/mdast-comment-marker-1.1.1.tgz", - "integrity": "sha512-TWZDaUtPLwKX1pzDIY48MkSUQRDwX/HqbTB4m3iYdL/zosi/Z6Xqfdv0C0hNVKvzrPjZENrpWDt4p4odeVO0Iw==", + "version": "1.1.2", + "resolved": "https://registry.npmjs.org/mdast-comment-marker/-/mdast-comment-marker-1.1.2.tgz", + "integrity": "sha512-vTFXtmbbF3rgnTh3Zl3irso4LtvwUq/jaDvT2D1JqTGAwaipcS7RpTxzi6KjoRqI9n2yuAhzLDAC8xVTF3XYVQ==", "dev": true }, "mdast-util-compact": { @@ -1855,9 +1855,9 @@ } }, "remark-frontmatter": { - "version": "1.3.2", - "resolved": "https://registry.npmjs.org/remark-frontmatter/-/remark-frontmatter-1.3.2.tgz", - "integrity": "sha512-2eayxITZ8rezsXdgcXnYB3iLivohm2V/ZT4Ne8uhua6A4pk6GdLE2ZzJnbnINtD1HRLaTdB7RwF9sgUbMptJZA==", + "version": "1.3.3", + "resolved": "https://registry.npmjs.org/remark-frontmatter/-/remark-frontmatter-1.3.3.tgz", + "integrity": "sha512-fM5eZPBvu2pVNoq3ZPW22q+5Ativ1oLozq2qYt9I2oNyxiUd/tDl0iLLntEVAegpZIslPWg1brhcP1VsaSVUag==", "dev": true, "requires": { "fault": "^1.0.1", @@ -1865,18 +1865,18 @@ } }, "remark-lint": { - "version": "6.0.5", - "resolved": "https://registry.npmjs.org/remark-lint/-/remark-lint-6.0.5.tgz", - "integrity": "sha512-o1I3ddm+KNsTxk60wWGI+p2yU1jB1gcm8jo2Sy6VhJ4ab2TrQIp1oQbp5xeLoFXYSh/NAqCpKjHkCM/BYpkFdQ==", + "version": "6.0.6", + "resolved": "https://registry.npmjs.org/remark-lint/-/remark-lint-6.0.6.tgz", + "integrity": "sha512-JBY6zz5fYQFN724Vq6VeiHwhyjVIlrww/dE1+hWGcDyUuz7YNCqwZKwBdQGDvslICkzHw/wEExNEb8D4PNiLlA==", "dev": true, "requires": { "remark-message-control": "^4.0.0" } }, "remark-lint-fenced-code-flag": { - "version": "1.0.3", - "resolved": "https://registry.npmjs.org/remark-lint-fenced-code-flag/-/remark-lint-fenced-code-flag-1.0.3.tgz", - "integrity": "sha512-X8Oi6dhfqV9NI3cVg29myvT/NATDHVgRGCpnNz76w7VXwzhBvQtJr1MxZzuPxfWLox+ARCXF2rY9n9hbYFHYTg==", + "version": "1.0.4", + "resolved": "https://registry.npmjs.org/remark-lint-fenced-code-flag/-/remark-lint-fenced-code-flag-1.0.4.tgz", + "integrity": "sha512-bkQvlEYco6ZzdzvGPrY7DBsqSq/2mZEmdhpn0KdMEZ9kcKJP4unQdVQys04SKnf9QISqQ446VnQj5Q4E3HMSkQ==", "dev": true, "requires": { "unified-lint-rule": "^1.0.0", @@ -1886,9 +1886,9 @@ } }, "remark-lint-no-shell-dollars": { - "version": "1.0.3", - "resolved": "https://registry.npmjs.org/remark-lint-no-shell-dollars/-/remark-lint-no-shell-dollars-1.0.3.tgz", - "integrity": "sha512-fT3lQMTjEkPryL+63qDP1NfrohP3tG5i3SkNWSSR4VLU6OSsSSXlHGQGjo0ag//+EPKHB5/9frB/YQ0gDEPRGQ==", + "version": "1.0.4", + "resolved": "https://registry.npmjs.org/remark-lint-no-shell-dollars/-/remark-lint-no-shell-dollars-1.0.4.tgz", + "integrity": "sha512-YXFj8FUVTKkVvoAbFY3zv1Ol7Kj1i+qdze3pXSgRG61y1LpfL8/HpnvFrseMbBmNw6o4WpjTo7GoArngJ1sCeg==", "dev": true, "requires": { "unified-lint-rule": "^1.0.0", @@ -2542,9 +2542,9 @@ "dev": true }, "unist-util-position": { - "version": "3.0.3", - "resolved": "https://registry.npmjs.org/unist-util-position/-/unist-util-position-3.0.3.tgz", - "integrity": "sha512-28EpCBYFvnMeq9y/4w6pbnFmCUfzlsc41NJui5c51hOFjBA1fejcwc+5W4z2+0ECVbScG3dURS3JTVqwenzqZw==", + "version": "3.1.0", + "resolved": "https://registry.npmjs.org/unist-util-position/-/unist-util-position-3.1.0.tgz", + "integrity": "sha512-w+PkwCbYSFw8vpgWD0v7zRCl1FpY3fjDSQ3/N/wNd9Ffa4gPi8+4keqt99N3XW6F99t/mUzp2xAhNmfKWp95QA==", "dev": true }, "unist-util-remove-position": { diff --git a/package.json b/package.json index 275dc1e8cf71..c67bba90c76b 100644 --- a/package.json +++ b/package.json @@ -5,10 +5,10 @@ "dependencies": {}, "devDependencies": { "remark-cli": "^7.0.1", - "remark-frontmatter": "^1.3.2", - "remark-lint": "^6.0.5", - "remark-lint-fenced-code-flag": "^1.0.3", - "remark-lint-no-shell-dollars": "^1.0.3", + "remark-frontmatter": "^1.3.3", + "remark-lint": "^6.0.6", + "remark-lint-fenced-code-flag": "^1.0.4", + "remark-lint-no-shell-dollars": "^1.0.4", "remark-stringify": "^7.0.4", "textlint": "^11.6.3", "textlint-rule-common-misspellings": "^1.0.1", diff --git a/source/_docs/installation/raspberry-pi.markdown b/source/_docs/installation/raspberry-pi.markdown index c25e90461a12..b77961584490 100644 --- a/source/_docs/installation/raspberry-pi.markdown +++ b/source/_docs/installation/raspberry-pi.markdown @@ -1,10 +1,10 @@ --- title: "Manual installation on a Raspberry Pi" -description: "Instructions to install Home Assistant on a Raspberry Pi running Raspbian Lite." +description: "Instructions to install Home Assistant Core on a Raspberry Pi running Raspbian Lite." redirect_from: /getting-started/installation-raspberry-pi/ --- -This installation of Home Assistant requires the Raspberry Pi to run [Raspbian Lite](https://www.raspberrypi.org/downloads/raspbian/). The installation will be installed in a [Virtual Environment](/docs/installation/virtualenv) with minimal overhead. Instructions assume this is a new installation of Raspbian Lite. +This installation of Home Assistant Core requires the Raspberry Pi to run [Raspbian Lite](https://www.raspberrypi.org/downloads/raspbian/). The installation will be installed in a [Virtual Environment](/docs/installation/virtualenv) with minimal overhead. Instructions assume this is a new installation of Raspbian Lite. You must have Python 3.7 or later installed (including the package `python3-dev`) which is *not* the case for Raspbian Stretch. @@ -44,14 +44,14 @@ Install the dependencies. sudo apt-get install python3 python3-dev python3-venv python3-pip libffi-dev libssl-dev ``` -Add an account for Home Assistant called `homeassistant`. -Since this account is only for running Home Assistant the extra arguments of `-rm` is added to create a system account and create a home directory. The arguments `-G dialout,gpio,i2c` adds the user to the `dialout`, `gpio` and the `i2c` group. The first is required for using Z-Wave and Zigbee controllers, while the second is required to communicate with Raspberry's GPIO. +Add an account for Home Assistant Core called `homeassistant`. +Since this account is only for running Home Assistant Core the extra arguments of `-rm` is added to create a system account and create a home directory. The arguments `-G dialout,gpio,i2c` adds the user to the `dialout`, `gpio` and the `i2c` group. The first is required for using Z-Wave and Zigbee controllers, while the second is required to communicate with Raspberry's GPIO. ```bash sudo useradd -rm homeassistant -G dialout,gpio,i2c ``` -Next we will create a directory for the installation of Home Assistant and change the owner to the `homeassistant` account. +Next we will create a directory for the installation of Home Assistant Core and change the owner to the `homeassistant` account. ```bash cd /srv @@ -59,7 +59,7 @@ sudo mkdir homeassistant sudo chown homeassistant:homeassistant homeassistant ``` -Next up is to create and change to a virtual environment for Home Assistant. This will be done as the `homeassistant` account. +Next up is to create and change to a virtual environment for Home Assistant Core. This will be done as the `homeassistant` account. ```bash sudo -u homeassistant -H -s @@ -73,13 +73,13 @@ Once you have activated the virtual environment (notice the prompt change to `(h python3 -m pip install wheel ``` -Once you have installed the required Python package it is now time to install Home Assistant! +Once you have installed the required Python package it is now time to install Home Assistant Core! ```bash pip3 install homeassistant ``` -Start Home Assistant for the first time. This will complete the installation for you, automatically creating the `.homeassistant` configuration directory in the `/home/homeassistant` directory, and installing any basic dependencies. +Start Home Assistant Core for the first time. This will complete the installation for you, automatically creating the `.homeassistant` configuration directory in the `/home/homeassistant` directory, and installing any basic dependencies. ```bash hass @@ -92,11 +92,11 @@ When you run the `hass` command for the first time, it will download, install an -If you want to setup `hass` as a daemon and autostart it on boot please refer to [Autostart Home Assistant](/docs/autostart/). +If you want to setup `hass` as a daemon and autostart it on boot please refer to [Autostart Home Assistant Core](/docs/autostart/). ### Updating -To update to the latest version of Home Assistant follow these simple steps: +To update to the latest version of Home Assistant Core follow these simple steps: ```bash sudo -u homeassistant -H -s @@ -104,11 +104,11 @@ source /srv/homeassistant/bin/activate pip3 install --upgrade homeassistant ``` -Once the last command executes, restart the Home Assistant service to apply the latest updates. Please keep in mind that some updates may take longer to start up than others. If Home Assistant fails to start, make sure you check the **Breaking Changes** from the [Release Notes](https://github.com/home-assistant/home-assistant/releases). +Once the last command executes, restart the Home Assistant Core service to apply the latest updates. Please keep in mind that some updates may take longer to start up than others. If Home Assistant Core fails to start, make sure you check the **Breaking Changes** from the [Release Notes](https://github.com/home-assistant/home-assistant/releases). ### Run a specific version -In the event that a Home Assistant version doesn't play well with your hardware setup, you can downgrade to a previous release. For example: +In the event that a Home Assistant Core version doesn't play well with your hardware setup, you can downgrade to a previous release. For example: ```bash sudo -u homeassistant -H -s @@ -128,7 +128,7 @@ pip3 install --pre --upgrade homeassistant ### Run the development version -If you want to stay on the bleeding-edge Home Assistant development branch, you can upgrade to `dev`. +If you want to stay on the bleeding-edge Home Assistant Core development branch, you can upgrade to `dev`.
The "dev" branch is likely to be unstable. Potential consequences include loss of data and instance corruption. diff --git a/source/_integrations/manual.markdown b/source/_integrations/manual.markdown index ed33d84527cc..005610be2949 100644 --- a/source/_integrations/manual.markdown +++ b/source/_integrations/manual.markdown @@ -45,17 +45,17 @@ code_arm_required: type: boolean default: true delay_time: - description: The time in seconds of the pending time before triggering the alarm. + description: The time in seconds of the 'pending' state before triggering the alarm. required: false type: integer default: 0 -pending_time: - description: The time in seconds of the pending time before effecting a state change. +arming_time: + description: The time in seconds of the 'arming' state before effecting a state change. required: false type: integer default: 60 trigger_time: - description: The time in seconds of the trigger time in which the alarm is firing. + description: The time in seconds of the 'triggered' state in which the alarm is firing. required: false type: integer default: 120 @@ -73,8 +73,8 @@ armed_custom_bypass/armed_home/armed_away/armed_night/disarmed/triggered: description: State specific setting for **delay_time** (all states except **triggered**) required: false type: integer - pending_time: - description: State specific setting for **pending_time** (all states except **disarmed**) + arming_time: + description: State specific setting for **arming_time** (all states except **disarmed**) required: false type: integer trigger_time: @@ -86,21 +86,20 @@ armed_custom_bypass/armed_home/armed_away/armed_night/disarmed/triggered: ## State machine The state machine of the manual alarm integration is complex but powerful. The -transitions are timed according to three values, **delay_time**, **pending_time** -and **trigger_time**. The values in turn can come from the default configuration +transitions are timed according to three values, **delay_time**, **arming_time** +and **trigger_time**. The values in turn can come from the default configuration variable or from a state-specific override. -When the alarm is armed, its state first goes to **pending** for a number -of seconds equal to the destination state's **pending_time**, and then +When the alarm is armed, its state first goes to **arming** for a number +of seconds equal to the destination state's **arming_time**, and then transitions to one of the "armed" states. Note that **code_template** -never receives "pending" in the **to_state** variable; instead, +never receives "arming" in the **to_state** variable; instead, **to_state** contains the state which the user has requested. However, -**from_state** *can* contain "pending". +**from_state** *can* contain "arming". When the alarm is triggered, its state goes to **pending** for a number of -seconds equal to the previous state's **delay_time** plus the triggered -state's **pending_time**. Then the alarm transitions to the "triggered" -states. The code is never checked when triggering the alarm, so the +seconds equal to the previous state's **delay_time**. Then the alarm transitions to the "triggered" +states. The code is never checked when triggering the alarm, so the **to_state** variable of **code_template** cannot ever contain "triggered" either; again, **from_state** *can* contain "triggered". @@ -110,12 +109,11 @@ it goes back to either the previous state or **disarmed**. If the previous state's **trigger_time** is zero, the transition to "triggered" is entirely blocked and the alarm remains in the armed state. -Each of the settings is useful in different scenarios. **pending_time** gives -you some time to leave the building (for "armed" states) or to disarm the alarm -(for the "triggered" state). +Each of the settings is useful in different scenarios. **arming_time** gives +you some time to leave the building (for "armed" states). -**delay_time** can also be used to allow some time to disarm the alarm, but with -more flexibility. For example, you could specify a delay time for the +**delay_time** can be used to allow some time to disarm the alarm, with +flexibility. For example, you could specify a delay time for the "armed away" state, in order to avoid triggering the alarm while the garage door opens, but not for the "armed home" state. @@ -136,13 +134,13 @@ alarm_control_panel: - platform: manual name: Home Alarm code: 1234 - pending_time: 30 + arming_time: 30 delay_time: 20 trigger_time: 4 disarmed: trigger_time: 0 armed_home: - pending_time: 0 + arming_time: 0 delay_time: 0 ``` diff --git a/source/_integrations/netatmo.markdown b/source/_integrations/netatmo.markdown index 24e50cfe73d6..16cd34fbe5b7 100644 --- a/source/_integrations/netatmo.markdown +++ b/source/_integrations/netatmo.markdown @@ -23,6 +23,7 @@ There is currently support for the following device types within Home Assistant: - [Camera](#camera) - [Climate](#climate) - [Sensor](#sensor) +- [Webhooks](#webhooks) ## Configuration @@ -70,21 +71,98 @@ That's it. You can copy and paste your new `client id` and `client secret` in yo ## Camera -The `netatmo` camera platform is consuming the information provided by a [Netatmo](https://www.netatmo.com) camera. This integration allows you to view the current live stream created by the Camera. +The `netatmo` camera platform is consuming the information provided by a [Netatmo Smart Indoor](https://www.netatmo.com/en-gb/security/cam-indoor) or [Outdoor](https://www.netatmo.com/en-gb/security/cam-outdoor) camera. This integration allows you to view the current live stream created by the camera. ## Climate -The `netatmo` thermostat platform is consuming the information provided by a [Netatmo Smart Thermostat](https://www.netatmo.com/product/energy/thermostat) thermostat. This integration allows you to view the current temperature and setpoint. +The `netatmo` thermostat platform is consuming the information provided by a [Netatmo Smart Thermostat](https://www.netatmo.com/product/energy/thermostat) or [Netatmo Smart Radiator Valve](https://www.netatmo.com/en-gb/energy/additional-valve). This integration allows you to view the current temperature and control the setpoint. ## Sensor -The `netatmo` sensor platform is consuming the information provided by a [Netatmo Weather Station](https://www.netatmo.com/en-us/weather/weatherstation) or a -[Netatmo Home Coach](https://www.netatmo.com/en-us/aircare/homecoach) [Netatmo](https://www.netatmo.com) device. +The `netatmo` sensor platform is consuming the information provided by a [Netatmo Smart Home Weather Station](https://www.netatmo.com/en-us/weather/weatherstation) or a +[Netatmo Smart Indoor Air Quality Monitor](https://www.netatmo.com/en-us/aircare/homecoach) device. ## Webhooks -The smart indoor and outdoor cameras, as well as the smart smoke alarm, send instant events to Home Assistant by using webhooks. It is required to have your camera enabled in Home Assistant. +The [Netatmo Smart Indoor](https://www.netatmo.com/en-gb/security/cam-indoor) or [Outdoor](https://www.netatmo.com/en-gb/security/cam-outdoor) cameras, [Smart Door and Window Sensors](https://www.netatmo.com/en-gb/security/cam-indoor/tag), as well as the [Netatmo Smart Smoke Alarm](https://www.netatmo.com/en-gb/security/smoke-alarm), send instant events to Home Assistant by using webhooks. It is required to have your camera enabled in Home Assistant. -To be able to receive events from Netatmo, your Home Assistant instance needs to be accessible from the web. To achieve this you can either use your Nabu Casa account or ([Home Assistant instructions](/addons/duckdns/)) and you need to have the `base_url` configured for the HTTP integration ([documentation](/integrations/http/#base_url)). +To be able to receive events from [Netatmo](https://www.netatmo.com/en-gb/), your Home Assistant instance needs to be accessible from the web over port `80` or `443`. To achieve this you can either use your Nabu Casa account or for example Duck DNS ([Home Assistant instructions](/addons/duckdns/)). You also need to have the `base_url` configured for the HTTP integration ([documentation](/integrations/http/#base_url)). Events coming in from Netatmo will be available as an event in Home Assistant and are fired as `netatmo_event`, along with their data. You can use these events to trigger automations. + +You can find the available event types at the [official Netatmo API documentation](https://dev.netatmo.com/apidocumentation/security#events). + +Example: + +{% raw %} + +```yaml +# Example automation for webhooks based Netatmo events +- alias: Netatmo event example + description: "Count all events pushed by the Netatmo API" + trigger: + - event_data: {} + event_type: netatmo_event + platform: event + action: + - data: {} + entity_id: counter.event_counter + service: counter.increment +``` + +{% endraw %} + +Example: + +{% raw %} + +```yaml +# Example automation +- alias: Motion at home + description: 'Motion detected at home' + trigger: + - event_type: netatmo_event + platform: event + event_data: + type: movement + action: + - data_template: + message: > + {{ trigger.event.data["data"]["message"] }} + at {{ trigger.event.data["data"]["home_name"] }} + title: Netatmo event + service: persistent_notification.create +``` + +{% endraw %} + +Example: + +{% raw %} + +```yaml +# Example automation +- alias: door or window open or movement + description: 'Notifies which door or window is open or was moved' + trigger: + - event_type: netatmo_event + platform: event + event_data: + type: tag_open + - event_type: netatmo_event + platform: event + event_data: + type: tag_big_move + - event_type: netatmo_event + platform: event + event_data: + type: tag_small_move + action: + - data_template: + message: > + {{ trigger.event.data["data"]["message"] }} + title: Netatmo event + service: persistent_notification.create +``` + +{% endraw %} diff --git a/source/_integrations/recorder.markdown b/source/_integrations/recorder.markdown index 4bd3af529933..11e39f16ada0 100644 --- a/source/_integrations/recorder.markdown +++ b/source/_integrations/recorder.markdown @@ -137,8 +137,8 @@ recorder: - media_player exclude: entities: - - sensor.last_boot - - sensor.date + - sensor.last_boot + - sensor.date ``` If you only want to hide events from your history, take a look at the [`history` integration](/integrations/history/). The same goes for the [logbook](/integrations/logbook/). But if you have privacy concerns about certain events or want them in neither the history or logbook, you should use the `exclude`/`include` options of the `recorder` integration. That way they aren't even in your database, you can reduce storage and keep the database small by excluding certain often-logged events (like `sensor.last_boot`). diff --git a/source/_integrations/rfxtrx.markdown b/source/_integrations/rfxtrx.markdown index 98bf36747b9e..d85a80d6060e 100644 --- a/source/_integrations/rfxtrx.markdown +++ b/source/_integrations/rfxtrx.markdown @@ -55,7 +55,7 @@ dummy: ## Supported protocols -Not all protocols as advertised are enabled on the initial setup of your transceiver. Enabling all protocols is not recommended either. Your 433.92 product not showing in the logs? Visit the RFXtrx website to [download RFXmgmr](http://www.rfxcom.com/epages/78165469.sf/nl_NL/?ObjectPath=/Shops/78165469/Categories/Downloads) and enable the required protocol. +Not all protocols as advertised are enabled on the initial setup of your transceiver. Enabling all protocols is not recommended either. Your 433.92 product not showing in the logs? Visit the RFXtrx website to [download RFXmgmr](http://www.rfxcom.com/epages/78165469.sf/en_GB/?ViewObjectPath=%2FShops%2F78165469%2FCategories%2FDownloads) and enable the required protocol. ### ser2net diff --git a/source/_integrations/samsungtv.markdown b/source/_integrations/samsungtv.markdown index ba59ec7f139f..82c629ba8d62 100644 --- a/source/_integrations/samsungtv.markdown +++ b/source/_integrations/samsungtv.markdown @@ -97,11 +97,11 @@ For example: for model `UN55NU7100`, the `UN55` would mean it's an LED, North Am - F6500 - F7000 - F8000BF -- K5579 (On/Off, Forward/Backward, Volume control, but no Play button) +- K5579 - K5600AK (partially supported, turn on works but state is not updated) - K6500AF -- KS7005 (MAC address must be provided, On/Off, Volume are OK, no channel change) -- KS7502 (turn on doesn't work, turn off works fine) +- KS7005 (no channel change) +- KS7502 (On doesn't work, Off works fine) - KS8000 - KS8005 - KS8500 @@ -109,21 +109,19 @@ For example: for model `UN55NU7100`, the `UN55` would mean it's an LED, North Am - KU6100 - KU6290 - KU6400U +- KU6470 - KU7000 - M5620 - MU6170UXZG -- NU7090 (On/Off, MAC must be specified for Power On) +- MU6179 +- MU6199 +- NU7090 (On/Off) - NU7400 - NU8000 +- NU8070 - U6000 - U6300 -- UE46ES5500 (partially supported, turn on doesn't work) -- UE46D7000 -- UE49KU6470 (On/Off, Forward/Backward, Volume are OK, but no Play button) -- UE55MU6179 -- UE55NU8070 -- UE6199UXZG (On/Off, Forward/Backward, Volume control, but no Play button) -- UE65KS8005 (On/Off, Forward/Backward, Volume are OK, but no Play button) +- RU7172 #### Models tested but not yet working diff --git a/source/_integrations/switch.modbus.markdown b/source/_integrations/switch.modbus.markdown index 067148d940a3..0809e71a75c7 100644 --- a/source/_integrations/switch.modbus.markdown +++ b/source/_integrations/switch.modbus.markdown @@ -58,12 +58,12 @@ coils: description: Coil number. required: true type: integer -register: +registers: description: A list of relevant registers to read from/write to. required: false type: map keys: - hub_name: + hub: description: The hub to use. required: false default: default diff --git a/source/_posts/2020-03-18-release-107.markdown b/source/_posts/2020-03-18-release-107.markdown index 4ec1c6731e8b..65410529d8a2 100644 --- a/source/_posts/2020-03-18-release-107.markdown +++ b/source/_posts/2020-03-18-release-107.markdown @@ -495,6 +495,47 @@ Experiencing issues introduced by this release? Please report them in our [issue [totalconnect docs]: /integrations/totalconnect/ [zha docs]: /integrations/zha/ +## Release 0.107.6 - March 24 + +- Integrate dockerbuild ([@pvizeli] - [#33168]) +- Fix script logging with name ([@balloob] - [#33120]) +- Fix minut point updating frozen config entry data ([@frenck] - [#33148]) ([point docs]) +- Bump OZW fork to 0.1.10 ([@pvizeli] - [#33205]) ([zwave docs]) + +[#33120]: https://github.com/home-assistant/core/pull/33120 +[#33148]: https://github.com/home-assistant/core/pull/33148 +[#33168]: https://github.com/home-assistant/core/pull/33168 +[#33205]: https://github.com/home-assistant/core/pull/33205 +[@balloob]: https://github.com/balloob +[@frenck]: https://github.com/frenck +[@pvizeli]: https://github.com/pvizeli +[point docs]: /integrations/point/ +[zwave docs]: /integrations/zwave/ + +## Release 0.107.7 - March 25 + +- Fix velbus dimming control ([@brefra] - [#33139]) ([velbus docs]) +- Increase timeout setting up IPMA ([@dgomes] - [#33194]) ([ipma docs]) +- Refactor ZHA platform setup ([@Adminiuga] - [#33226]) ([zha docs]) +- Ensure recorder event loop recovers if the database server dis… ([@bdraco] - [#33253]) ([recorder docs]) +- Schedule Unifi shutdown callback earlier ([@jjlawren] - [#33257]) ([unifi docs]) + +[#33139]: https://github.com/home-assistant/core/pull/33139 +[#33194]: https://github.com/home-assistant/core/pull/33194 +[#33226]: https://github.com/home-assistant/core/pull/33226 +[#33253]: https://github.com/home-assistant/core/pull/33253 +[#33257]: https://github.com/home-assistant/core/pull/33257 +[@Adminiuga]: https://github.com/Adminiuga +[@bdraco]: https://github.com/bdraco +[@brefra]: https://github.com/brefra +[@dgomes]: https://github.com/dgomes +[@jjlawren]: https://github.com/jjlawren +[ipma docs]: /integrations/ipma/ +[recorder docs]: /integrations/recorder/ +[unifi docs]: /integrations/unifi/ +[velbus docs]: /integrations/velbus/ +[zha docs]: /integrations/zha/ + ## All changes - Nuki: add support for unique id ([@pvizeli] - [#31824]) ([nuki docs])