From d1b96324eaecfec998a68f33ca02436dfd4c9ef9 Mon Sep 17 00:00:00 2001 From: "dependabot[bot]" <49699333+dependabot[bot]@users.noreply.github.com> Date: Tue, 23 Feb 2021 08:43:41 +0100 Subject: [PATCH 1/4] Bump actions/setup-node from v2.1.4 to v2.1.5 (#16704) --- .github/workflows/test.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/.github/workflows/test.yml b/.github/workflows/test.yml index c3658569cdd..d1c5f0229ec 100644 --- a/.github/workflows/test.yml +++ b/.github/workflows/test.yml @@ -10,7 +10,7 @@ jobs: - name: Check out files from GitHub uses: actions/checkout@v2 - name: Setting up Node.js ${{ matrix.node-version }} - uses: actions/setup-node@v2.1.4 + uses: actions/setup-node@v2.1.5 with: node-version: 12.x - name: Setup NPM cache @@ -33,7 +33,7 @@ jobs: - name: Check out files from GitHub uses: actions/checkout@v2 - name: Setting up Node.js ${{ matrix.node-version }} - uses: actions/setup-node@v2.1.4 + uses: actions/setup-node@v2.1.5 with: node-version: 12.x - name: Setup NPM cache From 863aec8e0f3ec85a38072e4bb2ad042e74063f32 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Thomas=20Lov=C3=A9n?= Date: Tue, 23 Feb 2021 10:53:19 +0100 Subject: [PATCH 2/4] Update git repository reference (#16706) --- source/_includes/common-tasks/development_version.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_includes/common-tasks/development_version.md b/source/_includes/common-tasks/development_version.md index 05f38c199b2..346fafccb93 100644 --- a/source/_includes/common-tasks/development_version.md +++ b/source/_includes/common-tasks/development_version.md @@ -51,7 +51,7 @@ ha os update --version {{current_version}} 3. Download and install the version you want ```bash - pip3 install --upgrade git+git://github.com/home-assistant/home-assistant.git@dev + pip3 install --upgrade git+git://github.com/home-assistant/core.git@dev ``` 4. When that is complete restart the service for it to use the new files. From 6a9280320b3807658b74ef9c8013ed0e02f63322 Mon Sep 17 00:00:00 2001 From: Abel Matser <33466359+abelmatser@users.noreply.github.com> Date: Tue, 23 Feb 2021 12:09:26 +0100 Subject: [PATCH 3/4] Update link to replaced section in documentation (#16710) --- source/_integrations/spotify.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/spotify.markdown b/source/_integrations/spotify.markdown index 52618769f9d..adda3ba816f 100644 --- a/source/_integrations/spotify.markdown +++ b/source/_integrations/spotify.markdown @@ -83,7 +83,7 @@ modification to the `configuration.yaml` file is needed. Multiple Spotify accounts can be linked to a _single_ Spotify application. To add an additional Spotify account to Home Assistant, go to the Spotify website and log out, then repeat _only_ the steps -in the [Activating the Spotify integration](#activating-the-spotify-integration) section. +in the [Configuration](#configuration) section. ## Playing Spotify playlists From a11076376c9b4ee339711c35a9e7071a84b4bbdd Mon Sep 17 00:00:00 2001 From: Philip Allgaier Date: Tue, 23 Feb 2021 12:55:21 +0100 Subject: [PATCH 4/4] KNX docs improvements (#16708) --- source/_integrations/knx.markdown | 22 +++++++++++----------- 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/source/_integrations/knx.markdown b/source/_integrations/knx.markdown index 764ac939732..2508ed72b8f 100644 --- a/source/_integrations/knx.markdown +++ b/source/_integrations/knx.markdown @@ -90,7 +90,7 @@ config_file: required: false type: string individual_address: - description: The KNX individual address (IA) that shall be used for routing or if a tunnelling server doesn't assign an IA at connection. + description: The KNX individual address (IA) that shall be used for routing or if a tunneling server doesn't assign an IA at connection. required: false type: string default: "15.15.250" @@ -122,7 +122,7 @@ Under normal conditions no connection configuration should be needed. The integr ### Tunneling -If you want to connect to a sepcific tunnelling server or if the auto detection of the KNX/IP device does not work the IP or/and port of the tunneling device can be configurated. +If you want to connect to a specific tunneling server or if the auto detection of the KNX/IP device does not work the IP or/and port of the tunneling device can be configurated. ```yaml knx: @@ -178,10 +178,10 @@ event_filter: Every telegram that matches the filter with its destination field will be announced on the event bus as a `knx_event` event containing data attributes -- `data` contains the raw payload data (eg. 1 or "[12, 55]"). -- `destination` the KNX group address the telegram is sent to as string (eg. "1/2/3). +- `data` contains the raw payload data (e.g., 1 or "[12, 55]"). +- `destination` the KNX group address the telegram is sent to as string (e.g., "1/2/3). - `direction` the direction of the telegram as string ("Incoming" / "Outgoing"). Currently only incoming telegrams generate the event. -- `source` the KNX indidividual address of the sender as string (eg. "1.2.3"). +- `source` the KNX individual address of the sender as string (e.g., "1.2.3"). - `telegramtype` the APCI service of the telegram. "GroupValueWrite", "GroupValueRead" or "GroupValueResponse" generate a knx_event. ## Services @@ -214,7 +214,7 @@ You can also use the `homeassistant.update_entity` service call to issue GroupVa ### Register Event -The `knx.event_register` service can be used to register (or unregister) group addresses to fire `knx_event` Events. Events for group addresses matching the `event_filter` attribute in `configuration.yaml` can not be unregistered. See [knx_event](#events) +The `knx.event_register` service can be used to register (or unregister) group addresses to fire `knx_event` Events. Events for group addresses matching the `event_filter` attribute in `configuration.yaml` cannot be unregistered. See [knx_event](#events) {% configuration %} address: @@ -275,12 +275,12 @@ entity_id: required: false attribute: description: Attribute of the entity that shall be sent to the KNX bus. If not set (or `None`) the state will be sent. - Eg. for a light the state is eigther "on" or "off". With `attribute` you can expose its "brightness". + For example for a light the state is either "on" or "off". With `attribute` you can expose its "brightness". type: string required: false default: description: Default value to send to the bus if the state or attribute value is `None`. - Eg. a light with state "off" has no brightness attribute so a default value of `0` could be used. + For example a light with state "off" has no brightness attribute so a default value of `0` could be used. If not set (or `None`) no value would be sent to the bus and a GroupReadRequest to the address would return the last known value. type: [boolean, string, integer, float] default: None @@ -384,7 +384,7 @@ name: required: false type: string counter: - description: Set to 2 if your only want the action to be executed if the button was pressed twice. To 3 for three times button pressed. + description: Set to 2 if you only want the action to be executed if the button was pressed twice. Set to 3 for three times button pressed. required: false type: integer default: 1 @@ -657,7 +657,7 @@ move_long_address: required: false type: string move_short_address: - description: KNX group address for moving the cover short time up or down. *DPT 1* + description: KNX group address for moving the cover short time up or down. Used by some covers also as the means to stop the cover, if no dedicated `stop_address` exists on the actuator. *DPT 1* required: false type: string stop_address: @@ -691,7 +691,7 @@ travelling_time_up: default: 25 type: integer invert_position: - description: Set this to `true` if your actuator report fully closed as 0% in KNX. + description: Set this to `true` if your actuator reports fully closed as 0% in KNX. required: false default: false type: boolean