Home Assistant Server (#16867)

source/_integrations/asterisk_mbox.markdown

@@ -44,5 +44,5 @@ port:
 {% endconfiguration %}
 
 <div class='note warning'>
-Communication between the Asterisk PBX server and the Home Assistant server is password-protected, but the data transmission is not encrypted. It is recommended to only use this integration when communication is contained within a local area network.
+Communication between the Asterisk PBX server and Home Assistant is password-protected, but the data transmission is not encrypted. It is recommended to only use this integration when communication is contained within a local area network.
 </div>

source/_integrations/cloudflare.markdown

@@ -69,7 +69,7 @@ For SSH usage (according to [this](https://blog.cloudflare.com/cloudflare-now-su
 
 #### The minimum DNS record settings (if you have set up HTTPS already)
 
-To redirect from your domain to the IP address of your Home Assistant server set this DNS record:
+To redirect from your domain to the IP address of your Home Assistant instance, set this DNS record:
 
 ```text
 Type: A

source/_integrations/debugpy.markdown

@@ -63,9 +63,9 @@ wait:
 
 Ensure if this is a public-facing server, that the port is secured. Anyone who
 is able to access the debugger port can *execute arbitrary code* on the
-Home Assistant server, which is very unsafe.
+Home Assistant instance, which is very unsafe.
 
-If the Home Assistant server is behind your firewall with only the http(s) port
+If the Home Assistant instance is behind your firewall with only the http(s) port
 exposed, then this is safe from outside connections.
 
 ## Performance and Memory Use

source/_integrations/dialogflow.markdown

@@ -49,7 +49,7 @@ To get the webhook URL, go to the integrations page in the configuration screen
 - At the bottom of the page, expand "Fulfillment" and check "Use webhook".
 - Click "Save".
 - At the top right of the screen where it says "Try it now...", type, or say, the phrase you have previously defined and hit enter.
-- Dialogflow will now send a request to your Home Assistant server and display the response.
+- Dialogflow will now send a request to your Home Assistant instance and display the response.
 
 <div class='note warning'>
 

source/_integrations/fail2ban.markdown

@@ -128,7 +128,7 @@ proxy_set_header X-Real-IP $remote_addr;
 proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
 ```
 
-This snippet should be added within your Home Assistant server configuration, so you have something like the following:
+This snippet should be added within your Home Assistant configuration, so you have something like the following:
 
 ```bash
 server {

source/_integrations/geniushub.markdown

@@ -191,7 +191,7 @@ This is the recommended option.
 - Polls the hub directly (so is faster, say ~1s response time).
 - You have the option of specifying a MAC address (not recommended, see above).
 
-The hub does not have to be in the same subnet as your Home Assistant server.
+The hub does not have to be in the same subnet as your Home Assistant instance.
 
 ### Option 2: hub token only
 

source/_integrations/geofency.markdown

@@ -15,7 +15,7 @@ This integration sets up integration with [Geofency](https://www.geofency.com/).
 
 ## Configuration
 
-To configure Geofency, you must set it up via the integrations panel in the configuration screen. You must then configure the iOS app (via the Webhook feature) to send a POST request to your Home Assistant server at the webhook URL provided by the integration during setup. Use the default POST format. Make sure to enable the 'Update Geo-Position' functionality for mobile beacons.
+To configure Geofency, you must set it up via the integrations panel in the configuration screen. You must then configure the iOS app (via the Webhook feature) to send a POST request to your Home Assistant instance at the webhook URL provided by the integration during setup. Use the default POST format. Make sure to enable the 'Update Geo-Position' functionality for mobile beacons.
 
 Geofency will automatically generate the device tracker name used for geofences, and you will find it in the integrations section after the first request. For beacons, the device name will be `beacon_<name from Geofency>`, e.g., `device_tracker.beacon_car`.
 

source/_integrations/homematic.markdown

@@ -46,7 +46,7 @@ Device support is available for most of the wired and wireless devices, as well
 
 <div class='note info'>
 
-Since CCU Version 3, the internal firewalls are enabled by default. You have to grant full access for the `XML-RPC API` or specify the IP-address of the Home Assistant server and whitelist it, inside the CCU's security settings.
+Since CCU Version 3, the internal firewalls are enabled by default. You have to grant full access for the `XML-RPC API` or specify the IP-address of the Home Assistant instance and allowlist it, inside the CCU's security settings.
 
 </div>
 

source/_integrations/ifttt.markdown

@@ -66,7 +66,7 @@ ifttt:
 Property screen of the Maker Channel
 </p>
 
-Once you have added your key to your `configuration.yaml` file, restart your Home Assistant server. This will load up the IFTTT integration and make a service available to trigger events in IFTTT.
+Once you have added your key to your `configuration.yaml` file, restart your Home Assistant instance. This will load up the IFTTT integration and make a service available to trigger events in IFTTT.
 
 <div class='note'>
 After restarting the server, be sure to watch the console for any logging errors that show up in red, white or yellow.

source/_integrations/locative.md

@@ -15,7 +15,7 @@ Install on your smartphone:
 
 - [iOS](https://apps.apple.com/us/app/locative/id725198453?ign-mpt=uo%3D4)
 
-To configure Locative, you must set it up via the integrations panel in the configuration screen. You must set up the app to send a POST request to your Home Assistant server at the webhook URL provided by the integration during setup. When you enter or exit a geofence, Locative will send the appropriate request to that URL, updating Home Assistant. You are not able to specify a device name in Locative. Instead, you will need to look in your `dev-state` menu for a new device that Locative will have created on it's first `GET`. If you had been or are using Owntracks as well, you will need to update the device name used in the Owntracks setup with the name that Locative generated.
+To configure Locative, you must set it up via the integrations panel in the configuration screen. You must set up the app to send a POST request to your Home Assistant instance at the webhook URL provided by the integration during setup. When you enter or exit a geofence, Locative will send the appropriate request to that URL, updating Home Assistant. You are not able to specify a device name in Locative. Instead, you will need to look in your `dev-state` menu for a new device that Locative will have created on it's first `GET`. If you had been or are using Owntracks as well, you will need to update the device name used in the Owntracks setup with the name that Locative generated.
 
 <p class='img'>
   <img src='/images/screenshots/locative.png'/>

source/_integrations/otp.markdown

@@ -57,5 +57,5 @@ Token: IHEDPEBEVA2WVHB7
 Copy and paste the token into your Home Assistant configuration and add it to your OTP generator. Verify that they generate the same code.
 
 <div class='note warning'>
-It is vital that your system clock is correct both on your Home Assistant server and on your OTP generator device (e.g., your phone). If not, the generated codes will not match! Make sure NTP is running and syncing your time correctly before creating an issue.
+It is vital that your system clock is correct both on your Home Assistant instance and on your OTP generator device (e.g., your phone). If not, the generated codes will not match! Make sure NTP is running and syncing your time correctly before creating an issue.
 </div>

source/_integrations/sonos.markdown

@@ -190,7 +190,7 @@ sonos:
       - 192.0.2.27
 ```
 
-If your Home Assistant server has multiple IP addresses, you can provide the IP address that should be used for Sonos auto-discovery. This is rarely needed since all addresses should be tried by default.
+If your Home Assistant instance has multiple IP addresses, you can provide the IP address that should be used for Sonos auto-discovery. This is rarely needed since all addresses should be tried by default.
 
 ```yaml
 # Example configuration.yaml entry using Sonos discovery on a specific interface

source/_integrations/wink.markdown

@@ -68,7 +68,7 @@ No settings are required in the `configuration.yaml` other than `wink:`.
 After adding `wink:` to your `configuration.yaml` and restarting Home Assistant you will see a persistent notification on the frontend with a `CONFIGURE` button that will guide you through the setup via the frontend configurator.
 
 <div class='note'>
-When using the configurator make sure the initial setup is performed on the same local network as the Home Assistant server, if not from the same box Home Assistant is running on. This will allow for authentication redirects to happen correctly.
+When using the configurator make sure the initial setup is performed on the same local network as the Home Assistant instance, if not from the same box Home Assistant is running on. This will allow for authentication redirects to happen correctly.
 </div>
 
 ```yaml

source/_posts/2020-07-01-release-112.markdown

@@ -213,7 +213,7 @@ An improvement in the battery of your device and your data cap are going to
 like:
 
 When the Home Assistant UI is not visible for longer than 5 minutes, it
-disconnects from your Home Assistant server. This means you no longer get data or
+disconnects from your Home Assistant instance. This means you no longer get data or
 camera streams and your device can optimize resource and power consumption.
 
 Of course, when showing the browser (or browser tab) again, it will

source/_posts/2020-08-28-android-230-release.markdown

@@ -13,7 +13,7 @@ Hey there, its been so long since we last gave an update on our mobile apps we t
 
 ## Manage Sensors
 
-Starting from version 2.2.0 there is a new Manage Sensors screen that you can find under App Configuration. Users can now disable sensors they don't want while continuing to receive updates from the sensors they do care about. This includes turning off the Geocoded sensor while keeping location tracking on. Speaking of which the 2 location toggles that used to be found in App Configuration are now located in this new screen. You can expect to see the live data that was recently sent over to your Home Assistant server as well as the attributes and other sensor details.
+Starting from version 2.2.0 there is a new Manage Sensors screen that you can find under App Configuration. Users can now disable sensors they don't want while continuing to receive updates from the sensors they do care about. This includes turning off the Geocoded sensor while keeping location tracking on. Speaking of which the 2 location toggles that used to be found in App Configuration are now located in this new screen. You can expect to see the live data that was recently sent over to your Home Assistant instance as well as the attributes and other sensor details.
 
 <p class='img'>
 <img src='/images/blog/2020-08-28-android-230-release/manage_sensors.png' alt='Screenshot of Manage Sensors'></a>
@@ -27,7 +27,7 @@ Screenshot of Sensor Management.
 
 ## New Sensors
 
-We have had quite a bit of sensors get added since we last spoke so here's whats new. Some of these sensors will update their state in your Home Assistant server upon certain state changes. All of the sensors listed below will also update during the normal 15 minute update interval. To get more details about what to expect from each sensor check out the [docs](https://companion.home-assistant.io/docs/core/sensors).
+We have had quite a bit of sensors get added since we last spoke so here's whats new. Some of these sensors will update their state in your Home Assistant instance upon certain state changes. All of the sensors listed below will also update during the normal 15 minute update interval. To get more details about what to expect from each sensor check out the [docs](https://companion.home-assistant.io/docs/core/sensors).
 
 Available for Google Play Store version only:
 

source/_posts/2020-09-12-android-240-release.markdown

@@ -15,7 +15,7 @@ Hey there, I hope everyone has been enjoying the last release of the Android app
 
 Sometimes when we move really fast, we may move a bit too fast. While we had fun adding all the new sensors, we didn't stop to think about the new user experience and how we are making a burden on them by having non-static attributes for some of the sensors. In reality, these attributes are a state and we need to treat them as such. If we don't, there will be a need to use templates that are not user-friendly. We wanted to fix this issue and be courteous to our current users, so we have made a few changes. Some of which take place in this release and some in the following release after 2.4.0.
 
-The first major change in this release is that the app will no longer send needless updates to your Home Assistant server when there is nothing new to report state-wise. This helps cut down on the amount of data that gets sent out. Some attributes attached to some sensors update outside of the state, to combat this change, we have split those attributes to become their own sensor. For example, the audio sensor had an attribute to tell if headphones were currently plugged into the device. This, by itself, is a state change and thus now a binary sensor.
+The first major change in this release is that the app will no longer send needless updates to your Home Assistant instance when there is nothing new to report state-wise. This helps cut down on the amount of data that gets sent out. Some attributes attached to some sensors update outside of the state, to combat this change, we have split those attributes to become their own sensor. For example, the audio sensor had an attribute to tell if headphones were currently plugged into the device. This, by itself, is a state change and thus now a binary sensor.
 
 We have opted to keep the existing attributes where they are for this release, this way they do not break existing templates. However, they may trigger slower until you move to the new sensor. All of the new sensors are also disabled by default (with the exception of battery), so you may want to enable the ones you care for. The following sensors have had their attributes split up:
 

source/_posts/2020-09-17-release-115.markdown

@@ -230,7 +230,7 @@ this means that this setting is device-based and will be cleared when you logout
 You can now upload images for a person in the frontend!
 
 Select or drop an image in the input field and then crop it to a square. The
-image is stored on your Home Assistant server.
+image is stored on your Home Assistant instance.
 
 <div class='videoWrapper'>
 <iframe width="560" height="315" src="https://www.youtube-nocookie.com/embed/rOlRnwaaT7Y" frameborder="0" allowfullscreen></iframe>

source/_posts/2020-11-06-android-300-release.markdown

@@ -55,9 +55,9 @@ Screenshot of location settings.
 </p>
 
 - Next Alarm - This sensor has a setting for an allow list. This means that if you have an app that reports really odd timestamps as an actual alarm, you can now ignore them by telling the app which packages to send reports from. By default the list is blank. Tasker users are recommended to make use of this setting.
-- Last Notification - This sensor also has an allow list to let the user create a list of apps from which they want notification data from. By default all notifications are sent to your Home Assistant server. We highly recommend that you set up an allow list as soon as you can think of one to prevent a high amount of updates. You will be surprised by the amount of data that will show up in a short time period.
+- Last Notification - This sensor also has an allow list to let the user create a list of apps from which they want notification data from. By default all notifications are sent to your Home Assistant instance. We highly recommend that you set up an allow list as soon as you can think of one to prevent a high amount of updates. You will be surprised by the amount of data that will show up in a short time period.
 - Last Reboot - A bug was discovered where sometimes the timing in the calculation of the device's last reboot could be off causing an unnecessary update. There is now a deadband setting to allow you to adjust the timing to ignore updates. By default this is set to 1 minute, you most likely won't need to change this.
-- Location Sensors - All 3 location sensors now have settings to allow you to adjust the minimum accuracy required to send a update to your Home Assistant server. There is also a setting to adjust the minimum amount of time between updates. This should help a lot of users out who don't get the location results they expect. We recommend changing this setting after you evaluate all of the location fixes in 3.0.0 as location tracking may already be improved without needing to adjust these.
+- Location Sensors - All 3 location sensors now have settings to allow you to adjust the minimum accuracy required to send a update to your Home Assistant instance. There is also a setting to adjust the minimum amount of time between updates. This should help a lot of users out who don't get the location results they expect. We recommend changing this setting after you evaluate all of the location fixes in 3.0.0 as location tracking may already be improved without needing to adjust these.
 - WiFi BSSID - This sensor has a setting that will allow the user to provide an alias for the currently connected BSSID. Not everyone can remember a MAC address let alone dozens of them. This setting is designed to help out those who use this sensor to make better sense of things without the need for secrets or templates. If you live in a household with multiple access points you may find it useful to set up an alias to help with things like room presence. By default this sensor reports the connected MAC address.