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-19 15:26:59 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge branch 'current' into next

Browse Source
This commit is contained in:
Franck Nijhof 2020-04-22 20:23:22 +02:00
commit c66d51c910
No known key found for this signature in database
GPG Key ID: D62583BA8AB11CA3
9 changed files with 270 additions and 44 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
_config.yml
View File

@ -101,8 +101,8 @@ social:
# Home Assistant release details # Home Assistant release details
current_major_version: 0 current_major_version: 0
current_minor_version: 108 current_minor_version: 108
current_patch_version: 6 current_patch_version: 8
date_released: 2020-04-16 date_released: 2020-04-22
# Either # or the anchor link to latest release notes in the blog post. # Either # or the anchor link to latest release notes in the blog post.
# Must be prefixed with a # and have double quotes around it. # Must be prefixed with a # and have double quotes around it.

12
source/_docs/automation/trigger.markdown
View File

@ -341,7 +341,7 @@ Do not prefix numbers with a zero - using `'00'` instead of '0' for example will
### Webhook trigger ### Webhook trigger
Webhook trigger fires when a web request is made to the webhook endpoint: `/api/webhook/<webhook_id>`. This endpoint does not require authentication besides knowing the webhook id. You can either send encoded form or JSON data, available in the template as either `trigger.json` or `trigger.data`. URL query parameters are available in the template as `trigger.query`. Webhook trigger fires when a web request is made to the webhook endpoint: `/api/webhook/<webhook_id>`. The webhook endpoint is created automatically when you set it as the `webhook_id` in an automation trigger.
```yaml ```yaml
automation: automation:
@ -350,9 +350,15 @@ automation:
webhook_id: some_hook_id webhook_id: some_hook_id
``` ```
You could run the above automation by sending a POST HTTP request to `http://your-home-assistant:8123/api/webhook/some_hook_id`. An example with no data sent to a SSL/TLS secured installation and using the command-line curl program is `curl -d "" https://your-home-assistant:8123/api/webhook/some_hook_id`. You can run this automation by sending an HTTP POST request to `http://your-home-assistant:8123/api/webhook/some_hook_id`. Here is an example using the **curl** command line program, with an empty data payload:
Note that each webhook can only be used in one automation at a time. ```shell
curl -d "" https://your-home-assistant:8123/api/webhook/some_hook_id
```
Webhook endpoints don't require authentication, other than knowing a valid webhook ID. You can send a data payload, either as encoded form data or JSON data. The payload is available in an automation template as either `trigger.json` or `trigger.data`. URL query parameters are available in the template as `trigger.query`. Remember to use an HTTPS URL if you've secured your Home Assistant installation with SSL/TLS.
Note that a given webhook can only be used in one automation at a time. That is, only one automation trigger can use a specific webhook ID.
### Zone trigger ### Zone trigger

151
source/_docs/z-wave/device-specific.markdown
View File

