jeans/home-assistant.io
jeans/home-assistant.io
1
0
Fork 0
mirror of https://github.com/home-assistant/home-assistant.io.git synced 2025-07-24 17:57:14 +00:00
Code Issues Packages Projects Releases Wiki Activity

Extends textlint Terminology list; part 2 (#12068)

Browse Source
This commit is contained in:
Franck Nijhof 2020-02-12 19:59:10 +01:00 committed by GitHub
parent fb5245e54c
commit f0d37f49db
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
105 changed files with 244 additions and 189 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

58
.textlintrc.json
View File

@ -8,11 +8,13 @@
"defaultTerms": false,
"skip": ["Blockquote"],
"terms": [
" API ",
"Abode",
"Acer",
"Actiontec",
"AdGuard Home",
"AdGuard",
"ADS",
"Aeotec",
"AfterShip",
"Airly",
@ -35,8 +37,10 @@
"AWS",
"Axis",
"Beckhoff",
"Cisco IOS",
"Dark Sky",
"deCONZ",
"DNS",
"ecobee",
"Elgato Key Light",
"Elgato",
@ -58,19 +62,71 @@
"Home Assistant",
"HomeKit",
"Honeywell",
"HTTP",
"HTTPS",
"iCloud",
"IFTTT",
"IKEA",
"IntesisHome",
"iOS",
"IoT",
"IP",
"JSON",
"KEF",
"Life360",
"Lovelace",
"macOS",
"Microsoft",
"MikroTik",
"MJPEG",
"MQTT",
"NodeMCU",
"Philips",
"Plex Media Server",
"Plex",
"PTZ",
"REST API",
"RFXtrx",
"RouterOS",
"Samung",
"Sentry",
"Signal Messenger",
"SmartThings",
"Sonos",
"Spotify",
"SSL",
"Stookalert",
"Sure Petcare",
"Tahoma",
"TCP/IP",
"TMB",
"TwinCAT",
"Twitter",
"UART",
"UI",
"URL",
"Velbus",
"Vera",
"Vizio",
"Wink",
"WLED",
"Xiaomi",
"YAML",
"Yeelight",
"YouTube",
"Z-Wave",
"ZHA",
"Zigbee",
[" HA ", "Home Assistant"],
["Alarm ?dot ?com", "Alarm.com"],
["an URL", "a URL"],
["API['’]?s", "APIs"],
["hass", "Home Assistant"],
["Home-?Ass?s?iss?tt?ant", "Home Assistant"],
["Mac ?OS", "macOS"],
["OS ?X", "macOS"]
["OS ?X", "macOS"],
["URL['’]?s", "URLs"],
["ZWave", "Z-Wave"]
]
}
}

4
source/_cookbook/automation_first_light.markdown
View File

