diff --git a/source/_addons/snips.markdown b/source/_addons/snips.markdown index 851afd8e7d9..e8377a1b5a7 100644 --- a/source/_addons/snips.markdown +++ b/source/_addons/snips.markdown @@ -13,7 +13,7 @@ footer: true The Snips add-on depends on the Mosquitto add on to bridge to Home Assistant, so make sure that is installed. -HomeAssistant comes with certain Intents builtin to handle common tasks. A complete list of Intents can be found in this wiki [Hass Snips Bundle](https://github.com/tschmidty69/hass-snips-bundle-intents/wiki). +Home Assistant comes with certain Intents builtin to handle common tasks. A complete list of Intents can be found in this wiki [Hass Snips Bundle](https://github.com/tschmidty69/hass-snips-bundle-intents/wiki). The Snips addon by default comes with an assistant that allows you to turn on lights or switches, open covers, or add and list items to a shopping list if that component is enabled. @@ -25,7 +25,7 @@ Open garage door What is on my shopping list ``` -To get started creating your own configuration, follow [their tutorial](https://snips.gitbook.io/documentation/console) to create an assistant and download the training data. You can also add the HomeAssistant Skill to your assistant to enable the built-in intents, and add or create your own intents to do more complex tasks. +To get started creating your own configuration, follow [their tutorial](https://snips.gitbook.io/documentation/console) to create an assistant and download the training data. You can also add the Home Assistant Skill to your assistant to enable the built-in intents, and add or create your own intents to do more complex tasks. Now install and activate the [Samba](/addons/samba/) add-on so you can upload your training data. Connect to the "share" Samba share and copy your assistant over. Name the file `assistant.zip` or whatever you have configured in the configuration options. @@ -114,4 +114,3 @@ searchWeatherForecast: Now just restart HassIO and ask it what the weather is like. [their tutorial]: https://github.com/snipsco/snips-platform-documentation/wiki/2.-Create-an-assistant-using-an-existing-bundle - diff --git a/source/_components/rss_feed_template.markdown b/source/_components/rss_feed_template.markdown index d5ac1313672..36fcddfc51f 100644 --- a/source/_components/rss_feed_template.markdown +++ b/source/_components/rss_feed_template.markdown @@ -20,7 +20,7 @@ For example, on Android, the app "Simple RSS Widget" can be used to display temp ```yaml # Example configuration.yaml entry rss_feed_template: - # Accessible on /api/rss_template/garden + # Accessible on /api/rss_template/garden # Example: https://localhost:8123/api/rss_template/garden garden: requires_api_password: False diff --git a/source/_components/sensor.nest.markdown b/source/_components/sensor.nest.markdown index f31f62b9b3e..99d40e63016 100644 --- a/source/_components/sensor.nest.markdown +++ b/source/_components/sensor.nest.markdown @@ -59,9 +59,9 @@ The following conditions are available by device: ## {% linkable_title Security State %}

-This feature is not designed to transfer your Home Assitant to a security system, neither Home Assistant nor Nest be liable to You for damages, +This feature is not designed to transfer your Home Assistant to a security system, neither Home Assistant nor Nest be liable to You for damages, or consequential damages of any character arising as a result of use this feature. - + This feature does not depend on the [Nest Secure alarm system](https://nest.com/alarm-system/overview/) and is not a reflection of the status of that system, nor does it react to state changes in that system.

diff --git a/source/_docs/ecosystem/appdaemon/api.markdown b/source/_docs/ecosystem/appdaemon/api.markdown index 8efa974eb47..be4a60c0245 100755 --- a/source/_docs/ecosystem/appdaemon/api.markdown +++ b/source/_docs/ecosystem/appdaemon/api.markdown @@ -942,7 +942,7 @@ time, interval, kwargs = self.info_timer(handle) All of the scheduler calls above support 2 additional optional arguments, `random_start` and `random_end`. Using these arguments it is possible to randomize the firing of callbacks to the degree desired by setting the appropriate number of seconds with the parameters. - `random_start` - start of range of the random time -- `random_end` - end of range of the random time +- `random_end` - end of range of the random time `random_start` must always be numerically lower than `random_end`, they can be negative to denote a random offset before and event, or positive to denote a random offset after an event. The event would be an absolute or relative time or sunrise/sunset depending on which scheduler call you use and these values affect the base time by the spcified amount. If not specified, they will default to `0`. @@ -1490,7 +1490,7 @@ service, kwargs = self.info_listen_event(handle) ### {% linkable_title fire_event() %} -Fire an event on the HomeAssistant bus, for other components to hear. +Fire an event on the Home Assistant bus, for other components to hear. #### {% linkable_title Synopsis %} diff --git a/source/_docs/security/porosity.markdown b/source/_docs/security/porosity.markdown index 19941ab8208..4858aa0a04c 100644 --- a/source/_docs/security/porosity.markdown +++ b/source/_docs/security/porosity.markdown @@ -15,7 +15,7 @@ The IP address of the Home Assistant machine is 192.168.0.215. The system which ## {% linkable_title SSH server Add-on %} -To get access to Hass.io in secure way, SSH is provided by the [SSH server add-on](/addons/ssh/). +To get access to Hass.io in secure way, SSH is provided by the [SSH server add-on](/addons/ssh/). ```bash $ sudo nmap -A -n --reason -Pn -T5 -p1-65535 192.168.0.215 @@ -27,13 +27,13 @@ Not shown: 65532 closed ports Reason: 65532 resets PORT STATE SERVICE REASON VERSION 22/tcp open ssh syn-ack ttl 63 OpenSSH 7.5 (protocol 2.0) -| ssh-hostkey: +| ssh-hostkey: | 2048 e3:a2:2d:20:3a:67:68:b9:b1:9e:16:fa:48:80:82:96 (RSA) | 256 92:f0:f4:be:4f:44:60:0e:c4:92:8a:cb:34:9e:c5:c2 (ECDSA) |_ 256 09:da:a2:14:cd:c4:69:e9:13:e6:70:64:98:d0:55:0c (EdDSA) 8123/tcp open http syn-ack ttl 64 aiohttp 3.1.3 (Python 3.6) |_http-open-proxy: Proxy might be redirecting requests -| http-robots.txt: 1 disallowed entry +| http-robots.txt: 1 disallowed entry |_/ |_http-server-header: Python/3.6 aiohttp/3.1.3 |_http-title: Home Assistant @@ -70,15 +70,15 @@ Not shown: 65532 closed ports Reason: 65532 resets PORT STATE SERVICE REASON VERSION 1883/tcp open mosquitto version 1.4.12 syn-ack ttl 63 -| mqtt-subscribe: -| Topics and their most recent payloads: +| mqtt-subscribe: +| Topics and their most recent payloads: | $SYS/broker/load/connections/5min: 0.39 [...] | $SYS/broker/load/connections/15min: 0.13 |_ $SYS/broker/clients/total: 2 8123/tcp open http syn-ack ttl 64 aiohttp 3.1.3 (Python 3.6) |_http-open-proxy: Proxy might be redirecting requests -| http-robots.txt: 1 disallowed entry +| http-robots.txt: 1 disallowed entry |_/ |_http-server-header: Python/3.6 aiohttp/3.1.3 |_http-title: Home Assistant @@ -119,7 +119,7 @@ PORT STATE SERVICE REASON VERSION 445/tcp open netbios-ssn syn-ack ttl 64 Samba smbd 4.7.3 (workgroup: WORKGROUP) 8123/tcp open http syn-ack ttl 64 aiohttp 3.1.3 (Python 3.6) |_http-open-proxy: Proxy might be redirecting requests -| http-robots.txt: 1 disallowed entry +| http-robots.txt: 1 disallowed entry |_/ |_http-server-header: Python/3.6 aiohttp/3.1.3 |_http-title: Home Assistant @@ -134,21 +134,21 @@ Service Info: Host: HASSIO; OS: Linux; CPE: cpe:/o:linux:linux_kernel Host script results: |_nbstat: NetBIOS name: HASSIO, NetBIOS user: , NetBIOS MAC: (unknown) -| smb-os-discovery: +| smb-os-discovery: | OS: Windows 6.1 (Samba 4.7.3) | Computer name: \x00 | NetBIOS computer name: HASSIO\x00 | Workgroup: WORKGROUP\x00 |_ System time: 2018-05-29T16:41:05+02:00 -| smb-security-mode: +| smb-security-mode: | account_used: guest | authentication_level: user | challenge_response: supported |_ message_signing: disabled (dangerous, but default) -| smb2-security-mode: -| 2.02: +| smb2-security-mode: +| 2.02: |_ Message signing enabled but not required -| smb2-time: +| smb2-time: | date: 2018-05-29 16:41:05 |_ start_date: 1601-01-01 00:53:28 @@ -172,7 +172,7 @@ $ smbclient -L //192.168.0.215 -U% share Disk backup Disk IPC$ IPC -IPC Service (Samba HomeAssistant config share) +IPC Service (Samba Home Assistant config share) Reconnecting with SMB1 for workgroup listing. Server Comment diff --git a/source/_posts/2016-04-30-ibeacons-part-1-making-presence-detection-work-better.markdown b/source/_posts/2016-04-30-ibeacons-part-1-making-presence-detection-work-better.markdown index 8a1a8dae127..5f06498882e 100644 --- a/source/_posts/2016-04-30-ibeacons-part-1-making-presence-detection-work-better.markdown +++ b/source/_posts/2016-04-30-ibeacons-part-1-making-presence-detection-work-better.markdown @@ -35,7 +35,7 @@ You then have to (A) tell Home Assistant where the beacon is located and (B) tel #### {% linkable_title A. Tell Home Assistant where your beacon is located %} -You tell HomeAssistant about fixed locations by creating a Zone with the longitude and latitude of your beacon. You should also give the zone a name which you will also use when you set up OwnTracks. An an example this zone specifies the location of my drive way. +You tell Home Assistant about fixed locations by creating a Zone with the longitude and latitude of your beacon. You should also give the zone a name which you will also use when you set up OwnTracks. An an example this zone specifies the location of my drive way. **Example `configuration.yaml` entry** diff --git a/source/_posts/2018-07-06-release-73.markdown b/source/_posts/2018-07-06-release-73.markdown index 2f08a40ce8b..e63aea2452b 100644 --- a/source/_posts/2018-07-06-release-73.markdown +++ b/source/_posts/2018-07-06-release-73.markdown @@ -73,7 +73,7 @@ Experiencing issues introduced by this release? Please report them in our [issue - Remove typing ([@fabaff] - [#15018]) - Add support for Homekit battery service ([@schmittx] - [#14288]) ([homekit docs]) - Update PostNL unit of measure to align with UPS ([@keesschollaart81] - [#15023]) ([sensor.postnl docs]) (breaking change) -- Expose Wemo component availability to home assistant ([@gstorer] - [#14995]) ([light.wemo docs]) +- Expose Wemo component availability to Home Assistant ([@gstorer] - [#14995]) ([light.wemo docs]) - Improve volume support for Vizio Smartcast ([@JeffLIrion] - [#14981]) ([media_player.vizio docs]) - Upgrade requests to 2.19.1 ([@fabaff] - [#15019]) - Show running apps as sources for Fire TV ([@JeffLIrion] - [#15033]) ([media_player.firetv docs]) @@ -125,7 +125,7 @@ Experiencing issues introduced by this release? Please report them in our [issue - Adding 'namespace' for prometheus metrics ([@alexbarcelo] - [#13738]) ([prometheus docs]) (breaking change) - Storage auth ([@balloob] - [#15192]) - Make sure we check access token expiration ([@balloob] - [#15207]) ([frontend docs]) -- Migrate home assistant auth provider to use storage helper ([@balloob] - [#15200]) +- Migrate Home Assistant auth provider to use storage helper ([@balloob] - [#15200]) - Fix zwave climate operation mode mappings ([@cdce8p] - [#15162]) ([climate.zwave docs]) (breaking change) - Fixed Indentation error ([@vaidyasr] - [#15210]) ([camera.xiaomi docs]) - X-Forwarded-For improvements and bug fixes ([@colinodell] - [#15204]) ([emulated_hue docs]) ([http docs]) (breaking change) diff --git a/source/lovelace/index.markdown b/source/lovelace/index.markdown index 0588126e2df..848cfeef188 100644 --- a/source/lovelace/index.markdown +++ b/source/lovelace/index.markdown @@ -116,7 +116,7 @@ views: Now restart Home Assistant, navigate to `/lovelace`. When you make changes to `ui-lovelace.yaml`, you don't have to restart Home Assistant or refresh the page. Just hit the refresh button at the top of the UI. ## {% linkable_title Setting Lovelace as the Default UI %} -Once you are ready to start using Lovelace UI as your main user interface, click on info, the "i" icon under 'Developer Tools" in the home assistant side-bar. Next, locate >>Set lovelace as default page on this device<< under the home assistant version information and click it. +Once you are ready to start using Lovelace UI as your main user interface, click on info, the "i" icon under 'Developer Tools" in the Home Assistant side-bar. Next, locate >>Set Lovelace as default page on this device<< under the Home Assistant version information and click it. Note that this is a per-device setting and will need to be changed on each device you access the UI from.