@ -191,9 +191,9 @@ Triple tap on|2|4
5x tap off|1|6 5x tap off|1|6
5x tap on|2|6 5x tap on|2|6
### Zooz Scene Capable On/Off and Dimmer Wall Switches (Zen21v2 & Zen22v2 - Firmware 3.0+ and Zen26 & Zen27 - Firmware 2.0+) ### Zooz Scene Capable On/Off and Dimmer Wall Switches (Zen21v2 & Zen22v2 - Firmware 3.0+, Zen26 & Zen27 - Firmware 2.0+, Zen30 Double Switch)
Many Zooz Zen26/27 switches that have been sold do not have firmware 2.0+. Contact Zooz to obtain the over the air firmware update instructions and new user manual for the switches. Many Zooz switches that have been sold do not have the latest firmwares. Contact Zooz to obtain the over the air firmware update instructions and new user manual for the switches.
Once the firmware is updated, the the new configuration parameters will have to be added to the `zwcfg` file. Replace the existing `COMMAND_CLASS_CONFIGURATION` with the one of the following options (depending on your model of switch): Once the firmware is updated, the the new configuration parameters will have to be added to the `zwcfg` file. Replace the existing `COMMAND_CLASS_CONFIGURATION` with the one of the following options (depending on your model of switch):
@ -587,6 +587,138 @@ Zen27 (Dimmer):
</CommandClass> </CommandClass>
``` ```
Zen30 (Double Switch):
```xml
<CommandClass id="112">
<Value type="list" genre="config" index="1" label="LED Indicator Mode for Dimmer" size="1" min="0" max="3" value="0">
<Help>LED Indicator Mode for Dimmer. Normal has the dimmer (top) LED indication on when the switch is off, off when the switch is on. Default: Normal</Help>
<Item label="Normal" value="0"/>
<Item label="Reverse" value="1"/>
<Item label="Always Off" value="2"/>
<Item label="Always On" value="3"/>
</Value>
<Value type="list" genre="config" index="2" label="LED Indicator Mode for Relay" size="1" min="0" max="3" value="0">
<Help>LED Indicator Mode for Relay. Normal has the relay (bottom) LED indication on when the switch is off, off when the switch is on. Default: Normal</Help>
<Item label="Normal" value="0"/>
<Item label="Reverse" value="1"/>
<Item label="Always Off" value="2"/>
<Item label="Always On" value="3"/>
</Value>
<Value type="list" genre="config" index="3" label="LED Indicator Color for Dimmer" size="1" min="0" max="3" value="0">
<Help>LED Indicater color for Dimmer. White, Blue, Green or Red. Default: White</Help>
<Item label="white" value="0"/>
<Item label="blue" value="1"/>
<Item label="green" value="2"/>
<Item label="red" value="3"/>
</Value>
<Value type="list" genre="config" index="4" label="LED Indicator Color for Relay" size="1" min="0" max="3" value="0">
<Help>LED Indicater color for Relay. White, Blue, Green or Red. Default: White</Help>
<Item label="white" value="0"/>
<Item label="blue" value="1"/>
<Item label="green" value="2"/>
<Item label="red" value="3"/>
</Value>
<Value type="list" genre="config" index="5" label="LED Indicator Brightness for Dimmer" size="1" min="0" max="2" value="1">
<Help>LED Indicater Brightness for Dimmer. Bright (100%), Medium (60%) or Low (30%). Default: Medium</Help>
<Item label="bright" value="0"/>
<Item label="medium" value="1"/>
<Item label="low" value="2"/>
</Value>
<Value type="list" genre="config" index="6" label="LED Indicator Brightness for Relay" size="1" min="0" max="2" value="1">
<Help>LED Indicater Brightness for Relay. Bright (100%), Medium (60%) or Low (30%). Default: Medium</Help>
<Item label="bright" value="0"/>
<Item label="medium" value="1"/>
<Item label="low" value="2"/>
</Value>
<Value type="list" genre="config" index="7" label="LED Indicator Mode for Scene Control" size="1" min="0" max="1" value="1">
<Help>LED Indicator Mode for Scene Control. Enable/Disable LED indicators next to the dimmer lighting up when a scene is selected. Default: disabled</Help>
<Item label="enabled" value="0"/>
<Item label="disabled" value="1"/>
</Value>
<Value type="int" genre="config" index="8" label="Auto Turn-Off Timer for Dimmer" size="4" min="0" max="65535" value="0" units="minutes">
<Help>Auto Turn-Off Timer for Dimmer. Sets the time (in minutes) after which you want the dimmer to automatically turn off once it has been turned on. Range: 1-65535. Default: 0 (disabled)</Help>
</Value>
<Value type="int" genre="config" index="9" label="Auto Turn-On Timer for Dimmer" size="4" min="0" max="65535" value="0" units="minutes">
<Help>Auto Turn-On Timer for Dimmer. Sets the time (in minutes) after which you want the dimmer to automatically turn on once it has been turned off. Range: 1-65535. Default: 0 (disabled)</Help>
</Value>
<Value type="int" genre="config" index="10" label="Auto Turn-Off Timer for Relay" size="4" min="0" max="65535" value="0" units="minutes">
<Help>Auto Turn-Off Timer for Relay. Sets the time (in minutes) after which you want the relay to automatically turn off once it has been turned on. Range: 1-65535. Default: 0 (disabled)</Help>
</Value>
<Value type="int" genre="config" index="11" label="Auto Turn-On Timer for Relay" size="4" min="0" max="65535" value="0" units="minutes">
<Help>Auto Turn-On Timer for Relay. Sets the time (in minutes) after which you want the relay to automatically turn on once it has been turned off. Range: 1-65535. Default: 0 (disabled)</Help>
</Value>
<Value type="list" genre="config" index="12" label="On Off Status After Power Failure" size="1" min="0" max="8" value="3">
<Help>On Off Status After Power Failure. Default: Restore both to prior state</Help>
<Item label="Both forced off" value="0"/>
<Item label="Dimmer off/Relay on" value="1"/>
<Item label="Dimmer on/Relay off" value="2"/>
<Item label="Restore both to prior state" value="3"/>
<Item label="Restore Dimmer/Relay On" value="4"/>
<Item label="Restore Dimme/Relay Off" value="5"/>
<Item label="Dimmer On/Restore Relay" value="6"/>
<Item label="Dimmer Off/Restore Relay" value="7"/>
<Item label="Both forced on" value="8"/>
</Value>
<Value type="byte" genre="config" index="13" label="Ramp Rate Control for Dimmer" size="1" min="0" max="99" value="1" units="seconds">
<Help>Ramp Rate Control for Dimmer. Adjust the ramp rate for your dimmer (fade-in / fade-out effect for on / off operation). Values correspond to the number of seconds it take for the dimmer to reach full brightness or turn off when operated manually. Note that 0 is instant. Default: 1</Help>
</Value>
<Value type="byte" genre="config" index="14" label="Minimum Brightness" size="1" min="1" max="99" value="1" units="%">
<Help>Minimum Brightness. Set the minimum brightness level (in %) for your dimmer. You won't be able to dim the light below the set value. Default: 1</Help>
</Value>
<Value type="byte" genre="config" index="15" label="Maximum Brightness" size="1" min="1" max="99" value="99" units="%">
<Help>Maximum Brightness. Set the maximum brightness level (in %) for your dimmer. You won't be able to add brightness to the light beyond the set value. Default: 99</Help>
</Value>
<Value type="list" genre="config" index="17" label="Double Tap Function for Dimmer" size="1" min="0" max="1" value="0">
<Help>Double Tap Function for Dimmer. When set to full, turns light on to 100%. If set to maximum level, turns light on to % set in Parameter 15. Default: full</Help>
<Item label="full" value="0"/>
<Item label="maximum level" value="1"/>
</Value>
<Value type="list" genre="config" index="18" label="Enable/Disable Double-tap for Dimmer" size="1" min="0" max="2" value="0">
<Help>Enable/Disable Double-tap for Dimmer. Enables/Disables the double-tap fucntion and assign brightness to single tap. enabled: single tap turns on to maximum brightness level. disabled (last level): single tap returns to last brightness level. disabled (full/max level): single tap returns to full brightmess. Default: enabled</Help>
<Item label="enabled" value="0"/>
<Item label="disabled (last level)" value="1"/>
<Item label="disabled (full/max level)" value="2"/>
</Value>
<Value type="list" genre="config" index="19" label="Enable/Disable Load Control for Dimmer" size="1" min="0" max="2" value="1">
<Help>Enable/Disable Load Control for Dimmer (Smart Bulb Setting). Enable or disable direct manual and Z-Wave control of the connected light (works great for smart bulb control). If disabled, the dimmer will no longer control the connected bulb directly but will still send on/off and brightness reports to the hub so you cn use them to create automations for your smart bulbs or other switches. Scenes and other functionality will still be available through the paddles. Default: manual disabled</Help>
<Item label="manual disabled" value="0"/>
<Item label="manual enabled" value="1"/>
<Item label="manual and z-wave disabled" value="2"/>
</Value>
<Value type="list" genre="config" index="20" label="Enable/Disable Load Control for Relay" size="1" min="0" max="2" value="1">
<Help>Enable/Disable Load Control for Relay (Smart Bulb Setting). Enable or disable direct manual and Z-Wave control of the connected light (works great for smart bulb control). If disabled, the relay will no longer control the connected bulb directly but will still send on/off and brightness reports to the hub so you cn use them to create automations for your smart bulbs or other switches. Scenes and other functionality will still be available through the paddles. Default: manual disabled</Help>
<Item label="manual disabled" value="0"/>
<Item label="manual enabled" value="1"/>
<Item label="manual and z-wave disabled" value="2"/>
</Value>
<Value type="byte" genre="config" index="21" label="Manual Dimming Speed" size="1" min="1" max="99" value="4" units="seconds">
<Help>Choose how many seconds it takes for the dimmer to go from 0% to 100% brightness when pressing and holding the paddle. Default: 4.</Help>
</Value>
<Value type="byte" genre="config" index="23" label="Default Brightness Level On for Dimmer" size="1" min="0" max="99" value="0" units="%">
<Help>Default Brightness Level On for Dimmer. Set custom brightness level (in %) for the dimmer to come on to at single tap. Choose 0 for last brightness level. Default: 0.</Help>
</Value>
<Value type="list" genre="config" index="24" label="Behavior of the dimmer when physical control is disabled" size="1" min="0" max="1" value="0">
<Help>Sets behavior of the dimmer when physical control is disabled</Help>
<Item label="Reports on/off and multilevel values back to the hub when buttons are pressed, changes LED indicator to indicate status (default)" value="0"/>
<Item label="Doesn't report on/off or multilevel status back to the hub and doesn't change LED indicator status when physical control for the dimmer is disabled" value="1"/>
</Value>
<Value type="list" genre="config" index="25" label="Behavior of the relay when physical control is disabled" size="1" min="0" max="1" value="0">
<Help>Sets behavior of the relay when physical control is disabled</Help>
<Item label="Reports on/off and multilevel values back to the hub when buttons are pressed, changes LED indicator to indicate status (default)" value="0"/>
<Item label="Doesn't report on/off or multilevel status back to the hub and doesn't change LED indicator status when physical control for the dimmer is disabled" value="1"/>
</Value>
<Value type="byte" genre="config" index="26" label="Night Light Mode" units="" min="0" max="99" value="20">
<Help>Set the brightness level the dimmer will turn on to when off and when lower paddle is held DOWN for a second. Default: 20</Help>
</Value>
<Value type="list" genre="config" index="27" label="Paddle Control" size="1" min="0" max="2" value="0">
<Help>Normal mode: Upper paddle turns the light on, lower paddle turns the light off. Reverse mode: Upper paddle turns the light off, lower paddle turns the light on. Toggle mode: Either paddle toggles the light.</Help>
<Item label="Normal" value="0"/>
<Item label="Reverse" value="1"/>
<Item label="Toggle" value="2"/>
</Value>
</CommandClass>
```
For Zooz switches, you'll need to update (or possibly add) the `COMMAND_CLASS_CENTRAL_SCENE` for each node in your `zwcfg` file with the following: For Zooz switches, you'll need to update (or possibly add) the `COMMAND_CLASS_CENTRAL_SCENE` for each node in your `zwcfg` file with the following:
```xml ```xml
<CommandClass id="91" name="COMMAND_CLASS_CENTRAL_SCENE" version="1" request_flags="4" innif="true" scenecount="0"> <CommandClass id="91" name="COMMAND_CLASS_CENTRAL_SCENE" version="1" request_flags="4" innif="true" scenecount="0">
@ -597,6 +729,17 @@ For Zooz switches, you'll need to update (or possibly add) the `COMMAND_CLASS_CE
</CommandClass> </CommandClass>
``` ```
For the Zooz Zen30 Double Switch, you'll need to add the `COMMAND_CLASS_CENTRAL_SCENE` for each node in your `zwcfg` file with the following:
```xml
<CommandClass id="91" name="COMMAND_CLASS_CENTRAL_SCENE" version="1" request_flags="4" innif="true" scenecount="0">
<Instance index="1" />
<Value type="int" genre="system" instance="1" index="0" label="Scene Count" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="-2147483648" max="2147483647" value="2" />
<Value type="int" genre="user" instance="1" index="1" label="Bottom Button Scene" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="-2147483648" max="2147483647" value="3" />
<Value type="int" genre="user" instance="1" index="2" label="Top Button Scene" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="-2147483648" max="2147483647" value="3" />
<Value type="int" genre="user" instance="1" index="3" label="Relay Button Scene" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="-2147483648" max="2147483647" value="3" />
</CommandClass>
```
Go to the Z-Wave Network Management section in the Home Assistant Configuration, select the node which has just been updated and enable the scene support configuration parameter. Go to the Z-Wave Network Management section in the Home Assistant Configuration, select the node which has just been updated and enable the scene support configuration parameter.
Once this is complete, you should see the following `zwave.scene_activated` events: Once this is complete, you should see the following `zwave.scene_activated` events:
@ -613,6 +756,10 @@ Triple tap on|2|7920
4x tap on|2|7980 4x tap on|2|7980
5x tap off|1|8040 5x tap off|1|8040
5x tap on|2|8040 5x tap on|2|8040
Held off|1|7800
Held on|2|7800
Released off|1|7740
Released on|2|7740
### HomeSeer Switches ### HomeSeer Switches

