Merge branch 'current' into next

This commit is contained in:
Franck Nijhof 2021-12-09 13:26:30 +01:00
commit c0bbcd7f82
No known key found for this signature in database
GPG Key ID: D62583BA8AB11CA3
13 changed files with 106 additions and 36 deletions

42
package-lock.json generated
View File

@ -10,9 +10,9 @@
"devDependencies": {
"remark-cli": "^10.0.1",
"remark-frontmatter": "^4.0.1",
"remark-lint": "^9.1.0",
"remark-lint-fenced-code-flag": "^3.1.0",
"remark-lint-no-shell-dollars": "^3.1.0",
"remark-lint": "^9.1.1",
"remark-lint-fenced-code-flag": "^3.1.1",
"remark-lint-no-shell-dollars": "^3.1.1",
"remark-stringify": "^10.0.2",
"textlint": "^12.1.0",
"textlint-rule-common-misspellings": "^1.0.1",
@ -4881,9 +4881,9 @@
}
},
"node_modules/remark-lint": {
"version": "9.1.0",
"resolved": "https://registry.npmjs.org/remark-lint/-/remark-lint-9.1.0.tgz",
"integrity": "sha512-47ZaPj1HSs17nqsu3CPg4nIhaj+XTEXJM9cpFybhyA4lzVRZiRXy43BokbEjBt0f1fhY3coQoOh16jJeGBvrJg==",
"version": "9.1.1",
"resolved": "https://registry.npmjs.org/remark-lint/-/remark-lint-9.1.1.tgz",
"integrity": "sha512-zhe6twuqgkx/9KgZyNyaO0cceA4jQuJcyzMOBC+JZiAzMN6mFUmcssWZyY30ko8ut9vQDMX/pyQnolGn+Fg/Tw==",
"dev": true,
"dependencies": {
"@types/mdast": "^3.0.0",
@ -4896,9 +4896,9 @@
}
},
"node_modules/remark-lint-fenced-code-flag": {
"version": "3.1.0",
"resolved": "https://registry.npmjs.org/remark-lint-fenced-code-flag/-/remark-lint-fenced-code-flag-3.1.0.tgz",
"integrity": "sha512-s96DWERWUeDi3kcDbW6TQo4vRUsGJUNhT1XEsmUzYlwJJ+2uGit9O5dAxvEnwF3gZxp/09hPsQ+QSxilC1sxLg==",
"version": "3.1.1",
"resolved": "https://registry.npmjs.org/remark-lint-fenced-code-flag/-/remark-lint-fenced-code-flag-3.1.1.tgz",
"integrity": "sha512-FFVZmYsBccKIIEgOtgdZEpQdARtAat1LTLBydnIpyNIvcntzWwtrtlj9mtjL8ZoSRre8HtwmEnBFyOfmM/NWaA==",
"dev": true,
"dependencies": {
"@types/mdast": "^3.0.0",
@ -4914,9 +4914,9 @@
}
},
"node_modules/remark-lint-no-shell-dollars": {
"version": "3.1.0",
"resolved": "https://registry.npmjs.org/remark-lint-no-shell-dollars/-/remark-lint-no-shell-dollars-3.1.0.tgz",
"integrity": "sha512-f4+NPey3yzd9TpDka5Bs3W+MMJBPz6bQ7zK3M9Qc133lqZ81hKMGVRrOBafS1RNqD5htLZbbGyCoJa476QtW1w==",
"version": "3.1.1",
"resolved": "https://registry.npmjs.org/remark-lint-no-shell-dollars/-/remark-lint-no-shell-dollars-3.1.1.tgz",
"integrity": "sha512-Q3Ad1TaOPxbYog5+Of/quPG3Fy+dMKiHjT8KsU7NDiHG6YJOnAJ3f3w+y13CIlNIaKc/MrisgcthhrZ7NsgXfA==",
"dev": true,
"dependencies": {
"@types/mdast": "^3.0.0",
@ -9698,9 +9698,9 @@
}
},
"remark-lint": {
"version": "9.1.0",
"resolved": "https://registry.npmjs.org/remark-lint/-/remark-lint-9.1.0.tgz",
"integrity": "sha512-47ZaPj1HSs17nqsu3CPg4nIhaj+XTEXJM9cpFybhyA4lzVRZiRXy43BokbEjBt0f1fhY3coQoOh16jJeGBvrJg==",
"version": "9.1.1",
"resolved": "https://registry.npmjs.org/remark-lint/-/remark-lint-9.1.1.tgz",
"integrity": "sha512-zhe6twuqgkx/9KgZyNyaO0cceA4jQuJcyzMOBC+JZiAzMN6mFUmcssWZyY30ko8ut9vQDMX/pyQnolGn+Fg/Tw==",
"dev": true,
"requires": {
"@types/mdast": "^3.0.0",
@ -9709,9 +9709,9 @@
}
},
"remark-lint-fenced-code-flag": {
"version": "3.1.0",
"resolved": "https://registry.npmjs.org/remark-lint-fenced-code-flag/-/remark-lint-fenced-code-flag-3.1.0.tgz",
"integrity": "sha512-s96DWERWUeDi3kcDbW6TQo4vRUsGJUNhT1XEsmUzYlwJJ+2uGit9O5dAxvEnwF3gZxp/09hPsQ+QSxilC1sxLg==",
"version": "3.1.1",
"resolved": "https://registry.npmjs.org/remark-lint-fenced-code-flag/-/remark-lint-fenced-code-flag-3.1.1.tgz",
"integrity": "sha512-FFVZmYsBccKIIEgOtgdZEpQdARtAat1LTLBydnIpyNIvcntzWwtrtlj9mtjL8ZoSRre8HtwmEnBFyOfmM/NWaA==",
"dev": true,
"requires": {
"@types/mdast": "^3.0.0",
@ -9723,9 +9723,9 @@
}
},
"remark-lint-no-shell-dollars": {
"version": "3.1.0",
"resolved": "https://registry.npmjs.org/remark-lint-no-shell-dollars/-/remark-lint-no-shell-dollars-3.1.0.tgz",
"integrity": "sha512-f4+NPey3yzd9TpDka5Bs3W+MMJBPz6bQ7zK3M9Qc133lqZ81hKMGVRrOBafS1RNqD5htLZbbGyCoJa476QtW1w==",
"version": "3.1.1",
"resolved": "https://registry.npmjs.org/remark-lint-no-shell-dollars/-/remark-lint-no-shell-dollars-3.1.1.tgz",
"integrity": "sha512-Q3Ad1TaOPxbYog5+Of/quPG3Fy+dMKiHjT8KsU7NDiHG6YJOnAJ3f3w+y13CIlNIaKc/MrisgcthhrZ7NsgXfA==",
"dev": true,
"requires": {
"@types/mdast": "^3.0.0",

View File

@ -6,9 +6,9 @@
"devDependencies": {
"remark-cli": "^10.0.1",
"remark-frontmatter": "^4.0.1",
"remark-lint": "^9.1.0",
"remark-lint-fenced-code-flag": "^3.1.0",
"remark-lint-no-shell-dollars": "^3.1.0",
"remark-lint": "^9.1.1",
"remark-lint-fenced-code-flag": "^3.1.1",
"remark-lint-no-shell-dollars": "^3.1.1",
"remark-stringify": "^10.0.2",
"textlint": "^12.1.0",
"textlint-rule-common-misspellings": "^1.0.1",

View File

@ -268,7 +268,7 @@ alarm_control_panel:
### Configurations with remote code validation
The example below shows a full configuration with local code validation and `command_template`.
The example below shows a full configuration with remote code validation and `command_template`.
{% raw %}

View File

@ -55,7 +55,7 @@ There is currently support for the following device types within Home Assistant:
## Recommended way of running deCONZ
An official add-on for deCONZ is available in the Home Assistant add-on store.
Otherwise, use [community container](https://hub.docker.com/r/marthoc/deconz/) by Marthoc for your deCONZ needs.
Otherwise, use [community container](https://github.com/deconz-community/deconz-docker) for your deCONZ needs.
### Supported devices

View File

@ -31,7 +31,7 @@ There are two Dexcom Share servers, `US` for United States customers, and `OUS`
### Unit of measurement
The integrations allows both `mg/dL` and `mmol/l` units of measurement for blood glucose values. To change your preferred unit of measurement, got to **Configuration** >> **Devices & Services** in the UI, and click `OPTIONS`.
The integrations allows both `mg/dL` and `mmol/l` units of measurement for blood glucose values. To change your preferred unit of measurement, go to **Configuration** >> **Devices & Services** in the UI, and click `OPTIONS`.
## Sensor

View File

@ -73,3 +73,17 @@ To experiment with values:
```bash
ffmpeg -i YOUR_INPUT -vn -filter:a silencedetect=n=-30dB:d=1 -f null -
```
### Troubleshooting
#### Unresponsive after a while
If the noise sensor becomes unresponsive, make sure you have `extra_arguments: -nostats` in the configuration.
```yaml
# Example configuration.yaml entry
binary_sensor:
- platform: ffmpeg_noise
input: FFMPEG_SUPPORTED_INPUT
extra_arguments: -nostats
```

View File

@ -105,6 +105,53 @@ A list of RGB colors can be entered to create an effect. The effect speed can be
**Custom Effect Type**\
This determines the transition between each color.
### Supported Models
The following models have been tested with integration.
| Model | Description | Notes |
| ----- | --------------------------- | ------------------------------- |
| 0x04 | UFO Controller RGBW | |
| 0x06 | Controller RGBW | |
| 0x07 | Controller RGBCW | |
| 0x08 | Controller RGB with MIC | |
| 0x09 | Switch 1c | |
| 0x0E | Floor Lamp RGBCW | |
| 0x1C | Table Light CCT | |
| 0x21 | Bulb Dimmable | |
| 0x25 | Controller RGB/WW/CW | Supports RGB,RGBW,RGBWW,CW,DIM |
| 0x33 | Controller RGB | |
| 0x35 | Bulb RGBCW | |
| 0x41 | Controller Dimmable | |
| 0x44 | Bulb RGBW | |
| 0x54 | Downlight RGBW | |
| 0x93 | Switch 1c | |
| 0x94 | Switch 1c Watt | |
| 0x97 | Socket 1c | |
| 0xA1 | Addressable v1 | |
| 0xA2 | Addressable v2 | |
| 0xA3 | Addressable v3 | |
### Unsupported Models
The following models have not been tested with integration but may work.
| Model | Description | Notes |
| ----- | --------------------------- | ------------------------------- |
| 0x09 | Ceiling Light CCT | |
| 0x10 | Christmas Light | |
| 0x16 | Magnetic Light CCT | |
| 0x17 | Magnetic Light Dimmable | |
| 0x19 | Socket 2 USB | |
| 0x1A | Christmas Light | |
| 0x18 | Plant Light | |
| 0x1B | Spray Light | |
| 0x52 | Bulb CCT | May be discontinued |
| 0x95 | Switch 2c | |
| 0x96 | Switch 4c | |
| 0xD1 | Digital Light | |
| 0xE1 | Ceiling Light | |
| 0xE2 | Ceiling Light Assist | |
### Effects

View File

@ -26,11 +26,12 @@ Reads the configuration files and checks them for correctness, but **does not**
Reloads an integration config entry.
| Service data attribute | Description |
|---------------------------|-------------------------------------------------------|
| `entity_id` | List of entity ids used to reference a config entry. |
| `area_id` | List of area ids used to reference a config entry. |
| `device_id` | List of device ids used to reference a config entry. |
| Service data attribute | Description |
|---------------------------|-------------------------------------------------------------|
| `entity_id` | List of entity ids used to reference a config entry. |
| `area_id` | List of area ids used to reference a config entry. |
| `device_id` | List of device ids used to reference a config entry. |
| `entry_id` | A single config entry id used to reference a config entry. |
### Service `homeassistant.reload_core_config`

View File

@ -158,6 +158,10 @@ homekit:
description: The `entity_id` of a `binary_sensor` entity to use as the doorbell sensor of the camera accessory to enable doorbell notifications. HomeKit will cache an accessory's feature set on the first run so a device must be [reset](#resetting-accessories) for any change to take effect.
required: false
type: string
linked_humidity_sensor:
description: The `entity_id` of a `sensor` entity to use as the humidity sensor of the humidifier/dehumidifier accessory. HomeKit will cache an accessory's feature set on the first run so a device must be [reset](#resetting-accessories) for any change to take effect.
required: false
type: string
linked_motion_sensor:
description: The `entity_id` of a `binary_sensor` entity to use as the motion sensor of the camera accessory to enable motion notifications. HomeKit will cache an accessory's feature set on the first run so a device must be [reset](#resetting-accessories) for any change to take effect.
required: false

View File

@ -174,6 +174,7 @@ configure Pub/Sub.
You now should have everything needed to configure Nest in Home Assistant. Edit your `configuration.yaml` file and populate a `nest` entry in the format of the example configuration below.
```yaml
# Example configuration.yaml entry
nest:
@ -183,6 +184,8 @@ nest:
project_id: PROJECT_ID
```
Then make sure to restart Home Assistant under _**Server Controls**_. {% my server_controls badge %}
{% configuration %}
client_id:
description: Your Device Access or Nest developer client ID.
@ -210,7 +213,7 @@ Once `configuration.yaml` has a valid `nest` entry, you need to add Nest to your
{% details "Manual configuration steps" %}
1. Browse to your Home Assistant instance using.
1. Browse to your Home Assistant instance.
1. In the sidebar click on _**{% my config icon %}**_.
1. From the configuration menu select: _**{% my integrations icon %}**_.
1. In the bottom right, click on the
@ -237,7 +240,7 @@ In this section you will authorize Home Assistant to access your account by gene
1. A new tab opens, allowing you to chooce a Google account. This should be the same developer account you configured above.
1. The *Google Nest permissions* screen will allow you to choose which devices to configure and lets you select devices from multiple homes. You likely want to enable everything, however, you can leave out any feature you do not wish to use with Home Assistant.
1. The *Google Nest permissions* screen will allow you to choose which devices to configure. You likely want to enable everything, however, you can leave out any feature you do not wish to use with Home Assistant. You can select devices from multiple homes using the drop down.
![Screenshot of Nest permissions authorization](/images/integrations/nest/oauth_approve.png)

View File

@ -147,6 +147,7 @@ The list with all known valid keys can be found [here](https://github.com/floria
- TX-55FZ802B
- TX-58AX802B
- TX-58DX700B
- TX-58DX800E
- TX-65CX800E
- TX-65EXW784
- TX-65FX720W

View File

@ -47,4 +47,4 @@ Transfer playback from one player to another.
| Service data attribute | Optional | Description |
| ---------------------- | -------- | ----------- |
| `entity_id` | yes | id of the source player.
| `transfer_name` | no | id of the destination player.
| `transfer_id` | no | id of the destination player.

View File

@ -196,7 +196,7 @@ Available services: `button`, `command`
| Service data attribute | Optional | Description |
| ---------------------- | -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `entity_id` | no | Target a specific webostv media player. |
| `button` | no | Name of the button. Known possible values are `LEFT`, `RIGHT`, `DOWN`, `UP`, `HOME`, `MENU`, `BACK`, `ENTER`, `DASH`, `INFO`, `ASTERISK`, `CC`, `EXIT`, `MUTE`, `RED`, `GREEN`, `BLUE`, `VOLUMEUP`, `VOLUMEDOWN`, `CHANNELUP`, `CHANNELDOWN`, `PLAY`, `PAUSE`, `0`, `1`, `2`, `3`, `4`, `5`, `6`, `7`, `8`, `9` |
| `button` | no | Name of the button. Known possible values are `LEFT`, `RIGHT`, `DOWN`, `UP`, `HOME`, `MENU`, `BACK`, `ENTER`, `DASH`, `INFO`, `ASTERISK`, `CC`, `EXIT`, `MUTE`, `RED`, `GREEN`, `BLUE`, `VOLUMEUP`, `VOLUMEDOWN`, `CHANNELUP`, `CHANNELDOWN`, `PLAY`, `PAUSE`, `NETFLIX`, `GUIDE`, `AMAZON`, `0`, `1`, `2`, `3`, `4`, `5`, `6`, `7`, `8`, `9` |
### Service `webostv.command`