Note: group_name is not linked to Home Assistant group name.
** Finding Group and Scene Names **
+Finding Group and Scene Names
How do you find these names?
The easiest way to do this is only use the scenes from the 2nd generation Hue app. That is organized by room (group) and scene Name. Use the values of room name and scene name that you see in the app. You can test these work on the dev-service console of your Home Assistant instance.
Alternatively, you can dump all rooms and scene names using this gist. This does not tell you which groups and scenes work together but it’s sufficient to get values that you can test in the dev-service console.
** Caveats **
+Caveats
The Hue API doesn’t activate scenes directly, only on a Hue Group (typically rooms, especially if using the 2nd gen app). But Hue Scenes don’t actually reference their group. So heuristic matching is used.
Neither group names or scene names are guaranteed unique in Hue. If you are getting non deterministic behavior, adjust your Hue scenes via the App to be more identifying.
The Hue hub has limited spaces for scenes, and will delete scenes if new ones get created that would overflow that space. The API docs say this is based on “Least Recently Used”.
diff --git a/docs/installation/docker/index.html b/docs/installation/docker/index.html index 140cc6fd00..a5732ef731 100644 --- a/docs/installation/docker/index.html +++ b/docs/installation/docker/index.html @@ -132,12 +132,49 @@ netsh interface portproxy add v4tov4 listenaddress=0.0.0.0 listenport=8123 conne If you want to use a USB Bluetooth adapter or Z-Wave USB Stick with Home Assistant on Synology Docker these instructions do not correctly configure the container to access the USB devices. To configure these devices on your Synology Docker Home Assistant you can follow the instructions provided here by Phil Hawthorne.Restart
-This will launch Home Assistant and serve the web interface from port 8123 on your Docker host.
If you change the configuration you have to restart the server. To do that you have 2 options.
- You can go to the
service developer tools, select the service homeassistant/restartand click “Call Service”. - Or you can restart it from a terminal by running
docker restart home-assistant
Docker Compose
+As the docker command becomes more complex, switching to docker-compose can be preferable and support automatically restarting on failure or system restart. Create a docker-compose.yml file:
version: '3'
+ services:
+ web:
+ image: homeassistant/home-assistant
+ volumes:
+ - /path/to/your/config:/config
+ - /etc/localtime:/etc/localtime:ro
+ restart: always
+ network_mode: host
+Then start the container with:
+$ docker-compose up -d
+Exposing Devices
+In order to use z-wave, zigbee or other components that require access to devices, you need to map the appropriate device into the container. Ensure the user that is running the container has the correct privileges to access the /dev/tty* file, then add the device mapping to your docker command:
$ docker run -d --name="home-assistant" -v /path/to/your/config:/config -v /etc/localtime:/etc/localtime:ro --device /dev/ttyUSB0:/dev/ttyUSB0 --net=host homeassistant/home-assistant
+or in a docker-compose.yml file:
version: '3'
+ services:
+ web:
+ image: homeassistant/home-assistant
+ volumes:
+ - /path/to/your/config:/config
+ - /etc/localtime:/etc/localtime:ro
+ devices:
+ - /dev/ttyUSB0:/dev/ttyUSB0
+ - /dev/ttyUSB1:/dev/ttyUSB1
+ - /dev/ttyACM0:/dev/ttyACM0
+ restart: always
+ network_mode: host
+