✅ Fixes spelling of 'Home Assistant' everywhere (#3524)
This commit is contained in:
Franck Nijhof
Fredrik Lindqvist
parent
664e1bf86e
commit
443904de16
22 changed files with 34 additions and 34 deletions
|
|
@ -14,7 +14,7 @@ This example demonstrates how you can configure Apache to act as a proxy for Hom
|
|||
|
||||
This is useful if you want to have:
|
||||
|
||||
* a subdomain redirecting to your home assistant instance
|
||||
* a subdomain redirecting to your Home Assistant instance
|
||||
* several subdomain for several instance
|
||||
* HTTPS redirection
|
||||
|
||||
|
|
@ -73,8 +73,8 @@ You already have Home Assistant running on http://localhost:8123 and available a
|
|||
You want another instance available at https://countryside.example.org
|
||||
|
||||
You can either :
|
||||
* Create a new user, `bob`, to hold the configuration file in `/home/bob/.homeassistant/configuration.yaml` and run home assistant as this new user
|
||||
* Create another configuration directory in `/home/alice/.homeassistan2/configuration.yaml` and run home assistant using `hass --config /home/alice/.homeassistant2/`
|
||||
* Create a new user, `bob`, to hold the configuration file in `/home/bob/.homeassistant/configuration.yaml` and run Home Assistant as this new user
|
||||
* Create another configuration directory in `/home/alice/.homeassistan2/configuration.yaml` and run Home Assistant using `hass --config /home/alice/.homeassistant2/`
|
||||
|
||||
In both solution, change port number used by modifying `configuration.yaml`
|
||||
|
||||
|
|
|
|||
|
|
@ -1552,7 +1552,7 @@ The custom event `MODE_CHANGE` would be subscribed to with:
|
|||
self.listen_event(self.mode_event, "MODE_CHANGE")
|
||||
```
|
||||
|
||||
Home Assistant can send these events in a variety of other places - within automations, and also directly from Alexa intents. Home Assistant can also listen for custom events with it's automation component. This can be used to signal from AppDaemon code back to home assistant. Here is a sample automation:
|
||||
Home Assistant can send these events in a variety of other places - within automations, and also directly from Alexa intents. Home Assistant can also listen for custom events with it's automation component. This can be used to signal from AppDaemon code back to Home Assistant. Here is a sample automation:
|
||||
|
||||
```yaml
|
||||
automation:
|
||||
|
|
|
|||
|
|
@ -31,13 +31,13 @@ module = hello
|
|||
class = HelloWorld
|
||||
```
|
||||
|
||||
- `ha_url` is a reference to your home assistant installation and must include the correct port number and scheme (`http://` or `https://` as appropriate)
|
||||
- `ha_url` is a reference to your Home Assistant installation and must include the correct port number and scheme (`http://` or `https://` as appropriate)
|
||||
- `ha_key` should be set to your key if you have one, otherwise it can be removed.
|
||||
- `logfile` (optional) is the path to where you want `AppDaemon` to keep its main log. When run from the command line this is not used - log messages come out on the terminal. When running as a daemon this is where the log information will go. In the example above I created a directory specifically for AppDaemon to run from, although there is no reason you can't keep it in the `appdaemon` directory of the cloned repository. If `logfile = STDOUT`, output will be sent to stdout instead of stderr when running in the foreground, if not specified, output will be sent to STDOUT.
|
||||
- `errorfile` (optional) is the name of the logfile for errors - this will usually be errors during compilation and execution of the apps. If `errorfile = STDERR` errors will be sent to stderr instead of a file, if not specified, output will be sent to STDERR.
|
||||
- `app_dir` (optional) is the directory the apps are placed in. If not specified, AppDaemon will look first in `~/.homeassistant` then `/etc/appdaemon` for a subdirectory named `apps`
|
||||
- `threads` - the number of dedicated worker threads to create for running the apps. Note, this will bear no resembelance to the number of apps you have, the threads are re-used and only active for as long as required to tun a particular callback or initialization, leave this set to 10 unless you experience thread starvation
|
||||
- `latitude`, `longitude`, `elevation`, `timezone` - should all be copied from your home assistant configuration file
|
||||
- `latitude`, `longitude`, `elevation`, `timezone` - should all be copied from your Home Assistant configuration file
|
||||
- `cert_path` (optional) - path to root CA cert directory - use only if you are using self signed certs.
|
||||
|
||||
The `#Apps` section is the configuration for the Hello World program and should be left in place for initial testing but can be removed later if desired, as other Apps are added, App configuration is described in the [API doc](API.md).
|
||||
|
|
|
|||
|
|
@ -37,7 +37,7 @@ The app allows you to use your own custom sounds in push notifications. The soun
|
|||
2. Go to the device in iTunes.
|
||||
3. Select "Apps" on the left sidebar.
|
||||
4. Scroll down until you see the section labeled "File Sharing".
|
||||
5. Select HomeAssistant.
|
||||
5. Select Home Assistant.
|
||||
6. Drag and drop properly formatted sounds.
|
||||
7. Click Sync in the lower right.
|
||||
8. Once sync is complete, disconnect the device from the computer.
|
||||
|
|
|
|||
|
|
@ -13,7 +13,7 @@ This example demonstrates how you can configure NGINX to act as a proxy for Home
|
|||
|
||||
This is useful if you want to have:
|
||||
|
||||
* a subdomain redirecting to your home assistant instance
|
||||
* a subdomain redirecting to your Home Assistant instance
|
||||
* several subdomain for several instance
|
||||
* HTTPS redirection
|
||||
|
||||
|
|
@ -63,8 +63,8 @@ You already have Home Assistant running on http://localhost:8123 and available a
|
|||
You want another instance available at https://countryside.example.org
|
||||
|
||||
You can either :
|
||||
* Create a new user, `bob`, to hold the configuration file in `/home/bob/.homeassistant/configuration.yaml` and run home assistant as this new user
|
||||
* Create another configuration directory in `/home/alice/.homeassistan2/configuration.yaml` and run home assistant using `hass --config /home/alice/.homeassistant2/`
|
||||
* Create a new user, `bob`, to hold the configuration file in `/home/bob/.homeassistant/configuration.yaml` and run Home Assistant as this new user
|
||||
* Create another configuration directory in `/home/alice/.homeassistan2/configuration.yaml` and run Home Assistant using `hass --config /home/alice/.homeassistant2/`
|
||||
|
||||
In both solution, change port number used by modifying `configuration.yaml` file.
|
||||
|
||||
|
|
|
|||
|
|
@ -100,7 +100,7 @@ For a more advanced way to use the output try the following. In configuration.ya
|
|||
scene: !include_dir_list scenes
|
||||
```
|
||||
|
||||
This will tell home assistant to look in the subdirectory `scenes` for yaml files containing scene information. Each file will be named for the scene it will create and should contain information formatted as above. Then simply run Scenegen and redirect its output to the scenes subdirectory:
|
||||
This will tell Home Assistant to look in the subdirectory `scenes` for yaml files containing scene information. Each file will be named for the scene it will create and should contain information formatted as above. Then simply run Scenegen and redirect its output to the scenes subdirectory:
|
||||
|
||||
```
|
||||
$ ./scenegen.py https://<some url> -k <some api key> > scenes/my_new_scene.yaml
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue