This is a fully event-based component. Any event sent by the Envisalink device will be immediately reflected within Home Assistant.
+As of 0.29, the alarm_trigger service is supported. It is possible to fire off an envisalink-based alarm directly from Home Assistant. For example, a newer zwave/zigbee sensor can now be integrated into a legacy alarm system using a Home Assistant automation.
+An envisalink section must be present in the configuration.yaml file and contain the following options as required:
# Example configuration.yaml entry
@@ -116,6 +118,7 @@
evl_version: 3
keepalive_interval: 60
zonedump_interval: 30
+ panic_type: Police
zones:
11:
name: 'Back Door'
@@ -141,6 +144,7 @@
evl_version (Optional): 3 for evl3, or 4 for evl4. Default: 3
keepalive_interval (Optional): This is a periodic heartbeat signal (measured in seconds) sent to your Envisalink board to keep it from restarting. This is required for DSC and Honeywell systems. Defaults to 60 seconds.
zonedump_interval (Optional): This is an interval (measured in seconds) where the evl will dump out all zone statuses. This is required for Honeywell systems, which do not properly send zone closure events. DSC boards do not technically need this. Default: 30
+ panic_type (Optional): Both DSC and Honeywell boards support a “panic” alarm. This is used when the alarm_trigger service is called in home assistant. This determines which type of panic alarm to raise. Default = Police. Valid values are: Police, Fire, Ambulance
zones (Optional): Envisalink boards have no way to tell us which zones are actually in use, so each zone must be configured in Home Assistant. For each zone, at least a name must be given. Note: if no zones are specified, Home Assistant will not load any binary_sensor components.
partitions (Optional): Again, Envisalink boards do not tell us what is in use and what is not, so each partition must be configured with a partition name. If no partition parameter is specified, then no alarm_panel or sensor components are loaded.
diff --git a/components/media_player.mpd/index.html b/components/media_player.mpd/index.html
index c44c131dab..67ad5606b2 100644
--- a/components/media_player.mpd/index.html
+++ b/components/media_player.mpd/index.html
@@ -91,6 +91,8 @@
The mpd platform allows you to control a Music Player Daemon from Home Assistant. Unfortunatly you will not be able to manipulate the playlist (add or delete songs) or add transitions between the songs.
+Even though no playlist manipulation is possible, it is possible to use the play_media service to load an existing saved playlist as part of an automation or scene.
+
To add MPD to your installation, add the following to your configuration.yaml file:
# Example configuration.yaml entry
@@ -112,6 +114,23 @@
password (Optional): Password for your Music Player Daemon.
+Example script to load a saved playlist called “DeckMusic” and set the volume:
+
+relaxdeck:
+ sequence:
+ - service: media_player.play_media
+ data:
+ entity_id: media_player.main
+ media_content_type: playlist
+ media_content_id: DeckMusic
+
+ - service: media_player.volume_set
+ data:
+ entity_id: media_player.main
+ volume_level: 0.60
+
+
+
This platform works with Music Player Daemon and mopidy with Mopidy-MPD as used by Pi MusicBox.
diff --git a/sitemap.xml b/sitemap.xml
index 73b565ec1e..e4d883886f 100644
--- a/sitemap.xml
+++ b/sitemap.xml
@@ -844,9 +844,6 @@
https://home-assistant.io/components/sensor.mqtt/
-https://home-assistant.io/components/media_player.mpd/
-
-
https://home-assistant.io/components/switch.transmission/
@@ -1675,9 +1672,6 @@
https://home-assistant.io/components/media_player.cmus/
-https://home-assistant.io/components/envisalink/
-
-
https://home-assistant.io/components/sensor.fixer/
@@ -1969,6 +1963,12 @@
https://home-assistant.io/components/cover.mqtt/
+https://home-assistant.io/components/envisalink/
+
+
+https://home-assistant.io/components/media_player.mpd/
+
+
https://home-assistant.io/cookbook/automation_for_rainy_days/
@@ -2105,62 +2105,62 @@
https://home-assistant.io/demo/frontend.html
-2016-09-30T19:35:22+00:00
+2016-10-01T10:10:34+00:00
https://home-assistant.io/demo/index.html
-2016-09-30T19:35:22+00:00
+2016-10-01T10:10:34+00:00
https://home-assistant.io/demo/panels/ha-panel-dev-event.html
-2016-09-30T19:35:22+00:00
+2016-10-01T10:10:34+00:00
https://home-assistant.io/demo/panels/ha-panel-dev-info.html
-2016-09-30T19:35:22+00:00
+2016-10-01T10:10:34+00:00
https://home-assistant.io/demo/panels/ha-panel-dev-service.html
-2016-09-30T19:35:22+00:00
+2016-10-01T10:10:34+00:00
https://home-assistant.io/demo/panels/ha-panel-dev-state.html
-2016-09-30T19:35:22+00:00
+2016-10-01T10:10:34+00:00
https://home-assistant.io/demo/panels/ha-panel-dev-template.html
-2016-09-30T19:35:22+00:00
+2016-10-01T10:10:34+00:00
https://home-assistant.io/demo/panels/ha-panel-history.html
-2016-09-30T19:35:22+00:00
+2016-10-01T10:10:34+00:00
https://home-assistant.io/demo/panels/ha-panel-iframe.html
-2016-09-30T19:35:22+00:00
+2016-10-01T10:10:34+00:00
https://home-assistant.io/demo/panels/ha-panel-logbook.html
-2016-09-30T19:35:22+00:00
+2016-10-01T10:10:34+00:00
https://home-assistant.io/demo/panels/ha-panel-map.html
-2016-09-30T19:35:22+00:00
+2016-10-01T10:10:34+00:00
https://home-assistant.io/googlef4f3693c209fe788.html
-2016-09-30T19:35:22+00:00
+2016-10-01T10:10:34+00:00
https://home-assistant.io/static/fonts/roboto/DESCRIPTION.en_us.html
-2016-09-30T19:35:22+00:00
+2016-10-01T10:10:34+00:00
https://home-assistant.io/static/fonts/robotomono/DESCRIPTION.en_us.html
-2016-09-30T19:35:22+00:00
+2016-10-01T10:10:34+00:00
https://home-assistant.io/static/mdi-demo.html
-2016-09-30T19:35:22+00:00
+2016-10-01T10:10:34+00:00