@ -4,7 +4,7 @@ description: "Automation examples that trigger lights in the morning."
ha_category: Automation Examples
---
#### Create an input_boolean in your configuration.yaml
#### Create an input_boolean
```yaml
input_boolean:
@ -13,7 +13,7 @@ input_boolean:
icon: mdi:kettle
```
#### The Main Automation
#### The Main Automation
```yaml
## These first two control t input_boolean that allows the "first morning action" to occur

10
source/_docs/authentication.markdown
View File

@ -15,9 +15,9 @@ If you are starting Home Assistant for the first time, or you have logged out, y
When you start Home Assistant for the first time the _owner_ user account is created. This account has some special privileges and can:
- Create and manage other user accounts.
- Configure integrations and other settings (coming soon).
- Configure Hass.io (coming soon).
- Create and manage other user accounts.
- Configure integrations and other settings (coming soon).
- Configure Hass.io (coming soon).
<div class='note'>
For the moment, other user accounts will have the same access as the owner account. In the future, non-owner accounts will be able to have restrictions applied.
@ -86,11 +86,11 @@ While you should hopefully be storing your passwords in a password manager, if y
When you start Home Assistant next, you'll be required to set up authentication again.
### Error: invalid client id or redirect url
### Error: invalid client id or redirect URL
<img src='/images/docs/authentication/error-invalid-client-id.png' alt='Screenshot of Error: invalid client id or redirect url'>
You have to use a domain name, not IP address, to remote access Home Assistant otherwise you will get **Error: invalid client id or redirect url** error on the login form. However, you can use the IP address to access Home Assistant in your home network.
You have to use a domain name, not IP address, to remote access Home Assistant otherwise you will get `Error: invalid client id or redirect url` error on the login form. However, you can use the IP address to access Home Assistant in your home network.
This is because we only allow an IP address as a client ID when your IP address is an internal network address (e.g., `192.168.0.1`) or loopback address (e.g., `127.0.0.1`).

22
source/_docs/automation/templating.markdown
View File

@ -31,7 +31,7 @@ automation 2:
notify.{{ trigger.topic.split('/')[-1] }}
data_template:
message: '{{ trigger.payload }}'
automation 3:
trigger:
# Multiple entities for which you want to perform the same action.
@ -84,7 +84,7 @@ Knowing how to access the [state object](/docs/configuration/state_object/) of a
The following tables show the available trigger data per platform.
### event
### Event
| Template variable | Data |
| ---- | ---- |
@ -92,7 +92,7 @@ The following tables show the available trigger data per platform.
| `trigger.event` | Event object that matched.
| `trigger.event.data` | Optional data
### mqtt
### MQTT
| Template variable | Data |
| ---- | ---- |
@ -102,7 +102,7 @@ The following tables show the available trigger data per platform.
| `trigger.payload_json` | Dictonary of the JSON parsed payload.
| `trigger.qos` | QOS of payload.
### numeric_state
### Numeric State
| Template variable | Data |
| ---- | ---- |
@ -114,7 +114,7 @@ The following tables show the available trigger data per platform.
| `trigger.to_state` | The new [state object] that triggered trigger.
| `trigger.for` | Timedelta object how long state has met above/below criteria, if any.
### state
### State
| Template variable | Data |
| ---- | ---- |
@ -124,7 +124,7 @@ The following tables show the available trigger data per platform.
| `trigger.to_state` | The new [state object] that triggered trigger.
| `trigger.for` | Timedelta object how long state has been to state, if any.
### sun
### Sun
| Template variable | Data |
| ---- | ---- |
@ -132,7 +132,7 @@ The following tables show the available trigger data per platform.
| `trigger.event` | The event that just happened: `sunset` or `sunrise`.
| `trigger.offset` | Timedelta object with offset to the event, if any.
### template
### Template
| Template variable | Data |
| ---- | ---- |
@ -142,21 +142,21 @@ The following tables show the available trigger data per platform.
| `trigger.to_state` | New [state object] of entity that caused template to change.
| `trigger.for` | Timedelta object how long state has been to state, if any.
### time
### Time
| Template variable | Data |
| ---- | ---- |
| `trigger.platform` | Hardcoded: `time`
| `trigger.now` | DateTime object that triggered the time trigger.
### time pattern
### Time Pattern
| Template variable | Data |
| ---- | ---- |
| `trigger.platform` | Hardcoded: `time_pattern`
| `trigger.now` | DateTime object that triggered the time_pattern trigger.
### webhook
### Webhook
| Template variable | Data |
| ---- | ---- |
@ -165,7 +165,7 @@ The following tables show the available trigger data per platform.
| `trigger.json` | The JSON data of the request (if it had a JSON content type).
| `trigger.data` | The form data of the request (if it had a form data content type).
### zone
### Zone
| Template variable | Data |
| ---- | ---- |

4
source/_docs/configuration/secrets.markdown
View File

@ -4,9 +4,9 @@ description: "Storing secrets outside of your configuration.yaml."
redirect_from: /topics/secrets/
---
The `configuration.yaml` file is a plain-text file, thus it is readable by anyone who has access to the file. The file contains passwords and API tokens which need to be redacted if you want to share your configuration. By using `!secret` you can remove any private information from your configuration files. This separation can also help you to keep easier track of your passwords and API keys, as they are all stored at one place and no longer spread across the `configuration.yaml` file or even multiple yaml files if you [split up your configuration](/docs/configuration/splitting_configuration/).
The `configuration.yaml` file is a plain-text file, thus it is readable by anyone who has access to the file. The file contains passwords and API tokens which need to be redacted if you want to share your configuration. By using `!secret` you can remove any private information from your configuration files. This separation can also help you to keep easier track of your passwords and API keys, as they are all stored at one place and no longer spread across the `configuration.yaml` file or even multiple YAML files if you [split up your configuration](/docs/configuration/splitting_configuration/).
### Using secrets.yaml
### Using `secrets.yaml`
The workflow for moving private information to `secrets.yaml` is very similar to the [splitting of the configuration](/docs/configuration/splitting_configuration/). Create a `secrets.yaml` file in your Home Assistant [configuration directory](/docs/configuration/).

2
source/_docs/configuration/splitting_configuration.markdown
View File

@ -4,7 +4,7 @@ description: "Splitting the configuration.yaml into several files."
redirect_from: /topics/splitting_configuration/
---
So you've been using Home Assistant for a while now and your configuration.yaml file brings people to tears or you simply want to start off with the distributed approach, here's how to "split the configuration.yaml" into more manageable (read: humanly readable) pieces.
So you've been using Home Assistant for a while now and your `configuration.yaml` file brings people to tears or you simply want to start off with the distributed approach, here's how to split the `configuration.yaml` into more manageable (read: humanly readable) pieces.
First off, several community members have sanitized (read: without API keys/passwords etc) versions of their configurations available for viewing, you can see a list of them [here](/cookbook/#example-configurationyaml).

2
source/_docs/configuration/troubleshooting.markdown
View File

@ -24,7 +24,7 @@ One of the most common problems with Home Assistant is an invalid `configuration
- On Hass.io you can use the [`hassio` command](/hassio/commandline/#home-assistant): `hassio homeassistant check`.
- On Docker you can use `docker exec home-assistant python -m homeassistant --script check_config --config /config` - where `home-assistant` is the name of the container.
- The configuration files, including `configuration.yaml` must be UTF-8 encoded. If you see error like `'utf-8' codec can't decode byte`, edit the offending configuration and re-save it as UTF-8.
- You can verify your configuration's yaml structure using [this online YAML parser](http://yaml-online-parser.appspot.com/) or [YAML Lint](http://www.yamllint.com/).
- You can verify your configuration's YAML structure using [this online YAML parser](http://yaml-online-parser.appspot.com/) or [YAML Lint](http://www.yamllint.com/).
- To learn more about the quirks of YAML, read [YAML IDIOSYNCRASIES](https://docs.saltstack.com/en/latest/topics/troubleshooting/yaml_idiosyncrasies.html) by SaltStack (the examples there are specific to SaltStack, but do explain YAML issues well).
`configuration.yaml` does not allow multiple sections to have the same name. If you want to load multiple platforms for one component, you can append a [number or string](/getting-started/devices/#style-2-list-each-device-separately) to the name or nest them using [this style](/getting-started/devices/#style-1-collect-every-entity-under-the-parent):

2
source/_docs/ecosystem/haproxy.markdown
View File

@ -90,7 +90,7 @@ Replace 443 with whatever port you chose to bind to in the config if different.
### Configure Home Assistant HTTP Component
In your `configuration.yaml` file, edit the [http component](/integrations/http/).
In your `configuration.yaml` file, edit the [HTTP component](/integrations/http/).
```text
http:

8
source/_docs/frontend/mobile.markdown
View File

@ -6,9 +6,9 @@ redirect_from: /getting-started/mobile/
Home Assistant has [a companion app for both Android and iOS](/docs/ecosystem/ios/).
As an alternative to the iOS and Android companion apps, you can add the Home Assistant "web app" to your homescreen as if it was native (Home Assistant leverages the W3C [manifest.json](https://w3c.github.io/manifest/) support).
As an alternative to the iOS and Android companion apps, you can add the Home Assistant "web app" to your homescreen as if it was native (Home Assistant leverages the W3C [`manifest.json`](https://w3c.github.io/manifest/) support).
### Android
## Android
1. Open Chrome
2. Navigate to your Home Assistant instance
@ -17,10 +17,10 @@ As an alternative to the iOS and Android companion apps, you can add the Home As
5. A dialog will popup; tap on Add
<p class='img' style='max-width:500px; margin-left: auto; margin-right: auto;'>
<img src='/images/screenshots/android-homescreen-guide.gif' />
<img src='/images/screenshots/android-homescreen-guide.gif' />
</p>
### iOS
## iOS
1. Open Safari
2. Navigate to your Home Assistant instance

2
source/_docs/installation/synology.markdown
View File

@ -213,7 +213,7 @@ Update your firewall (if it is turned on the Synology device):
- Click on OK again
Copy your configuration.yaml file into the config folder
Copy your `configuration.yaml` file into the config folder
That's it... you're all set to go
Here are some useful commands:

2
source/_docs/mqtt/broker.markdown
View File

@ -148,7 +148,7 @@ Home Assistant contains an embedded MQTT broker called [HBMQTT](https://pypi.pyt
| Port | 1883 |
| Protocol | 3.1.1 |
| User | `homeassistant` |
| Password | _password set under mqtt settings_ |
| Password | _password set under MQTT settings_ |
| Websocket port | 8080 |
```yaml

3
source/_docs/tools/dev-tools.markdown
View File

@ -20,6 +20,7 @@ Screenshot of Home Assistant's Developer Tools.
| Info | Details about Home Assistant |
## What can I do with Developer Tools?
The Developer Tools is meant for **all** (not just for the developers) to quickly try out things - like calling services, update states, raising events, and publish messages in mqtt…etc.). It is also a necessary tool for those who write custom automations and scripts by hand. The following describes each of the section in detail.
## Services
@ -88,7 +89,7 @@ For more information about jinja2, visit [jinja2 documentation](http://jinja.poc
## MQTT
This section is only visible if the MQTT integration is configured. To configure MQTT, add `mqtt:` to the `configuration.yaml` file. For more information, refer to the [mqtt](/integrations/mqtt/) component.
This section is only visible if the MQTT integration is configured. To configure MQTT, add `mqtt:` to the `configuration.yaml` file. For more information, refer to the [MQTT](/integrations/mqtt/) integration.
Even though MQTT in general provides deeper functionality, the developer tools section of MQTT is limited to publishing messages to a given topic. It supports templates for the payload. To publish a message, simply specify the topic name and the payload and click “PUBLISH” button.

2
source/_docs/z-wave/adding.markdown
View File

@ -26,7 +26,7 @@ When you add a device, it may initially appear without a specific entity ID (e.g
Security Z-Wave devices require a network key. Some devices only expose their full capabilities when included this way. You should always read the manual for your device to find out the recommended inclusion method. Note, secure devices that had been connected to another hub/network in the past may have a "theft protection" feature which requires to first exclude the device successfully from the previous hub using the previous hub/Software setup before it can be enrolled in a new hub/network.
A valid network key will be a 16 byte value, defined in the zwave section of your configuration, such as the following example:
A valid network key will be a 16 byte value, defined in the Z-Wave section of your configuration, such as the following example:
```yaml
zwave:

2
source/_docs/z-wave/device-specific.markdown
View File

@ -457,7 +457,7 @@ Press circle and plus simultaneously to wake up the device.
<!-- from https://products.z-wavealliance.org/products/2817 -->
Once you've added the NanoMote to your z-wave network, you'll need to update your zwcfg_\*.xml file with the below xml data. Stop Home Assistant and open your zwcfg_\*.xml file (located in your config folder). Find the NanoMote device section and then its corresponding `CommandClass` section with id="91". Replace the entire CommandClass section with the below xml data. Save the file and restart Home Assistant.
Once you've added the NanoMote to your Z-Wave network, you'll need to update your zwcfg_\*.xml file with the below xml data. Stop Home Assistant and open your zwcfg_\*.xml file (located in your config folder). Find the NanoMote device section and then its corresponding `CommandClass` section with id="91". Replace the entire CommandClass section with the below xml data. Save the file and restart Home Assistant.
```xml
<CommandClass id="91" name="COMMAND_CLASS_CENTRAL_SCENE" version="1" request_flags="4" innif="true" scenecount="0">

8
source/_integrations/alarm_control_panel.ifttt.markdown
View File

@ -87,7 +87,7 @@ For this system to operate correctly, the following IFTTT applets have to be set
* **IF** Webhook event `YOUR_ARM_HOME_EVENT` is called, **THEN** set the alarm system to armed home.
* **IF** Webhook event `YOUR_ARM_NIGHT_EVENT` is called, **THEN** set the alarm system to armed away.
* **IF** Webhook event `YOUR_DISARM_EVENT` is called, **THEN** set the alarm system to armed night.
* **IF** the alarm system was disarmed, **THEN** perform a Webhook `POST` web request to url `https://HASS_URL/api/services/ifttt/push_alarm_state?api_password=API_PASSWORD` with content type `application/json` and body `{"entity_id": "alarm_control_panel.DEVICE_NAME", "state": "disarmed"}`.
* **IF** the alarm system state changed to armed home, **THEN** perform a Webhook `POST` web request to url `https://HASS_URL/api/services/ifttt/push_alarm_state?api_password=API_PASSWORD` with content type `application/json` and body `{"entity_id": "alarm_control_panel.DEVICE_NAME", "state": "armed_home"}`.
* **IF** the alarm system state changed to armed away, **THEN** perform a Webhook `POST` web request to url `https://HASS_URL/api/services/ifttt/push_alarm_state?api_password=API_PASSWORD` with content type `application/json` and body `{"entity_id": "alarm_control_panel.DEVICE_NAME", "state": "armed_away"}`.
* **IF** the alarm system state changed to armed night, **THEN** perform a Webhook `POST` web request to url `https://HASS_URL/api/services/ifttt/push_alarm_state?api_password=API_PASSWORD` with content type `application/json` and body `{"entity_id": "alarm_control_panel.DEVICE_NAME", "state": "armed_night"}`.
* **IF** the alarm system was disarmed, **THEN** perform a Webhook `POST` web request to URL `https://HASS_URL/api/services/ifttt/push_alarm_state?api_password=API_PASSWORD` with content type `application/json` and body `{"entity_id": "alarm_control_panel.DEVICE_NAME", "state": "disarmed"}`.
* **IF** the alarm system state changed to armed home, **THEN** perform a Webhook `POST` web request to URL `https://HASS_URL/api/services/ifttt/push_alarm_state?api_password=API_PASSWORD` with content type `application/json` and body `{"entity_id": "alarm_control_panel.DEVICE_NAME", "state": "armed_home"}`.
* **IF** the alarm system state changed to armed away, **THEN** perform a Webhook `POST` web request to URL `https://HASS_URL/api/services/ifttt/push_alarm_state?api_password=API_PASSWORD` with content type `application/json` and body `{"entity_id": "alarm_control_panel.DEVICE_NAME", "state": "armed_away"}`.
* **IF** the alarm system state changed to armed night, **THEN** perform a Webhook `POST` web request to URL `https://HASS_URL/api/services/ifttt/push_alarm_state?api_password=API_PASSWORD` with content type `application/json` and body `{"entity_id": "alarm_control_panel.DEVICE_NAME", "state": "armed_night"}`.

10
source/_integrations/amcrest.markdown
View File

@ -87,8 +87,8 @@ ffmpeg_arguments:
default: -pred 1
authentication:
description: >
Defines which authentication method to use only when **stream_source**
is **mjpeg**. Currently, *aiohttp* only support *basic*.
Defines which authentication method to use only when `stream_source`
is `mjpeg`. Currently, `aiohttp` only support `basic`.
required: false
type: string
default: basic
@ -135,9 +135,9 @@ control_light:
stream `high` definition video with MJPEG encoding. You may need to use `low`
resolution stream or the `snapshot` stream source instead. If the quality seems
too poor, lower the `Frame Rate (FPS)` and max out the `Bit Rate` settings in
your camera's configuration manager. If you defined the *stream_source* to
**mjpeg**, make sure your camera supports *Basic* HTTP authentication.
Newer Amcrest firmware may not work, then **rtsp** is recommended instead.
your camera's configuration manager. If you defined the `stream_source` to
`mjpeg`, make sure your camera supports `Basic` HTTP authentication.
Newer Amcrest firmware may not work, then `rtsp` is recommended instead.
**Note:** If you set the `stream_source` option to `rtsp`,
make sure to follow the steps mentioned at [FFmpeg](/integrations/ffmpeg/)

2
source/_integrations/automatic.markdown
View File

@ -16,7 +16,7 @@ The `automatic` device tracker platform offers presence detection by retrieving
To use Automatic with Home Assistant, first you must [create a free development account](https://developer.automatic.com/). Automatic will generate a Client ID and Secret for you to use in your Home Assistant configuration. You will need to update your Event Delivery preferences to ensure Home Assistant can receive updates. On the developer page, under App Settings / Event Delivery, select "Websocket" for Event Delivery Preference. Next, specify the OAuth Redirect URL in the developer page. This should be configured to `<home-assistant-url>/api/automatic/callback`. (Example: `http://hassio.local:8123/api/automatic/callback`) Note that this URL only needs to be accessible from the browser you use to perform the authentication.
Home Assistant can also take advantage of `scope:current_location` if available. This will allow Home Assistant to receive periodic location updates during a trip. In order to use this functionality, you must request the scope for your application from Automatic. Once `scope:current_location` is available, change `current_location` to `true` in your configuration.yaml.
Home Assistant can also take advantage of `scope:current_location` if available. This will allow Home Assistant to receive periodic location updates during a trip. In order to use this functionality, you must request the scope for your application from Automatic. Once `scope:current_location` is available, change `current_location` to `true` in your `configuration.yaml`.
## Configuration

14
source/_integrations/binary_sensor.rfxtrx.markdown
View File

@ -9,17 +9,17 @@ ha_release: 0.48
The `rfxtrx` platform support binary sensors that
communicate in the frequency range of 433.92 MHz.
The rfxtrx binary sensor integration provides support for them.
The RFXtrx binary sensor integration provides support for them.
Many cheap sensors available on the web today are based on a particular RF chip
called *PT-2262*. Depending on the running firmware on the RFXcom box, some of
them may be recognized under the X10 protocol but most of them are recognized
under the *Lighting4* protocol. The rfxtrx binary sensor integration provides
some special options for them, while other rfxtrx protocols should work too.
under the *Lighting4* protocol. The RFXtrx binary sensor integration provides
some special options for them, while other RFXtrx protocols should work too.
## Setting up your devices
Once you have set up your [rfxtrx hub](/integrations/rfxtrx/), the easiest way
Once you have set up your [RFXtrx hub](/integrations/rfxtrx/), the easiest way
to find your binary sensors is to add this to your `configuration.yaml`:
```yaml
@ -90,7 +90,7 @@ automatic_add:
<div class='note warning'>
This integration and the [rfxtrx switch](/integrations/switch.rfxtrx/) can steal each other's devices when setting the `automatic_add` configuration parameter to `true`.
This integration and the [RFXtrx switch](/integrations/switch.rfxtrx/) can steal each other's devices when setting the `automatic_add` configuration parameter to `true`.
Set `automatic_add` only when you have some devices to add to your installation, otherwise leave it to `false`.
</div>
@ -186,7 +186,7 @@ devices:
command_off: 0x7
```
The *automatic_add* option makes the rfxtrx binary sensor integration calculate
The *automatic_add* option makes the RFXtrx binary sensor integration calculate
and display the configuration options for you in the Home Assistant logs:
```text
@ -203,7 +203,7 @@ want to configure your new devices and leave it off otherwise.
### Known working devices
The following devices are known to work with the rfxtrx binary sensor component.
The following devices are known to work with the RFXtrx binary sensor component.
There are too many other to list.
- Motion detectors:

3
source/_integrations/bluesound.markdown
View File

@ -10,8 +10,7 @@ ha_iot_class: Local Polling
The `bluesound` platform allows you to control your [Bluesound](https://www.bluesound.com/) HiFi wireless speakers and audio integrations from Home Assistant.
If you want to automatically discover new devices, just make sure you have discovery: in your configuration.yaml file. To manually add a Bluesound device to your installation, add the following to your configuration.yaml file:
If you want to automatically discover new devices, just make sure you have discovery: in your `configuration.yaml` file. To manually add a Bluesound device to your installation, add the following to your `configuration.yaml` file:
```yaml
# Example configuration.yaml

2
source/_integrations/broadlink.markdown
View File

@ -565,7 +565,7 @@ First get or learn all the remotes you want to add to Home Assistant in E-Contro
[+] Dumping codes to TV.txt
```
6. Now there should be a file with the name of the remote you chose in the same directory ending in `.txt`. Open that up and it will contain the Base64 code required for Home Assistant. To ensure these codes work correctly you may need to add `==` to the end of the code in your config.yaml file (or wherever you have your switches).
6. Now there should be a file with the name of the remote you chose in the same directory ending in `.txt`. Open that up and it will contain the Base64 code required for Home Assistant. To ensure these codes work correctly you may need to add `==` to the end of the code in your `configuration.yaml` file (or wherever you have your switches).
### Using Windows to obtain codes with Broadlink Manager

2
source/_integrations/cert_expiry.markdown
View File

@ -19,7 +19,7 @@ The `cert_expiry` sensor fetches information from a configured URL and displays
There are 2 options in configuring the `cert_expiry` sensor:
- Via the Home Assistant user interface where it will let you enter a name, host and port for the certificate to check.
- Via the Home Assistant configuration.yaml file.
- Via the Home Assistant `configuration.yaml` file.
```yaml

2
source/_integrations/cisco_ios.markdown
View File

@ -9,7 +9,7 @@ ha_codeowners:
- '@fbradyirl'
---
This is a presence detection scanner for [Cisco](https://www.cisco.com/) IOS devices.
This is a presence detection scanner for [Cisco IOS](https://www.cisco.com/) devices.
<div class='note warning'>
This device tracker needs SSH to be enabled on the router.

2
source/_integrations/cloudflare.markdown
View File

@ -90,7 +90,7 @@ cloudflare:
- EXAMPLE.COM
```
#### The minimum DNS record settings are (if you have set up https already):
#### 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:

4
source/_integrations/config.markdown
View File

@ -53,11 +53,11 @@ This section enables you to organize entities to physical areas of your home.
### Automation
This section enables you to create and modify automations from within Home Assistant, without needing to write out the yaml code.
This section enables you to create and modify automations from within Home Assistant, without needing to write out the YAML code.
### Script
Similar to the automation editor, this section enables you to create and modify scripts from within Home Assistant, without needing to write out the yaml code.
Similar to the automation editor, this section enables you to create and modify scripts from within Home Assistant, without needing to write out the YAML code.
### Z-Wave

2
source/_integrations/cover.rfxtrx.markdown
View File

@ -9,7 +9,7 @@ ha_release: 0.27
The `rfxtrx` platform supports Siemens/LightwaveRF and RFY roller shutters that communicate in the frequency range of 433.92 MHz.
First you have to set up your [rfxtrx hub](/integrations/rfxtrx/).
First you have to set up your [RFXtrx hub](/integrations/rfxtrx/).
### Configuration

4
source/_integrations/darksky.markdown
View File

@ -68,12 +68,12 @@ language:
latitude:
description: Latitude coordinate to monitor weather of (required if **longitude** is specified).
required: false
default: coordinates defined in your `configuration.yaml`
default: coordinates from the Home Assistant configuration
type: float
longitude:
description: Longitude coordinate to monitor weather of (required if **latitude** is specified).
required: false
default: coordinates defined in your `configuration.yaml`
default: coordinates from the Home Assistant configuration
type: float
monitored_conditions:
description: Conditions to display in the frontend.

2
source/_integrations/device_tracker.markdown
View File

@ -88,7 +88,7 @@ In the example above, `devicename` refers to the detected name of the device. F
|----------------|-------------------------------|---------------------------------------------------------------------------------------------------------|
| `name` | Host name or "Unnamed Device" | The friendly name of the device. |
| `mac` | None | The MAC address of the device. Add this if you are using a network device tracker like Nmap or SNMP. |
| `picture` | None | A picture that you can use to easily identify the person or device. You can also save the image file in a folder "www" in the same location (can be obtained from developer tools) where you have your configuration.yaml file and just use `picture: /local/favicon-192x192.png`. The path 'local' is mapped to the 'www' folder you create. |
| `picture` | None | A picture that you can use to easily identify the person or device. You can also save the image file in a folder "www" in the same location (can be obtained from developer tools) where you have your `configuration.yaml` file and just use `picture: /local/favicon-192x192.png`. The path 'local' is mapped to the 'www' folder you create. |
| `icon` | mdi:account | An icon for this device (use as an alternative to `picture`). |
| `gravatar` | None | An email address for the device's owner. If provided, it will override `picture`. |
| `track` | [uses platform setting] | If `yes`/`on`/`true` then the device will be tracked. Otherwise its location and state will not update. |

4
source/_integrations/dialogflow.markdown
View File

@ -39,7 +39,7 @@ To get the webhook URL, go to the integrations page in the configuration screen
- Select name, language (if you are planning to use Google Actions check their [supported languages](https://support.google.com/assistant/answer/7108196?hl=en)) and time zone
- Click "Save"
- Now go to "Fulfillment" (in the left menu)
- Enable Webhook and set your Dialogflow webhook url as the endpoint, e.g., `https://myhome.duckdns.org/api/webhook/800b4cb4d27d078a8871656a90854a292651b20635685f8ea23ddb7a09e8b417`
- Enable Webhook and set your Dialogflow webhook URL as the endpoint, e.g., `https://myhome.duckdns.org/api/webhook/800b4cb4d27d078a8871656a90854a292651b20635685f8ea23ddb7a09e8b417`
- Click "Save"
- Create a new intent
- Below "User says" write one phrase that you, the user, will tell Dialogflow, e.g., `What is the temperature at home?`
@ -52,7 +52,7 @@ To get the webhook URL, go to the integrations page in the configuration screen
<div class='note warning'>
The V1 api will be deprecated on October 23, 2019. If you are still using the V1 API, it is recommended to change your settings in Dialogflow to use the V2 API. No changes to your intents yaml configuration need to take place after upgrading to the V2 API. Change to the V2 API by clicking on the cog button [here](https://console.dialogflow.com/) and then select the V2 API.
The V1 API will be deprecated on October 23, 2019. If you are still using the V1 API, it is recommended to change your settings in Dialogflow to use the V2 API. No changes to your intents YAML configuration need to take place after upgrading to the V2 API. Change to the V2 API by clicking on the cog button [here](https://console.dialogflow.com/) and then select the V2 API.
</div>

4
source/_integrations/discovery.markdown
View File

@ -25,7 +25,7 @@ Home Assistant can discover and automatically configure [zeroconf](https://en.wi
* [Netgear routers](/integrations/netgear)
* [Panasonic Viera](/integrations/panasonic_viera)
* [Philips Hue](/integrations/hue)
* [Plex media server](/integrations/plex#media-player)
* [Plex Media Server](/integrations/plex#media-player)
* [Roku media player](/integrations/roku#media-player)
* [SABnzbd downloader](/integrations/sabnzbd)
* [Samsung SyncThru Printer](/integrations/syncthru)
@ -86,7 +86,7 @@ Valid values for ignore are:
* `openhome`: Linn / Openhome
* `panasonic_viera`: Panasonic Viera
* `philips_hue`: Philips Hue
* `plex_mediaserver`: Plex media server
* `plex_mediaserver`: Plex Media Server
* `roku`: Roku media player
* `sabnzbd`: SABnzbd downloader
* `samsung_printer`: Samsung SyncThru Printer

2
source/_integrations/ecobee.markdown
View File

@ -50,7 +50,7 @@ To configure the ecobee integration in Home Assistant, you can either use the **
3. In the next pop-up box, you will be presented with a unique four-character PIN code which you will need to authorize in the [ecobee consumer portal](https://www.ecobee.com/consumerportal/index.html). You can do this by logging in, selecting **My Apps** from the hamburger menu, clicking **Add Application** on the left, entering the PIN code from Home Assistant, and clicking **Validate** and then **Add Application** in the bottom right.
4. After authorizing the App on ecobee.com, return to Home Assistant and hit **Submit**. If the authorization was successful, a config entry will be created and your thermostats and sensors will be available in Home Assistant.
### Setup via configuration.yaml
### Setup via `configuration.yaml`
If you prefer to initially set up this integration in [`configuration.yaml`](/docs/configuration/), you may do so by adding your API key (and optional parameters) as follows (however, you must still complete authorization via the **Integrations** menu):

18
source/_integrations/emoncms.markdown
View File

@ -23,15 +23,15 @@ sensor:
## Configuration variables
- **api_key** (*Required*): The read API key for your Emoncms user.
- **url** (*Required*): The base URL of Emoncms, use "https://emoncms.org" for the cloud based version.
- **id** (*Required*): Positive integer identifier for the sensor. Must be unique if you specify multiple Emoncms sensors.
- **include_only_feed_id** (*Optional*): Positive integer list of Emoncms feed IDs. Only the feeds with feed IDs specified here will be displayed. Can not be specified if `exclude_feed_id` is specified.
- **exclude_feed_id** (*Optional*): Positive integer list of Emoncms feed IDs. All the feeds will be displayed as sensors except the ones listed here. Can not be specified if `include_only_feed_id` is specified.
- **sensor_names** (*Optional*): Dictionary of names for the sensors created that are created based on feed ID. The dictionary consists of `feedid: name` pairs. Sensors for feeds with their feed ID mentioned here will get the chosen name instead of the default name
- **value_template** (*Optional*): Defines a [template](/docs/configuration/templating/#processing-incoming-data) to alter the feed value.
- **scan_interval** (*Optional*): Defines the update interval of the sensor in seconds.
- **unit_of_measurement** (*Optional*): Defines the unit of measurement of for all the sensors. default is "W".
- `api_key` (*Required*): The read API key for your Emoncms user.
- `url` (*Required*): The base URL of Emoncms, use <https://emoncms.org> for the cloud based version.
- `id` (*Required*): Positive integer identifier for the sensor. Must be unique if you specify multiple Emoncms sensors.
- `include_only_feed_id` (*Optional*): Positive integer list of Emoncms feed IDs. Only the feeds with feed IDs specified here will be displayed. Can not be specified if `exclude_feed_id` is specified.
- `exclude_feed_id` (*Optional*): Positive integer list of Emoncms feed IDs. All the feeds will be displayed as sensors except the ones listed here. Can not be specified if `include_only_feed_id` is specified.
- `sensor_names` (*Optional*): Dictionary of names for the sensors created that are created based on feed ID. The dictionary consists of `feedid: name` pairs. Sensors for feeds with their feed ID mentioned here will get the chosen name instead of the default name
- `value_template` (*Optional*): Defines a [template](/docs/configuration/templating/#processing-incoming-data) to alter the feed value.
- `scan_interval` (*Optional*): Defines the update interval of the sensor in seconds.
- `unit_of_measurement` (*Optional*): Defines the unit of measurement of for all the sensors. default is "W".
## Default naming scheme

4
source/_integrations/emoncms_history.markdown
View File

@ -24,11 +24,11 @@ emoncms_history:
{% configuration %}
api_key:
description: Your Emoncms write api key
description: Your Emoncms write API key
required: true
type: string
url:
description: The root URL of your Emoncms installation. (Use https://emoncms.org for the cloud based version)
description: The root URL of your Emoncms installation. (Use `https://emoncms.org` for the cloud based version)
required: true
type: string
inputnode:

6
source/_integrations/entur_public_transport.markdown
View File

@ -107,18 +107,18 @@ sensor:
[Entur's travel planer](https://en-tur.no) has a map of all stops used in Norway. Use the map to find the stops you're interested in. When you have found one of your stops, click on it.
Now the web browser should contain an URL with the id in it. Such as this:
Now the web browser should contain a URL with the id in it. Such as this:
`https://en-tur.no/nearby-stop-place-detail?id=NSR:StopPlace:32376`
The stop id is the content after `id=` parameter in the url. Copy paste this into the configuration.
The stop id is the content after `id=` parameter in the URL. Copy paste this into the configuration.
## FAQ - Troubleshooting
**Q:** I have multiple stop ids and have added whitelisting of a line. Now some of the stop places are showing `unknown`.
**A:** A whitelisting of lines takes affect on all of the stops. So you have to whitelist all lines you are interested in on all stop places.
---
**Q:** I have added whitelisting of lines, and everything has worked as fine before, but now it has stopped updating all of a sudden.

2
source/_integrations/fail2ban.markdown
View File

@ -60,7 +60,7 @@ These steps assume you already have the Home Assistant docker running behind NGI
For those of us using Docker, the above tutorial may not be sufficient. The following steps specifically outline how to set up `fail2ban` and Home Assistant when running Home Assistant within a Docker behind NGINX. The setup this was tested on was an unRAID server using the [let's encrypt docker](https://github.com/linuxserver/docker-letsencrypt) from linuxserver.io.
#### Set http logger
#### Set HTTP logger
In your `configuration.yaml` file, add the following to the `logger` integration to ensure that Home Assistant prints failed login attempts to the log.

2
source/_integrations/feedreader.markdown
View File

@ -22,7 +22,7 @@ feedreader:
{% configuration %}
urls:
description: List of URLS for your feeds.
description: List of URLs for your feeds.
required: true
type: list
scan_interval:

2
source/_integrations/foursquare.markdown
View File

@ -42,7 +42,7 @@ https://foursquare.com/oauth2/authenticate?client_id=CLIENT_ID&response_type=tok
and change the `CLIENT_ID` and `YOUR_REGISTERED_REDIRECT_URL` to your actual values.
You will receive an OAuth request landing page, asking you if you want to connect your Foursquare account to your newly created app. Say "Yes".
After that, you will get redirected to your `REDIRECT_URL` with the `access_token` as an HTTP GET variable. Copy everything after the = and paste it in your configuration.yaml as the `access_token`.
After that, you will get redirected to your `REDIRECT_URL` with the `access_token` as an HTTP GET variable. Copy everything after the = and paste it in your `configuration.yaml` as the `access_token`.
### Real-Time API

8
source/_integrations/freebox.markdown
View File

@ -35,18 +35,18 @@ freebox:
{% configuration %}
host:
description: The url of the Freebox.
description: The URL of the Freebox.
required: true
type: string
port:
description: The https port the Freebox is listening on.
description: The HTTPS port the Freebox is listening on.
required: true
type: string
{% endconfiguration %}
You can find out your Freebox host and port by opening the address <http://mafreebox.freebox.fr/api_version> in your browser. The
returned json should contain an api_domain (`host`) and a https_port (`port`).
Please consult the [api documentation](https://dev.freebox.fr/sdk/os/) for more information.
returned JSON should contain an `api_domain` (`host`) and a `https_port` (`port`).
Please consult the [API documentation](https://dev.freebox.fr/sdk/os/) for more information.
<div class='note warning'>

2
source/_integrations/gearbest.markdown
View File

@ -25,7 +25,7 @@ sensor:
{% configuration %}
currency:
description: "The currency in which the products should be tracked. Currently supported: USD, EUR, GBP, AUD, CAD, CHF, HKD, CNY, NZD, JPY, RUB, BRL, CLP, NOK, DKK, SEK, KRW, ILS, COP, MXN, PEN, THB, IDR, UAH, PLN, INR, BGN, HUF, RON, TRY, CZK, HRK, MAD, AED, SAR, ZAR, SGD, MYR, TWD, RSD, NGN - if the currency could not be found in the conversion rate list, USD will be used as default. Either an ID or an URL must be present."
description: "The currency in which the products should be tracked. Currently supported: USD, EUR, GBP, AUD, CAD, CHF, HKD, CNY, NZD, JPY, RUB, BRL, CLP, NOK, DKK, SEK, KRW, ILS, COP, MXN, PEN, THB, IDR, UAH, PLN, INR, BGN, HUF, RON, TRY, CZK, HRK, MAD, AED, SAR, ZAR, SGD, MYR, TWD, RSD, NGN - if the currency could not be found in the conversion rate list, USD will be used as default. Either an ID or a URL must be present."
required: true
type: string
items:

2
source/_integrations/geniushub.markdown
View File

@ -161,7 +161,7 @@ value_template: "{{ state_attr('climate.genius_zone_12', 'status').occupied }}"
## Configuration
To set up this integration, add one of the following to your **configuration.yaml** file.
To set up this integration, add one of the following to your `configuration.yaml` file.
If required, you can switch between one Option and the other and, as the `unique_id` remains consistent, state history will be preserved. This assumes that the correct MAC address is provided for Option 2, below. If a wrong MAC address was provided for Option 1, then the MAC address can be overridden for Option 1 to maintain these links within the entity registry.

6
source/_integrations/habitica.markdown
View File

@ -65,7 +65,7 @@ The API is exposed to Home Assistant as a service called `habitica.api_call`. To
|----------------------|--------|--------|----------------|
| `name` | yes | string | Habitica's username as per `configuration.yaml` entry. |
| `path` | yes | [string] | Items from API URL in form of an array with method attached at the end. See the example below. |
| `args` | no | map | Any additional json or url parameter arguments. See the example below and [apidoc](https://habitica.com/apidoc/). |
| `args` | no | map | Any additional JSON or URL parameter arguments. See the example below and [apidoc](https://habitica.com/apidoc/). |
A successful call to this service will fire an event `habitica_api_call_success`.
@ -73,13 +73,13 @@ A successful call to this service will fire an event `habitica_api_call_success`
|----------------------|--------|----------------|
| `name` | string | Copied from service data attribute. |
| `path` | [string] | Copied from service data attribute. |
| `data` | map | Deserialized `data` field of JSON object Habitica's server returned in response to api call. For more info see [docs](https://habitica.com/apidoc/). |
| `data` | map | Deserialized `data` field of JSON object Habitica's server returned in response to API call. For more info see [docs](https://habitica.com/apidoc/). |
#### Let's consider some examples on how to call the service.
For example, let's say that there is a configured `habitica` platform for user `xxxNotAValidNickxxx` with their respective `api_user` and `api_key`.
Let's create a new task (a todo) for this user via Home Assistant. There is an [API call](https://habitica.com/apidoc/#api-Task-CreateUserTasks) for this purpose.
To create a new task one should hit `https://habitica.com/api/v3/tasks/user` endpoint with `POST` request with a json object with task properties.
To create a new task one should hit `https://habitica.com/api/v3/tasks/user` endpoint with `POST` request with a JSON object with task properties.
So let's call the API on `habitica.api_call`.
* The `name` key becomes `xxxNotAValidNickxxx`.

2
source/_integrations/harmony.markdown
View File

@ -90,7 +90,7 @@ Turn off all devices that were switched on from the start of the current activit
### Service `remote.turn_on`
Start an activity. Will start the default `activity` from configuration.yaml if no activity is specified. The specified activity can either be the activity name or the activity ID from the configuration file written to your [Home Assistant configuration directory](/docs/configuration/).
Start an activity. Will start the default `activity` from `configuration.yaml` if no activity is specified. The specified activity can either be the activity name or the activity ID from the configuration file written to your [Home Assistant configuration directory](/docs/configuration/).
| Service data attribute | Optional | Description |
| ---------------------- | -------- | ----------- |

2
source/_integrations/heos.markdown
View File

@ -118,7 +118,7 @@ You can play a HEOS Quick Select by nubmer or name with the `media_player.play_m
| `media_content_type` | Set to the value `quick_select`
| `media_content_id` | The quick select number (i.e. `1`) or name (i.e. `Quick Select 1`)
#### Play Url
#### Play URL
You can play a URL through a HEOS media player using the `media_player.play_media` service. The HEOS player must be able to reach the URL. Example service data payload:

2
source/_integrations/hikvision.markdown
View File

@ -98,7 +98,7 @@ port:
type: integer
default: 80
ssl:
description: "`true` if you want to connect with https. Be sure to set the port also."
description: "`true` if you want to connect with HTTPS. Be sure to set the port also."
required: false
type: boolean
default: false

2
source/_integrations/honeywell.markdown
View File

@ -18,7 +18,7 @@ If your system is compatible with this integration, then you will be able access
## Configuration
To set up this integration, add the following to the `climate:` section of your **configuration.yaml** file:
To set up this integration, add the following to the `climate:` section of your `configuration.yaml` file:
```yaml
climate:

2
source/_integrations/hyperion.markdown
View File

@ -76,7 +76,7 @@ automation:
effect: "Full color mood blobs"
```
To have the lights playing an effect when pausing, idle or turn off a media player like plex you can use this example:
To have the lights playing an effect when pausing, idle or turn off a media player like Plex you can use this example:
```yaml
- alias: Set hyperion effect after playback

2
source/_integrations/ifttt.markdown
View File

@ -100,7 +100,7 @@ Service Data | `{"event": "EventName", "value1": "Hello World"}`
When your screen looks like this, click the 'call service' button.
</p>
By default the trigger is sent to all the api keys from `configuration.yaml`. If you
By default, the trigger is sent to all the API keys from `configuration.yaml`. If you
want to send the trigger to a specific key use the `target` field:
Field | Value

2
source/_integrations/image_processing.markdown
View File

@ -8,7 +8,7 @@ Image processing enables Home Assistant to process images from [cameras](/integr
<div class='note'>
If you are running Home Assistant over SSL or from within a container, you will have to setup a base URL (`base_url`) inside the [http component](/integrations/http/).
If you are running Home Assistant over SSL or from within a container, you will have to setup a base URL (`base_url`) inside the [HTTP component](/integrations/http/).
</div>

2
source/_integrations/incomfort.markdown
View File

@ -54,7 +54,7 @@ Other properties are available via each device's attributes.
## Configuration
To set up this integration, add one of the following to your **configuration.yaml** file:
To set up this integration, add one of the following to your `configuration.yaml` file:
The hub does not have to be in the same network as HA, but must be reachable via port 80/HTTP.

8
source/_integrations/influxdb.markdown
View File

@ -60,12 +60,12 @@ database:
default: home_assistant
ssl:
type: boolean
description: Use https instead of http to connect.
description: Use HTTPS instead of HTTP to connect.
required: false
default: false
verify_ssl:
type: boolean
description: Verify SSL certificate for https request.
description: Verify SSL certificate for HTTPS request.
required: false
default: true
max_retries:
@ -212,12 +212,12 @@ password:
required: false
type: string
ssl:
description: Use https instead of http to connect.
description: Use HTTPS instead of HTTP to connect.
required: false
default: false
type: boolean
verify_ssl:
description: Verify SSL certificate for https request.
description: Verify SSL certificate for HTTP request.
required: false
default: false
type: boolean

2
source/_integrations/iperf3.markdown
View File

@ -111,7 +111,7 @@ You can use the service `sensor.iperf3_update` to trigger a manual speed test fo
Once loaded, the `iperf3` integration will expose a service (`iperf3.speedtest`) that can be called to run a speed test on demand. This can be useful if you have enabled manual mode.
| Service data attribute | Description |
| `host` | String that point at a configured `host` from configuration.yaml. Otherwise, tests will be run against all configured hosts.
| `host` | String that point at a configured `host` from `configuration.yaml`. Otherwise, tests will be run against all configured hosts.
Example Service data:

4
source/_integrations/joaoapps_join.markdown
View File

@ -14,8 +14,8 @@ divided up in two locations, the Join component, and the Join notify platform.
The notify platform allows us to send messages to Join devices, the component
allows us to access the other special features that Join offers. When in doubt, you can reference the [API documentation](https://joaoapps.com/join/api/) this is based on.
In the `configuration.yaml` file you need to provide the api key and device id
or name of the target device. You can find your device id and api key
In the `configuration.yaml` file you need to provide the API key and device id
or name of the target device. You can find your device id and API key
[here](https://joinjoaomgcd.appspot.com/).
To set it up, add the following information to your `configuration.yaml` file:

2
source/_integrations/kodi.markdown
View File

@ -385,7 +385,7 @@ data:
type: map
keys:
icon:
description: "Kodi comes with 3 default icons: `info`, `warning` and `error`, an URL to an image is also valid."
description: "Kodi comes with 3 default icons: `info`, `warning` and `error`, a URL to an image is also valid."
required: false
default: "`info`"
type: string

2
source/_integrations/lannouncer.markdown
View File

@ -48,7 +48,7 @@ More information can be found [here](https://www.keybounce.com/lannouncer/config
Lannouncer supports two types of messages.
Spoken messages is the default method (`speak`). You just invoke the `notify` service with the following json and the device will speak out the specified message.
Spoken messages is the default method (`speak`). You just invoke the `notify` service with the following JSON and the device will speak out the specified message.
```json
{

2
source/_integrations/lcn.markdown
View File

@ -44,7 +44,7 @@ There is currently support for the following device types within Home Assistant:
To use your LCN system in your installation, add the following lines to your `configuration.yaml` file.
You have to specify at least one IP/port with login credentials for a PCHK host.
Consider to store your credentials in a [secrets.yaml](/docs/configuration/secrets).
Consider to store your credentials in a [`secrets.yaml`](/docs/configuration/secrets).
```yaml
lcn:

2
source/_integrations/light.mqtt.markdown
View File

@ -335,7 +335,7 @@ light:
## Default schema - Implementations
- A [basic example](https://github.com/mertenats/open-home-automation/tree/master/ha_mqtt_light) using a nodeMCU board (ESP8266) to control its built-in LED (on/off).
- A [basic example](https://github.com/mertenats/open-home-automation/tree/master/ha_mqtt_light) using a NodeMCU board (ESP8266) to control its built-in LED (on/off).
- Another [example](https://github.com/mertenats/open-home-automation/tree/master/ha_mqtt_rgb_light) to control a RGB LED (on/off, brightness, and colors).
- [Integration guide](https://github.com/xoseperez/espurna/wiki/HomeAssistant) for the ESPUrna firmware (ESP8285/ESP8266).

2
source/_integrations/light.rfxtrx.markdown
View File

@ -10,7 +10,7 @@ ha_iot_class: Assumed State
The `rfxtrx` platform support lights that communicate in the frequency range of 433.92 MHz.
First you have to set up your [rfxtrx hub](/integrations/rfxtrx/).
First you have to set up your [RFXtrx hub](/integrations/rfxtrx/).
The easiest way to find your lights is to add this to your `configuration.yaml`:

2
source/_integrations/light.xiaomi_aqara.markdown
View File

@ -9,7 +9,7 @@ ha_iot_class: Local Push
---
The `xiaomi aqara` light platform allows you to control the internal light of the xiaomi gateway. The integration will be loaded automatically and provides a device called `light.gateway_light_28ffffffffff`.
The `xiaomi aqara` light platform allows you to control the internal light of the Xiaomi gateway. The integration will be loaded automatically and provides a device called `light.gateway_light_28ffffffffff`.
The requirement is that you have setup [Xiaomi aqara](/integrations/xiaomi_aqara/).

2
source/_integrations/light.xiaomi_miio.markdown
View File

@ -98,7 +98,7 @@ Supported models: `philips.light.moonlight`
Please follow the instructions on [Retrieving the Access Token](/integrations/vacuum.xiaomi_miio/#retrieving-the-access-token) to get the API token to use in the `configuration.yaml` file.
To add a Xiaomi Philips Light to your installation, add the following to your configuration.yaml file:
To add a Xiaomi Philips Light to your installation, add the following to your `configuration.yaml` file:
```yaml
# Example configuration.yaml entries

2
source/_integrations/mailgun.markdown
View File

@ -12,7 +12,7 @@ To be able to receive webhooks from Mailgun, your Home Assistant instance needs
To set it up, go to the integrations page in the configuration screen and find Mailgun. Click on configure. Follow the instructions on the screen to configure Mailgun.
You will get a URL of the following format: `https://<home-assistant-domain>/api/webhook/9940e99a26fae4dcf6fe0a478124b6b58b578ea4c55c9a584beb1c9f5057bb91`. To receive webhooks from Mailgun, you need to provide that url as a callback URL in the Webhooks tab of the Mailgun Control Panel.
You will get a URL of the following format: `https://<home-assistant-domain>/api/webhook/9940e99a26fae4dcf6fe0a478124b6b58b578ea4c55c9a584beb1c9f5057bb91`. To receive webhooks from Mailgun, you need to provide that URL as a callback URL in the Webhooks tab of the Mailgun Control Panel.
There is currently support for the following device types within Home Assistant:

4
source/_integrations/mikrotik.markdown
View File

@ -34,7 +34,7 @@ Go to **IP** -> **Services** -> **API** and enable it.
Make sure that port 8728 or the port you choose is accessible from your network.
Home Assistant offers Mikrotik integration through **Configuration** -> **Integrations** -> **Mikrotik**.
Home Assistant offers MikroTik integration through **Configuration** -> **Integrations** -> **MikroTik**.
It also allows importing from the `configuration.yaml` file:
```yaml
@ -48,7 +48,7 @@ mikrotik:
{% configuration %}
name:
description: The name of your Mikrotik device.
description: The name of your MikroTik device.
required: true
default: Mikrotik
type: string

2
source/_integrations/minio.markdown
View File

@ -45,7 +45,7 @@ secret_key:
required: true
type: string
secure:
description: Whether to use http or https connection
description: Whether to use HTTP or HTTPS connection
required: true
type: boolean
default: false

2
source/_integrations/mjpeg.markdown
View File

@ -50,7 +50,7 @@ authentication:
type: string
default: basic
verify_ssl:
description: Validate the ssl certificate for this camera.
description: Validate the SSL certificate for this camera.
required: false
type: boolean
default: true

2
source/_integrations/neato.markdown
View File

@ -26,7 +26,7 @@ Menu: *Configuration* -> *Integrations*
Search for or select **Neato** from the list and configure the integration. You will need to enter your username and password and whether you are using a Neato or Vorwerk device.
After that, all the entities will automatically show up in Home Assistant.
## Setup the integration via configuration.yaml
## Setup the integration via `configuration.yaml`
Add the following to your configuration.yaml:

2
source/_integrations/netatmo.markdown
View File

@ -48,7 +48,7 @@ client_secret:
type: string
{% endconfiguration %}
<b>After the client_id and client_secret is added to your configuration.yaml you must enable Netatmo through the integrations page.</b>
**After the client_id and client_secret is added to your `configuration.yaml` you must enable Netatmo through the integrations page.**
### Get API and Secret Key

2
source/_integrations/netdata.markdown
View File

@ -62,7 +62,7 @@ Alternatively you can browse to the built in Netdata API in your browser `http:/
},
```
Once the `data_group` "system.load" and the `element` "load15" have been identified from the JSON it can be configured in your configuration.yaml like the example below.
Once the `data_group` "system.load" and the `element` "load15" have been identified from the JSON it can be configured in your `configuration.yaml` like the example below.
## Configuration

4
source/_integrations/nfandroidtv.markdown
View File

@ -97,8 +97,8 @@ The following attributes can be placed inside `data` to send images.
| `file` | yes | Groups the attributes for file upload. If present, either `url` or `path` have to be provided.
| `path` | yes | Local path of an image file. Is placed inside `file`.
| `url` | yes | URL of an image file. Is placed inside `file`.
| `username` | yes | Username if the url requires authentication. Is placed inside `file`.
| `password` | yes | Password if the url requires authentication. Is placed inside `file`.
| `username` | yes | Username if the URL requires authentication. Is placed inside `file`.
| `password` | yes | Password if the URL requires authentication. Is placed inside `file`.
| `auth` | yes | If set to `digest` HTTP-Digest-Authentication is used. If missing, HTTP-BASIC-Authentication is used. Is placed inside `file`.
Example for posting file from URL:

2
source/_integrations/openhome.markdown
View File

@ -10,7 +10,7 @@ ha_iot_class: Local Polling
The `openhome` platform allows you to connect an [Openhome Compliant Renderer](http://openhome.org/) to Home Assistant such as a [Linn Products Ltd](https://www.linn.co.uk) HiFi streamer. It will allow you to control media playback, volume, source and see the current playing item. Openhome devices should be discovered by using the [the discovery component](/integrations/discovery/), their device names are taken from the name of the room configured on the device.
### Example configuration.yaml entry
### Example `configuration.yaml` entry
```yaml
discovery:

4
source/_integrations/opnsense.markdown
View File

@ -32,7 +32,7 @@ to the OPNsense [documentation](https://docs.opnsense.org/development/how-tos/ap
{% configuration %}
url:
description: The URL for the OPNsense api endpoint of your router.
description: The URL for the OPNsense API endpoint of your router.
type: string
required: true
api_key:
@ -44,7 +44,7 @@ api_secret:
type: string
required: true
verify_ssl:
description: Set to true to enable the validation of the OPNsense API's SSL.
description: Set to true to enable the validation of the OPNsense API SSL.
type: boolean
required: false
default: false

2
source/_integrations/owntracks.markdown
View File

@ -124,7 +124,7 @@ Owntracks v2.0.0 removes support for iBeacons on Android.
When run in the usual *significant changes mode* (which is kind to your phone battery), Owntracks sometimes doesn't update your location as quickly as you'd like when you arrive at a zone. This can be annoying if you want to trigger an automation when you get home. You can improve the situation using iBeacons.
iBeacons are simple Bluetooth devices that send out an "I'm here" message. They are supported by IOS and some Android devices. Owntracks explain more [here](https://owntracks.org/booklet/guide/beacons/).
iBeacons are simple Bluetooth devices that send out an "I'm here" message. They are supported by iOS and some Android devices. Owntracks explain more [here](https://owntracks.org/booklet/guide/beacons/).
When you enter an iBeacon region, Owntracks will send a `region enter` message to HA as described above. So if you want to have an event triggered when you arrive home, you can put an iBeacon outside your front door. If you set up an OwnTracks iBeacon region called `home` then getting close to the beacon will trigger an update to HA that will set your zone to be `home`.

2
source/_integrations/plugwise.markdown
View File

@ -21,7 +21,7 @@ The password can be found on the bottom of your Smile, it should consist of 6 ch
## Configuration
You have to add the following to your configuration.yaml file:
You have to add the following to your `configuration.yaml` file:
```yaml
# Minimal configuration.yaml entry

2
source/_integrations/ps4.markdown
View File

@ -165,7 +165,7 @@ When the integration retrieves data from the PlayStation Store, it stores it in
| ----- | ----- | ----------- |
| `locked` | boolean | Must be `true` or `false`
| `media_content_type` | string | Must be `game` or `app`
| `media_image_url` | string | Any valid url for an image
| `media_image_url` | string | Any valid URL for an image
| `media_title` | string | The title of the game or app
The data in the example shows 2 entries.

8
source/_integrations/pushbullet.markdown
View File

@ -143,7 +143,7 @@ action:
url: google.com
```
- **url** (*Required*): Page URL to send with Pushbullet.
- `url` (*Required*): Page URL to send with Pushbullet.
### File support
@ -157,7 +157,7 @@ action:
file: /path/to/my/file
```
- **file** (*Required*): File to send with Pushbullet.
- `file` (*Required*): File to send with Pushbullet.
### File URL support
@ -171,7 +171,7 @@ action:
file_url: https://cdn.pixabay.com/photo/2014/06/03/19/38/test-361512_960_720.jpg
```
- **file_url** (*Required*): File to send with Pushbullet.
- `file_url` (*Required*): File to send with Pushbullet.
### Single target
@ -184,7 +184,7 @@ action:
target: device/DEVICE_NAME
```
- **target**: Pushbullet device to receive the notification.
- `target`: Pushbullet device to receive the notification.
<div class='note'>

6
source/_integrations/rejseplanen.markdown
View File

@ -14,13 +14,13 @@ The `rejseplanen` sensor will provide you with travel details for Danish public
The `stop_id` can be obtained through the following steps:
If you know the exact name of the stop you can search the stop_id with the following url [http://xmlopen.rejseplanen.dk/bin/rest.exe/location?format=json&input=STOP_NAME](http://xmlopen.rejseplanen.dk/bin/rest.exe/location?format=json&input=STOP_NAME) and put in the name of the stop instead of "STOP_NAME" in the end of the url.
If you know the exact name of the stop you can search the stop_id with the following URL [http://xmlopen.rejseplanen.dk/bin/rest.exe/location?format=json&input=STOP_NAME](http://xmlopen.rejseplanen.dk/bin/rest.exe/location?format=json&input=STOP_NAME) and put in the name of the stop instead of "STOP_NAME" in the end of the URL.
If you don't know the name of the stop follow this guide:
- Go to [https://www.openstreetmap.org](https://www.openstreetmap.org)
- Make a search and fill in the location you want to find for.
- The url will look like this [https://www.openstreetmap.org/#map=18/56.15756/10.20674](https://www.openstreetmap.org/#map=18/56.15756/10.20674)
- Now insert the coordinates for the location in the url, in this example it will be: [http://xmlopen.rejseplanen.dk/bin/rest.exe/stopsNearby?coordX=56.15756&coordY=10.20674&](http://xmlopen.rejseplanen.dk/bin/rest.exe/stopsNearby?coordX=56.15756&coordY=10.20674&)
- The URL will look like this [https://www.openstreetmap.org/#map=18/56.15756/10.20674](https://www.openstreetmap.org/#map=18/56.15756/10.20674)
- Now insert the coordinates for the location in the URL, in this example it will be: [http://xmlopen.rejseplanen.dk/bin/rest.exe/stopsNearby?coordX=56.15756&coordY=10.20674&](http://xmlopen.rejseplanen.dk/bin/rest.exe/stopsNearby?coordX=56.15756&coordY=10.20674&)
- You will now see the 30 stops closest to your location.
You will see an output like this:

12
source/_integrations/rocketchat.markdown
View File

@ -24,13 +24,13 @@ notify:
room: YOUR_ROOM_NAME
```
- **name** (*Optional*): Name displayed in the frontend. The notifier will bind to the service `notify.NOTIFIER_NAME`.
- **url** (*Required*): The URL of your Rocket.Chat instance.
- **username** (*Required*): The Rocket.Chat username.
- **password** (*Required*): The Rocker.Chat password.
- **room** (*Required*): The chat room name to send messages to.
- `name` (*Optional*): Name displayed in the frontend. The notifier will bind to the service `notify.NOTIFIER_NAME`.
- `url` (*Required*): The URL of your Rocket.Chat instance.
- `username` (*Required*): The Rocket.Chat username.
- `password` (*Required*): The Rocker.Chat password.
- `room` (*Required*): The chat room name to send messages to.
### script.yaml example
### Script example
```yaml
rocketchat_notification:

2
source/_integrations/rova.markdown
View File

@ -12,7 +12,7 @@ ha_iot_class: Cloud Polling
## Configuration
To use the ROVA sensor in your installation, add the following to your configuration.yaml file:
To use the ROVA sensor in your installation, add the following to your `configuration.yaml` file:
```yaml
# Example configuration.yaml entry

2
source/_integrations/sensor.command_line.markdown
View File

@ -108,7 +108,7 @@ sensor:
command: "grep -c 'Login attempt' /home/hass/.homeassistant/home-assistant.log"
```
Make sure to configure the [logger component](/integrations/logger) to monitor the [http component](/integrations/http/) at least the `warning` level.
Make sure to configure the [Logger integration](/integrations/logger) to monitor the [HTTP integration](/integrations/http/) at least the `warning` level.
```yaml
# Example working logger settings that works

2
source/_integrations/sensor.metoffice.markdown
View File

@ -13,7 +13,7 @@ The `metoffice` sensor platform uses the Met Office's [DataPoint API](https://ww
- Each sensor will be given the `device_id` of "Met Office [condition]" if `name:` is not set.
- The sensor checks for new data every minute, starting 30 minutes after the timestamp of the most recent data as the data is updated every half hour.
To add the Met Office weather to your installation you'll need to register for a free api key at the link above and then add the following to your `configuration.yaml` file:
To add the Met Office weather to your installation you'll need to register for a free API key at the link above and then add the following to your `configuration.yaml` file:
```yaml
# Example configuration.yaml entry

2
source/_integrations/sensor.rfxtrx.markdown
View File

@ -10,7 +10,7 @@ ha_release: 0.7
The `rfxtrx` platform support sensors that communicate in the frequency range of 433.92 MHz.
First you have to set up your [rfxtrx hub](/integrations/rfxtrx/).
First you have to set up your [RFXtrx hub](/integrations/rfxtrx/).
The easiest way to find your sensors is to add this to your `configuration.yaml`:
```yaml

4
source/_integrations/slack.markdown
View File

@ -77,8 +77,8 @@ The following attributes can be placed inside `data` for extended functionality.
| `file` | yes | Groups the attributes for file upload. If present, either `url` or `path` have to be provided.
| `path ` | yes | Local path of file, photo etc to post to slack. Is placed inside `file`.
| `url` | yes | URL of file, photo etc to post to slack. Is placed inside `file`.
| `username` | yes | Username if the url requires authentication. Is placed inside `file`.
| `password` | yes | Password if the url requires authentication. Is placed inside `file`.
| `username` | yes | Username if the URL requires authentication. Is placed inside `file`.
| `password` | yes | Password if the URL requires authentication. Is placed inside `file`.
| `auth` | yes | If set to `digest` HTTP-Digest-Authentication is used. If missing HTTP-BASIC-Authentication is used. Is placed inside `file`.
| `attachments` | yes | Array of [Slack attachments](https://api.slack.com/docs/message-attachments). See [the attachment documentation](https://api.slack.com/docs/message-attachments) for how to format. *NOTE*: if using `attachments`, they are shown **in addition** to `message`

2
source/_integrations/smartthings.markdown
View File

@ -49,7 +49,7 @@ If you are using Home Assistant Cloud (Nabu Casa) the integration will create a
1. A [personal access token](https://account.smartthings.com/tokens) tied to a Samsung or SmartThings account (see below for instructions).
2. Home Assistant setup for [remote access](/docs/configuration/remote/) via a domain name secured with SSL. *Self-signed SSL certificates are not supported by the SmartThings Cloud API.*
3. [`base_url` of the http integration](/integrations/http#base_url) set the URL that Home Assistant is available on the internet. SmartThings requires the `base_url` and Home Assistant to use the standard HTTPS port (443).
3. [`base_url` of the HTTP integration](/integrations/http#base_url) set the URL that Home Assistant is available on the internet. SmartThings requires the `base_url` and Home Assistant to use the standard HTTPS port (443).
## Setup instructions

4
source/_integrations/snmp.markdown
View File

@ -34,8 +34,8 @@ The following OID examples pull the current MAC Address table from a router. Thi
| Aruba | IAP325 on AOS 6.5.4.8 | `1.3.6.1.4.1.14823.2.3.3.1.2.4.1.1` |
| BiPAC | 7800DXL Firmware 2.32e | `1.3.6.1.2.1.17.7.1.2.2.1.1` |
| DD-WRT | unknown version/model | `1.3.6.1.2.1.4.22.1.2` |
| Mikrotik | unknown RouterOS version/model | `1.3.6.1.4.1.14988.1.1.1.2.1.1` |
| Mikrotik | RouterOS 6.x on RB2011 | `1.3.6.1.2.1.4.22.1.2` |
| MikroTik | unknown RouterOS version/model | `1.3.6.1.4.1.14988.1.1.1.2.1.1` |
| MikroTik | RouterOS 6.x on RB2011 | `1.3.6.1.2.1.4.22.1.2` |
| OpenWrt | Chaos Calmer 15.05 | `1.3.6.1.2.1.4.22.1.2` |
| OPNSense | 19.1 | `1.3.6.1.2.1.4.22.1.2` |
| pfSense | 2.2.4 | `1.3.6.1.2.1.4.22.1.2` |

2
source/_integrations/solaredge_local.markdown
View File

@ -27,7 +27,7 @@ If your inverter does not support the local API, you can use the [cloud based ve
## Configuration
To use the SolarEdge sensors in your installation, add the following to your configuration.yaml file:
To use the SolarEdge sensors in your installation, add the following to your `configuration.yaml` file:
```yaml
# Example configuration.yaml entry

2
source/_integrations/solax.markdown
View File

@ -15,7 +15,7 @@ The `solax` integration connects Home Assistant to Solax solar power inverters.
## Configuration
To use the Solax sensors in your installation, add the following to your configuration.yaml file:
To use the Solax sensors in your installation, add the following to your `configuration.yaml` file:
```yaml
# Example configuration.yaml entry

4
source/_integrations/somfy.markdown
View File

@ -11,7 +11,7 @@ ha_codeowners:
- '@tetienne'
---
The Somfy integration will allow users to integrate their Somfy devices into Home Assistant using the [official API](https://developer.somfy.com/somfy-open-api/apis), unlike the [tahoma](/integrations/tahoma/) component.
The Somfy integration will allow users to integrate their Somfy devices into Home Assistant using the [official API](https://developer.somfy.com/somfy-open-api/apis), unlike the [Tahoma](/integrations/tahoma/) integration.
## Installation
@ -62,7 +62,7 @@ client_secret:
### Potential duplicate with the Tahoma integration
If you use the [tahoma](/integrations/tahoma) component, you will have to exclude the covers added by this one. Otherwise, they will be added twice.
If you use the [Tahoma](/integrations/tahoma) integration, you will have to exclude the covers added by this one. Otherwise, they will be added twice.
```yaml
# Example configuration.yaml entry

2
source/_integrations/spotcrime.markdown
View File

@ -9,7 +9,7 @@ ha_iot_class: Cloud Polling
SpotCrime is no longer handing out API keys to integrate their services.
</div>
The `spotcrime` sensor allows one to track reported incidents occurring in a given area. Incidents include anything reported to [Spot Crime](https://www.spotcrime.info). Your regional emergency services may or may not report data. The sensor defaults to counting incidents within one day, but can be customized via configuration.yaml.
The `spotcrime` sensor allows one to track reported incidents occurring in a given area. Incidents include anything reported to [Spot Crime](https://www.spotcrime.info). Your regional emergency services may or may not report data. The sensor defaults to counting incidents within one day, but can be customized via `configuration.yaml`.
## Configuration

2
source/_integrations/ssdp.markdown
View File

@ -9,7 +9,7 @@ logo: home-assistant.png
The `ssdp` "Simple Service Discovery Protocol" integration will scan the network for supported devices and services. Discovered integrations will show up in the discovered section on the integrations page in the config panel.
Integrations can opt-in to be found by adding [an SSDP section](https://developers.home-assistant.io/docs/en/next/creating_integration_manifest.html#ssdp) to their manifest.json.
Integrations can opt-in to be found by adding [an SSDP section](https://developers.home-assistant.io/docs/en/next/creating_integration_manifest.html#ssdp) to their `manifest.json`.
## Configuration

3
source/_integrations/stookalert.markdown
View File

@ -11,8 +11,7 @@ ha_codeowners:
- '@fwestenberg'
---
The `stookalert` sensor platform queries the [RIVM stookalert](https://www.rivm.nl/stookalert) API for unfavorable weather conditions or poor air quality. With a Stookalert, the RIVM calls on people not to burn wood. This can prevent health problems in people in the area.
The `stookalert` sensor platform queries the [RIVM Stookalert](https://www.rivm.nl/stookalert) API for unfavorable weather conditions or poor air quality. With a Stookalert, the RIVM calls on people not to burn wood. This can prevent health problems in people in the area.
## Configuration

2
source/_integrations/supla.markdown
View File

@ -40,7 +40,7 @@ server:
access_token:
description:
An access token for REST API configuration. Can be acquired from
http[s]://your.server.org/integrations/tokens (please add at least Channel's Read and Action Execution permissions).
`http[s]://your.server.org/integrations/tokens` (please add at least Channel's Read and Action Execution permissions).
required: true
type: string
{% endconfiguration %}

6
source/_integrations/switch.rfxtrx.markdown
View File

@ -11,7 +11,7 @@ The `rfxtrx` platform support switches that communicate in the frequency range o
## Configuration
First you have to set up your [rfxtrx hub](/integrations/rfxtrx/).
First you have to set up your [RFXtrx hub](/integrations/rfxtrx/).
The easiest way to find your switches is to add this to your `configuration.yaml`:
```yaml
@ -68,7 +68,7 @@ signal_repetitions:
<div class='note warning'>
This integration and the [rfxtrx binary sensor](/integrations/binary_sensor.rfxtrx/) can steal each other's devices when setting the `automatic_add` configuration parameter to `true`. Set `automatic_add` only when you have some devices to add to your installation, otherwise leave it to `false`.
This integration and the [RFXtrx binary sensor](/integrations/binary_sensor.rfxtrx/) can steal each other's devices when setting the `automatic_add` configuration parameter to `true`. Set `automatic_add` only when you have some devices to add to your installation, otherwise leave it to `false`.
</div>
@ -88,7 +88,7 @@ If you need to generate codes for switches you can use a template (useful for ex
{% raw %}0b11000{{ range(100,700) | random | int }}bc0cfe0{{ range(0,10) | random | int }}010f70{% endraw %}
```
- Use this code to add a new switch in your configuration.yaml
- Use this code to add a new switch in your `configuration.yaml`
- Launch your Home Assistant and go to 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

2
source/_integrations/tautulli.markdown
View File

@ -56,7 +56,7 @@ port:
default: 8181
type: integer
path:
description: The Base Url path of your Tautulli server.
description: The Base URL path of your Tautulli server.
required: false
type: string
ssl:

2
source/_integrations/telegram_broadcast.markdown
View File

@ -38,7 +38,7 @@ parse_mode:
type: string
default: "`markdown`"
proxy_url:
description: Proxy url if working behind one (`socks5://proxy_ip:proxy_port`).
description: Proxy URL if working behind one (`socks5://proxy_ip:proxy_port`).
required: false
type: string
proxy_params:

2
source/_integrations/telegram_polling.markdown
View File

@ -40,7 +40,7 @@ parse_mode:
type: string
default: "`markdown`"
proxy_url:
description: Proxy url if working behind one (`socks5://proxy_ip:proxy_port`).
description: Proxy URL if working behind one (`socks5://proxy_ip:proxy_port`).
required: false
type: string
proxy_params:

2
source/_integrations/telegram_webhooks.markdown
View File

@ -46,7 +46,7 @@ parse_mode:
default: markdown
type: string
proxy_url:
description: Proxy url if working behind one (`socks5://proxy_ip:proxy_port`).
description: Proxy URL if working behind one (`socks5://proxy_ip:proxy_port`).
required: false
type: string
proxy_params:

2
source/_integrations/tomato.markdown
View File

@ -44,7 +44,7 @@ ssl:
type: boolean
default: false
verify_ssl:
description: "If SSL verification for https resources needs to be turned off (for self-signed certs, etc.) this can take on boolean values `false` or `true` or you can pass a location on the device where a certificate can be used for verification e.g., `/mnt/NAS/router_cert.pem`."
description: "If SSL verification for HTTPS resources needs to be turned off (for self-signed certs, etc.) this can take on boolean values `false` or `true` or you can pass a location on the device where a certificate can be used for verification e.g., `/mnt/NAS/router_cert.pem`."
required: false
type: [string, boolean]
default: true

2
source/_integrations/transmission.markdown
View File

@ -119,7 +119,7 @@ Example of configuration of an automation with completed torrents:
### Service `add_torrent`
Adds a new torrent to download. It can either be a URL (http, https or ftp), magnet link or a local file (make sure that the path is [white listed](/docs/configuration/basic/#whitelist_external_dirs)).
Adds a new torrent to download. It can either be a URL (HTTP, HTTPS or FTP), magnet link or a local file (make sure that the path is [white listed](/docs/configuration/basic/#whitelist_external_dirs)).
| Service data attribute | Optional | Description |
| ---------------------- | -------- | ----------- |

10
source/_integrations/tts.markdown
View File

@ -20,7 +20,7 @@ tts:
<div class='note'>
Depending on your setup, you might need to set a base URL (`base_url`) inside the [http component](/integrations/http/) or in the parameters of this component.
Depending on your setup, you might need to set a base URL (`base_url`) inside the [HTTP component](/integrations/http/) or in the parameters of this component.
</div>
@ -43,7 +43,7 @@ time_memory:
type: integer
default: 300
base_url:
description: A base URL to use *instead* of the one set in the [http component](/integrations/http/). It is used as-is by the `tts` component. In particular, you need to include the protocol scheme `http://` or `https://` and the correct port number. They will not be automatically added for you.
description: A base URL to use *instead* of the one set in the [HTTP component](/integrations/http/). It is used as-is by the `tts` component. In particular, you need to include the protocol scheme `http://` or `https://` and the correct port number. They will not be automatically added for you.
required: false
type: string
default: value of ``http.base_url``
@ -75,7 +75,7 @@ In the above example, `base_url` is custom to this particular TTS platform confi
## When do you need to set `base_url` here?
The general answer is "whenever the global `base_url` set in [http component](/integrations/http/) is not adequate to allow the `say` service to run". The `say` service operates by generating a media file that contains the speech corresponding to the text passed to the service. Then the `say` service sends a message to the media device with a URL pointing to the file. The device fetches the media file at the URL and plays the media. Some combinations of a media device, network configuration and Home Assistant configuration can make it so that the device cannot fetch the media file.
The general answer is "whenever the global `base_url` set in [HTTP component](/integrations/http/) is not adequate to allow the `say` service to run". The `say` service operates by generating a media file that contains the speech corresponding to the text passed to the service. Then the `say` service sends a message to the media device with a URL pointing to the file. The device fetches the media file at the URL and plays the media. Some combinations of a media device, network configuration and Home Assistant configuration can make it so that the device cannot fetch the media file.
The following sections describe some of the problems encountered with media devices.
@ -83,7 +83,7 @@ The following sections describe some of the problems encountered with media devi
This problem occurs when your Home Assistant instance is configured to be accessed through SSL, and you are using a self-signed certificate.
The `tts` service will send an `https://` URL to the media device, which will check the certificate, and reject it. So it won't play your file. If you could make the device accept your certificate, it would play the file. However, many media devices do not allow changing settings to accept self-signed certificates. Ultimately, your option may be to serve files to the device as `http://` rather than `https://`. To do this, you *could* change the `base_url` setting in [http component](/integrations/http/), but that would turn off SSL for all services that use `base_url`. Instead, setting a `base_url` for the `tts` service allows turning off SSL only for this component.
The `tts` service will send an `https://` URL to the media device, which will check the certificate, and reject it. So it won't play your file. If you could make the device accept your certificate, it would play the file. However, many media devices do not allow changing settings to accept self-signed certificates. Ultimately, your option may be to serve files to the device as `http://` rather than `https://`. To do this, you *could* change the `base_url` setting in [HTTP component](/integrations/http/), but that would turn off SSL for all services that use `base_url`. Instead, setting a `base_url` for the `tts` service allows turning off SSL only for this component.
### Google cast devices
@ -145,7 +145,7 @@ The integration has two caches. Both caches can be controlled with the `cache` o
### POST `/api/tts_get_url`
Returns an URL to the generated TTS file. Platform and message are required.
Returns a URL to the generated TTS file. Platform and message are required.
```json
{

2
source/_integrations/unifiled.markdown
View File

@ -29,7 +29,7 @@ light:
{% configuration %}
host:
description: Ip address or hostname used to connect to the Unifi LED controller.
description: IP address or hostname used to connect to the Unifi LED controller.
type: string
required: true
default: None

6
source/_integrations/vacuum.mqtt.markdown
View File

@ -320,7 +320,7 @@ payload_pause:
type: string
default: pause
state_topic:
description: The MQTT topic subscribed to receive state messages from the vacuum. State topic is extracting json if no `value_template` is defined.
description: The MQTT topic subscribed to receive state messages from the vacuum. State topic is extracting JSON if no `value_template` is defined.
required: false
type: string
value_template:
@ -417,7 +417,7 @@ Vacuum send_command allows three parameters:
- params - optional
If params are not provided it sends command as payload to MQTT send_command topic.
If params are provided service sends json as payload with such structure:
If params are provided service sends JSON as payload with such structure:
```json
{
@ -492,7 +492,7 @@ Vacuum send_command allows three parameters:
- params - optional
If params are not provided it sends command as payload to MQTT send_command topic.
If params are provided service sends json as payload with such structure:
If params are provided service sends JSON as payload with such structure:
```json
{

4
source/_integrations/velbus.markdown
View File

@ -32,7 +32,7 @@ The pushbutton LEDs of input modules are disabled by default. These can be enabl
## Configuration
There are 2 options in configuring the velbus integration:
There are 2 options in configuring the Velbus integration:
- Via the Home Assistant user interface where it will let you enter the port string to connect to the Velbus bus.
- Via the Home Assistant `configuration.yaml` file.
@ -48,7 +48,7 @@ velbus:
The port string used in the user interface or the configuration file can have 2 formats:
- For a serial device: /dev/ttyUSB00
- For a tcp/ip device: 127.0.0.1:3678
- For a TCP/IP device: 127.0.0.1:3678
{% configuration %}
port:

4
source/_integrations/vera.markdown
View File

@ -32,7 +32,7 @@ and will be automatically added when HA connects to your Vera controller.
## Configuration
To use Vera devices in your installation, add the following to your configuration.yaml file using the IP and port number of your Vera controller:
To use Vera devices in your installation, add the following to your `configuration.yaml` file using the IP and port number of your Vera controller:
```yaml
vera:
@ -77,7 +77,7 @@ If you want to use a Z-Wave device from the Vera controller in Home Assistant au
The `vera` platform allows you to get data from your [Vera](https://getvera.com/) sensors from within Home Assistant.
Please note that some vera sensors (such as _motion_ and _flood_ sensors) are _armable_ which means that vera will send alerts (email messages to txts) when they are _armed_ and change state.
Please note that some Vera sensors (such as _motion_ and _flood_ sensors) are _armable_ which means that Vera will send alerts (email messages to txts) when they are _armed_ and change state.
Home Assistant will display the state of these sensors regardless of the _armed_ state.

Some files were not shown because too many files have changed in this diff Show More