jeans/home-assistant.io
jeans/home-assistant.io
1
0
Fork 0
mirror of https://github.com/home-assistant/home-assistant.io.git synced 2025-07-21 08:16:53 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge branch 'current' into next

Browse Source
This commit is contained in:
Franck Nijhof 2021-02-23 14:40:59 +01:00
commit 0f1b6d5b7d
No known key found for this signature in database
GPG Key ID: D62583BA8AB11CA3
4 changed files with 15 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
.github/workflows/test.yml vendored
View File

@ -10,7 +10,7 @@ jobs:
- name: Check out files from GitHub - name: Check out files from GitHub
uses: actions/checkout@v2 uses: actions/checkout@v2
- name: Setting up Node.js ${{ matrix.node-version }} - name: Setting up Node.js ${{ matrix.node-version }}
uses: actions/setup-node@v2.1.4 uses: actions/setup-node@v2.1.5
with: with:
node-version: 12.x node-version: 12.x
- name: Setup NPM cache - name: Setup NPM cache
@ -33,7 +33,7 @@ jobs:
- name: Check out files from GitHub - name: Check out files from GitHub
uses: actions/checkout@v2 uses: actions/checkout@v2
- name: Setting up Node.js ${{ matrix.node-version }} - name: Setting up Node.js ${{ matrix.node-version }}
uses: actions/setup-node@v2.1.4 uses: actions/setup-node@v2.1.5
with: with:
node-version: 12.x node-version: 12.x
- name: Setup NPM cache - name: Setup NPM cache

2
source/_includes/common-tasks/development_version.md
View File

@ -51,7 +51,7 @@ ha os update --version {{current_version}}
3. Download and install the version you want 3. Download and install the version you want
```bash ```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. 4. When that is complete restart the service for it to use the new files.

22
source/_integrations/knx.markdown
View File

@ -92,7 +92,7 @@ config_file:
required: false required: false
type: string type: string
individual_address: 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 required: false
type: string type: string
default: "15.15.250" default: "15.15.250"
@ -124,7 +124,7 @@ Under normal conditions no connection configuration should be needed. The integr
### Tunneling ### 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 ```yaml
knx: knx:
@ -180,10 +180,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 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]"). - `data` contains the raw payload data (e.g., 1 or "[12, 55]").
- `destination` the KNX group address the telegram is sent to as string (eg. "1/2/3). - `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"). - `direction` the direction of the telegram as string ("Incoming" / "Outgoing").
- `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. - `telegramtype` the APCI service of the telegram. "GroupValueWrite", "GroupValueRead" or "GroupValueResponse" generate a knx_event.
## Services ## Services
@ -260,7 +260,7 @@ automation:
### Register Event ### 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 %} {% configuration %}
address: address:
@ -333,12 +333,12 @@ entity_id:
required: false required: false
attribute: attribute:
description: Attribute of the entity that shall be sent to the KNX bus. If not set (or `None`) the state will be sent. 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 type: string
required: false required: false
default: default:
description: Default value to send to the bus if the state or attribute value is `None`. 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. 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] type: [boolean, string, integer, float]
default: None default: None
@ -442,7 +442,7 @@ name:
required: false required: false
type: string type: string
counter: 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 required: false
type: integer type: integer
default: 1 default: 1
@ -720,7 +720,7 @@ move_long_address:
required: false required: false
type: string type: string
move_short_address: 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 required: false
type: string type: string
stop_address: stop_address:
@ -754,7 +754,7 @@ travelling_time_up:
default: 25 default: 25
type: integer type: integer
invert_position: 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 required: false
default: false default: false
type: boolean type: boolean

2
source/_integrations/spotify.markdown
View File

@ -83,7 +83,7 @@ modification to the `configuration.yaml` file is needed. Multiple Spotify
accounts can be linked to a _single_ Spotify application. 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 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 ## Playing Spotify playlists