The configurator component allows components to request information from the user. It is currently implemented as the minimum viable product: it supports showing a text, image and button to the user. It will trigger a callback when the button is pressed.
See the source for more details on how to use the configurator component.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/components/tellstick_sensor.html b/components/conversation.html
similarity index 83%
rename from components/tellstick_sensor.html
rename to components/conversation.html
index 5d7fd5ac36..d158bb886a 100644
--- a/components/tellstick_sensor.html
+++ b/components/conversation.html
@@ -9,20 +9,20 @@
- Tellstick Sensors - Home Assistant
+ Conversation - Home Assistant
-
+
-
+
-
+
-
+
@@ -89,24 +89,22 @@
- Tellstick Sensors
+ Conversation
-
Shows the values of that sensors that is connected to your Tellstick.
-
-
To enable it, add the following lines to your configuration.yaml:
+
The conversation component can process sentences into commands for Home Assistant. It is currently limited to parsing commands in the format turn <Friendly Name> <on/off>.
1
-
tellstick_sensor:
+
conversation:
+
When this component is active and you are using a supported browser voice commands will be activated in the frontend. Browse to the demo in Chrome to see it in action.
-
-
-This component is going to be merged into the sensor component.
+
diff --git a/components/chromecast.html b/components/media_player.html
similarity index 81%
rename from components/chromecast.html
rename to components/media_player.html
index 072cc6f9d4..63fabd8508 100644
--- a/components/chromecast.html
+++ b/components/media_player.html
@@ -9,20 +9,20 @@
- Chromecast - Home Assistant
+ Media Player - Home Assistant
-
+
-
+
-
+
-
+
@@ -89,25 +89,29 @@
- Chromecast
+ Media Player
-
+
Interacts with media players on your network. Currently only supports Chromecasts. These will be automatically discovered if you setup the discovery component. Can also be forced to load by adding the following lines to your configuration.yaml:
+
+
1
+2
+
media_player:
+ platform: chromecast
+
+
+
+
+
Chromecasts have recently received a new API which is not yet supported by Home Assistant. Therefore we currently can only detect them and do not know what they are up to.
-
Interacts with Chromecasts on your network. Will be automatically discovered if you setup the discovery component. Can also be forced to load by adding the following lines to your configuration.yaml:
-
-
1
-
chromecast:
-
-
Services
Media control services
@@ -126,7 +130,7 @@ Chromecasts have recently received a new API which is not yet supported by Home
entity_id
yes
-
Target a specific chromecast. Defaults to all.
+
Target a specific media player. Defaults to all.
@@ -134,11 +138,11 @@ Chromecasts have recently received a new API which is not yet supported by Home
Media play services
-
There are three services to start playing YouTube video’s on the ChromeCast.
+
There are three services to start playing YouTube video’s on the media player.
-
Service chromecast/play_youtube_video
+
Service media_player/play_youtube_video
-
Service to start playing a YouTube vide on the Chromecast.
+
Service to start playing a YouTube vide on the media player.
@@ -152,7 +156,7 @@ Chromecasts have recently received a new API which is not yet supported by Home
entity_id
yes
-
Target a specific chromecast. Defaults to all.
+
Target a specific media player. Defaults to all.
video
@@ -163,9 +167,9 @@ Chromecasts have recently received a new API which is not yet supported by Home
-
Service chromecast/start_fireplace and chromecast/start_epic_sax
+
Service media_player/start_fireplace and media_player/start_epic_sax
-
Will either start a fireplace or Epic Sax Guy 10h on the Chromecast.
+
Will either start a fireplace or Epic Sax Guy 10h on the media player.
@@ -179,7 +183,7 @@ Chromecasts have recently received a new API which is not yet supported by Home