A full configuration example will look like the sample below:
diff --git a/cookbook/tor_configuration/index.html b/cookbook/tor_configuration/index.html index bc426b1d62..f6586fcd4a 100644 --- a/cookbook/tor_configuration/index.html +++ b/cookbook/tor_configuration/index.html @@ -116,7 +116,7 @@First, install Tor. On a Debain-based system, you can install the package easily:
+First, install Tor. On a Debian-based system, you can install the package easily:
$ sudo apt-get install tor
With this configuration, only you can access your Home Assistant instance Onion site through Tor, and no one else. You can share the authentication cookie with multiple devices and users, or you can generate a unique one for each - up to you! If you have multiple, say for an industrial, business or corporate configuration, this would provide an easy way to revoke access to a specific user or device.
-If you always access your Home Assistant instance via Tor, you can easily run this on an isolated “IoT” network segment at your install site, keeping your internal home network traffic seperate from any potentially compromised devices (like cheap “smart” lightbulbs with backdoors!).
+If you always access your Home Assistant instance via Tor, you can easily run this on an isolated “IoT” network segment at your install site, keeping your internal home network traffic separate from any potentially compromised devices (like cheap “smart” lightbulbs with backdoors!).
You could also use Tor as a means to connect your Home Assistant instance to a remote device, sensor or other service that you do not want to or connect provide a direct, open IP connection to. Again, Tor provides authenticated and confidential routing (aka “privacy and encryption”) by default, without having to setup TLS/SSL or VPN. It is just important to secure IoT nodes within your network, as it is to secure remote access!
diff --git a/sitemap.xml b/sitemap.xml index 40adfd1c27..bfe7aaf9fd 100644 --- a/sitemap.xml +++ b/sitemap.xml @@ -2257,62 +2257,62 @@Next two statements result in same value if state exists. Second one will result in an error if state does not exist.
+The next two statements result in same value if state exists. The second one will result in an error if state does not exist.
{{ states('device_tracker.paulus') }}
{{ states.device_tracker.paulus.state }}
@@ -213,7 +213,7 @@ The frontend has a template editor developer tool to help develop and debug temp
Distance examples
-If only 1 location is passed in will measure the distance from home.
+If only 1 location is passed in, Home Assistant will measure the distance from home.
Using Lat Lng coordinates: {{ distance(123.45, 123.45) }}
@@ -245,7 +245,7 @@ Closest to an entity: {{ closest(states.zone.school, 'group.children') }}
Combined
-Since closest returns a state, we can combine it with distance too
+Since closest returns a state, we can combine it with distance too.
{{ closest(states).name }} is {{ distance(closest(states)) }} meters away.
@@ -255,7 +255,7 @@ Closest to an entity: {{ closest(states.zone.school, 'group.children') }}
The other part of templating is processing incoming data. It will allow you to modify incoming data and extract only the data you care about. This will work only for platforms and components that mentioned support for this in their documentation.
-It depends per component or platform but it is common to be able to define a template using the value_template configuration key. When a new value arrives, your template will be rendered while having access to the following values on top of the usual Home Assistant extensions:
+It depends per component or platform, but it is common to be able to define a template using the value_template configuration key. When a new value arrives, your template will be rendered while having access to the following values on top of the usual Home Assistant extensions: