-It's recommened that you only open your firewall to the SSL/TLS port (8883) and only use the insecure port (1883) for local devices. Also, disable `anonymous:` and set `logins:`. +It's recommended that you only open your firewall to the SSL/TLS port (8883) and only use the insecure port (1883) for local devices. Also, disable `anonymous:` and set `logins:`.
diff --git a/source/_components/alarm_control_panel.ifttt.markdown b/source/_components/alarm_control_panel.ifttt.markdown index 9dcf52521f3..e2f1a13955a 100644 --- a/source/_components/alarm_control_panel.ifttt.markdown +++ b/source/_components/alarm_control_panel.ifttt.markdown @@ -38,7 +38,7 @@ alarm_control_panel: ```-It is strongly discouraged to use this platform when you don't use encryption; otherwise, your API password will be send unprotected through the IFTTT Webhooks. It is adviced to [setup encryption using Let's Encrypt](https://home-assistant.io/blog/2017/09/27/effortless-encryption-with-lets-encrypt-and-duckdns/). +It is strongly discouraged to use this platform when you don't use encryption; otherwise, your API password will be send unprotected through the IFTTT Webhooks. It is advised to [setup encryption using Let's Encrypt](https://home-assistant.io/blog/2017/09/27/effortless-encryption-with-lets-encrypt-and-duckdns/).
{% linkable_title Required IFTTT applets %} @@ -86,7 +86,7 @@ For this system to operate correctly, the following IFTTT applets have to be set type: string default: alarm_disarm optimistic: - description: Specify if the state will be updated by a ifttt_push_alarm_state call (false) or can be set immediately (true). + description: Specify if the state will be updated by an ifttt_push_alarm_state call (false) or can be set immediately (true). required: false type: boolean default: false diff --git a/source/_components/doorbird.markdown b/source/_components/doorbird.markdown index 9db3c71d864..a16e7908624 100644 --- a/source/_components/doorbird.markdown +++ b/source/_components/doorbird.markdown @@ -46,7 +46,7 @@ You can create an automation that triggers on event `doorbird_doorbell` to play [`SONOS`](http://www.sonos.com) players have features allowing for "snapshotting" the current state of some or all players so those state(s) can be "restored" at a later time. This feature is perfect for implementing a doorbell sound (from Doorbird or any other Doorbell setup for that matter). The [`media_player.sonos`](/components/media_player.sonos/) platform includes the [`SONOS_SNAPSHOT`](/components/media_player.sonos/#service-sonos_snapshot) and [`SONOS_RESTORE`](/components/media_player.sonos/#service-sonos_restore) features. The result of not using these features is any currently playing songs or media will not continue playing after the doorbell sound has played and you will be left with the doorbell sound queued as the last played song. This setup allows for seamless ringing of the doorbell and all SONOS devices continuing nicely on as if nothing had happened. -The example script below takes a snapshot of three SONOS players that are not currently grouped together, joins the three players in a group (so the sound plays at the same time on all players), plays the doorbell MP3 sound, unjoins the players from the group and finally restores the players to their original state. When the players are grouped they are controlled by refering to the `master`. +The example script below takes a snapshot of three SONOS players that are not currently grouped together, joins the three players in a group (so the sound plays at the same time on all players), plays the doorbell MP3 sound, unjoins the players from the group and finally restores the players to their original state. When the players are grouped they are controlled by referring to the `master`. Automation file: diff --git a/source/_components/fan.template.markdown b/source/_components/fan.template.markdown index b7822ce308f..974eb7508e4 100644 --- a/source/_components/fan.template.markdown +++ b/source/_components/fan.template.markdown @@ -94,7 +94,7 @@ fan: required: false type: action set_oscillating: - description: Defines an action to run when the fan is given a osc state command. + description: Defines an action to run when the fan is given an osc state command. required: false type: action set_direction: diff --git a/source/_components/light.yeelight.markdown b/source/_components/light.yeelight.markdown index e19afdac670..c446d5950f7 100644 --- a/source/_components/light.yeelight.markdown +++ b/source/_components/light.yeelight.markdown @@ -72,7 +72,7 @@ This component is tested to work with the following models. If you have a differ ### {% linkable_title Service `light.yeelight_set_mode` %} -Set a operation mode. +Set an operation mode. | Service data attribute | Optional | Description | |---------------------------|----------|---------------------------------------------------------------------------------------------| diff --git a/source/_components/matrix.markdown b/source/_components/matrix.markdown index 1047d540534..e98604403d7 100644 --- a/source/_components/matrix.markdown +++ b/source/_components/matrix.markdown @@ -39,7 +39,7 @@ password: required: true type: string homeserver: - description: "The full URL for your homeserver. If you use the defauls matrix.org homeserver, this is 'https://matrix.org'." + description: "The full URL for your homeserver. If you use the default matrix.org homeserver, this is 'https://matrix.org'." required: true type: string verify_ssl: diff --git a/source/_components/notify.lametric.markdown b/source/_components/notify.lametric.markdown index 41d4aaa36d6..b9ee3343439 100644 --- a/source/_components/notify.lametric.markdown +++ b/source/_components/notify.lametric.markdown @@ -91,7 +91,7 @@ To add a notification sound, icon, cycles, or priority override, it has to be do ### {% linkable_title Only notify specific device %} -If you have more than one La Metric device, you can specify which will recieve the message by adding `target:` to the service data: +If you have more than one La Metric device, you can specify which will receive the message by adding `target:` to the service data: ```yaml action: diff --git a/source/_components/sensor.mitemp_bt.markdown b/source/_components/sensor.mitemp_bt.markdown index 248d61b8ba8..12a67606d42 100644 --- a/source/_components/sensor.mitemp_bt.markdown +++ b/source/_components/sensor.mitemp_bt.markdown @@ -73,7 +73,7 @@ sensor: - **cache_value** (*Optional*): Define cache expiration value in seconds (defaults to 1200 if not defined) - **adapter** (*Optional*): Define the Bluetooth adapter to use (defaults to hci0). Run `hciconfig` to get a list of available adapters. -Note that by default the sensor is only polled once every 5 minutes. This means with the `median: 3` setting will take as least 15 minutes before the sensor will report a value after a Home Assistant restart. Even though the hardware is able to provide new values every second, room temperaturs don't change that quickly. +Note that by default the sensor is only polled once every 5 minutes. This means with the `median: 3` setting will take as least 15 minutes before the sensor will report a value after a Home Assistant restart. Even though the hardware is able to provide new values every second, room temperatures don't change that quickly. Reducing polling intervals will have a negative effect on the battery life. A full configuration example could look like the one below: diff --git a/source/_components/snips.markdown b/source/_components/snips.markdown index 20580aa73bc..16acc2b3de6 100644 --- a/source/_components/snips.markdown +++ b/source/_components/snips.markdown @@ -115,8 +115,8 @@ site_ids: description: A list of siteIds if using multiple Snips instances. Used to make sure feedback is toggled on or off for all sites. required: false type: str -probability_threshhold: - description: Threshhold for intent probability. Range is from 0.00 to 1.00, 1 being highest match. Intents under this level are discarded. +probability_threshold: + description: Threshold for intent probability. Range is from 0.00 to 1.00, 1 being highest match. Intents under this level are discarded. require: false type: float {% endconfiguration %} diff --git a/source/_posts/2018-06-04-esphomelib.markdown b/source/_posts/2018-06-04-esphomelib.markdown index bdacd8fdfe2..a338c4f71a1 100644 --- a/source/_posts/2018-06-04-esphomelib.markdown +++ b/source/_posts/2018-06-04-esphomelib.markdown @@ -15,7 +15,7 @@ The [ESP8266](https://www.espressif.com/en/products/hardware/esp8266ex/overview) Setting up these microcontrollers for some basic functionality has also gotten really easy over the years with popular projects like ESPEasy or Sonoff-Tasmota: You just download their firmware and flash it onto your chip. But if you’ve ever tried to go a bit beyond the basic set of functions of those frameworks and tried to do some customization, you will have probably noticed that it’s not that easy. Often times you’ll end up having to download some Arduino code project from the internet and customizing it to your needs. -This is where esphomlib comes in: The [esphomelib suite](https://esphomelib.com/esphomeyaml/index.html) is a set of tools that are designed with the goal of achieving the best possible user experience. esphomelib a) allows for lots of customization without touching *a single line* of code and b) has complete Home Assistant integration. Inside the esphomelib ecosystem, you essentially just have to write a simple YAML configuration file. The rest like compiling, flashing, uploading etc. will then be taken care of automatically. +This is where esphomelib comes in: The [esphomelib suite](https://esphomelib.com/esphomeyaml/index.html) is a set of tools that are designed with the goal of achieving the best possible user experience. esphomelib a) allows for lots of customization without touching *a single line* of code and b) has complete Home Assistant integration. Inside the esphomelib ecosystem, you essentially just have to write a simple YAML configuration file. The rest like compiling, flashing, uploading etc. will then be taken care of automatically.