From 7440fc56131d7a289e6b69315a7193da709729a8 Mon Sep 17 00:00:00 2001 From: Devon Kerkhove Date: Wed, 10 Feb 2021 09:11:08 +0100 Subject: [PATCH 01/13] Fix table markdown (#16485) Last commit introduced incorrect markdown for the compatibility table, this should fix that. --- source/_integrations/yeelight.markdown | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/source/_integrations/yeelight.markdown b/source/_integrations/yeelight.markdown index 0b261a09ff3..84cf33c2645 100644 --- a/source/_integrations/yeelight.markdown +++ b/source/_integrations/yeelight.markdown @@ -181,8 +181,7 @@ This integration is tested to work with the following models. If you have a diff | `lamp1` | MJTD01YL | Xiaomi Mijia Smart LED Desk Lamp (autodiscovery isn't possible because the device doesn't support mDNS due to the small amount of RAM) | | `ceiling1` | YLXD01YL | Yeelight Ceiling Light | | `ceiling2` | YLXD03YL | Yeelight Ceiling Light - Youth Version | - -| ? | YLXD62YI | Yeelight Ceiling Light (Jiaoyue 260) | +| ? | YLXD62YI | Yeelight Ceiling Light (Jiaoyue 260) | | ?, may be `ceiling3` | YLXD04YL | Yeelight Ceiling Light (Jiaoyue 450) | | `ceiling3` | YLXD05YL | Yeelight Ceiling Light (Jiaoyue 480) | | `ceiling4` | YLXD02YL | Yeelight Ceiling Light (Jiaoyue 650) | From 906d311f5089cb0aaf472f9ed4089f5992883a64 Mon Sep 17 00:00:00 2001 From: Franck Nijhof Date: Wed, 10 Feb 2021 09:14:40 +0100 Subject: [PATCH 02/13] Remove an advanced instruction from Z-Wave JS documentation (#16486) --- source/_integrations/zwave_js.markdown | 4 ---- 1 file changed, 4 deletions(-) diff --git a/source/_integrations/zwave_js.markdown b/source/_integrations/zwave_js.markdown index 63d198d598a..f03e223526d 100644 --- a/source/_integrations/zwave_js.markdown +++ b/source/_integrations/zwave_js.markdown @@ -347,7 +347,3 @@ Correct. Only a few devices actually support having their name stored in the har When trying to determine why something isn't working as you expect, or when reporting an issue with the integration, it is helpful to know what Z-Wave JS sees as the current state of your Z-Wave network. To get a dump of your current network state, follow the menu: **Configuration** -> **Integrations** -> **Z-Wave JS** -> **Configure** -> **Download a dump of your network to help diagnose issues** - -### Watch traffic between the server and the integration (Advanced Users) - -Z-Wave JS Server comes with a client that can be used to see the messages that the server is sending and to check the state of a node/all nodes as well. Visit the [`zwave-js-server` repository](https://github.com/zwave-js/zwave-js-server/) and follow the instructions in the README. From d73b1ab673cdfbe51d3517e7cba3e95dcae1e08d Mon Sep 17 00:00:00 2001 From: Nick Date: Wed, 10 Feb 2021 03:17:17 -0500 Subject: [PATCH 03/13] Update http.markdown (#16479) `trusted_networks` is no longer a valid option for the HTTP integration (and isn't mentioned elsewhere on this page) and so it shouldn't be referenced --- source/_integrations/http.markdown | 6 ------ 1 file changed, 6 deletions(-) diff --git a/source/_integrations/http.markdown b/source/_integrations/http.markdown index 81ad50380d9..8bdf1dd1fa4 100644 --- a/source/_integrations/http.markdown +++ b/source/_integrations/http.markdown @@ -130,12 +130,6 @@ If you want to apply additional IP filtering, and automatically ban brute force After a ban is added a Persistent Notification is populated to the Home Assistant frontend. -
- -Please note, that sources from `trusted_networks` won't be banned automatically. - -
- ## Hosting files If you want to use Home Assistant to host or serve static files then create a directory called `www` under the configuration path (`/config`). The static files in `www/` can be accessed by the following URL `http://your.domain:8123/local/`, for example `audio.mp3` would be accessed as `http://your.domain:8123/local/audio.mp3`. From df4003a3c08d0ca0e54cc1b02061f9da02191d2f Mon Sep 17 00:00:00 2001 From: jtaseff Date: Wed, 10 Feb 2021 03:18:25 -0600 Subject: [PATCH 04/13] Add nest troubleshooting item to doc (#16480) --- source/_integrations/nest.markdown | 2 ++ 1 file changed, 2 insertions(+) diff --git a/source/_integrations/nest.markdown b/source/_integrations/nest.markdown index 58cedd3c0a4..c47c822d087 100644 --- a/source/_integrations/nest.markdown +++ b/source/_integrations/nest.markdown @@ -246,6 +246,8 @@ everything, however, you can leave out any feature you do not wish to use with H - *Not receiving updates* typically means a problem with the subscriber configuration. Changes for things like sensors or thermostat temperature set points should be instantly published to a topic and received by the Home Assistant susbcriber when everything is configured correctly. +- *invalid_grant: Token has been expired or revoked* can mean the OAuth token was revoked by Google due to account changes like resetting a password. In addition, if the app is marked as "testing" and not "production" mode, the token may automatically expire after 7 days. Go to the project page to publish it to production mode. + - You can see stats about your subscriber in the [Cloud Console](https://console.cloud.google.com/cloudpubsub/subscription/list) which includes counts of messages published by your devices, and how many have been acknowledged by your Home Assistant subscriber. You can also `View Messages` to see examples of published. Many old unacknowledged messages indicate the subscriber is not receivng the messages and working properly or not connected at all. Double check the `subscriber_id` matches the `Subscription Name` - To aid in diagnosing subscriber problems or camera stream issues it may help to turn up verbose logging by adding some or all of these to your `configuration.yaml` depending on where you are having trouble: From c22ce2e2263cd698f500cc1a2b55dd6230ba9dea Mon Sep 17 00:00:00 2001 From: Franck Nijhof Date: Wed, 10 Feb 2021 10:56:22 +0100 Subject: [PATCH 05/13] Migrate setup-ruby GitHub Action (#16483) --- .github/workflows/test.yml | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/.github/workflows/test.yml b/.github/workflows/test.yml index c7484284e30..c3658569cdd 100644 --- a/.github/workflows/test.yml +++ b/.github/workflows/test.yml @@ -57,7 +57,7 @@ jobs: - name: Check out files from GitHub uses: actions/checkout@v2 - name: Setting up Ruby 2.6 - uses: actions/setup-ruby@v1.1.2 + uses: ruby/setup-ruby@v1.64.1 with: ruby-version: 2.6 - name: Setup Ruby Gems cache @@ -76,7 +76,9 @@ jobs: uses: actions/cache@v2.1.4 with: path: source/.jekyll-cache - key: jekyll-${{ hashFiles('**/Gemfile.lock') }}-${{ hashFiles('**/_config.yml') }} + key: + jekyll-${{ hashFiles('**/Gemfile.lock') }}-${{ + hashFiles('**/_config.yml') }} restore-keys: | jekyll-${{ hashFiles('**/Gemfile.lock') }}- jekyll- From af597b955b7d9995ccca4f2f1fe148fb5f2b773d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Joakim=20S=C3=B8rensen?= Date: Wed, 10 Feb 2021 12:55:48 +0100 Subject: [PATCH 06/13] Open feedback links in new tabs (#16491) --- source/_includes/edit_github.html | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/source/_includes/edit_github.html b/source/_includes/edit_github.html index ecbe0f9c3af..4316dffe242 100644 --- a/source/_includes/edit_github.html +++ b/source/_includes/edit_github.html @@ -4,16 +4,16 @@ Suggest an edit to this page, or provide/view feedback for this page. From db2a9a4a5a35981bced728480435dfa75d461964 Mon Sep 17 00:00:00 2001 From: Franck Nijhof Date: Wed, 10 Feb 2021 13:56:13 +0100 Subject: [PATCH 07/13] Update YAML standards for automation pages (#16488) --- source/_docs/automation/action.markdown | 7 +++-- source/_docs/automation/condition.markdown | 17 +++++++---- source/_docs/automation/editor.markdown | 1 - source/_docs/automation/templating.markdown | 6 +++- .../automation/using_blueprints.markdown | 3 +- source/_docs/automation/yaml.markdown | 28 +++++++++++-------- 6 files changed, 38 insertions(+), 24 deletions(-) diff --git a/source/_docs/automation/action.markdown b/source/_docs/automation/action.markdown index 79aa15e22f3..3297a6749ef 100644 --- a/source/_docs/automation/action.markdown +++ b/source/_docs/automation/action.markdown @@ -53,7 +53,7 @@ automation: action: - service: notify.notify data: - message: Testing conditional actions + message: "Testing conditional actions" - condition: or conditions: - condition: numeric_state @@ -63,6 +63,7 @@ automation: - condition: state entity_id: sensor.office_illuminance below: 10 - - service: scene.turn_on - entity_id: scene.office_at_evening + - service: scene.turn_on + target: + entity_id: scene.office_at_evening ``` diff --git a/source/_docs/automation/condition.markdown b/source/_docs/automation/condition.markdown index 0ed6610d36e..b530f18e5de 100644 --- a/source/_docs/automation/condition.markdown +++ b/source/_docs/automation/condition.markdown @@ -21,13 +21,17 @@ automation: condition: condition: or conditions: - - condition: template - value_template: "{{ state_attr('sun.sun', 'elevation') < 4 }}" - - condition: template - value_template: "{{ states('sensor.sensorluz_7_0') < 10 }}" + - condition: numeric_state + entity_id: sun.sun + attribute: elevation + below: 4 + - condition: numeric_state + entity_id: sensor.sensorluz_7_0 + below: 10 action: - service: scene.turn_on - entity_id: scene.DespiertaDespacho + target: + entity_id: scene.DespiertaDespacho ``` {% endraw %} @@ -46,7 +50,8 @@ automation: condition: "{{ state_attr('sun.sun', 'elevation') < 4 }}" action: - service: scene.turn_on - entity_id: scene.DespiertaDespacho + target: + entity_id: scene.DespiertaDespacho ``` {% endraw %} diff --git a/source/_docs/automation/editor.markdown b/source/_docs/automation/editor.markdown index 6e3b2e3b0da..4e51eee8d1c 100644 --- a/source/_docs/automation/editor.markdown +++ b/source/_docs/automation/editor.markdown @@ -30,4 +30,3 @@ message: Sensor value greater than 10 ``` Don't forget to save your new automation rule. For your saved automation rule to come into effect, you will need to go to the **Configuration** page and click on **Reload Automation**. - diff --git a/source/_docs/automation/templating.markdown b/source/_docs/automation/templating.markdown index 26c7aa5ea70..254ac9b3345 100644 --- a/source/_docs/automation/templating.markdown +++ b/source/_docs/automation/templating.markdown @@ -10,11 +10,13 @@ Automations support [templating](/docs/configuration/templating/) in the same wa Be aware that if you reference a `trigger` state object in templates of an automation' `action` or `condition` sections, attempting to test that automation by calling the `automation.trigger` service or by clicking EXECUTE in the More Info box for the automation will not work. This is because the trigger state object doesn't exist in those contexts. One way to test automations like these is to manually check that the templates work as expected by pasting them in Developer Tools > Template together with your trigger's definition like: {%raw%} + ```yaml {% set trigger={'to_state':{'state': 'heat'}} %} {% set option = trigger.to_state.state %} {{ 'on' if option == 'heat' else 'off' }} ``` + {%endraw%} @@ -119,6 +121,7 @@ The following tables show the available trigger data per platform. ## Examples {% raw %} + ```yaml # Example configuration.yaml entries automation: @@ -155,10 +158,11 @@ automation 3: for: "00:10:00" action: - service: light.turn_off - data: + target: # Turn off whichever entity triggered the automation. entity_id: "{{ trigger.entity_id }}" ``` + {% endraw %} [state object]: /docs/configuration/state_object/ diff --git a/source/_docs/automation/using_blueprints.markdown b/source/_docs/automation/using_blueprints.markdown index 4b6ae955fc0..5f10a2d25a1 100644 --- a/source/_docs/automation/using_blueprints.markdown +++ b/source/_docs/automation/using_blueprints.markdown @@ -6,7 +6,8 @@ description: "How to create automations based off blueprints." Automation blueprints are pre-made automations that you can easily add to your Home Assistant instance. Each blueprint can be added as many times as you want. Quick links: - - [Blueprints in the Home Assistant forums][blueprint-forums] + +- [Blueprints in the Home Assistant forums][blueprint-forums] ## Blueprint Automations diff --git a/source/_docs/automation/yaml.markdown b/source/_docs/automation/yaml.markdown index b21bcea57c4..3422ba0a7ad 100644 --- a/source/_docs/automation/yaml.markdown +++ b/source/_docs/automation/yaml.markdown @@ -26,6 +26,7 @@ You can add as many labeled `automation` blocks as you want. Example of a YAML based automation that you can add to `configuration.yaml`. {% raw %} + ```yaml # Example of entry in configuration.yaml automation my_lights: @@ -53,7 +54,8 @@ automation my_lights: action: # With a single service call, we don't need a '-' before service - though you can if you want to service: homeassistant.turn_on - entity_id: group.living_room + target: + entity_id: group.living_room # Turn off lights when everybody leaves the house - alias: "Rule 2 - Away Mode" @@ -63,7 +65,8 @@ automation my_lights: to: "not_home" action: service: light.turn_off - entity_id: all + target: + entity_id: all # Notify when Paulus leaves the house in the evening - alias: "Leave Home notification" @@ -94,6 +97,7 @@ automation my_lights: title: "Cube event detected" message: "Cube has triggered this event: {{ trigger.event }}" ``` + {% endraw %} @@ -124,18 +128,18 @@ If you want to migrate your manual automations to use the editor, you'll have to - id: my_unique_id # <-- Required for editor to work, for automations created with the editor the id will be automatically generated. alias: Hello world trigger: - - platform: state - entity_id: sun.sun - from: below_horizon - to: above_horizon + - platform: state + entity_id: sun.sun + from: below_horizon + to: above_horizon condition: - - condition: numeric_state - entity_id: sensor.temperature - above: 17 - below: 25 - value_template: "{{ float(state.state) + 2 }}" + - condition: numeric_state + entity_id: sensor.temperature + above: 17 + below: 25 + value_template: "{{ float(state.state) + 2 }}" action: - - service: light.turn_on + - service: light.turn_on ``` {% endraw %} From 2a5fc2a062a1f088c8100218823426dae880c3f7 Mon Sep 17 00:00:00 2001 From: Franck Nijhof Date: Wed, 10 Feb 2021 16:13:17 +0100 Subject: [PATCH 08/13] Rename github edit to feedback (#16493) --- source/_includes/edit_github.html | 21 ----------------- source/_includes/feedback.html | 38 +++++++++++++++++++++++++++++++ source/_layouts/page.html | 4 ++-- source/blue/index.html | 2 +- source/conference/index.markdown | 3 +-- source/cookbook/index.markdown | 2 +- source/docs/index.markdown | 1 + source/faq/index.markdown | 3 +-- source/index.html | 2 +- source/integrations/index.html | 2 +- 10 files changed, 47 insertions(+), 31 deletions(-) delete mode 100644 source/_includes/edit_github.html create mode 100644 source/_includes/feedback.html diff --git a/source/_includes/edit_github.html b/source/_includes/edit_github.html deleted file mode 100644 index 4316dffe242..00000000000 --- a/source/_includes/edit_github.html +++ /dev/null @@ -1,21 +0,0 @@ -{% if page.hide_github_edit != true %} - -{% endif %} diff --git a/source/_includes/feedback.html b/source/_includes/feedback.html new file mode 100644 index 00000000000..0201b541641 --- /dev/null +++ b/source/_includes/feedback.html @@ -0,0 +1,38 @@ +{% unless page.feedback == false %} + +{% endunless %} diff --git a/source/_layouts/page.html b/source/_layouts/page.html index 07fd6cfb5df..d11479071c8 100644 --- a/source/_layouts/page.html +++ b/source/_layouts/page.html @@ -13,6 +13,6 @@ layout: default
{% endif %} {{ content }} - - {% include edit_github.html %} + + {% include feedback.html %} diff --git a/source/blue/index.html b/source/blue/index.html index 731a2ebdb98..7d82f5baa9a 100644 --- a/source/blue/index.html +++ b/source/blue/index.html @@ -3,7 +3,7 @@ title: "Home Assistant Blue!" description: "Where style and performance meet privacy" sidebar: false is_homepage: true -hide_github_edit: true +feedback: false body_id: blue show_title: false og_image: /images/blue/blue_hero.jpg diff --git a/source/conference/index.markdown b/source/conference/index.markdown index 23e5b3e5dd2..651b5619abe 100644 --- a/source/conference/index.markdown +++ b/source/conference/index.markdown @@ -1,8 +1,7 @@ --- title: Home Assistant Conference 2020 show_title: false -# is_homepage: true -hide_github_edit: true +feedback: false description: December 13, 2020 we will host the first online Home Assistant Conference. og_image: /images/conference/social.png --- diff --git a/source/cookbook/index.markdown b/source/cookbook/index.markdown index 87a5bf0ac12..1d5e4510f94 100644 --- a/source/cookbook/index.markdown +++ b/source/cookbook/index.markdown @@ -3,7 +3,7 @@ title: "Cookbook" description: "Community maintained list of different ways to use Home Assistant." sidebar: false regenerate: true -hide_github_edit: true +feedback: false --- This is a community curated list of different ways to use Home Assistant. Most diff --git a/source/docs/index.markdown b/source/docs/index.markdown index f074423ba76..a95282fdbb6 100644 --- a/source/docs/index.markdown +++ b/source/docs/index.markdown @@ -1,6 +1,7 @@ --- title: "Documentation" description: "Documentation for Home Assistant" +feedback: false --- The documentation covers beginner to advanced topics around the installation, setup, configuration, and usage of Home Assistant. diff --git a/source/faq/index.markdown b/source/faq/index.markdown index 641ce337d90..195c80fe474 100644 --- a/source/faq/index.markdown +++ b/source/faq/index.markdown @@ -2,7 +2,7 @@ title: "FAQ" description: "Home Assistant's FAQ" regenerate: true -hide_github_edit: true +feedback: false --- This is a community curated list of frequently asked questions (FAQ) about the installation, setup, and usage of Home Assistant. If you want to get details about a term, please check the [glossary](/docs/glossary/). @@ -23,4 +23,3 @@ This is a community curated list of frequently asked questions (FAQ) about the i {% endif %} {% endfor %} {% endfor %} - diff --git a/source/index.html b/source/index.html index f9c571a0ea4..5c81818cab3 100644 --- a/source/index.html +++ b/source/index.html @@ -4,7 +4,7 @@ sidebar: false hero_unit: true is_homepage: true regenerate: true -hide_github_edit: true +feedback: false description: Open source home automation that puts local control and privacy first. --- diff --git a/source/integrations/index.html b/source/integrations/index.html index cdbf40701da..8ca9b2cd2b8 100644 --- a/source/integrations/index.html +++ b/source/integrations/index.html @@ -3,7 +3,7 @@ title: "Integrations" description: "List of the built-in integrations of Home Assistant." sidebar: false is_homepage: true -hide_github_edit: true +feedback: false body_id: components-page regenerate: false --- From 218cdcc8808b3726e5a59087531c1a25aa4860e1 Mon Sep 17 00:00:00 2001 From: Sean Mooney Date: Wed, 10 Feb 2021 14:02:12 -0500 Subject: [PATCH 09/13] Add UI config instructions for UPnP integration (#16500) Previously had just YAML instructions, despite having a config flow. Now mentions how to set it up via the UI. Fixes https://github.com/home-assistant/home-assistant.io/issues/16499 --- source/_integrations/upnp.markdown | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/source/_integrations/upnp.markdown b/source/_integrations/upnp.markdown index d801768338c..952e91142bb 100644 --- a/source/_integrations/upnp.markdown +++ b/source/_integrations/upnp.markdown @@ -22,7 +22,9 @@ Please note that UPnP or NAT-PMP needs to be enabled on your router for this int ## Configuration -To integrate this into Home Assistant, add the following section to your `configuration.yaml` file: +The UPnP integration can be set up via the user interface at **Configuration** -> **Integrations** -> **Add Integration**. From the list of available integrations, select UPnP and follow the on-screen instructions. + +Alternatively, you can use YAML by adding the following section to your `configuration.yaml` file: ```yaml # Example configuration.yaml entry From b8aa9c0e8afb1dcfb35f7e3638ca0a78349eefb4 Mon Sep 17 00:00:00 2001 From: Hmmbob <33529490+hmmbob@users.noreply.github.com> Date: Wed, 10 Feb 2021 21:04:36 +0100 Subject: [PATCH 10/13] Update "observe" box / featured links on frontpage (#16501) --- source/_includes/custom/grid_item_left.html | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/source/_includes/custom/grid_item_left.html b/source/_includes/custom/grid_item_left.html index c3c404e24f5..502c2c7e90d 100644 --- a/source/_includes/custom/grid_item_left.html +++ b/source/_includes/custom/grid_item_left.html @@ -12,7 +12,7 @@ Google Cast - Google Cast + Google Assistant MQTT @@ -30,19 +30,19 @@ Plex - IKEA + IKEA Tradfri Vera - OpenWRT + Sonos - Arduino + Zigbee Home Automation - - Arduino + + Z-Wave JS From 6e24ff30b2644e43f4e13cddd7fa59478dea07fa Mon Sep 17 00:00:00 2001 From: "J. Nick Koston" Date: Wed, 10 Feb 2021 11:07:52 -1000 Subject: [PATCH 11/13] Remove YAML instructions from Roomba (#16467) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit YAML support was removed but the docs were never updated 😨 --- source/_integrations/roomba.markdown | 52 +--------------------------- 1 file changed, 1 insertion(+), 51 deletions(-) diff --git a/source/_integrations/roomba.markdown b/source/_integrations/roomba.markdown index f2565e15d92..b7b81110f02 100644 --- a/source/_integrations/roomba.markdown +++ b/source/_integrations/roomba.markdown @@ -28,41 +28,6 @@ This platform has been tested and is confirmed to be working with the iRobot Roo To add your Roomba to your installation, go to **Configuration** >> **Integrations** in the UI, click the button with + sign and from the list of integrations select iRobot Roomba. -To add your Roomba vacuum to your installation, add the following to your `configuration.yaml` file: - -```yaml -# Example configuration.yaml entry -roomba: - - host: IP_ADDRESS_OR_HOSTNAME - blid: BLID - password: PASSWORD -``` - -{% configuration %} -host: - description: The hostname or IP address of the Roomba. - required: true - type: string -blid: - description: The username (BLID) for your device. - required: true - type: string -password: - description: The password for your device. - required: true - type: string -continuous: - description: Whether to operate in continuous mode. - required: false - type: boolean - default: true -delay: - description: Custom connection delay (in seconds) for periodic mode - required: false - type: integer - default: 1 -{% endconfiguration %} -
The Roomba's MQTT server only allows a single connection. Enabling continuous mode will force the App to connect via the cloud to your Roomba. [More info here](https://github.com/NickWaterton/Roomba980-Python#firmware-2xx-notes) @@ -77,22 +42,7 @@ Sensors: - roomba_battery_level : The status of your battery - roomba_bin_full (if Roomba has the capacity to do) : Bin Full status -### Multiple Roomba vacuums - -```yaml -# Example configuration.yaml entry -roomba: - - host: IP_ADDRESS_OR_HOSTNAME_1 - blid: BLID_1 - password: PASSWORD_1 - - host: IP_ADDRESS_OR_HOSTNAME_2 - blid: BLID_2 - password: PASSWORD_2 - continuous: false - delay: 5 -``` - -### Retrieving your credentials +### Manually retrieving your credentials Please refer to [here](https://github.com/NickWaterton/Roomba980-Python#how-to-get-your-usernameblid-and-password) or [here](https://github.com/koalazak/dorita980#how-to-get-your-usernameblid-and-password) to retrieve both the BLID (username) and the password. From bf01058c52c7d4e6f6af0626663d5e302dcab107 Mon Sep 17 00:00:00 2001 From: Stephen Littman Date: Thu, 11 Feb 2021 03:39:56 -0500 Subject: [PATCH 12/13] added openMqttgateway to the list (#16503) Works great for me --- source/_integrations/mqtt_room.markdown | 1 + 1 file changed, 1 insertion(+) diff --git a/source/_integrations/mqtt_room.markdown b/source/_integrations/mqtt_room.markdown index 43ed9ecad9e..94a842014fd 100644 --- a/source/_integrations/mqtt_room.markdown +++ b/source/_integrations/mqtt_room.markdown @@ -67,3 +67,4 @@ Instead of developing your own application, you can also use any of these alread - [**room-assistant**](https://github.com/mKeRix/room-assistant): looks for Bluetooth LE beacons, based on Node.js - [**Happy Bubbles Presence Server**](https://github.com/happy-bubbles/presence): presence detection server for Happy Bubbles BLE-scanning devices, based on Go - [**ESP32-MQTT-room**](https://jptrsn.github.io/ESP32-mqtt-room/): runs on an ESP32, and looks for Bluetooth LE devices, based on C++/Arduino +- [**OpenMQTTGateway**](https://github.com/1technophile/OpenMQTTGateway): uses ESP32 Bluetooth Low Energy to scan BLE Broadcaster like smart watch/band and moch more to get sensor values From 58496da744f7b54e1b1cf61e472b4b2f3f037364 Mon Sep 17 00:00:00 2001 From: Franck Nijhof Date: Thu, 11 Feb 2021 12:56:04 +0100 Subject: [PATCH 13/13] 2021.2.3 --- _config.yml | 4 +- .../_posts/2021-02-03-release-20212.markdown | 51 +++++++++++++++++++ 2 files changed, 53 insertions(+), 2 deletions(-) diff --git a/_config.yml b/_config.yml index 6fcb521c223..b7a22d6845d 100644 --- a/_config.yml +++ b/_config.yml @@ -102,8 +102,8 @@ social: # Home Assistant release details current_major_version: 2021 current_minor_version: 2 -current_patch_version: 2 -date_released: 2021-02-09 +current_patch_version: 3 +date_released: 2021-02-11 # 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/_posts/2021-02-03-release-20212.markdown b/source/_posts/2021-02-03-release-20212.markdown index fa3c6cfc3b1..07df11c9bd2 100644 --- a/source/_posts/2021-02-03-release-20212.markdown +++ b/source/_posts/2021-02-03-release-20212.markdown @@ -51,6 +51,7 @@ Enjoy the release! - [Integrations now available to set up from the UI](#integrations-now-available-to-set-up-from-the-ui) - [Release 2021.2.1 - February 5](#release-202121---february-5) - [Release 2021.2.2 - February 9](#release-202122---february-9) +- [Release 2021.2.3 - February 11](#release-202123---february-11) - [If you need help...](#if-you-need-help) - [Breaking Changes](#breaking-changes) - [Farewell to the following](#farewell-to-the-following) @@ -444,6 +445,56 @@ The following integrations are now available via the Home Assistant UI: [zwave docs]: /integrations/zwave/ [zwave_js docs]: /integrations/zwave_js/ +## Release 2021.2.3 - February 11 + +- Fix SNMP engine memory leak in Brother integration ([@bieniu] - [#46272]) ([brother docs]) +- Use oauthv3 for Tesla ([@alandtse] - [#45766]) ([tesla docs]) (breaking-change) +- Bump pymyq to 3.0.1 ([@ehendrix23] - [#46079]) ([myq docs]) +- Revert transmission to check torrent lists by name rather than object ([@JPHutchins] - [#46190]) ([transmission docs]) +- Update powerwall for new authentication requirements ([@bdraco] - [#46254]) ([powerwall docs]) +- Fix Lutron Integration Protocol reconnect logic ([@bdraco] - [#46264]) ([lutron_caseta docs]) +- Bump roonapi to 0.0.32 ([@pavoni] - [#46286]) ([roon docs]) +- Add guards for missing value in binary_sensor platform of zwave_js integration ([@marcelveldt] - [#46293]) ([zwave_js docs]) +- Add reauth support for tesla ([@bdraco] - [#46307]) ([tesla docs]) +- Add `already_in_progress` string to roku config flow ([@bramkragten] - [#46333]) ([roku docs]) +- Restore Google/Alexa extra significant change checks ([@balloob] - [#46335]) ([alexa docs]) ([google_assistant docs]) +- Fix Shelly relay device set to light appliance type ([@thecode] - [#46181]) ([shelly docs]) + +[#45766]: https://github.com/home-assistant/core/pull/45766 +[#46079]: https://github.com/home-assistant/core/pull/46079 +[#46181]: https://github.com/home-assistant/core/pull/46181 +[#46190]: https://github.com/home-assistant/core/pull/46190 +[#46254]: https://github.com/home-assistant/core/pull/46254 +[#46264]: https://github.com/home-assistant/core/pull/46264 +[#46272]: https://github.com/home-assistant/core/pull/46272 +[#46286]: https://github.com/home-assistant/core/pull/46286 +[#46293]: https://github.com/home-assistant/core/pull/46293 +[#46307]: https://github.com/home-assistant/core/pull/46307 +[#46333]: https://github.com/home-assistant/core/pull/46333 +[#46335]: https://github.com/home-assistant/core/pull/46335 +[@JPHutchins]: https://github.com/JPHutchins +[@alandtse]: https://github.com/alandtse +[@balloob]: https://github.com/balloob +[@bdraco]: https://github.com/bdraco +[@bieniu]: https://github.com/bieniu +[@bramkragten]: https://github.com/bramkragten +[@ehendrix23]: https://github.com/ehendrix23 +[@marcelveldt]: https://github.com/marcelveldt +[@pavoni]: https://github.com/pavoni +[@thecode]: https://github.com/thecode +[alexa docs]: /integrations/alexa/ +[brother docs]: /integrations/brother/ +[google_assistant docs]: /integrations/google_assistant/ +[lutron_caseta docs]: /integrations/lutron_caseta/ +[myq docs]: /integrations/myq/ +[powerwall docs]: /integrations/powerwall/ +[roku docs]: /integrations/roku/ +[roon docs]: /integrations/roon/ +[shelly docs]: /integrations/shelly/ +[tesla docs]: /integrations/tesla/ +[transmission docs]: /integrations/transmission/ +[zwave_js docs]: /integrations/zwave_js/ + ## If you need help... ...don't hesitate to use our very active [forums](https://community.home-assistant.io/) or join us for a little [chat](https://discord.gg/c5DvZ4e).