diff --git a/atom.xml b/atom.xml index 1e867ba1ca..55b62c1e5e 100644 --- a/atom.xml +++ b/atom.xml @@ -4,7 +4,7 @@
In order to connect to the device, you need a login id. The easiest way to obtain this identifier is to use the apple_tv_scan service (described below). Additional information about start_off and credentials can also be found under the guides section.
To scan for devices, press the icon in the upper left corner and select the leftmost icon according to the image:
+Make sure Home Sharing is enabled on the Apple TV.
+To scan for devices and determine the login_id, press the icon in the upper left corner and select the leftmost icon according to the image:

Select apple_tv as domain and apple_tv_scan as service then press the button:

Just copy and paste the login id from the device you want to add. For more details about atvremote, see: this page.
The Apple TV will automatically turn on if a request is sent to it, e.g., if a button is pressed, something is streamed to it via AirPlay or if current state (currently playing) is accessed. This is how Apple has designed it, and it will cause problems if you are using HDMI CEC. Every time Home Assistant is started, a new request is sent to the device to figure out what is currently playing. When using CEC, this will wake up your TV and other devices you have configured.
-So, if your TV is randomly turning on, this is probably the reason. As stated, this is by design, and there is no real fix for it. There’s also no known way to turn off the Apple TV via the protocol used for communication. You have the following options:
-The first two points are quite obvious. Fake standby is a concept implemented in this platform that disables all requests to the device and makes it appear as being “off” in the web interface. This will make sure that the device is not woken up, but it will of course not show any information or allow you to control it. It is however easy to turn it on (or off) in the web interface or to use an automation with turn_on. To make it more useful, you can write automations that turn it on or off depending on some other device, like the input source on your receiver.
To put a device into fake standby when starting Home Assistant, add start_off: true to your configuration.
-Turning the device on/off in the user interface will not turn the physical device on/off according to the description above. -
+Just copy and paste the login_id from the device you want to add. For more details about atvremote, see: this page.
If you, when playing media with play_url, get the following error message:
“This AirPlay connection requires iOS 7.1 or later, OS X 10.10 or later, or iTunes 11.2 or later.”
@@ -154,6 +142,19 @@ Turning the device on/off in the user interface will not turn the physiRestart Home Assistant, and you should now be able to use play_url as before.
The Apple TV will automatically turn on if a request is sent to it, e.g., if a button is pressed, something is streamed to it via AirPlay or if current state (currently playing) is accessed. This is how Apple has designed it, and it will cause problems if you are using HDMI CEC. Every time Home Assistant is started, a new request is sent to the device to figure out what is currently playing. When using CEC, this will wake up your TV and other devices you have configured.
+So, if your TV is randomly turning on, this is probably the reason. As stated, this is by design, and there is no real fix for it. There’s also no known way to turn off the Apple TV via the protocol used for communication. You have the following options:
+The first two points are quite obvious. Fake standby is a concept implemented in this platform that disables all requests to the device and makes it appear as being “off” in the web interface. This will make sure that the device is not woken up, but it will of course not show any information or allow you to control it. It is however easy to turn it on (or off) in the web interface or to use an automation with turn_on. To make it more useful, you can write automations that turn it on or off depending on some other device, like the input source on your receiver.
To put a device into fake standby when starting Home Assistant, add start_off: true to your configuration.
+Turning the device on/off in the user interface will not turn the physical device on/off according to the description above. +
apple_tv_authenticateTo play media on an Apple TV with device authentication enabled (e.g., ATV4 with tvOS 10.2+), Home Assistant must be properly authenticated. This method starts the process and presents the credentials needed for playback as a persistent notification. Please see guide above for usage.
diff --git a/components/device_tracker.luci/index.html b/components/device_tracker.luci/index.html index 830915f679..0d19d02b6a 100644 --- a/components/device_tracker.luci/index.html +++ b/components/device_tracker.luci/index.html @@ -76,6 +76,9 @@This is one of the two ways we support OpenWRT. If you encounter problems, try ubus.
This is a presence detection scanner for OpenWRT using luci.
++This component requires a workaround when using luci with HTTPS and a self-signed certificate. +
Before this scanner can be used you have to install the luci RPC package on OpenWRT:
# opkg install luci-mod-rpc
diff --git a/components/media_player.yamaha_musiccast/index.html b/components/media_player.yamaha_musiccast/index.html
index 4790d98de3..6d3d28852e 100644
--- a/components/media_player.yamaha_musiccast/index.html
+++ b/components/media_player.yamaha_musiccast/index.html
@@ -76,7 +76,7 @@
The yamaha_musiccast platform allows you to control Yamaha MusicCast Receivers from Home Assistant.
Supported devices are listed on their German site.
-To add a Yamaha Network Receiver to your installation, add the following to your configuration.yaml file:
To add a Yamaha MusicCast Receiver to your installation, add the following to your configuration.yaml file:
# Example configuration.yaml entry
media_player:
- platform: yamaha_musiccast
@@ -86,7 +86,7 @@
Configuration variables:
- host (Required): IP address or hostname of the device
- - port (Optional): UDP Port
+ - port (Optional): UDP source port. If multiple devices are present, specify a different port per device
- interval_seconds (Optional): Polling interval (default: 480 seconds = 8 minutes)
A few notes:
diff --git a/docs/configuration/devices/index.html b/docs/configuration/devices/index.html
index 685fb5a76e..fa035215ae 100644
--- a/docs/configuration/devices/index.html
+++ b/docs/configuration/devices/index.html
@@ -114,10 +114,12 @@
Each group consists of a name and a list of entity IDs. Entity IDs can be retrieved from the web interface by using the Set State page in the Developer Tools (
).
# Example configuration.yaml entry showing two styles
group:
- living_room: light.table_lamp, switch.ac
+ living_room:
+ entities: light.table_lamp, switch.ac
bedroom:
- - light.bedroom
- - media_player.nexus_player
+ entities:
+ - light.bedroom
+ - media_player.nexus_player
For more details please check the Group page.
diff --git a/sitemap.xml b/sitemap.xml
index fa3223b83c..4ea1aca8f2 100644
--- a/sitemap.xml
+++ b/sitemap.xml
@@ -3826,7 +3826,7 @@
https://home-assistant.io/components/switch.hook/
-2018-01-05T12:20:56+00:00
+2018-01-05T16:45:13+00:00
https://home-assistant.io/cookbook/automation_for_rainy_days/
@@ -4506,99 +4506,99 @@
https://home-assistant.io/docs/autostart/init.d/
-2018-01-05T12:20:56+00:00
+2018-01-05T16:45:13+00:00
https://home-assistant.io/docs/ecosystem/appdaemon/
-2018-01-05T12:20:56+00:00
+2018-01-05T16:45:13+00:00
https://home-assistant.io/docs/ecosystem/appdaemon/api/
-2018-01-05T12:20:56+00:00
+2018-01-05T16:45:13+00:00
https://home-assistant.io/docs/ecosystem/appdaemon/configuration/
-2018-01-05T12:20:56+00:00
+2018-01-05T16:45:13+00:00
https://home-assistant.io/docs/ecosystem/appdaemon/example_apps/
-2018-01-05T12:20:56+00:00
+2018-01-05T16:45:13+00:00
https://home-assistant.io/docs/ecosystem/appdaemon/installation/
-2018-01-05T12:20:56+00:00
+2018-01-05T16:45:13+00:00
https://home-assistant.io/docs/ecosystem/appdaemon/operation/
-2018-01-05T12:20:56+00:00
+2018-01-05T16:45:13+00:00
https://home-assistant.io/docs/ecosystem/appdaemon/reboot/
-2018-01-05T12:20:56+00:00
+2018-01-05T16:45:13+00:00
https://home-assistant.io/docs/ecosystem/appdaemon/running/
-2018-01-05T12:20:56+00:00
+2018-01-05T16:45:13+00:00
https://home-assistant.io/docs/ecosystem/appdaemon/tutorial/
-2018-01-05T12:20:56+00:00
+2018-01-05T16:45:13+00:00
https://home-assistant.io/docs/ecosystem/appdaemon/updating/
-2018-01-05T12:20:56+00:00
+2018-01-05T16:45:13+00:00
https://home-assistant.io/docs/ecosystem/appdaemon/windows/
-2018-01-05T12:20:56+00:00
+2018-01-05T16:45:13+00:00
https://home-assistant.io/docs/ecosystem/certificates/
-2018-01-05T12:20:56+00:00
+2018-01-05T16:45:13+00:00
https://home-assistant.io/docs/ecosystem/hadashboard/
-2018-01-05T12:20:56+00:00
+2018-01-05T16:45:13+00:00
https://home-assistant.io/docs/ecosystem/hass-configurator/
-2018-01-05T12:20:56+00:00
+2018-01-05T16:45:13+00:00
https://home-assistant.io/docs/ecosystem/ios/
-2018-01-05T12:20:56+00:00
+2018-01-05T16:45:13+00:00
https://home-assistant.io/docs/ecosystem/nginx/
-2018-01-05T12:20:56+00:00
+2018-01-05T16:45:13+00:00
https://home-assistant.io/docs/ecosystem/notebooks/
-2018-01-05T12:20:56+00:00
+2018-01-05T16:45:13+00:00
https://home-assistant.io/docs/ecosystem/scenegen/
-2018-01-05T12:20:56+00:00
+2018-01-05T16:45:13+00:00
https://home-assistant.io/docs/ecosystem/synology/
-2018-01-05T12:20:56+00:00
+2018-01-05T16:45:13+00:00
https://home-assistant.io/docs/tools/
-2018-01-05T12:20:56+00:00
+2018-01-05T16:45:13+00:00
https://home-assistant.io/docs/tools/dev-tools/
-2018-01-05T12:20:56+00:00
+2018-01-05T16:45:13+00:00
https://home-assistant.io/docs/tools/hass/
-2018-01-05T12:20:56+00:00
+2018-01-05T16:45:13+00:00
https://home-assistant.io/docs/tools/scripts/
-2018-01-05T12:20:56+00:00
+2018-01-05T16:45:13+00:00
https://home-assistant.io/faq/after-upgrading/
@@ -5734,62 +5734,62 @@
https://home-assistant.io/demo/frontend.html
-2018-01-05T12:20:12+00:00
+2018-01-05T16:44:28+00:00
https://home-assistant.io/demo/index.html
-2018-01-05T12:20:12+00:00
+2018-01-05T16:44:28+00:00
https://home-assistant.io/demo/panels/ha-panel-dev-event.html
-2018-01-05T12:20:12+00:00
+2018-01-05T16:44:28+00:00
https://home-assistant.io/demo/panels/ha-panel-dev-info.html
-2018-01-05T12:20:12+00:00
+2018-01-05T16:44:28+00:00
https://home-assistant.io/demo/panels/ha-panel-dev-service.html
-2018-01-05T12:20:12+00:00
+2018-01-05T16:44:28+00:00
https://home-assistant.io/demo/panels/ha-panel-dev-state.html
-2018-01-05T12:20:12+00:00
+2018-01-05T16:44:28+00:00
https://home-assistant.io/demo/panels/ha-panel-dev-template.html
-2018-01-05T12:20:12+00:00
+2018-01-05T16:44:28+00:00
https://home-assistant.io/demo/panels/ha-panel-history.html
-2018-01-05T12:20:12+00:00
+2018-01-05T16:44:28+00:00
https://home-assistant.io/demo/panels/ha-panel-iframe.html
-2018-01-05T12:20:12+00:00
+2018-01-05T16:44:28+00:00
https://home-assistant.io/demo/panels/ha-panel-logbook.html
-2018-01-05T12:20:12+00:00
+2018-01-05T16:44:28+00:00
https://home-assistant.io/demo/panels/ha-panel-map.html
-2018-01-05T12:20:12+00:00
+2018-01-05T16:44:28+00:00
https://home-assistant.io/googlef4f3693c209fe788.html
-2018-01-05T12:20:12+00:00
+2018-01-05T16:44:28+00:00
https://home-assistant.io/static/fonts/roboto/DESCRIPTION.en_us.html
-2018-01-05T12:20:12+00:00
+2018-01-05T16:44:28+00:00
https://home-assistant.io/static/fonts/robotomono/DESCRIPTION.en_us.html
-2018-01-05T12:20:12+00:00
+2018-01-05T16:44:28+00:00
https://home-assistant.io/static/mdi-demo.html
-2018-01-05T12:20:12+00:00
+2018-01-05T16:44:28+00:00