I recently learned about the ESP8266, a $5 chip that includes WiFi and is Arduino compatible. This means that all your DIY projects can now be done for a fraction of the price.
-For this tutorial, I’ll walk through how to get going with ESP8266, get the temperature and humidity and report it to MQTT where Home Asssistant can pick it up.
+For this tutorial, I’ll walk through how to get going with ESP8266, get the temperature and humidity and report it to MQTT where Home Assistant can pick it up.
Picture of the final setup (+ 2 LED for decoration)
diff --git a/components/binary_sensor.flic/index.html b/components/binary_sensor.flic/index.html
index 194190013d..1bac9ca5df 100644
--- a/components/binary_sensor.flic/index.html
+++ b/components/binary_sensor.flic/index.html
@@ -75,7 +75,7 @@
The flic platform allows you to connect with multiple flic smart buttons.
The platform does not directly interact with the buttons, but communicates with the flic service that manages the buttons. The service can run on the same instance as home assistant or any other reachable machine. For setup instructions visit the GitHub repository of the service for Linux, OS X or Windows.
+The platform does not directly interact with the buttons, but communicates with the flic service that manages the buttons. The service can run on the same instance as Home Assistant or any other reachable machine. For setup instructions visit the GitHub repository of the service for Linux, OS X or Windows.
To use your flic buttons in your installation, add the following to your configuration.yaml file:
# Example configuration.yaml entry
binary_sensor:
diff --git a/components/envisalink/index.html b/components/envisalink/index.html
index 28664a1811..1333e6b3ea 100644
--- a/components/envisalink/index.html
+++ b/components/envisalink/index.html
@@ -120,7 +120,7 @@
- evl_version (Optional): 3 for evl3, or 4 for evl4. Default:
3
- keepalive_interval (Optional): This is a periodic heartbeat signal (measured in seconds) sent to your Envisalink board to keep it from restarting. This is required for DSC and Honeywell systems. Defaults to
60 seconds.
- zonedump_interval (Optional): This is an interval (measured in seconds) where the evl will dump out all zone statuses. This is required for Honeywell systems, which do not properly send zone closure events. DSC boards do not technically need this. Default:
30
- - panic_type (Optional): Both DSC and Honeywell boards support a “panic” alarm. This is used when the alarm_trigger service is called in home assistant. This determines which type of panic alarm to raise. Default = Police. Valid values are: Police, Fire, Ambulance
+ - panic_type (Optional): Both DSC and Honeywell boards support a “panic” alarm. This is used when the alarm_trigger service is called in Home Assistant. This determines which type of panic alarm to raise. Default = Police. Valid values are: Police, Fire, Ambulance
- zones (Optional): Envisalink boards have no way to tell us which zones are actually in use, so each zone must be configured in Home Assistant. For each zone, at least a name must be given. For more information on the available zone types, take a look at the Binary Sensor docs. Note: If no zones are specified, Home Assistant will not load any binary_sensor components.
- partitions (Optional): Again, Envisalink boards do not tell us what is in use and what is not, so each partition must be configured with a partition name. If no partition parameter is specified, then no alarm_panel or sensor components are loaded.
diff --git a/components/light.decora/index.html b/components/light.decora/index.html
index 4f1fabcc82..9c956b0855 100644
--- a/components/light.decora/index.html
+++ b/components/light.decora/index.html
@@ -113,7 +113,7 @@ Jun 20 19:41:18 androlapin hass[29588]: OSError: [Errno 8] Exec format error
1. Go to your .homeassistant folder
2. Then go to deps/bluepy subfolder.
3. Then run make all
-4. Restart home assistant
+4. Restart Home Assistant
Philips Hue support is integrated into Home Assistant as a light platform. The preferred way to setup the Philips Hue platform is by enabling the discovery component.
-Once discovered, if you have a custom default view, locate configurator.philips_hue in the entities list ( < > ) and add it to a group in configuration.yaml. Restart Home Assistant so that the configurator is visible in the Home Assistant dashboard. Once Home Assistant is restarted, locate and click on configurator.philips_hue to bring up the initiation dialog. This will prompt you to press the Hue button to register the Hue hub in home assistant. Once complete, the configurator entity isn’t needed anymore and can be removed from any visible group in configuration.yaml.
Once discovered, if you have a custom default view, locate configurator.philips_hue in the entities list ( < > ) and add it to a group in configuration.yaml. Restart Home Assistant so that the configurator is visible in the Home Assistant dashboard. Once Home Assistant is restarted, locate and click on configurator.philips_hue to bring up the initiation dialog. This will prompt you to press the Hue button to register the Hue hub in Home Assistant. Once complete, the configurator entity isn’t needed anymore and can be removed from any visible group in configuration.yaml.
When you configure the Hue bridge from Home Assistant, it writes a token to a file in your Home Assistant configuration directory. That token authenticates the communication with the Hue bridge. This token uses the IP Address of the Hue Bridge. If the IP address for the Hue Bridge changes, you will need to register the Hue Bridge with Home Assistant again. To avoid this you may set up DHCP registration for your Hue Bridge, so that it always has the same IP address.
-Restarting Home Assistant once more should result in the Hue lights listed as “light” entities. Add these light entities to configuration.yaml and restart home assistant once more to complete the installation.
+Restarting Home Assistant once more should result in the Hue lights listed as “light” entities. Add these light entities to configuration.yaml and restart Home Assistant once more to complete the installation.
If you want to enable the component without relying on the discovery component, add the following lines to your configuration.yaml file:
# Example configuration.yaml entry
light:
diff --git a/components/media_player.frontier_silicon/index.html b/components/media_player.frontier_silicon/index.html
index cbcb9f103d..4501f2d870 100644
--- a/components/media_player.frontier_silicon/index.html
+++ b/components/media_player.frontier_silicon/index.html
@@ -84,7 +84,7 @@
This component was developed and tested with a Hama DIR3110 and a Medion MD 87466.
Configuration
-Your Frontier Silicon based device should be automatically discovered by home assistant. The auto-discovery service assumes that the device uses the default PIN code: 1234. If you have changed the PIN code, the auto-discovery will fail as home assistant will not be able to connect to the device. You can set the PIN code of your device (depending on manufacturer) under:
+Your Frontier Silicon based device should be automatically discovered by Home Assistant. The auto-discovery service assumes that the device uses the default PIN code: 1234. If you have changed the PIN code, the auto-discovery will fail as Home Assistant will not be able to connect to the device. You can set the PIN code of your device (depending on manufacturer) under:
MENU button > Main Menu > System setting > Network > NetRemote PIN setup
If your device was not automatically discovered or you have changed the PIN you can alternatively add the following to your configuration.yaml file:
# Example configuration.yaml entry
@@ -128,8 +128,8 @@
is based on tiwillam’s fsapi project. Special thanks to both developers, this component would have not been possible without their work.
Notes and Limitations
-The Frontier Silicon API does not provide a multi-user environment. There is always a single user (session) controlling a device, which means that once home assistant connects to a device all other sessions will be invalidated. This renders the usage of UNDOK almost impossible, as the home assistant component polls the device state every 30 seconds or issues a command by creating a new session.
-If you want to prevent home assistant to auto connect to your device, simply change the PIN code of the device to something else than: 1234
+The Frontier Silicon API does not provide a multi-user environment. There is always a single user (session) controlling a device, which means that once Home Assistant connects to a device all other sessions will be invalidated. This renders the usage of UNDOK almost impossible, as the Home Assistant component polls the device state every 30 seconds or issues a command by creating a new session.
+If you want to prevent Home Assistant to auto connect to your device, simply change the PIN code of the device to something else than: 1234
diff --git a/components/mysensors/index.html b/components/mysensors/index.html
index bc4e01d30d..e3400bc880 100644
--- a/components/mysensors/index.html
+++ b/components/mysensors/index.html
@@ -235,7 +235,7 @@ The MQTT gateway requires MySensors version 2.0 and only the MQTT client gateway
Heartbeats
Sending a heartbeat from the MySensors device to Home Assistant activates the SmartSleep functionality in Home Assistant. This means that messages are buffered and only sent to the device upon receiving a heartbeat from the device. State changes are stored so that only the last requested state change is sent to the device. Other types of messages are queued in a FIFO queue. SmartSleep is useful for battery powered actuators that are waiting for commands. See the MySensors library API for information on how to send heartbeats and sleep device.
Message validation
-Messages sent to or from Home Assistant from or to a MySensors device will be validated according to the MySensors serial API. If a message doesn’t pass validation, it will be dropped and not be passed forward either to or from home assistant. Make sure you follow the serial API for your version of MySensors when writing your Arduino sketch.
+Messages sent to or from Home Assistant from or to a MySensors device will be validated according to the MySensors serial API. If a message doesn’t pass validation, it will be dropped and not be passed forward either to or from Home Assistant. Make sure you follow the serial API for your version of MySensors when writing your Arduino sketch.
If you experience dropped messages or that a device is not added to Home Assistant, please turn on debug logging for the mysensors component and the mysensors package.
logger:
default: info
diff --git a/components/notify.telegram/index.html b/components/notify.telegram/index.html
index 898e23803b..591dbd23fd 100644
--- a/components/notify.telegram/index.html
+++ b/components/notify.telegram/index.html
@@ -169,7 +169,7 @@
- inline_keyboard (Optional): List of rows of commands, comma-separated, to make a custom inline keyboard with buttons with associated callback data.
-Since Homeassistant version 0.48 you have to whitelist the source folder of the file you want to include in the notification.
+Since Home Assistant version 0.48 you have to whitelist the source folder of the file you want to include in the notification.
yaml
configuration.yaml
...
diff --git a/components/pilight/index.html b/components/pilight/index.html
index 3b2f515fa0..928d364f66 100644
--- a/components/pilight/index.html
+++ b/components/pilight/index.html
@@ -75,8 +75,8 @@
Pilight is a modular and open source solution to communicate with 433 MHz devices and runs on various small form factor computers. A lot of common protocols are already available.
-This pilight hub connects to the pilight-daemon via a socket connection to receive and send codes. Thus home assistant does not have to run on the computer in charge of the RF communication.
-The received and supported RF codes are put on the event bus of home assistant and are therefore directly usable by other components (e.g. automation). Additionally a send service is provided to send RF codes.
+This pilight hub connects to the pilight-daemon via a socket connection to receive and send codes. Thus Home Assistant does not have to run on the computer in charge of the RF communication.
+The received and supported RF codes are put on the event bus of Home Assistant and are therefore directly usable by other components (e.g. automation). Additionally a send service is provided to send RF codes.
To integrate pilight into Home Assistant, add the following section to your configuration.yaml file:
# Example configuration.yaml entry
pilight:
diff --git a/components/sensor.pilight/index.html b/components/sensor.pilight/index.html
index c30bdff6a9..3315af2e21 100644
--- a/components/sensor.pilight/index.html
+++ b/components/sensor.pilight/index.html
@@ -74,7 +74,7 @@
- This pilight sensor platform for 433 MHz devices uses a value in the message payload as the sensor value. Unique identifiers (e.g. uuid) can be set to distinguish between multiple pilight devices. To use a pilight sensor the pilight home assistant hub has to be set up.
+ This pilight sensor platform for 433 MHz devices uses a value in the message payload as the sensor value. Unique identifiers (e.g. uuid) can be set to distinguish between multiple pilight devices. To use a pilight sensor the pilight Home Assistant hub has to be set up.
To use your sensor via pilight, make sure it is supported and add the following to your configuration.yaml file:
# Example configuration.yml entry
sensor:
diff --git a/components/switch.rfxtrx/index.html b/components/switch.rfxtrx/index.html
index 31e9afa53e..9e4fd9eaf8 100644
--- a/components/switch.rfxtrx/index.html
+++ b/components/switch.rfxtrx/index.html
@@ -83,7 +83,7 @@ The easiest way to find your switches is to add this to your automatic_add: True
-Launch your homeassistant and go the website.
+
Launch your Home Assistant and go the website.
Push your remote and your device should be added:
@@ -116,7 +116,7 @@ Then you should update your configuration to:
- Use this code to add a new switch in your configuration.yaml
- - Launch your homeassistant and go the website.
+ - Launch your Home Assistant and go the website.
- Enable learning mode on your switch (i.e. push learn button or plug it in a wall socket)
- Toggle your new switch in the Home Assistant interface
diff --git a/docs/configuration/group_visibility/index.html b/docs/configuration/group_visibility/index.html
index 9a019318a3..80f0d56bf0 100644
--- a/docs/configuration/group_visibility/index.html
+++ b/docs/configuration/group_visibility/index.html
@@ -156,7 +156,7 @@ If a sensor belongs to only one group and that group is hidden, the sensor will
-If you are using docker to run home assistant then the occasion.py script will be placed under /config. Your command should instead be: command: “python3 /command/occasion.py”
+If you are using docker to run Home Assistant then the occasion.py script will be placed under /config. Your command should instead be: command: “python3 /command/occasion.py”
To simplify things, we create a Home Assistant script that changes the visibility of a group, but also verifies that an entity is in a specific state:
script:
diff --git a/docs/ecosystem/apache/index.html b/docs/ecosystem/apache/index.html
index 88399d70e1..c1822a7b46 100644
--- a/docs/ecosystem/apache/index.html
+++ b/docs/ecosystem/apache/index.html
@@ -78,7 +78,7 @@
This example demonstrates how you can configure Apache to act as a proxy for Home Assistant.
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
@@ -124,8 +124,8 @@ In case you are getting occasional HTTP 504 error messages (“Gateway Timeout
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
http:
diff --git a/docs/ecosystem/appdaemon/api/index.html b/docs/ecosystem/appdaemon/api/index.html
index b71ce6576a..7ee98e0716 100644
--- a/docs/ecosystem/appdaemon/api/index.html
+++ b/docs/ecosystem/appdaemon/api/index.html
@@ -1082,7 +1082,7 @@
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:
automation:
trigger:
platform: event
diff --git a/docs/ecosystem/appdaemon/configuration/index.html b/docs/ecosystem/appdaemon/configuration/index.html
index 4d381f3f39..2fc768bbc3 100644
--- a/docs/ecosystem/appdaemon/configuration/index.html
+++ b/docs/ecosystem/appdaemon/configuration/index.html
@@ -95,13 +95,13 @@ 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 appsthreads - 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 starvationlatitude, longitude, elevation, timezone - should all be copied from your home assistant configuration filelatitude, longitude, elevation, timezone - should all be copied from your Home Assistant configuration filecert_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.
diff --git a/docs/ecosystem/ios/notifications/sounds/index.html b/docs/ecosystem/ios/notifications/sounds/index.html
index 1f8087572f..934ca81711 100644
--- a/docs/ecosystem/ios/notifications/sounds/index.html
+++ b/docs/ecosystem/ios/notifications/sounds/index.html
@@ -100,7 +100,7 @@
- Go to the device in iTunes.
- Select “Apps” on the left sidebar.
- Scroll down until you see the section labeled “File Sharing”.
- - Select HomeAssistant.
+ - Select Home Assistant.
- Drag and drop properly formatted sounds.
- Click Sync in the lower right.
- Once sync is complete, disconnect the device from the computer.
diff --git a/docs/ecosystem/nginx_subdomain/index.html b/docs/ecosystem/nginx_subdomain/index.html
index 42cf3aba55..a47ee6eded 100644
--- a/docs/ecosystem/nginx_subdomain/index.html
+++ b/docs/ecosystem/nginx_subdomain/index.html
@@ -78,7 +78,7 @@
This example demonstrates how you can configure NGINX to act as a proxy for Home Assistant.
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
@@ -121,8 +121,8 @@
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.
http:
diff --git a/docs/ecosystem/scenegen/index.html b/docs/ecosystem/scenegen/index.html
index a91dcfe032..21c2039f8a 100644
--- a/docs/ecosystem/scenegen/index.html
+++ b/docs/ecosystem/scenegen/index.html
@@ -145,7 +145,7 @@ entities:
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
diff --git a/docs/installation/centos/index.html b/docs/installation/centos/index.html
index 64e550c506..7f5430ab63 100644
--- a/docs/installation/centos/index.html
+++ b/docs/installation/centos/index.html
@@ -86,16 +86,16 @@
$ yum install rh-python35
-Once installed, switch to your homeassistant user (if you’ve set one up), enable the software collection and check that it has set up the new version of Python:
+Once installed, switch to your homeassistant user (if you’ve set one up), enable the software collection and check that it has set up the new version of Python:
$ scl enable rh-python35 bash
$ python --version
Python 3.5.1
-You will be in a command shell set up with Python 3.5 as your default version. The virtualenv and pip commands will be correct for this version, so you can now create a virtual environment and install home assistant following the main instructions.
+You will be in a command shell set up with Python 3.5 as your default version. The virtualenv and pip commands will be correct for this version, so you can now create a virtual environment and install Home Assistant following the main instructions.
You will need to enable the software collection each time you log on before you activate your virtual environment.
Systemd with Software Collections
-To autostart homeassistant using systemd follow the main instructions and adjust the template as follows:
+To autostart Home Assistant using systemd follow the main instructions and adjust the template as follows:
[Unit]
Description=Home Assistant
After=network.target
diff --git a/docs/installation/troubleshooting/index.html b/docs/installation/troubleshooting/index.html
index 8cb0e76ac7..250ea8e38c 100644
--- a/docs/installation/troubleshooting/index.html
+++ b/docs/installation/troubleshooting/index.html
@@ -116,7 +116,7 @@
After upgrading, your browser login gets stuck at the “loading data” step
After upgrading to a new version, you may notice your browser gets stuck at the “loading data” login screen. Close the window/tab and go into your browser settings and delete all the cookies for your URL. You can then log back in and it should work.
Android Chrome
-chrome -> settings -> site settings -> storage -> search for your URL for home assistant-> “clear & reset”
+chrome -> settings -> site settings -> storage -> search for your URL for Home Assistant-> “clear & reset”