28
source/_integrations/manual.markdown
View File

@ -1,5 +1,5 @@
--- ---
title: Manual title: Manual Alarm Control Panel
description: Instructions on how to integrate manual alarms into Home Assistant. description: Instructions on how to integrate manual alarms into Home Assistant.
ha_category: ha_category:
- Alarm - Alarm
@ -8,7 +8,7 @@ ha_quality_scale: internal
ha_domain: manual ha_domain: manual
--- ---
The `manual` alarm control panel platform enables you to set manual alarms in Home Assistant. The `manual` alarm control panel platform enables you to create an alarm system in Home Assistant.
## Configuration ## Configuration
@ -85,37 +85,37 @@ armed_custom_bypass/armed_home/armed_away/armed_night/disarmed/triggered:
## State machine ## State machine
The state machine of the manual alarm integration is complex but powerful. The The state machine of the manual alarm integration is complex but powerful. The
transitions are timed according to three values, **delay_time**, **pending_time** transitions are timed according to three values, **delay_time**, **pending_time**
and **trigger_time**. The values in turn can come from the default configuration and **trigger_time**. The values in turn can come from the default configuration
variable or from a state-specific override. variable or from a state-specific override.
When the alarm is armed, its state first goes to **pending** for a number When the alarm is armed, its state first goes to **pending** for a number
of seconds equal to the destination state's **pending_time**, and then of seconds equal to the destination state's **pending_time**, and then
transitions to one of the "armed" states. Note that **code_template** transitions to one of the "armed" states. Note that **code_template**
never receives "pending" in the **to_state** variable; instead, never receives "pending" in the **to_state** variable; instead,
**to_state** contains the state which the user has requested. However, **to_state** contains the state which the user has requested. However,
**from_state** *can* contain "pending". **from_state** *can* contain "pending".
When the alarm is triggered, its state goes to **pending** for a number of When the alarm is triggered, its state goes to **pending** for a number of
seconds equal to the previous state's **delay_time** plus the triggered seconds equal to the previous state's **delay_time** plus the triggered
state's **pending_time**. Then the alarm transitions to the "triggered" state's **pending_time**. Then the alarm transitions to the "triggered"
states. The code is never checked when triggering the alarm, so the states. The code is never checked when triggering the alarm, so the
**to_state** variable of **code_template** cannot ever contain "triggered" **to_state** variable of **code_template** cannot ever contain "triggered"
either; again, **from_state** *can* contain "triggered". either; again, **from_state** *can* contain "triggered".
The alarm remains in the "triggered" state for a number of seconds equal to the The alarm remains in the "triggered" state for a number of seconds equal to the
previous state's **trigger_time**. Then, depending on **disarm_after_trigger**, previous state's **trigger_time**. Then, depending on **disarm_after_trigger**,
it goes back to either the previous state or **disarmed**. If the previous it goes back to either the previous state or **disarmed**. If the previous
state's **trigger_time** is zero, the transition to "triggered" is entirely state's **trigger_time** is zero, the transition to "triggered" is entirely
blocked and the alarm remains in the armed state. blocked and the alarm remains in the armed state.
Each of the settings is useful in different scenarios. **pending_time** gives Each of the settings is useful in different scenarios. **pending_time** gives
you some time to leave the building (for "armed" states) or to disarm the alarm you some time to leave the building (for "armed" states) or to disarm the alarm
(for the "triggered" state). (for the "triggered" state).
**delay_time** can also be used to allow some time to disarm the alarm, but with **delay_time** can also be used to allow some time to disarm the alarm, but with
more flexibility. For example, you could specify a delay time for the more flexibility. For example, you could specify a delay time for the
"armed away" state, in order to avoid triggering the alarm while the "armed away" state, in order to avoid triggering the alarm while the
garage door opens, but not for the "armed home" state. garage door opens, but not for the "armed home" state.
@ -126,9 +126,9 @@ be used for example to sound the siren for a shorter time during the night.
In the configuration example below: In the configuration example below:
- the disarmed state never triggers the alarm; - The `disarmed` state never triggers the alarm.
- the armed_home state will leave no time to leave the building or disarm the alarm; - The `armed_home` state will leave no time to leave the building or disarm the alarm.
- while other states state will give 30 seconds to leave the building before triggering the alarm, and 20 seconds to disarm the alarm when coming back. - The other states will give 30 seconds to leave the building before triggering the alarm, and 20 seconds to disarm the alarm when coming back.
```yaml ```yaml
# Example configuration.yaml entry # Example configuration.yaml entry

1
source/_integrations/panasonic_viera.markdown
View File

@ -91,6 +91,7 @@ script:
### Currently known supported models ### Currently known supported models
- TC-P50ST50
- TC-P60S60 - TC-P60S60
- TC-P65VT30 - TC-P65VT30
- TX-32AS520E - TX-32AS520E

82
source/_integrations/plex.markdown
View File

@ -110,39 +110,79 @@ By default the Plex integration will create Media Player entities for all local,
### Service `play_media` ### Service `play_media`
Plays a song, playlist, TV episode, or video on a connected client. Plays a song, album, artist, playlist, TV show/season/episode, movie, or video on a connected client.
Required fields within the `media_content_id` payloads are marked as such, others are optional.
#### Music #### Music
| Service data attribute | Optional | Description | Example | | Service data attribute | Description |
| ---------------------- | -------- | ------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------- | | ---------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `entity_id` | no | `entity_id` of the client | media_player.theater_plex | | `entity_id` | `entity_id` of the client |
| `media_content_id` | no | Quote escaped JSON with `library_name`, `artist_name`, `album_name`, `track_name`, `shuffle` (0 or 1). | { \\"library_name\\" : \\"My Music\\", \\"artist_name\\" : \\"Adele\\", \\"album_name\\" : \\"25\\", \\"track_name\\" : \\"hello\\", \\"shuffle\\": \\"0\\" } | | `media_content_id` | Quoted JSON containing:<br/><ul><li>`library_name` (Required)</li><li>`artist_name` (Required)</li><li>`album_name`</li><li>`track_name`</li><li>`track_number`</li><li>`shuffle` (0 or 1)</li></ul> |
| `media_content_type` | no | Type of media to play, in this case `MUSIC` | MUSIC | | `media_content_type` | `MUSIC` |
##### Examples:
```yaml
entity_id: media_player.plex_player
media_content_type: MUSIC
media_content_id: '{ "library_name": "Music", "artist_name": "Adele", "album_name": "25", "track_name": "Hello" }'
```
```yaml
entity_id: media_player.plex_player
media_content_type: MUSIC
media_content_id: '{ "library_name": "Music", "artist_name": "Stevie Wonder", "shuffle": "1" }'
```
#### Playlist #### Playlist
| Service data attribute | Optional | Description | Example | | Service data attribute | Description |
| ---------------------- | -------- | ------------------------------------------------------------ | ------------------------------------------------------------------------ | | ---------------------- | --------------------------------------------------------------------------------------------------- |
| `entity_id` | no | `entity_id` of the client | media_player.theater_plex | | `entity_id` | `entity_id` of the client |
| `media_content_id` | no | Quote escaped JSON with `playlist_name`, `shuffle` (0 or 1). | { \\"playlist_name\\" : \\"The Best of Disco\\" \\"shuffle\\": \\"0\\" } | | `media_content_id` | Quoted JSON containing:<br/><ul><li>`playlist_name` (Required)</li><li>`shuffle` (0 or 1)</li></ul> |
| `media_content_type` | no | Type of media to play, in this case `PLAYLIST` | PLAYLIST | | `media_content_type` | `PLAYLIST` |
##### Example:
```yaml
entity_id: media_player.plex_player
media_content_type: PLAYLIST
media_content_id: '{ "playlist_name": "The Best of Disco", "shuffle": "1" }'
```
#### TV Episode #### TV Episode
| Service data attribute | Optional | Description | Example | | Service data attribute | Description |
| ---------------------- | -------- | ----------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- | | ---------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `entity_id` | no | `entity_id` of the client | media_player.theater_plex | | `entity_id` | `entity_id` of the client |
| `media_content_id` | no | Quote escaped JSON with `library_name`, `show_name`, `season_number`, `episode_number`, `shuffle` (0 or 1). | { \\"library_name\\" : \\"Adult TV\\", \\"show_name\\" : \\"Rick and Morty\\", \\"season_number\\" : 2, \\"episode_number\\" : 5, \\"shuffle\\": \\"0\\" } | | `media_content_id` | Quoted JSON containing:<br/><ul><li>`library_name` (Required)</li><li>`show_name` (Required)</li><li>`season_number`</li><li>`episode_number`</li><li>`shuffle` (0 or 1)</li></ul> |
| `media_content_type` | no | Type of media to play, in this case `EPISODE` | EPISODE | | `media_content_type` | `EPISODE` |
##### Examples:
```yaml
entity_id: media_player.plex_player
media_content_type: EPISODE
media_content_id: '{ "library_name": "Adult TV", "show_name": "Rick and Morty", "season_number": 2, "episode_number": 5 }'
```
```yaml
entity_id: media_player.plex_player
media_content_type: EPISODE
media_content_id: '{ "library_name": "Kid TV", "show_name": "Sesame Street", "shuffle": "1" }'
```
#### Video #### Video
| Service data attribute | Optional | Description | Example | | Service data attribute | Description |
| ---------------------- | -------- | ------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------- | | ---------------------- | ------------------------------------------------------------------------------------------------------- |
| `entity_id` | no | `entity_id` of the client | media_player.theater_plex | | `entity_id` | `entity_id` of the client |
| `media_content_id` | no | Quote escaped JSON with `library_name`, `video_name`, `shuffle` (0 or 1). | { \\"library_name\\" : \\"Adult Movies\\", \\"video_name\\" : \\"Blade\\", \\"shuffle\\": \\"0\\" } | | `media_content_id` | Quoted JSON containing:<br/><ul><li>`library_name` (Required)</li><li>`video_name` (Required)</li></ul> |
| `media_content_type` | no | Type of media to play, in this case `VIDEO` | VIDEO | | `media_content_type` | `VIDEO` |
##### Example:
```yaml
entity_id: media_player.plex_player
media_content_type: VIDEO
media_content_id: '{ "library_name": "Adult Movies", "video_name": "Blade" }'
```
### Compatibility ### Compatibility

