|
| 1 | +--- |
| 2 | +layout: page |
| 3 | +title: "Emulated Hue Bridge" |
| 4 | +description: "Emulated Hue Bridge" |
| 5 | +sidebar: true |
| 6 | +comments: false |
| 7 | +sharing: true |
| 8 | +footer: true |
| 9 | +--- |
| 10 | + |
| 11 | +The `emulated_hue` component provides a virtual Philips Hue bridge, written entirely in software, |
| 12 | +that allows services that work with the Hue API to interact with Home Assistant |
| 13 | +entities. The driving use case behind this functionality is to allow Home |
| 14 | +Assistant to work with an Amazon Echo with no set up cost outside of |
| 15 | +configuration changes. |
| 16 | + |
| 17 | +### {% linkable_title Configuration %} |
| 18 | + |
| 19 | +To enable the emulated Hue bridge, add the following to your `configuration.yaml` |
| 20 | +file: |
| 21 | + |
| 22 | +```yaml |
| 23 | +# Example configuration.yaml entry |
| 24 | +emulated_hue: |
| 25 | + host_ip: 192.168.1.186 |
| 26 | + listen_port: 8300 |
| 27 | + off_maps_to_on_domains: |
| 28 | + - script |
| 29 | + - scene |
| 30 | + expose_by_default: true |
| 31 | + exposed_domains: |
| 32 | + - light |
| 33 | + |
| 34 | +# Example customization |
| 35 | +homeassistant: |
| 36 | + customize: |
| 37 | + light.bedroom_light: |
| 38 | + # Don't allow light.bedroom_light to be controlled by the |
| 39 | + # emulated Hue bridge |
| 40 | + emulated_hue: false |
| 41 | + light.office_light: |
| 42 | + # Address light.office_light as "back office light" |
| 43 | + emulated_hue_name: "back office light" |
| 44 | +``` |
| 45 | +
|
| 46 | +- **host_ip** (*Optional*): The IP address that your Home Assistant installation is |
| 47 | + running on. If you do not specify this option, the component will attempt to |
| 48 | + determine the IP address on its own. |
| 49 | +
|
| 50 | +- **listen_port** (*Optional*): The port the Hue bridge API web server will run on. If |
| 51 | + not specified, this defaults to 8300. This can be any free port on your system. |
| 52 | +
|
| 53 | +- **off_maps_to_on_domains** (*Optional*): The domains that maps an "off" command to |
| 54 | + an "on" command. |
| 55 | + |
| 56 | + For example, if `script` is included in the list, and you |
| 57 | + ask Alexa to "turn off the *water plants* script," the command will be handled |
| 58 | + as if you asked her to turn on the script. |
| 59 | + |
| 60 | + If not specified, this defaults to the following list: |
| 61 | + |
| 62 | + - `script` |
| 63 | + - `scene` |
| 64 | + |
| 65 | +- **expose_by_default** (*Optional*): Whether or not entities should be exposed via the |
| 66 | + bridge by default instead of explicitly (see the 'echo' attribute later on). |
| 67 | + If not specified, this defaults to true. |
| 68 | + |
| 69 | +- **exposed_domains** (*Optional*): The domains that are exposed by default if |
| 70 | + `expose_by_default` is set to true. If not specified, this defaults to the |
| 71 | + following list: |
| 72 | + |
| 73 | + - `switch` |
| 74 | + - `light` |
| 75 | + - `group` |
| 76 | + - `input_boolean` |
| 77 | + - `media_player` |
| 78 | + |
| 79 | +The following are attributes that can be applied in the `customize` section: |
| 80 | + |
| 81 | +- **emulated_hue** (*Optional*): Whether or not the entity should be |
| 82 | + exposed by the emulated Hue bridge. The default value for this attribute is controlled |
| 83 | + by the `expose_by_default` option. |
| 84 | + |
| 85 | +- **emulated_hue_name** (*Optional*): The name that the emulated Hue will use. |
| 86 | + The default for this is the entity's friendly name. |
| 87 | + |
| 88 | +### {% linkable_title License %} |
| 89 | + |
| 90 | +Much of this code is based on work done by Bruce Locke on his [ha-local-echo](https://github.com/blocke/ha-local-echo) |
| 91 | +project, originally released under the MIT License. The license is located [here](https://github.com/blocke/ha-local-echo/blob/b9bf5dcaae6d8e305e2283179ffba64bde9ed29e/LICENSE). |
0 commit comments