Skip to content

Commit

Permalink
Sync notes
Browse files Browse the repository at this point in the history
  • Loading branch information
Koenkk committed Aug 11, 2020
1 parent fee7c1f commit 7e24549
Show file tree
Hide file tree
Showing 245 changed files with 5,822 additions and 9 deletions.
40 changes: 40 additions & 0 deletions docgen/device_page_notes.js
Original file line number Diff line number Diff line change
Expand Up @@ -1307,6 +1307,46 @@ e.g. \`1\` would add 1 to the pressure reported by the device; default \`0\`.
* \`transition\`: Controls the transition time (in seconds) of on/off, brightness,
color temperature (if applicable) and color (if applicable) changes. Defaults to \`0\` (no transition).
Note that this value is overridden if a \`transition\` value is present in the MQTT command payload.
`,
},
{
model: ['9GED18000-009'],
note: `
### Pin code usage
To retrieve the state, send a \`get\` message to the device topic (\`zigbee2mqtt/[DEVICE_FRIENDLY_NAME]/get\`) with the body \`{"pin_code":{"user":0}}\`. To set, sent a \`set\` message to the device topic (\`zigbee2mqtt/[DEVICE_FRIENDLY_NAME]/set\`) with the body \`{"pin_code":{"user":0,"pin_code":1234}}\`. To clear a code, call \`set\` but omit the value for \`pin_code\`.
### Device type specific configuration
*[How to use device type specific configuration](../information/configuration.md)*
* \`expose_pin\`: Allows to retrieve the \`pin_code\` value, rather than just user status (\`available\`/\`enabled\`), for \`pin_code\` endpoints (default: \`false\`)
`,
},
{
supports: ['color'],
notModel: ['324131092621', 'ICZB-KPD18S', 'ICZB-KPD14S', 'TYZS1L'],
note: `
* \`hue_correction\`: (optional) Corrects hue values based on a correction map for matching color
rendition to other lights. Provide a minimum of 2 data sets in the correction map. To build a map:
* choose one of your other lights to be the color reference
* send a sample color to both lights (reference and non-reference)
* modify hue value for non-reference light until it color matches the reference light
* take note of the in and out values, where
* \`in\` is the hue value you sent to your reference light
* \`out\` is the hue value you had to dial your non-reference light to
* repeat with a few other sample colors (4-5 should suffice)
**Example correction map:**
\`\`\`yaml
hue_correction:
- in: 28
out: 45
- in: 89
out: 109
- in: 184
out: 203
- in: 334
out: 318
\`\`\`
`,
},
{
Expand Down
24 changes: 24 additions & 0 deletions docs/devices/07004D.md
Original file line number Diff line number Diff line change
Expand Up @@ -27,6 +27,30 @@ color temperature (if applicable) and color (if applicable) changes. Defaults to
Note that this value is overridden if a `transition` value is present in the MQTT command payload.


* `hue_correction`: (optional) Corrects hue values based on a correction map for matching color
rendition to other lights. Provide a minimum of 2 data sets in the correction map. To build a map:
* choose one of your other lights to be the color reference
* send a sample color to both lights (reference and non-reference)
* modify hue value for non-reference light until it color matches the reference light
* take note of the in and out values, where
* `in` is the hue value you sent to your reference light
* `out` is the hue value you had to dial your non-reference light to
* repeat with a few other sample colors (4-5 should suffice)

**Example correction map:**
```yaml
hue_correction:
- in: 28
out: 45
- in: 89
out: 109
- in: 184
out: 203
- in: 334
out: 318
```


## Manual Home Assistant configuration
Although Home Assistant integration through [MQTT discovery](../integration/home_assistant) is preferred,
manual integration is possible with the following configuration:
Expand Down
24 changes: 24 additions & 0 deletions docs/devices/07008L.md
Original file line number Diff line number Diff line change
Expand Up @@ -31,6 +31,30 @@ color temperature (if applicable) and color (if applicable) changes. Defaults to
Note that this value is overridden if a `transition` value is present in the MQTT command payload.


* `hue_correction`: (optional) Corrects hue values based on a correction map for matching color
rendition to other lights. Provide a minimum of 2 data sets in the correction map. To build a map:
* choose one of your other lights to be the color reference
* send a sample color to both lights (reference and non-reference)
* modify hue value for non-reference light until it color matches the reference light
* take note of the in and out values, where
* `in` is the hue value you sent to your reference light
* `out` is the hue value you had to dial your non-reference light to
* repeat with a few other sample colors (4-5 should suffice)

**Example correction map:**
```yaml
hue_correction:
- in: 28
out: 45
- in: 89
out: 109
- in: 184
out: 203
- in: 334
out: 318
```


## Manual Home Assistant configuration
Although Home Assistant integration through [MQTT discovery](../integration/home_assistant) is preferred,
manual integration is possible with the following configuration:
Expand Down
24 changes: 24 additions & 0 deletions docs/devices/07115L.md
Original file line number Diff line number Diff line change
Expand Up @@ -27,6 +27,30 @@ color temperature (if applicable) and color (if applicable) changes. Defaults to
Note that this value is overridden if a `transition` value is present in the MQTT command payload.


* `hue_correction`: (optional) Corrects hue values based on a correction map for matching color
rendition to other lights. Provide a minimum of 2 data sets in the correction map. To build a map:
* choose one of your other lights to be the color reference
* send a sample color to both lights (reference and non-reference)
* modify hue value for non-reference light until it color matches the reference light
* take note of the in and out values, where
* `in` is the hue value you sent to your reference light
* `out` is the hue value you had to dial your non-reference light to
* repeat with a few other sample colors (4-5 should suffice)

**Example correction map:**
```yaml
hue_correction:
- in: 28
out: 45
- in: 89
out: 109
- in: 184
out: 203
- in: 334
out: 318
```


## Manual Home Assistant configuration
Although Home Assistant integration through [MQTT discovery](../integration/home_assistant) is preferred,
manual integration is possible with the following configuration:
Expand Down
24 changes: 24 additions & 0 deletions docs/devices/100.110.39.md
Original file line number Diff line number Diff line change
Expand Up @@ -27,6 +27,30 @@ color temperature (if applicable) and color (if applicable) changes. Defaults to
Note that this value is overridden if a `transition` value is present in the MQTT command payload.


* `hue_correction`: (optional) Corrects hue values based on a correction map for matching color
rendition to other lights. Provide a minimum of 2 data sets in the correction map. To build a map:
* choose one of your other lights to be the color reference
* send a sample color to both lights (reference and non-reference)
* modify hue value for non-reference light until it color matches the reference light
* take note of the in and out values, where
* `in` is the hue value you sent to your reference light
* `out` is the hue value you had to dial your non-reference light to
* repeat with a few other sample colors (4-5 should suffice)

**Example correction map:**
```yaml
hue_correction:
- in: 28
out: 45
- in: 89
out: 109
- in: 184
out: 203
- in: 334
out: 318
```


## Manual Home Assistant configuration
Although Home Assistant integration through [MQTT discovery](../integration/home_assistant) is preferred,
manual integration is possible with the following configuration:
Expand Down
24 changes: 24 additions & 0 deletions docs/devices/100.110.51.md
Original file line number Diff line number Diff line change
Expand Up @@ -27,6 +27,30 @@ color temperature (if applicable) and color (if applicable) changes. Defaults to
Note that this value is overridden if a `transition` value is present in the MQTT command payload.


* `hue_correction`: (optional) Corrects hue values based on a correction map for matching color
rendition to other lights. Provide a minimum of 2 data sets in the correction map. To build a map:
* choose one of your other lights to be the color reference
* send a sample color to both lights (reference and non-reference)
* modify hue value for non-reference light until it color matches the reference light
* take note of the in and out values, where
* `in` is the hue value you sent to your reference light
* `out` is the hue value you had to dial your non-reference light to
* repeat with a few other sample colors (4-5 should suffice)

**Example correction map:**
```yaml
hue_correction:
- in: 28
out: 45
- in: 89
out: 109
- in: 184
out: 203
- in: 334
out: 318
```


## Manual Home Assistant configuration
Although Home Assistant integration through [MQTT discovery](../integration/home_assistant) is preferred,
manual integration is possible with the following configuration:
Expand Down
24 changes: 24 additions & 0 deletions docs/devices/100.424.11.md
Original file line number Diff line number Diff line change
Expand Up @@ -27,6 +27,30 @@ color temperature (if applicable) and color (if applicable) changes. Defaults to
Note that this value is overridden if a `transition` value is present in the MQTT command payload.


* `hue_correction`: (optional) Corrects hue values based on a correction map for matching color
rendition to other lights. Provide a minimum of 2 data sets in the correction map. To build a map:
* choose one of your other lights to be the color reference
* send a sample color to both lights (reference and non-reference)
* modify hue value for non-reference light until it color matches the reference light
* take note of the in and out values, where
* `in` is the hue value you sent to your reference light
* `out` is the hue value you had to dial your non-reference light to
* repeat with a few other sample colors (4-5 should suffice)

**Example correction map:**
```yaml
hue_correction:
- in: 28
out: 45
- in: 89
out: 109
- in: 184
out: 203
- in: 334
out: 318
```


## Manual Home Assistant configuration
Although Home Assistant integration through [MQTT discovery](../integration/home_assistant) is preferred,
manual integration is possible with the following configuration:
Expand Down
24 changes: 24 additions & 0 deletions docs/devices/10011725.md
Original file line number Diff line number Diff line change
Expand Up @@ -27,6 +27,30 @@ color temperature (if applicable) and color (if applicable) changes. Defaults to
Note that this value is overridden if a `transition` value is present in the MQTT command payload.


* `hue_correction`: (optional) Corrects hue values based on a correction map for matching color
rendition to other lights. Provide a minimum of 2 data sets in the correction map. To build a map:
* choose one of your other lights to be the color reference
* send a sample color to both lights (reference and non-reference)
* modify hue value for non-reference light until it color matches the reference light
* take note of the in and out values, where
* `in` is the hue value you sent to your reference light
* `out` is the hue value you had to dial your non-reference light to
* repeat with a few other sample colors (4-5 should suffice)

**Example correction map:**
```yaml
hue_correction:
- in: 28
out: 45
- in: 89
out: 109
- in: 184
out: 203
- in: 334
out: 318
```


## Manual Home Assistant configuration
Although Home Assistant integration through [MQTT discovery](../integration/home_assistant) is preferred,
manual integration is possible with the following configuration:
Expand Down
24 changes: 24 additions & 0 deletions docs/devices/1741830P7.md
Original file line number Diff line number Diff line change
Expand Up @@ -75,6 +75,30 @@ color temperature (if applicable) and color (if applicable) changes. Defaults to
Note that this value is overridden if a `transition` value is present in the MQTT command payload.


* `hue_correction`: (optional) Corrects hue values based on a correction map for matching color
rendition to other lights. Provide a minimum of 2 data sets in the correction map. To build a map:
* choose one of your other lights to be the color reference
* send a sample color to both lights (reference and non-reference)
* modify hue value for non-reference light until it color matches the reference light
* take note of the in and out values, where
* `in` is the hue value you sent to your reference light
* `out` is the hue value you had to dial your non-reference light to
* repeat with a few other sample colors (4-5 should suffice)

**Example correction map:**
```yaml
hue_correction:
- in: 28
out: 45
- in: 89
out: 109
- in: 184
out: 203
- in: 334
out: 318
```


## OTA updates
This device supports OTA updates, for more information see [OTA updates](../information/ota_updates.md).

Expand Down
24 changes: 24 additions & 0 deletions docs/devices/1742930P7.md
Original file line number Diff line number Diff line change
Expand Up @@ -75,6 +75,30 @@ color temperature (if applicable) and color (if applicable) changes. Defaults to
Note that this value is overridden if a `transition` value is present in the MQTT command payload.


* `hue_correction`: (optional) Corrects hue values based on a correction map for matching color
rendition to other lights. Provide a minimum of 2 data sets in the correction map. To build a map:
* choose one of your other lights to be the color reference
* send a sample color to both lights (reference and non-reference)
* modify hue value for non-reference light until it color matches the reference light
* take note of the in and out values, where
* `in` is the hue value you sent to your reference light
* `out` is the hue value you had to dial your non-reference light to
* repeat with a few other sample colors (4-5 should suffice)

**Example correction map:**
```yaml
hue_correction:
- in: 28
out: 45
- in: 89
out: 109
- in: 184
out: 203
- in: 334
out: 318
```


## OTA updates
This device supports OTA updates, for more information see [OTA updates](../information/ota_updates.md).

Expand Down
24 changes: 24 additions & 0 deletions docs/devices/1743030P7.md
Original file line number Diff line number Diff line change
Expand Up @@ -75,6 +75,30 @@ color temperature (if applicable) and color (if applicable) changes. Defaults to
Note that this value is overridden if a `transition` value is present in the MQTT command payload.


* `hue_correction`: (optional) Corrects hue values based on a correction map for matching color
rendition to other lights. Provide a minimum of 2 data sets in the correction map. To build a map:
* choose one of your other lights to be the color reference
* send a sample color to both lights (reference and non-reference)
* modify hue value for non-reference light until it color matches the reference light
* take note of the in and out values, where
* `in` is the hue value you sent to your reference light
* `out` is the hue value you had to dial your non-reference light to
* repeat with a few other sample colors (4-5 should suffice)

**Example correction map:**
```yaml
hue_correction:
- in: 28
out: 45
- in: 89
out: 109
- in: 184
out: 203
- in: 334
out: 318
```


## OTA updates
This device supports OTA updates, for more information see [OTA updates](../information/ota_updates.md).

Expand Down
24 changes: 24 additions & 0 deletions docs/devices/1743130P7.md
Original file line number Diff line number Diff line change
Expand Up @@ -75,6 +75,30 @@ color temperature (if applicable) and color (if applicable) changes. Defaults to
Note that this value is overridden if a `transition` value is present in the MQTT command payload.


* `hue_correction`: (optional) Corrects hue values based on a correction map for matching color
rendition to other lights. Provide a minimum of 2 data sets in the correction map. To build a map:
* choose one of your other lights to be the color reference
* send a sample color to both lights (reference and non-reference)
* modify hue value for non-reference light until it color matches the reference light
* take note of the in and out values, where
* `in` is the hue value you sent to your reference light
* `out` is the hue value you had to dial your non-reference light to
* repeat with a few other sample colors (4-5 should suffice)

**Example correction map:**
```yaml
hue_correction:
- in: 28
out: 45
- in: 89
out: 109
- in: 184
out: 203
- in: 334
out: 318
```


## OTA updates
This device supports OTA updates, for more information see [OTA updates](../information/ota_updates.md).

Expand Down
Loading

0 comments on commit 7e24549

Please sign in to comment.