1
source/_integrations/proliphix.markdown
View File

@ -1,7 +1,6 @@
--- ---
title: Proliphix title: Proliphix
description: Instructions on how to integrate Proliphix thermostats within Home Assistant. description: Instructions on how to integrate Proliphix thermostats within Home Assistant.
logo: proliphix.png
ha_category: ha_category:
- Climate - Climate
ha_release: 0.11 ha_release: 0.11

1
source/_integrations/ripple.markdown
View File

@ -1,7 +1,6 @@
--- ---
title: Ripple title: Ripple
description: Instructions on how to integrate ripple.com data within Home Assistant. description: Instructions on how to integrate ripple.com data within Home Assistant.
logo: ripple.png
ha_category: ha_category:
- Finance - Finance
ha_release: 0.47 ha_release: 0.47

34
source/_posts/2020-04-08-release-108.markdown
View File

@ -543,6 +543,40 @@ These integrations have been removed. The websites for both have changed, causin
[sonos docs]: /integrations/sonos/ [sonos docs]: /integrations/sonos/
[vizio docs]: /integrations/vizio/ [vizio docs]: /integrations/vizio/
## Release 0.108.7 - April 21
- Fix setting up multiple UPSes with NUT in 0.108.x ([@bdraco] - [#34427]) ([nut docs])
- Cloud do checks during setup ([@balloob] - [#33507]) ([cloud docs])
- Rollback modbus to version 0.107.7 keep new functionality ([@janiversen] - [#34287]) ([modbus docs])
- Ensure nexia state file is in a writable location ([@bdraco] - [#34325]) ([nexia docs])
- Modify requirements for CameraStreamController in Alexa ([@ochlocracy] - [#34470]) ([alexa docs])
- Fix cloud binary_sensor & TTS/STT ([@pvizeli] - [#34505])
[#33507]: https://github.com/home-assistant/core/pull/33507
[#34287]: https://github.com/home-assistant/core/pull/34287
[#34325]: https://github.com/home-assistant/core/pull/34325
[#34427]: https://github.com/home-assistant/core/pull/34427
[#34470]: https://github.com/home-assistant/core/pull/34470
[#34505]: https://github.com/home-assistant/core/pull/34505
[@balloob]: https://github.com/balloob
[@bdraco]: https://github.com/bdraco
[@janiversen]: https://github.com/janiversen
[@ochlocracy]: https://github.com/ochlocracy
[@pvizeli]: https://github.com/pvizeli
[alexa docs]: /integrations/alexa/
[cloud docs]: /integrations/cloud/
[modbus docs]: /integrations/modbus/
[nexia docs]: /integrations/nexia/
[nut docs]: /integrations/nut/
## Release 0.108.8 - April 22
- Bump hass-nabucasa 0.34.1 ([@pvizeli] - [#34480]) ([cloud docs])
[#34480]: https://github.com/home-assistant/core/pull/34480
[@pvizeli]: https://github.com/pvizeli
[cloud docs]: /integrations/cloud/
## All changes ## All changes
<details> <details>