From b3e1607ba2291706ad7694f3fa4d800a7a17c706 Mon Sep 17 00:00:00 2001 From: Josh Nichols Date: Sat, 3 Sep 2016 13:30:27 -0400 Subject: [PATCH] Recommend to assign a static IP for emulated_hue component (#890) --- source/_components/emulated_hue.markdown | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/source/_components/emulated_hue.markdown b/source/_components/emulated_hue.markdown index facee1929f4..0d1af6ce973 100755 --- a/source/_components/emulated_hue.markdown +++ b/source/_components/emulated_hue.markdown @@ -15,6 +15,10 @@ ha_iot_class: "Local Push" The `emulated_hue` component provides a virtual Philips Hue bridge, written entirely in software, that allows services that work with the Hue API to interact with Home Assistant entities. The driving use case behind this functionality is to allow Home Assistant to work with an Amazon Echo with no set up cost outside of configuration changes. +

+ It is recommended to assign a static IP address to the computer running Home Assistant. This is because the Amazon Echo discovers devices by IP addresss, and if the IP changes, the Echo won't be able to control it. This is easiest done from your router, see your router's manual for details. +

+ ### {% linkable_title Configuration %} To enable the emulated Hue bridge, add the following to your `configuration.yaml` file: