mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-07-13 20:36:52 +00:00
Merge branch 'current' into next
This commit is contained in:
Franck Nijhof
commit
c5e83224bc
6
.github/workflows/test.yml
vendored
6
.github/workflows/test.yml
vendored
@ -10,7 +10,7 @@ jobs:
|
||||
- name: Check out files from GitHub
|
||||
uses: actions/checkout@v2.3.4
|
||||
- name: Setting up Node.js ${{ matrix.node-version }}
|
||||
uses: actions/setup-node@v2.2.0
|
||||
uses: actions/setup-node@v2.3.0
|
||||
with:
|
||||
node-version: 12.x
|
||||
- name: Setup NPM cache
|
||||
@ -33,7 +33,7 @@ jobs:
|
||||
- name: Check out files from GitHub
|
||||
uses: actions/checkout@v2.3.4
|
||||
- name: Setting up Node.js ${{ matrix.node-version }}
|
||||
uses: actions/setup-node@v2.2.0
|
||||
uses: actions/setup-node@v2.3.0
|
||||
with:
|
||||
node-version: 12.x
|
||||
- name: Setup NPM cache
|
||||
@ -57,7 +57,7 @@ jobs:
|
||||
- name: Check out files from GitHub
|
||||
uses: actions/checkout@v2.3.4
|
||||
- name: Setting up Ruby 2.6
|
||||
uses: ruby/setup-ruby@v1.77.0
|
||||
uses: ruby/setup-ruby@v1.78.0
|
||||
with:
|
||||
ruby-version: 2.6
|
||||
- name: Setup Ruby Gems cache
|
||||
|
||||
@ -66,7 +66,7 @@ GEM
|
||||
kramdown-parser-gfm (1.1.0)
|
||||
kramdown (~> 2.0)
|
||||
liquid (4.0.3)
|
||||
listen (3.5.1)
|
||||
listen (3.6.0)
|
||||
rb-fsevent (~> 0.10, >= 0.10.3)
|
||||
rb-inotify (~> 0.9, >= 0.9.10)
|
||||
mercenary (0.4.0)
|
||||
|
||||
@ -105,8 +105,8 @@ social:
|
||||
# Home Assistant release details
|
||||
current_major_version: 2021
|
||||
current_minor_version: 7
|
||||
current_patch_version: 3
|
||||
date_released: 2021-07-16
|
||||
current_patch_version: 4
|
||||
date_released: 2021-07-21
|
||||
|
||||
# Either # or the anchor link to latest release notes in the blog post.
|
||||
# Must be prefixed with a # and have double quotes around it.
|
||||
|
||||
@ -177,7 +177,7 @@ variables required for the library to compile without failing. These variables
|
||||
are preset because Sass will error without them, however they are **not** set in
|
||||
stone, and you are encouranged to override and experiment with them.
|
||||
|
||||
It is tempting to modify their vaules in the inuit.css submodule but this is
|
||||
It is tempting to modify their values in the inuit.css submodule but this is
|
||||
**not** the correct method for modifying inuit.css, and in doing so you will
|
||||
prevent yourself from being able to update inuit.css’ core library. The correct
|
||||
procedure is to redefine that variable in `_vars.scss` found in the inuit.css
|
||||
|
||||
@ -145,7 +145,7 @@
|
||||
/**
|
||||
* If you have set the additional `$responsive-extra` variable to ‘true’ in
|
||||
* `_vars.scss` then you now have access to the following class available to
|
||||
* accomodate much larger screen resolutions.
|
||||
* accommodate much larger screen resolutions.
|
||||
*/
|
||||
|
||||
@if $responsive-extra == true{
|
||||
|
||||
@ -46,7 +46,7 @@
|
||||
|
||||
|
||||
/**
|
||||
* Very infrequently occuring grid wrappers as children of grid wrappers.
|
||||
* Very infrequently occurring grid wrappers as children of grid wrappers.
|
||||
*/
|
||||
.grid > .grid{
|
||||
margin-left:0;
|
||||
|
||||
@ -11,7 +11,7 @@
|
||||
<i class="s s--help"></i> Help & support
|
||||
</a>
|
||||
*
|
||||
* However we will sometimes want a larger, explicity set gap:
|
||||
* However we will sometimes want a larger, explicitly set gap:
|
||||
<a href=# class=icon-text>
|
||||
<i class="icon-text__icon s s--help"></i>Help & support
|
||||
</a>
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
// // This file is just a butchered version fo the one included in the default Octopress theme.
|
||||
// // This file is just a butchered version of the one included in the default Octopress theme.
|
||||
// // It could most definitely do with some cleaning up in the future.
|
||||
|
||||
// @mixin selection($bg, $color: inherit, $text-shadow: none){
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
/*
|
||||
Add plugin stylesheets to this directory and they will be automatically
|
||||
Imported. Load order is alphabetical and styles can be overriden in
|
||||
Imported. Load order is alphabetical and styles can be overridden in
|
||||
custom/_style.scss which is loaded after all plugin stylesheets.
|
||||
*/
|
||||
|
||||
|
||||
@ -56,7 +56,7 @@ Before beginning make sure that you have the following:
|
||||
|
||||
- `host` (*Optional*): The IP address to listen on for client requests. This defaults to all IP addresses on the server. To listen only locally, choose `127.0.0.1`
|
||||
- `port` (*Optional*): The port to listen on for client requests. Defaults to 12345.
|
||||
- `password` (*Required*): A password shared between client and server. Use only alpha-numeric characters and spaces
|
||||
- `password` (*Required*): A password shared between client and server. Use only alphanumeric characters and spaces
|
||||
- `mbox_path` (*Required*): The path to the storage location of mailbox files. This is typically `/var/spool/asterisk/voicemail/default/<mailbox>/`
|
||||
- `cache_file` (*Required*): A fully-qualified path to a file that can be written by the server containing transcriptions of voicemails. Example: `/var/spool/asterisk/transcription.cache`
|
||||
- `google_key` (*Required*): Your 40 characters Google API key.
|
||||
|
||||
@ -49,7 +49,7 @@ The following describes trigger data associated with all platforms.
|
||||
| `trigger.platform` | Hardcoded: `mqtt`.
|
||||
| `trigger.topic` | Topic that received payload.
|
||||
| `trigger.payload` | Payload.
|
||||
| `trigger.payload_json` | Dictonary of the JSON parsed payload.
|
||||
| `trigger.payload_json` | Dictionary of the JSON parsed payload.
|
||||
| `trigger.qos` | QOS of payload.
|
||||
|
||||
### Numeric State
|
||||
|
||||
@ -173,7 +173,7 @@ automation:
|
||||
|
||||
## Numeric state trigger
|
||||
|
||||
Fires when the numeric value of an entity's state (or attribute's value if using the `attribute` property) crosses a given threshold. On state change of a specified entity, attempts to parse the state as a number and fires if the value is changing from above to below or from below to above the given threshold.
|
||||
Fires when the numeric value of an entity's state (or attribute's value if using the `attribute` property) **crosses** (and only when crossing) a given threshold. On state change of a specified entity, attempts to parse the state as a number and fires if the value is changing from above to below or from below to above the given threshold.
|
||||
|
||||
{% raw %}
|
||||
|
||||
@ -667,7 +667,7 @@ automation:
|
||||
You can run this automation by sending an HTTP POST request to `http://your-home-assistant:8123/api/webhook/some_hook_id`. Here is an example using the **curl** command line program, with an empty data payload:
|
||||
|
||||
```shell
|
||||
curl -X POST https://your-home-assistant:8123/api/webhook/some_hook_id
|
||||
curl -X POST -d '{ "key": "value"}' https://your-home-assistant:8123/api/webhook/some_hook_id
|
||||
```
|
||||
|
||||
Webhook endpoints don't require authentication, other than knowing a valid webhook ID. You can send a data payload, either as encoded form data or JSON data. The payload is available in an automation template as either `trigger.json` or `trigger.data`. URL query parameters are available in the template as `trigger.query`. Remember to use an HTTPS URL if you've secured your Home Assistant installation with SSL/TLS.
|
||||
|
||||
@ -3,16 +3,16 @@ title: "Adding devices to Home Assistant"
|
||||
description: "Steps to help you get your devices in Home Assistant."
|
||||
---
|
||||
|
||||
Home Assistant will be able to automatically discover many devices and services available on your network if you have [the discovery component](/integrations/discovery/) enabled (the default setting).
|
||||
Home Assistant will be able to automatically discover many devices and services
|
||||
available on your network.
|
||||
|
||||
See the [integrations overview page](/integrations/) to find installation instructions for your devices and services. If you can't find support for your favorite device or service, [consider adding support](/developers/add_new_platform/).
|
||||
See the [integrations overview page](/integrations/) to find installation
|
||||
instructions for your devices and services. Most integration can be
|
||||
fully configured via the user interface these days; however, some older or
|
||||
more complex integrations may need to be configured manually using YAML.
|
||||
|
||||
Classification for the available integrations:
|
||||
|
||||
- [IoT class](/blog/2016/02/12/classifying-the-internet-of-things): Classifier for the device's behavior.
|
||||
- [Quality scale](/docs/quality_scale/): Representation of the integration's quality.
|
||||
|
||||
Usually every entity needs its own entry in the `configuration.yaml` file. There are two styles for multiple entries:
|
||||
For some of these integrations, every entity needs its own entry in the
|
||||
`configuration.yaml` file. There are two styles for multiple entity entries:
|
||||
|
||||
## Style 1: Collect every entity under the "parent"
|
||||
|
||||
@ -32,9 +32,10 @@ switch:
|
||||
- platform: vera
|
||||
```
|
||||
|
||||
## Style 2: List each device separately
|
||||
## Style 2: List each entity separately
|
||||
|
||||
You need to append numbers or strings to differentiate the entries, as in the example below. The appended number or string must be unique.
|
||||
You need to append numbers or strings to differentiate the entries, as in the
|
||||
example below. The appended number or string must be unique.
|
||||
|
||||
```yaml
|
||||
sensor bedroom:
|
||||
@ -59,10 +60,12 @@ switch 2:
|
||||
platform: vera
|
||||
```
|
||||
|
||||
## Grouping devices
|
||||
## Grouping entities
|
||||
|
||||
Once you have several devices set up, it is time to organize them into groups.
|
||||
Each group consists of a name and a list of entity IDs. Entity IDs can be retrieved from the web interface by using the {% my developer_states title="States page in the Developer Tools" %}.
|
||||
Once you have several entities set up, it is time to organize them into groups.
|
||||
Each group consists of a name and a list of entity IDs. Entity IDs can be
|
||||
retrieved from the web interface by using the
|
||||
{% my developer_states title="States page in the Developer Tools" %}.
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
|
||||
@ -21,15 +21,27 @@ Connect a keyboard and monitor to your device.
|
||||
|
||||
`auth reset --username existing_user --password new_password`
|
||||
|
||||
#### To reset a user's password, via the container command line
|
||||
|
||||
If you are running Home Assistant in a container, you can use the command line in the container with the `hass` command to change your password. The steps below refer to a Home Assistant container in Docker named `ha`. Note that while working in the container, commands will take a few moments to execute.
|
||||
|
||||
1. `docker exec -it ha bash` to open to the container command line
|
||||
2. `hass` to create a default user, if this is your first time using the tool
|
||||
3. `hass --script auth --config /config change_password existing_user new_password` to change the password
|
||||
4. `exit` to exit the container command line
|
||||
5. `docker restart ha` to restart the container
|
||||
|
||||
#### To reset a user's password, as an administrator via the web interface
|
||||
|
||||
1. Click "Configuration" in the sidebar.
|
||||
2. Scroll down to "Users", and click in to that section.
|
||||
3. Click on the user, this should bring up a dialog box.
|
||||
4. At the bottom of the dialog box, click "Change Password".
|
||||
5. Enter the new password, and then click "OK".
|
||||
6. Confirm the new password by entering it again, and then click "OK" again.
|
||||
7. A confirmation box will be displayed with the text "Password was changed successfully".
|
||||
1. Confirm that you have "Advanced Mode" activated on your "Profile" page.
|
||||
2. Click "Configuration" in the sidebar.
|
||||
3. Scroll down to "Users", and click in to that section.
|
||||
4. Click on the user, this should bring up a dialog box.
|
||||
5. At the bottom of the dialog box, click "Change Password".
|
||||
- If you do not see the "Change Password" button, try using another interface, such as the mobile version.
|
||||
6. Enter the new password, and then click "OK".
|
||||
7. Confirm the new password by entering it again, and then click "OK" again.
|
||||
8. A confirmation box will be displayed with the text "Password was changed successfully".
|
||||
|
||||
#### To delete a user, as an administrator via the web interface
|
||||
|
||||
@ -40,9 +52,9 @@ Connect a keyboard and monitor to your device.
|
||||
5. A confirmation dialog box will be displayed, asking "Are you sure you want to delete <User>"?
|
||||
6. Click "OK".
|
||||
|
||||
### Home Assistant Core and Home Assistant Container
|
||||
#### Start a new onboarding process
|
||||
|
||||
While you should hopefully be storing your passwords in a password manager, if you lose the password associated with the owner account the only way to resolve this is to delete *all* the authentication data. You do this by shutting down Home Assistant and deleting the following files from the `.storage/` folder in your [configuration folder](/docs/configuration/):
|
||||
If you lose the password associated with the owner account and the steps above do not work to reset the password, the only way to resolve this is to delete *all* the authentication data. You do this by shutting down Home Assistant and deleting the following files from the `.storage/` folder in your [configuration folder](/docs/configuration/):
|
||||
|
||||
- `auth`
|
||||
- `auth_provider.homeassistant`
|
||||
|
||||
@ -464,7 +464,7 @@ Setting up a device tracker:
|
||||
- State topic: `homeassistant/device_tracker/paulus/state`
|
||||
- Example state payload: `home` or `not_home` or `location name`
|
||||
|
||||
If the device supports gps co-ordinates then they can be sent to Home Assistant by specifying an attributes topic (i.e. "json_attributes_topic") in the configuration payload:
|
||||
If the device supports gps coordinates then they can be sent to Home Assistant by specifying an attributes topic (i.e. "json_attributes_topic") in the configuration payload:
|
||||
|
||||
- Attributes topic: `homeassistant/device_tracker/paulus/attributes`
|
||||
- Example attributes payload:
|
||||
|
||||
@ -32,7 +32,7 @@ The following configuration works the same as the one listed above:
|
||||
|
||||
```yaml
|
||||
alias: "Paulus home AND temperature below 20"
|
||||
condition:
|
||||
conditions:
|
||||
- condition: state
|
||||
entity_id: "device_tracker.paulus"
|
||||
state: "home"
|
||||
|
||||
@ -11,18 +11,13 @@ This Z-Wave integration is deprecated and replaced with a [new implementation ba
|
||||
|
||||
## Supported Z-Wave USB Sticks & Hardware Modules
|
||||
|
||||
You need to have a compatible Z-Wave stick or module installed. This needs to be a *static controller*, which most Z-Wave sticks and modules will be. If yours is a *bridge* device then it won't work with [OpenZWave](http://openzwave.com/), which is what provides Home Assistant's Z-Wave capabilities. USB sticks using the new 700 series Z-Wave platform are not compatible. The following devices have been confirmed to work:
|
||||
You need to have a compatible Z-Wave stick or module installed. This needs to be a *static controller*, which most Z-Wave sticks and modules will be. If yours is a *bridge* device then it won't work with [OpenZWave](http://openzwave.com/), which is what provides Home Assistant's Z-Wave capabilities. The following devices have been confirmed to work:
|
||||
|
||||
<div class='note'>
|
||||
|
||||
There are [known compatibility issues](https://www.raspberrypi.org/forums/viewtopic.php?f=28&t=245031#p1502030) with older hardware versions of the Aeotec stick not working on the Raspberry Pi 4. Aeotec has released a 2020 hardware revision ZW090-A/B/C Gen5+ with Pi 4 compatibility. Both hardware revisions are still being sold, make informed purchasing decisions if using paired with a Pi 4.
|
||||
|
||||
</div>
|
||||
|
||||
- Aeotec Z-Stick Series 5
|
||||
- Aeotec Z-Stick Series 5 (see note below)
|
||||
- Everspring USB stick - Gen 5
|
||||
- GoControl HUSBZB-1 stick
|
||||
- Sigma Designs UZB stick
|
||||
- Silicon Labs SLUSB7000A
|
||||
- Vision USB stick - Gen5
|
||||
- Zooz Z-Wave Plus S2 stick ZST10
|
||||
- ZWave.me Razberry Board
|
||||
@ -47,6 +42,12 @@ The alternative to a stick is a hub that supports Z-Wave. Home Assistant support
|
||||
|
||||
### Aeotec Stick
|
||||
|
||||
<div class='note'>
|
||||
|
||||
There are [known compatibility issues](https://www.raspberrypi.org/forums/viewtopic.php?f=28&t=245031#p1502030) with older hardware versions of the Aeotec stick not working on the Raspberry Pi 4. Aeotec has released a 2020 hardware revision ZW090-A/B/C Gen5+ with Pi 4 compatibility. Both hardware revisions are still being sold, make informed purchasing decisions if using paired with a Pi 4.
|
||||
|
||||
</div>
|
||||
|
||||
By default this will turn on "disco lights", which you can turn off by following the instructions in the [device specific page](/docs/z-wave/device-specific/#aeotec-z-stick)
|
||||
|
||||
### Razberry Board
|
||||
|
||||
@ -62,7 +62,7 @@ For both processes below you will need to insert your SD card into your PC and o
|
||||
|
||||
#### Raspberry Pi 4 procedure
|
||||
|
||||
Add the following paramaters to the bottom of the `/boot/config.txt` file.
|
||||
Add the following parameters to the bottom of the `/boot/config.txt` file.
|
||||
|
||||
```text
|
||||
dtoverlay=disable-bt
|
||||
@ -384,7 +384,7 @@ Zen22v2 (Dimmer):
|
||||
<Item label="Enabled" value="1" />
|
||||
</Value>
|
||||
<Value type="list" genre="config" instance="1" index="14" label="Enable/Disable Double-tap" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="2" vindex="2" size="1">
|
||||
<Help>Enables/Disables the double-tap fucntion and assign brightness to single tap. Last level: single tap returns to last brightness level. Full/Max level: single tap returns to full/max level</Help>
|
||||
<Help>Enables/Disables the double-tap function and assign brightness to single tap. Last level: single tap returns to last brightness level. Full/Max level: single tap returns to full/max level</Help>
|
||||
<Item label="Enabled" value="0" />
|
||||
<Item label="Disabled (last level)" value="1" />
|
||||
<Item label="Disabled (full/max level)" value="2" />
|
||||
@ -708,7 +708,7 @@ Zen30 (Double Switch):
|
||||
<Item label="maximum level" value="1"/>
|
||||
</Value>
|
||||
<Value type="list" genre="config" index="18" label="Enable/Disable Double-tap for Dimmer" size="1" min="0" max="2" value="0">
|
||||
<Help>Enable/Disable Double-tap for Dimmer. Enables/Disables the double-tap fucntion and assign brightness to single tap. enabled: single tap turns on to maximum brightness level. disabled (last level): single tap returns to last brightness level. disabled (full/max level): single tap returns to full brightmess. Default: enabled</Help>
|
||||
<Help>Enable/Disable Double-tap for Dimmer. Enables/Disables the double-tap function and assign brightness to single tap. enabled: single tap turns on to maximum brightness level. disabled (last level): single tap returns to last brightness level. disabled (full/max level): single tap returns to full brightmess. Default: enabled</Help>
|
||||
<Item label="enabled" value="0"/>
|
||||
<Item label="disabled (last level)" value="1"/>
|
||||
<Item label="disabled (full/max level)" value="2"/>
|
||||
@ -899,7 +899,7 @@ Zen34 Remote Switch:
|
||||
<Item label="LED always on in color specific under parameter 3" value="3" />
|
||||
</Value>
|
||||
<Value type="list" index="2" genre="config" label="LED indicator color for upper paddle triggers" units="" min="0" max="6" value="0" size="1">
|
||||
<Help>Choose the LED indicator color for the upper paddle remote controle triggers</Help>
|
||||
<Help>Choose the LED indicator color for the upper paddle remote controlled triggers</Help>
|
||||
<Item label="White" value="0" />
|
||||
<Item label="Blue" value="1" />
|
||||
<Item label="Green" value="2" />
|
||||
|
||||
@ -37,9 +37,9 @@ You would then enter the IP address or hostname of your Home Assistant OS instan
|
||||
|
||||
### Installing and using the SSH add-on (requires enabling advanced mode for the HA user)
|
||||
|
||||
The Terminal & SSH add-on provides access over an SSH connection, and also includes nano and vi editors. It can be installed from the add-on store's Official add-on repository after enabling advanced mode for your Home Assistant user's profile. Addtionally, this add-on provides access to the Home Assistant Command Line Interface (CLI) which provides custom commands for checking logs, stopping and starting Home Assistant and add-ons, creating/restoring snapshots, and more. (See [Home Assistant via Command Line](https://www.home-assistant.io/hassio/commandline/) for further info). The Terminal & SSH add-on does *not* provide access to the underlying host file system.
|
||||
The Terminal & SSH add-on provides access over an SSH connection, and also includes nano and vi editors. It can be installed from the add-on store's Official add-on repository after enabling advanced mode for your Home Assistant user's profile. Additionally, this add-on provides access to the Home Assistant Command Line Interface (CLI) which provides custom commands for checking logs, stopping and starting Home Assistant and add-ons, creating/restoring snapshots, and more. (See [Home Assistant via Command Line](https://www.home-assistant.io/hassio/commandline/) for further info). The Terminal & SSH add-on does *not* provide access to the underlying host file system.
|
||||
|
||||
To use the add-on, enter a password or public key on its configuration page, then save and start the add-on.
|
||||
To use the add-on, enter a password or public key on its configuration page, then save and start the add-on.
|
||||
|
||||
The Terminal & SSH add-on also provides a web terminal which allows you to access a terminal via the Home Assistant user interface. In order to access from an ssh client, a port needs to be entered in the network section of the add-on's configuration page.
|
||||
|
||||
@ -49,7 +49,7 @@ The Terminal & SSH add-on also provides a web terminal which allows you to acces
|
||||
|
||||
The Visual Studio Code add-on provides access through a feature packed web-based version of the Visual Studio Code editor and currently only supports AMD64 and aarch64/ARM64 machines. This add-on can be installed in the add-on store from the Community add-on repository. The add-on also provides access to the Home Assistant Command Line Interface (CLI) using VSC's built in terminal, which allows for checking logs, stopping and starting Home Assistant and add-ons, creating/restoring snapshots, and more. (See [Home Assistant via Command Line](https://www.home-assistant.io/hassio/commandline/) for further info).
|
||||
|
||||
There is no configuration required for editing files within your `/config` directory. In order to enable access to other directories, it is necessary to edit the add-on's configuration from its configuration tab. See the add-on documentation for details.
|
||||
There is no configuration required for editing files within your `/config` directory. In order to enable access to other directories, it is necessary to edit the add-on's configuration from its configuration tab. See the add-on documentation for details.
|
||||
|
||||
---
|
||||
|
||||
@ -57,4 +57,4 @@ There is no configuration required for editing files within your `/config` direc
|
||||
|
||||
A more basic and light weight alternative to Visual Studio Code, the File Editor add-on provides access through Hass-Configurator, which is a web-based filesystem-browser and text-editor. YAML files are automatically checked for syntax errors while editing. This add-on can be installed via the add-on store from the official add-on repository.
|
||||
|
||||
There is no configuration required for editing files within your `/config` directory. In order to enable access to further directories, editing the add-on configuration is required. See the add-on documentation for details.
|
||||
There is no configuration required for editing files within your `/config` directory. In order to enable access to further directories, editing the add-on configuration is required. See the add-on documentation for details.
|
||||
|
||||
@ -22,7 +22,7 @@ The steps would be:
|
||||
|
||||
If you are using the built-in firewall, you must also add the port 8123 to allowed list. This can be found in "Control Panel -> Security" and then the Firewall tab. Click "Edit Rules" besides the Firewall Profile dropdown box. Create a new rule and select "Custom" for Ports and add 8123. Edit Source IP if you like or leave it at default "All". Action should stay at "Allow".
|
||||
|
||||
To use a Z-Wave USB stick for Z-Wave control, the HA Docker container needs extra configuration to access to the USB stick. While there are multiple ways to do this, the least privileged way of granting access can only be performed via the Terminal, at the time of writing. See this page for configuring Terminal acces to your Synology NAS:
|
||||
To use a Z-Wave USB stick for Z-Wave control, the HA Docker container needs extra configuration to access to the USB stick. While there are multiple ways to do this, the least privileged way of granting access can only be performed via the Terminal, at the time of writing. See this page for configuring Terminal access to your Synology NAS:
|
||||
|
||||
<https://www.synology.com/en-global/knowledgebase/DSM/help/DSM/AdminCenter/system_terminal>
|
||||
|
||||
|
||||
@ -4,11 +4,11 @@
|
||||
content: |
|
||||
|
||||
```bash
|
||||
docker run --init -d \
|
||||
docker run -d \
|
||||
--name homeassistant \
|
||||
--privileged \
|
||||
--restart=unless-stopped \
|
||||
-v /etc/localtime:/etc/localtime:ro \
|
||||
-e TZ=MY_TIME_ZONE \
|
||||
-v /PATH_TO_YOUR_CONFIG:/config \
|
||||
--network=host \
|
||||
{{ include.image | default: site.installation.container.base }}:{{ include.tag | default: 'stable' }}
|
||||
@ -34,12 +34,12 @@
|
||||
|
||||
```bash
|
||||
# finally, start a new one
|
||||
docker run --init -d \
|
||||
docker run -d \
|
||||
--name homeassistant \
|
||||
--restart=unless-stopped \
|
||||
--privileged \
|
||||
-e TZ=MY_TIME_ZONE \
|
||||
-v /PATH_TO_YOUR_CONFIG:/config \
|
||||
-v /etc/localtime:/etc/localtime:ro \
|
||||
--network=host \
|
||||
{{ include.image | default: site.installation.container.base }}:{{ include.tag | default: 'stable' }}
|
||||
```
|
||||
|
||||
@ -207,7 +207,7 @@ _All these can be extended if your usage calls for more resources._
|
||||
|
||||
- title: VMware ESXi/vSphere
|
||||
content: |
|
||||
Use the “E1001” or “E1001E” virtual network adapater. There are confirmed mDNS/Multicast discovery issues when using VMware’s “VMXnet3” virtual network adapter.
|
||||
Use the “E1001” or “E1001E” virtual network adapter. There are confirmed mDNS/Multicast discovery issues when using VMware’s “VMXnet3” virtual network adapter.
|
||||
{% endif %}
|
||||
{% if page.installation_type == 'windows' %}
|
||||
- title: Hyper-V
|
||||
|
||||
@ -104,7 +104,7 @@ device_class:
|
||||
|
||||
## Light
|
||||
|
||||
The `ads` light platform allows you to control your connecte ADS lights.
|
||||
The `ads` light platform allows you to control your connected ADS lights.
|
||||
|
||||
To use your ADS device, you first have to set up your [ADS hub](#configuration) and then add the following to your `configuration.yaml`
|
||||
file:
|
||||
|
||||
@ -11,7 +11,7 @@ ha_domain: alert
|
||||
|
||||
The `alert` integration is designed to notify you when problematic issues arise.
|
||||
For example, if the garage door is left open, the `alert` integration can be used
|
||||
remind you of this by sending you repeating notifications at customizable
|
||||
to remind you of this by sending you repeating notifications at customizable
|
||||
intervals. This is also used for low battery sensors,
|
||||
water leak sensors, or any condition that may need your attention.
|
||||
|
||||
@ -27,7 +27,7 @@ State | Description
|
||||
|
||||
### Basic Example
|
||||
|
||||
The `alert` integration makes use of any of the `notifications` integrations. To
|
||||
The `alert` integration makes use of any of the `notification` integrations. To
|
||||
setup the `alert` integration, first, you must setup a `notification` integration.
|
||||
Then, add the following to your configuration file:
|
||||
|
||||
|
||||
@ -86,12 +86,12 @@ home_mode_name:
|
||||
required: false
|
||||
type: string
|
||||
away_mode_name:
|
||||
description: "Arlo base station does not have a built-in away mode. You can map one of your custom modes to Home Assistant's away mode by setting the name of the custom mode in this configuration variable. The name of the custom mode should match eactly as you set it up in the Arlo app."
|
||||
description: "Arlo base station does not have a built-in away mode. You can map one of your custom modes to Home Assistant's away mode by setting the name of the custom mode in this configuration variable. The name of the custom mode should match exactly as you set it up in the Arlo app."
|
||||
required: false
|
||||
type: string
|
||||
default: "`Armed` mode in Arlo"
|
||||
night_mode_name:
|
||||
description: "Arlo base station does not have a built-in night mode. You can map one of your custom modes to Home Assistant's night mode by setting the name of the custom mode in this configuration variable. The name of the custom mode should match eactly as you set it up in the Arlo app."
|
||||
description: "Arlo base station does not have a built-in night mode. You can map one of your custom modes to Home Assistant's night mode by setting the name of the custom mode in this configuration variable. The name of the custom mode should match exactly as you set it up in the Arlo app."
|
||||
required: false
|
||||
type: string
|
||||
default: "`Armed` mode in Arlo"
|
||||
|
||||
@ -57,7 +57,7 @@ This integration supports the following services (see [Climate](/integrations/cl
|
||||
- `boost` enable fireplace mode
|
||||
|
||||
<div class='note'>
|
||||
`HVAC mode Auto` (Weather based) should not be confused with `Preset mode Auto` (Sheduled, thermostat mode).
|
||||
`HVAC mode Auto` (Weather based) should not be confused with `Preset mode Auto` (Scheduled, thermostat mode).
|
||||
Currently selection of custom timeframes in Extend, Away and boost modes is not supported. The default settings can be changed on the device.
|
||||
</div>
|
||||
|
||||
|
||||
@ -50,7 +50,7 @@ Please note that each camera reports two different states: one as `sensor.blink_
|
||||
|
||||
## Services
|
||||
|
||||
Any sequential calls to services relating to blink should have a minimum of a 5 second delay in between them to prevent the calls fro being throttled and ignored.
|
||||
Any sequential calls to services relating to blink should have a minimum of a 5 second delay in between them to prevent the calls from being throttled and ignored.
|
||||
|
||||
### `blink.blink_update`
|
||||
|
||||
|
||||
@ -43,7 +43,9 @@ device_id:
|
||||
default: "`-1` (The first available Bluetooth adapter)"
|
||||
{% endconfiguration %}
|
||||
|
||||
In some cases it can be that your device is not discovered. In that case let your phone scan for Bluetooth devices while you restart Home Assistant. Just hit `Scan` on your phone all the time until Home Assistant is fully restarted and the device should appear in `known_devices.yaml`.
|
||||
In some cases it can be that your device is not discovered. In that case let your phone scan for Bluetooth devices while you restart Home Assistant. Just hit `Scan` on your phone all the time (or keep the Bluetooth device view open on an iOS device) until Home Assistant is fully restarted and the device should appear in `known_devices.yaml`.
|
||||
|
||||
The integration will try to create an entity using the device name that is detected. If such an entity already exists (for example because you are already using the [Companion App](https://companion.home-assistant.io/) for this device) no entity will be created and the log file will show an error that the `The see service is not supported for this entity device_tracker.device` (as it is not a `device_tracker` entity). You can rename the other conflicting entity, next time the device is detected a new entity with the same name will be created.
|
||||
|
||||
For additional configuration variables check the [Device tracker page](/integrations/device_tracker/).
|
||||
|
||||
|
||||
@ -64,7 +64,7 @@ oversampling_humidity:
|
||||
default: 1
|
||||
type: integer
|
||||
filter_mode:
|
||||
description: IIR filter coeficient as described in the sensor datasheet.
|
||||
description: IIR filter coefficient as described in the sensor datasheet.
|
||||
required: false
|
||||
default: 0
|
||||
type: integer
|
||||
|
||||
@ -32,14 +32,14 @@ Ignore CEC:
|
||||
|
||||
## Home Assistant Cast
|
||||
|
||||
Home Assistant has its own Cast application to show the Home Assistant UI on any Chromecast device. You can use it by adding the [Cast entity row](/lovelace/entities/#cast) to your Lovelace UI, or by calling the `cast.show_lovelace_view` service. The service takes the path of a Lovelace view and an entity ID of a Cast device to show the view on. A `path` has to be defined in your Lovelace YAML for each view, as outlined in the [views documentation](/lovelace/views/#path). The `dashboard_path` is the part of the Lovelace UI URL that follows the defined `base_url` Typically "lovelace". The following is a full configuration for a script that starts casting the `downstairs` tab of the `lovelace-cast` path (note that `entity_id` is specified under `data` and not for the service call):
|
||||
Home Assistant has its own Cast application to show the Home Assistant UI on any Chromecast device. You can use it by adding the [Cast entity row](/lovelace/entities/#cast) to your Lovelace UI, or by calling the `cast.show_lovelace_view` service. The service takes the path of a Lovelace view and an entity ID of a Cast device to show the view on. A `path` has to be defined in your Lovelace YAML for each view, as outlined in the [views documentation](/lovelace/views/#path). The `dashboard_path` is the part of the Lovelace UI URL that follows the defined `base_url`, typically "lovelace". The following is a full configuration for a script that starts casting the `downstairs` tab of the `lovelace-cast` path (note that `entity_id` is specified under `data` and not for the service call):
|
||||
|
||||
```yaml
|
||||
cast_downstairs_on_kitchen:
|
||||
alias: "Show Downstairs on kitchen"
|
||||
sequence:
|
||||
- data:
|
||||
dashboard_path: lovelace
|
||||
dashboard_path: lovelace-cast
|
||||
entity_id: media_player.kitchen
|
||||
view_path: downstairs
|
||||
service: cast.show_lovelace_view
|
||||
@ -280,7 +280,7 @@ Example values to cast [BBC Radio 1](https://www.bbc.co.uk/sounds/play/live:bbc_
|
||||
|
||||
This app doesn't retrieve its own metadata, so if you want the cast interface or media player card to show titles and/or images you will have to provide the data yourself. See the examples below.
|
||||
|
||||
Note: Media ID is NOT the 8 digit alpha-numeric in the URL, it can be found by right-clicking the playing video. E.g., [this episode](https://www.bbc.co.uk/iplayer/episode/b09w7fd9/bitz-bob-series-1-1-castle-makeover) shows:
|
||||
Note: Media ID is NOT the 8 digit alphanumeric in the URL, it can be found by right-clicking the playing video. E.g., [this episode](https://www.bbc.co.uk/iplayer/episode/b09w7fd9/bitz-bob-series-1-1-castle-makeover) shows:
|
||||
|
||||
2908kbps | dash (mf_cloudfront_dash_https)
|
||||
b09w70r2 | 960x540
|
||||
|
||||
@ -26,7 +26,7 @@ This integration is by default enabled, unless you've disabled or removed the [`
|
||||
cloud:
|
||||
```
|
||||
|
||||
Documentation of further configuration possibilites are located at [NabuCasa](https://www.nabucasa.com/config/)
|
||||
Documentation of further configuration possibilities are located at [NabuCasa](https://www.nabucasa.com/config/)
|
||||
|
||||
Once activated, go to the configuration panel in Home Assistant and create an account and log in. If you are not seeing the **Configuration** panel, make sure you have the following option enabled in your `configuration.yaml` file.
|
||||
|
||||
|
||||
@ -554,7 +554,7 @@ cover:
|
||||
{% set tilt_value = min(max((tilt + movement), tilt_min), max) %}
|
||||
|
||||
{
|
||||
"postition": value,
|
||||
"position": value,
|
||||
"pos": position,
|
||||
"tilt": tilt,
|
||||
"tilt_value": tilt_value,
|
||||
|
||||
@ -12,7 +12,7 @@ ha_platforms:
|
||||
- sensor
|
||||
---
|
||||
|
||||
The `cups` sensor platform is using the open source printing system [CUPS](https://www.cups.org/) to show details about your printers, including the ink levels. It can obtain the informations using a CUPS server or communicating directly with the printer with the Internet Printing Protocol.
|
||||
The `cups` sensor platform is using the open source printing system [CUPS](https://www.cups.org/) to show details about your printers, including the ink levels. It can obtain the information using a CUPS server or communicating directly with the printer with the Internet Printing Protocol.
|
||||
|
||||
## Setup
|
||||
|
||||
|
||||
@ -42,7 +42,7 @@ host:
|
||||
|
||||
The following binary sensor is supported.
|
||||
|
||||
- **Bypass active:** Indicator if heat recovery is currrently bypassed.
|
||||
- **Bypass active:** Indicator if heat recovery is currently bypassed.
|
||||
|
||||
## Sensor
|
||||
|
||||
@ -57,7 +57,7 @@ The following sensors are supported.
|
||||
- **Fan step:** Fan step.
|
||||
- **Exhaust fan speed:** Exhausted fan speed.
|
||||
- **Supply fan speed:** Supply fan speed.
|
||||
- **Dial battery:** Dial bettery level in percent.
|
||||
- **Dial battery:** Dial battery level in percent.
|
||||
|
||||
## Switch
|
||||
|
||||
|
||||
@ -21,6 +21,7 @@ Home Assistant can discover and automatically configure [zeroconf](https://en.wi
|
||||
* [Linn / Openhome](/integrations/openhome)
|
||||
* [Logitech Harmony Hub](/integrations/harmony)
|
||||
* [Logitech Media Server (Squeezebox)](/integrations/squeezebox)
|
||||
* [Nanoleaf](/integrations/nanoleaf)
|
||||
* [NETGEAR routers](/integrations/netgear)
|
||||
* [Philips Hue](/integrations/hue)
|
||||
* [SABnzbd downloader](/integrations/sabnzbd)
|
||||
@ -75,6 +76,7 @@ Valid values for ignore are:
|
||||
* `frontier_silicon`: Frontier Silicon internet radios
|
||||
* `harmony`: Logitech Harmony Hub
|
||||
* `logitech_mediaserver`: Logitech Media Server (Squeezebox)
|
||||
* `nanoleaf_aurora`: Nanoleaf
|
||||
* `netgear_router`: NETGEAR routers
|
||||
* `octoprint`: Octoprint
|
||||
* `openhome`: Linn / Openhome
|
||||
|
||||
@ -145,7 +145,7 @@ sender_id:
|
||||
required: true
|
||||
type: list
|
||||
name:
|
||||
description: An identifier for the Ligh in the frontend.
|
||||
description: An identifier for the light in the frontend.
|
||||
required: false
|
||||
default: EnOcean Light
|
||||
type: string
|
||||
|
||||
@ -21,7 +21,7 @@ Please visit the [eyezon website](http://www.eyezon.com/) for further informatio
|
||||
There is currently support for the following device types within Home Assistant:
|
||||
|
||||
- Binary Sensor: Reports on zone status (Check the [type/class](/integrations/binary_sensor/#device-class) list for a possible visualization of your zone.)
|
||||
- Sensor: Emulates an alpha-numeric keypad attached to the alarm panel
|
||||
- Sensor: Emulates an alphanumeric keypad attached to the alarm panel
|
||||
- Alarm Control Panel: Reports on partition status, and can be used to arm/disarm the system
|
||||
|
||||
This is a fully event-based component. Any event sent by the Envisalink device will be immediately reflected within Home Assistant.
|
||||
|
||||
@ -55,7 +55,7 @@ accounts:
|
||||
type: list
|
||||
keys:
|
||||
account:
|
||||
description: The IBAN of the blance account.
|
||||
description: The IBAN of the balance account.
|
||||
required: true
|
||||
type: string
|
||||
name:
|
||||
|
||||
@ -70,7 +70,7 @@ sleep_tune:
|
||||
required: false
|
||||
type: float
|
||||
sampling_interval:
|
||||
description: Sampling interval in millseconds sent to Firmata. Most Firmata sketches will ignore any interval less than 10 milliseconds.
|
||||
description: Sampling interval in milliseconds sent to Firmata. Most Firmata sketches will ignore any interval less than 10 milliseconds.
|
||||
required: false
|
||||
type: integer
|
||||
switches:
|
||||
|
||||
@ -172,7 +172,7 @@ The Flux LED light offers a number of effects which are not included in other li
|
||||
| `random` | Chooses a random color by selecting random values for R, G, and B. |
|
||||
| `custom` | Custom effect (if defined, see below). |
|
||||
|
||||
Users can define their own custom effect. It consists of three parameters: a list of 1 to 16 colors, speed and type of transition. The controller will transition between the colors in a loop, with sepcified transition and speed. Here is an example of a custom effect that will quickly flash red, yellow, green, cyan, blue, magenta in a loop:
|
||||
Users can define their own custom effect. It consists of three parameters: a list of 1 to 16 colors, speed and type of transition. The controller will transition between the colors in a loop, with specified transition and speed. Here is an example of a custom effect that will quickly flash red, yellow, green, cyan, blue, magenta in a loop:
|
||||
|
||||
```yaml
|
||||
light:
|
||||
|
||||
@ -61,8 +61,8 @@ To use Google Assistant, your Home Assistant configuration has to be [externally
|
||||
3. Select the `Develop` tab at the top of the page, then in the upper right hand corner select the `Test` button to generate the draft version Test App. If you don't see this option, go to the `Test` tab instead, click on the `Settings` button in the top right below the header, and ensure `On device testing` is enabled (if it isn't, enable it).
|
||||
4. Add the `google_assistant` integration configuration to your `configuration.yaml` file and restart Home Assistant following the [configuration guide](#configuration) below.
|
||||
5. Add services in the Google Home App (Note that app versions may be slightly different.)
|
||||
1. Open the Google Home app and go to `Settings`.
|
||||
2. Click `Add...`, `+ Set up or add`, `+ Set up device`, and click `Have something already setup?`. You should have `[test] your app name` listed under 'Add new'. Selecting that should lead you to a browser to login your Home Assistant instance, then redirect back to a screen where you can set rooms and nicknames for your devices if you wish.
|
||||
1. Open the Google Home app.
|
||||
2. Click the `+` button on the top left corner, click `Set up device`, in the "Set up a device" screen click "Works with Google". You should have `[test] <Action Name>` listed under 'Add new'. Selecting that should lead you to a browser to login your Home Assistant instance, then redirect back to a screen where you can set rooms and nicknames for your devices if you wish.
|
||||
|
||||
<div class='note'>
|
||||
|
||||
@ -209,7 +209,7 @@ Currently, the following domains are available to be used with Google Assistant,
|
||||
- scene (on)
|
||||
- script (on)
|
||||
- switch (on/off)
|
||||
- fan (on/off/speed)
|
||||
- fan (on/off/speed percentage/preset mode)
|
||||
- light (on/off/brightness/rgb color/color temp)
|
||||
- lock
|
||||
- cover (on/off/set position)
|
||||
|
||||
@ -23,6 +23,10 @@ A quota can be set against the API to avoid exceeding the free credit amount. Se
|
||||
|
||||
{% include integrations/config_flow.md %}
|
||||
|
||||
## Manual Polling
|
||||
|
||||
Using automatic polling can lead to calls that exceed your API limit, especially when you are tracking multiple travel times using the same API key. To use more granular polling, disable automated polling in your config entry's System Options. To manually trigger a polling request, call the [`homeassistant.update_entity` service](/integrations/homeassistant/#service-homeassistantupdate_entity) as needed, either manually or via automations.
|
||||
|
||||
## Dynamic Configuration
|
||||
|
||||
Tracking can be setup to track entities of type `device_tracker`, `zone`, `sensor` and `person`. If an entity is placed in the Origin or Destination then every 5 minutes when the platform updates it will use the latest location of that entity.
|
||||
|
||||
@ -84,7 +84,7 @@ media_content_id: "Awesome Music"
|
||||
|
||||
#### Play Quick Select
|
||||
|
||||
You can play a HEOS Quick Select by nubmer or name with the `media_player.play_media` service. Example service data payload:
|
||||
You can play a HEOS Quick Select by number or name with the `media_player.play_media` service. Example service data payload:
|
||||
|
||||
```yaml
|
||||
entity_id: media_player.office
|
||||
|
||||
@ -21,7 +21,7 @@ You need to register for an API key (REST & XYZ HUB API/CLI) by following the in
|
||||
|
||||
HERE offers a Freemium Plan which includes 250,000 free Transactions per month. For the Routing API, one transaction equals one request with one starting point (no multi stop). More information can be found [here](https://developer.here.com/faqs#payment-subscription)
|
||||
|
||||
By default HERE will deactivate your account if you exceed the free Transaction limit for the month. You can add payment details to reenable your account as described [here](https://developer.here.com/faqs)
|
||||
By default HERE will deactivate your account if you exceed the free Transaction limit for the month. You can add payment details to re-enable your account as described [here](https://developer.here.com/faqs)
|
||||
|
||||
### Migrate from app_code to api_key
|
||||
|
||||
|
||||
@ -468,7 +468,7 @@ The following home hubs have been reported to have trouble with a large number o
|
||||
|
||||
1. Delete the `HomeKit` integration in the **{% my integrations %}** screen.
|
||||
2. **Restart** Home Assistant.
|
||||
3. The configuration will be automaticlly reimported from YAML.
|
||||
3. The configuration will be automatically reimported from YAML.
|
||||
4. [Pair the bridge or accessory](#setup).
|
||||
|
||||
### Resetting when created via the **Integrations** screen
|
||||
|
||||
@ -475,11 +475,11 @@ automation:
|
||||
|
||||
The important part is the `sensor.time` entity (from time_date component). This will update the binary sensor on every change of the sensor and every minute. If the Homematic sensor does not send any updates anymore, the `sensor.time` will set the binary sensor to `off` 10 minutes after the last sensor update. This will trigger the automation.
|
||||
|
||||
- If you have a CCU you can also create a system variable on the CCU, which stores its last reboot time. Since Home Assistant can still refresh system variables from the CCU (even after a reboot) this is another option to call *homematic.reconnect*. Even though this option might look preferrable to many since it does not rely on a sensor, **it is less fail-safe** than checking for updates of a sensor. Since the variable on the CCU is only changed on boot, any problem that causes the connection between Home Assistant and the CCU to break but will not result in a reboot will not be detected (eg. in case of networking issues). This is how this can be done:
|
||||
- If you have a CCU you can also create a system variable on the CCU, which stores its last reboot time. Since Home Assistant can still refresh system variables from the CCU (even after a reboot) this is another option to call *homematic.reconnect*. Even though this option might look preferable to many since it does not rely on a sensor, **it is less fail-safe** than checking for updates of a sensor. Since the variable on the CCU is only changed on boot, any problem that causes the connection between Home Assistant and the CCU to break but will not result in a reboot will not be detected (eg. in case of networking issues). This is how this can be done:
|
||||
|
||||
1. Create a string variable **V_Last_Reboot** on the CCU
|
||||
|
||||
2. Creata a new programm on the CCU **without any conditions**, which executes the following *HM-Script* with a delay of 30 seconds. The Script needs to be implemented within the section `Activity: Then`.
|
||||
2. Create a new program on the CCU **without any conditions**, which executes the following *HM-Script* with a delay of 30 seconds. The script needs to be implemented within the section `Activity: Then`.
|
||||
|
||||
```javascript
|
||||
var obj = dom.GetObject("V_Last_Reboot");
|
||||
|
||||
@ -105,13 +105,16 @@ http:
|
||||
|
||||
The [Set up encryption using Let's Encrypt](/blog/2015/12/13/setup-encryption-using-lets-encrypt/) blog post gives you details about the encryption of your traffic using free certificates from [Let's Encrypt](https://letsencrypt.org/).
|
||||
|
||||
## Reverse proxies
|
||||
|
||||
When using a reverse proxy, you will need to enable the `use_x_forwarded_for` and `trusted_proxies` options. Requests from reverse proxies will be blocked if these options are not set.
|
||||
|
||||
```yaml
|
||||
http:
|
||||
use_x_forwarded_for: true
|
||||
trusted_proxies:
|
||||
- 172.30.33.0/24 # Add the IP address of the proxy server
|
||||
- 10.0.0.200 # Add the IP address of the proxy server
|
||||
- 172.30.33.0/24 # You may also provide the subnet mask
|
||||
```
|
||||
|
||||
## APIs
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: HVV Departures
|
||||
description: Display the departures of busses, trains and ferries in Hamburg within Home Assistant.
|
||||
description: Display the departures of buses, trains and ferries in Hamburg within Home Assistant.
|
||||
ha_category:
|
||||
- Transport
|
||||
ha_iot_class: Cloud Polling
|
||||
@ -14,7 +14,7 @@ ha_platforms:
|
||||
- sensor
|
||||
---
|
||||
|
||||
The `hvv_departures` sensor will display the departures of busses, trains and ferries in Hamburg.
|
||||
The `hvv_departures` sensor will display the departures of buses, trains and ferries in Hamburg.
|
||||
|
||||
{% include integrations/config_flow.md %}
|
||||
|
||||
|
||||
@ -73,7 +73,7 @@ monitored_conditions:
|
||||
{% endconfiguration %}
|
||||
|
||||
<div class='note warning'>
|
||||
The Hydrawise API removed the ability to read the rain sensor status. Therefore it is no longer suppored by the Hydrawise integration to Home Assistant.
|
||||
The Hydrawise API removed the ability to read the rain sensor status. Therefore it is no longer supported by the Hydrawise integration to Home Assistant.
|
||||
</div>
|
||||
|
||||
## Sensor
|
||||
|
||||
@ -60,7 +60,7 @@ Sensors available in the library:
|
||||
| wem3080_voltage | V | Voltage. |
|
||||
| wem3080_current | A | current. |
|
||||
| wem3080_power | W | active power. |
|
||||
| wem3080_importenergy | kWh | Energy consumption from gird |
|
||||
| wem3080_importenergy | kWh | Energy consumption from grid |
|
||||
| wem3080_exportgrid | kWh | Energy export to grid |
|
||||
|
||||
### Three-phase energy meter (WEM3080T)
|
||||
|
||||
@ -33,9 +33,23 @@ You may receive an email and a notification from Apple saying that someone has l
|
||||
For the notification, press "Allow", then "OK".
|
||||
</div>
|
||||
|
||||
To prevent excessive battery drainage, a dynamic interval is used for each individual device instead of a fixed interval for all devices linked to one account. The dynamic interval is based on the current zone of a device, the distance towards home and the battery level of the device.
|
||||
|
||||
## Two Factor Authentication
|
||||
|
||||
If two-step authentication is enabled for your iCloud account, some time after Home Assistant startup the integration will ask to enter the verification code you receive on your device via a notification in the Home Assistant UI. The duration of this authentication is determined by Apple, so you will need to verify your account every now and then.
|
||||
|
||||
To prevent excessive battery drainage, a dynamic interval is used for each individual device instead of a fixed interval for all devices linked to one account. The dynamic interval is based on the current zone of a device, the distance towards home and the battery level of the device.
|
||||
### App Specific Passwords
|
||||
Apple allows you to provide an [App Specific Password](https://support.apple.com/en-gb/HT204397), which **don't require two factor authentication**, and one could argue more secure than storing your iCloud password within Home Assistant.
|
||||
#### How to generate an app-specific password
|
||||
|
||||
1. Sign in to your [Apple ID account page](https://appleid.apple.com/account/home).
|
||||
2. In the Security section, click Generate Password below App-Specific Passwords.
|
||||
3. Follow the steps on your screen.
|
||||
|
||||
After you generate your app-specific password, enter or paste it into the password field of the integration.
|
||||
|
||||
Any time you change or reset your primary Apple ID password, all your app-specific passwords are revoked automatically to protect the security of your account. You'll need to generate new app-specific passwords for any apps that you want to continue using.
|
||||
|
||||
## In case of troubleshooting
|
||||
|
||||
|
||||
@ -17,7 +17,7 @@ The `iqvia` sensor platform collects and displays allergy, asthma and disease
|
||||
information (based on a U.S. ZIP code) from [IQVIA](https://www.iqvia.com/).
|
||||
Data measured includes:
|
||||
|
||||
* Indicies for allergies, asthma and cold/flu indices
|
||||
* Indices for allergies, asthma and cold/flu indices
|
||||
* Trends
|
||||
* Current outlook
|
||||
* more!
|
||||
|
||||
@ -56,7 +56,7 @@ device_names:
|
||||
required: false
|
||||
type: string
|
||||
name:
|
||||
description: The name parameter is optional but needed if you want to use multiple notification platforms. The platform will be exposed as service `notify.<name>`. The name will defailt to `notify` if not supplied. See the [Notifications Component](/integrations/notify) for more details.
|
||||
description: The name parameter is optional but needed if you want to use multiple notification platforms. The platform will be exposed as service `notify.<name>`. The name will default to `notify` if not supplied. See the [Notifications Component](/integrations/notify) for more details.
|
||||
required: false
|
||||
type: string
|
||||
{% endconfiguration %}
|
||||
|
||||
@ -15,7 +15,7 @@ ha_platforms:
|
||||
|
||||
The `kaiterra` integration allows you to view the readings from your Laser Egg or Sensedge device using the [Kaiterra REST API](https://www.kaiterra.com/dev/).
|
||||
|
||||
To use the integration, you need to get the API key by signing up at [Kaiterra dashboard](https://dashboard.kaiterra.cn/), registring the device and create the key under `Settings -> Profile -> Developer`.
|
||||
To use the integration, you need to get the API key by signing up at [Kaiterra dashboard](https://dashboard.kaiterra.cn/), registering the device and create the key under `Settings -> Profile -> Developer`.
|
||||
|
||||
## Configuration
|
||||
|
||||
|
||||
@ -97,7 +97,7 @@ automation:
|
||||
entity_id: light.all
|
||||
```
|
||||
|
||||
`device_descriptor` or `device_name` may be specificed in the trigger so the automation will be fired only for that keyboard. This is especially useful if you wish to use several Bluetooth remotes to control different devices. Omit them to ensure the same key triggers the automation for all keyboards/remotes.
|
||||
`device_descriptor` or `device_name` may be specified in the trigger so the automation will be fired only for that keyboard. This is especially useful if you wish to use several Bluetooth remotes to control different devices. Omit them to ensure the same key triggers the automation for all keyboards/remotes.
|
||||
|
||||
## Disconnections
|
||||
|
||||
|
||||
@ -59,7 +59,7 @@ Spoken messages is the default method (`speak`). You just invoke the `notify` se
|
||||
}
|
||||
```
|
||||
|
||||
The second method is to play notifications (`alarm`). There are 4 build-in sounds (`chime`, `doorbell`, `alarm` and `siren`).
|
||||
The second method is to play notifications (`alarm`). There are 4 built-in sounds (`chime`, `doorbell`, `alarm` and `siren`).
|
||||
|
||||
```json
|
||||
{
|
||||
|
||||
@ -627,7 +627,7 @@ data:
|
||||
```
|
||||
|
||||
<div class='note'>
|
||||
Ensure that the LCN module is configured properly to provide acces to the defined variable.
|
||||
Ensure that the LCN module is configured properly to provide access to the defined variable.
|
||||
Otherwise the module might show unexpected behaviors or return error messages.
|
||||
</div>
|
||||
|
||||
|
||||
@ -22,7 +22,7 @@ profile,color_x,color_y,brightness,transition
|
||||
|
||||
The field transition is optional and can be omitted.
|
||||
|
||||
The `.default` suffix should be added to the entity identifier of each light to define a default value, e.g., for `light.ceiling_2` the `profile` field is `light.ceiling_2.default`. To define a default for all lights, the identifier `group.all_lights.default` can be used. Individual settings always supercede the `all_lights` default setting.
|
||||
The `.default` suffix should be added to the entity identifier of each light to define a default value, e.g., for `light.ceiling_2` the `profile` field is `light.ceiling_2.default`. To define a default for all lights, the identifier `group.all_lights.default` can be used. Individual settings always supersede the `all_lights` default setting.
|
||||
|
||||
<div class='note'>
|
||||
|
||||
|
||||
@ -10,11 +10,11 @@ ha_platforms:
|
||||
- sensor
|
||||
---
|
||||
|
||||
The `magicseaweed` platform uses the [Magicseaweed Forecast API](https://magicseaweed.com/developer/forecast-api) as a source for surf forecasting data for the surf spots of your choice.
|
||||
The `magicseaweed` platform uses the [Magicseaweed Forecast API](https://magicseaweed.com/docs/developers/59/) as a source for surf forecasting data for the surf spots of your choice.
|
||||
|
||||
## Setup
|
||||
|
||||
You need an API key which is free but requires [registration](https://magicseaweed.com/developer/sign-up). Magicseaweed is limiting users of the API to 1 spot for the free plan.
|
||||
You need an API key which is free but requires [registration](https://magicseaweed.com/docs/developers/59/sign-up/9908/). Magicseaweed is limiting users of the API to 1 spot for the free plan.
|
||||
|
||||
## Configuration
|
||||
|
||||
@ -63,7 +63,7 @@ hours:
|
||||
12AM:
|
||||
description: Display forecast for 12AM.
|
||||
spot_id:
|
||||
description: ID of the surf spot. Details for getting spot id available at [Magicseaweed](https://magicseaweed.com/developer/forecast-api)
|
||||
description: ID of the surf spot. Details for getting spot id available at [Magicseaweed](https://magicseaweed.com/docs/developers/59/)
|
||||
required: true
|
||||
type: string
|
||||
monitored_conditions:
|
||||
@ -84,4 +84,4 @@ units:
|
||||
type: string
|
||||
{% endconfiguration %}
|
||||
|
||||
Details about the API are available in the [Magicseaweed documentation](https://magicseaweed.com/developer/forecast-api).
|
||||
Details about the API are available in the [Magicseaweed documentation](https://magicseaweed.com/docs/developers/59/).
|
||||
|
||||
@ -106,8 +106,8 @@ metadata:
|
||||
|
||||
Documentation:
|
||||
|
||||
- [Google Dev Documentaion MediaData](https://developers.google.com/cast/docs/reference/messages#MediaData)
|
||||
- [Google Dev Documentaion MediaInformation](https://developers.google.com/cast/docs/reference/web_receiver/cast.framework.messages.MediaInformation)
|
||||
- [Google Dev Documentation MediaData](https://developers.google.com/cast/docs/reference/messages#MediaData)
|
||||
- [Google Dev Documentation MediaInformation](https://developers.google.com/cast/docs/reference/web_receiver/cast.framework.messages.MediaInformation)
|
||||
|
||||
|
||||
Example of calling media_player service with title and image set:
|
||||
|
||||
@ -12,7 +12,7 @@ ha_platforms:
|
||||
- binary_sensor
|
||||
---
|
||||
|
||||
The `MeteoAlarm` platform allows one to watch for weather alerts in europe from [MeteoAlarm](https://www.meteoalarm.org) (EUMETNET). To use this binary sensor, you need the name of your country and the province name from [MeteoAlarm](https://www.meteoalarm.org). Please note that you need to write the exact details from the website with capitals.
|
||||
The `MeteoAlarm` platform allows one to watch for weather alerts in europe from [MeteoAlarm](https://www.meteoalarm.org) (EUMETNET). To use this binary sensor, you need the name of your country and the province name from [MeteoAlarm](https://feeds.meteoalarm.org). Please note that you need to write the exact country name (with hyphens) as at the end of the URL starting with: `https://feeds.meteoalarm.org/feeds/meteoalarm-legacy-atom-`.
|
||||
|
||||
The binary sensor state shows if applicable the warning message. The details are available as attribute.
|
||||
|
||||
|
||||
@ -21,6 +21,7 @@ Additionally the following brands have been reported to also work with this inte
|
||||
- [Motion Blinds](https://motion-blinds.com)
|
||||
- [Dooya](http://www.dooya.com/)
|
||||
- [Bloc Blinds](https://www.blocblinds.com/)
|
||||
- [Brel Home](https://www.brel-home.nl/)
|
||||
|
||||
{% include integrations/config_flow.md %}
|
||||
|
||||
|
||||
@ -54,7 +54,7 @@ name:
|
||||
|
||||
## Examples
|
||||
|
||||
Send a mesage to Mycroft by calling `notify.mycroft` service:
|
||||
Send a message to Mycroft by calling `notify.mycroft` service:
|
||||
|
||||
```yaml
|
||||
message: "Hey Mycroft. Turn on the office light. "
|
||||
|
||||
@ -125,7 +125,7 @@ Some information about the capabilities might be found on the [Neato Developer P
|
||||
|
||||
Try to restart the vacuum and wait about 5 minutes to see if it is no longer unavailable. If you are still having issues check the Neato app and make sure your robot is connected and working. If it is not then follow the steps in the app to reset your robot and give it the same name as before then restart Home Assistant.
|
||||
|
||||
### My robot is not deteced by Home Assistant
|
||||
### My robot is not detected by Home Assistant
|
||||
|
||||
Please check your logs if there are any warnings. When there is a message about your robot being offline, check if it is connected to the internet and available though the app. If there is a message about a bad response, try to reset this robot via your app.
|
||||
|
||||
|
||||
@ -35,6 +35,10 @@ There is currently support for the following device types within Home Assistant:
|
||||
This integration supports two Nest APIs. The SDM API is the new primary API that accepts new users. The Legacy Works With Nest API is not accepting new users, but the documentation still exists at the bottom of the page so existing users can keep using it.
|
||||
</div>
|
||||
|
||||
Google applies strict [Redirect URI validation
|
||||
rules](https://developers.google.com/identity/protocols/oauth2/web-server#uri-validation) to keep your login
|
||||
credentials secure. In practice, this means that you must access Home Assistant *over SSL* and a *public top-level domain*. See the documentation on [Securing](/docs/configuration/securing/) or [Troubleshooting](#troubleshooting), and note that you don't need actually need to enable remote access.
|
||||
|
||||
## Overview: Supported Devices
|
||||
|
||||
Home Assistant is integrated with the following devices through the SDM API:
|
||||
@ -182,7 +186,7 @@ project_id:
|
||||
required: false
|
||||
type: string
|
||||
subscriber_id:
|
||||
description: Full path for the Pub/sub Subscription ID used to receive events. This is required to use the SDM API. Enter this exactly as it appers under "Subscription name" in the [Pub/Sub console](https://console.cloud.google.com/cloudpubsub/subscription/list).
|
||||
description: Full path for the Pub/sub Subscription ID used to receive events. This is required to use the SDM API. Enter this exactly as it appears under "Subscription name" in the [Pub/Sub console](https://console.cloud.google.com/cloudpubsub/subscription/list).
|
||||
type: string
|
||||
required: false
|
||||
{% endconfiguration %}
|
||||
@ -247,8 +251,8 @@ everything, however, you can leave out any feature you do not wish to use with H
|
||||
domain (such as .com or .org)* or *must use a valid domain that is a valid top private domain*. This means that you
|
||||
may need to change the URL you use to access Home Assistant in order to access your devices.
|
||||
|
||||
- A convienent solution is to use [Nabu Casa](https://www.nabucasa.com/)
|
||||
- There are subtle rules for what types of URLs are allowed, namely that they must use a publicly known hostname, though your Home Assistant ports do not need to be exposed to the internet.
|
||||
- See [Securing](https://www.home-assistant.io/docs/configuration/securing/) Home Assistant for convient solutions e.g. [Nabu Casa](https://www.nabucasa.com/) or Duck DNS.
|
||||
- There are subtle [rules](https://developers.google.com/identity/protocols/oauth2/web-server#uri-validation) for what types of URLs are allowed, namely that they must use SSL and a publicly known hostname, though your Home Assistant ports do not need to be exposed to the internet.
|
||||
- You can use any publicly known hostname you own
|
||||
- As a hack, you can use hosts tricks to temporarily assign a public hostname to your Home Assistant IP address.
|
||||
|
||||
@ -275,13 +279,14 @@ logger:
|
||||
homeassistant.components.nest.climate_sdm: debug
|
||||
homeassistant.components.nest.camera_sdm: debug
|
||||
homeassistant.components.nest.sensor_sdm: debug
|
||||
homeassistant.helpers.config_entry_flow: debug
|
||||
homeassistant.helpers.config_entry_oauth2_flow: debug
|
||||
google_nest_sdm: debug
|
||||
google_nest_sdm.device: debug
|
||||
google_nest_sdm.device_manager: debug
|
||||
google_nest_sdm.google_nest_subscriber: debug
|
||||
google_nest_sdm.event: debug
|
||||
google.cloud.pubsub_v1: debug
|
||||
google.cloud.pubsub_v1.subscriber._protocol.streaming_pull_manager: debug
|
||||
```
|
||||
|
||||
## Camera
|
||||
|
||||
@ -55,7 +55,7 @@ show_on_map:
|
||||
type: boolean
|
||||
{% endconfiguration %}
|
||||
|
||||
## Health risk index explainations
|
||||
## Health risk index explanations
|
||||
|
||||
Under the attributes from a NILU station, there will be a `nilu pollution index`. This indicates how polluted the air is in the area around the sensor station. Following is a longer explanation of what the indexes mean.
|
||||
|
||||
@ -75,7 +75,7 @@ Health effects may occur in asthmatics and people with other respiratory disease
|
||||
|
||||
Sensitive groups in the population can have health effects. Respiratory irritation and discomfort may occur in healthy subjects. People with heart or respiratory distress should reduce outdoor activity and not stay in the most polluted areas.
|
||||
|
||||
Source: [Explainations in Norwegian](http://www.luftkvalitet.info/home/Varslingsklasser.aspx)
|
||||
Source: [Explanations in Norwegian](http://www.luftkvalitet.info/home/Varslingsklasser.aspx)
|
||||
|
||||
## Available areas
|
||||
|
||||
|
||||
@ -79,6 +79,10 @@ device:
|
||||
description: The name of the device.
|
||||
required: false
|
||||
type: string
|
||||
suggested_area:
|
||||
description: 'Suggest an area if the device isn’t in one yet.'
|
||||
required: false
|
||||
type: string
|
||||
sw_version:
|
||||
description: The firmware version of the device.
|
||||
required: false
|
||||
|
||||
@ -77,6 +77,6 @@ If your ONVIF camera supports PTZ, you will be able to pan, tilt or zoom your ca
|
||||
| `speed` | Speed coefficient. Sets how fast PTZ will be executed. Allowed values: floating point numbers, 0 to 1. Default : 0.5 |
|
||||
| `preset` | PTZ preset profile token. Sets the preset profile token which is executed with GotoPreset. |
|
||||
| `move_mode` | PTZ moving mode. Allowed values: `ContinuousMove`, `RelativeMove`, `AbsoluteMove`, `GotoPreset`, `Stop`. Default :`RelativeMove` |
|
||||
| `continuous_duration` | Set ContinuousMove delay in seconds before stoping the move. Allowed values: floating point numbers or integer. Default : 0.5 |
|
||||
| `continuous_duration` | Set ContinuousMove delay in seconds before stopping the move. Allowed values: floating point numbers or integer. Default : 0.5 |
|
||||
|
||||
If you are running into trouble with this sensor, please refer to the [Troubleshooting section](/integrations/ffmpeg/#troubleshooting).
|
||||
|
||||
@ -62,7 +62,7 @@ Also for sensors a list of raw values is exposed as `sensor_values` attribute, a
|
||||
in automations, if you know what particular values mean for your sensor.
|
||||
|
||||
It is suggested to make [scan_interval](/docs/configuration/platform_options/#scan-interval)
|
||||
(30 seconds by default) less or equal to `interval_lightify_status`, oherwise the latter won't work
|
||||
(30 seconds by default) less or equal to `interval_lightify_status`, otherwise the latter won't work
|
||||
as expected. Shorter `scan_interval` may improve synchronization speed between individual lights and
|
||||
groups. For example, if you turn on a group, all its lights may be updated to `on` immediately,
|
||||
without querying the bridge.
|
||||
|
||||
@ -22,7 +22,14 @@ ha_platforms:
|
||||
- switch
|
||||
---
|
||||
|
||||
This integration allows you to utilize OpenZWave's ozwdaemon to control a Z-Wave network over MQTT. If you're starting out with Z-Wave in Home Assistant, we recommend that you use [the Z-Wave JS integration](/integrations/zwave_js).
|
||||
This integration allows you to utilize OpenZWave's ozwdaemon to control a Z-Wave network over MQTT.
|
||||
|
||||
<div class='note warning'>
|
||||
|
||||
As of mid-2021 this integration, as well as the upstream ozwdaemon project, are not currently maintained. If you're starting out with Z-Wave in Home Assistant, we recommend that you use [the Z-Wave JS integration](/integrations/zwave_js).
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
## Requirements
|
||||
|
||||
|
||||
@ -57,7 +57,7 @@ Alternatively, you can manually configure a Plex server connection by selecting
|
||||
|
||||
**Verify SSL certificate**: Verify the SSL certificate of your Plex server. May be used if connecting with an IP or if using a self-signed certificate.
|
||||
|
||||
**Token**: A valid authorization token for your Plex server. If provided without 'Host', a connection URL will be retreived from Plex.
|
||||
**Token**: A valid authorization token for your Plex server. If provided without 'Host', a connection URL will be retrieved from Plex.
|
||||
|
||||
## Sensor
|
||||
|
||||
|
||||
@ -68,7 +68,7 @@ Each home configured in the Point mobile application will show up as a separate
|
||||
|
||||
<div class="note">
|
||||
|
||||
The Point only supports a Arm/Disarm action, so it is only `Arm Away` that is implememented.
|
||||
The Point only supports a Arm/Disarm action, so it is only `Arm Away` that is implemented.
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
@ -173,6 +173,23 @@ You can then configure Prometheus to fetch metrics from Home Assistant by adding
|
||||
- targets: ['HOSTNAME:8123']
|
||||
```
|
||||
|
||||
The format to configure the bearer token has changed in Prometheus 2.26, so if you have a newer version, you can use this configuration sample:
|
||||
|
||||
```yaml
|
||||
# Example Prometheus scrape_configs entry (For version 2.26+
|
||||
- job_name: "hass"
|
||||
scrape_interval: 60s
|
||||
metrics_path: /api/prometheus
|
||||
|
||||
# Long-Lived Access Token
|
||||
authorization:
|
||||
credentials: "your.longlived.token"
|
||||
|
||||
scheme: https
|
||||
static_configs:
|
||||
- targets: ['HOSTNAME:8123']
|
||||
```
|
||||
|
||||
When looking into the metrics on the Prometheus side, there will be:
|
||||
|
||||
- All Home Assistant domains, which can be easily found through the common **namespace** prefix, if defined.
|
||||
|
||||
@ -162,7 +162,7 @@ The sensor can filter the timetables by one or more routes, directions and types
|
||||
| `type` | Transport type |
|
||||
| `route` | Route code |
|
||||
| `direction` | Destination stop |
|
||||
| `final_stop` | Final stop (if departure doesn't go all the way to the destionation stop) |
|
||||
| `final_stop` | Final stop (if departure doesn't go all the way to the destination stop) |
|
||||
| `stop` | Departure stop |
|
||||
| `stop_id` | ID of departure stop |
|
||||
| `track` | Departure track (if available) |
|
||||
@ -180,6 +180,6 @@ The sensor can filter the timetables by one or more routes, directions and types
|
||||
| `type` | Transport type |
|
||||
| `route` | Route code |
|
||||
| `direction` | Destination stop |
|
||||
| `final_stop` | Final stop (if departure doesn't go all the way to the destionation stop) |
|
||||
| `final_stop` | Final stop (if departure doesn't go all the way to the destination stop) |
|
||||
| `stop` | Departure stop |
|
||||
| `track` | Departure track (if available) |
|
||||
|
||||
@ -94,7 +94,7 @@ This undoes a zone bypass. You can only unbypass a zone when the partitions it b
|
||||
| ---------------------- | -------- | ----------- |
|
||||
| `entity_id` | no | String or list of strings of entity_ids of zones. Use entity_id: all to target all zones. |
|
||||
|
||||
## Supported Plaforms:
|
||||
## Supported Platforms:
|
||||
|
||||
- [Alarm Control Panel](/integrations/alarm_control_panel/)
|
||||
- [Binary Sensor](/integrations/binary_sensor/)
|
||||
|
||||
@ -16,6 +16,7 @@ ha_domain: rituals_perfume_genie
|
||||
ha_platforms:
|
||||
- binary_sensor
|
||||
- number
|
||||
- select
|
||||
- sensor
|
||||
- switch
|
||||
ha_quality_scale: silver
|
||||
|
||||
@ -36,7 +36,7 @@ Roon uses a path based on the roon browser hierarchy to specify which media to p
|
||||
| -----------------------| -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| `entity_id` | yes | Target a specific media player. To target all media players, use `all`. |
|
||||
| `media_content_id` | no | A path to specify the media you want to play, see examples below. |
|
||||
| `media_content_type` | no | Only `music` is suppported |
|
||||
| `media_content_type` | no | Only `music` is supported |
|
||||
|
||||
For example to play the album Harvest by Neil Young you should set `media_content_id` to `Library/Artists/Neil Young/Harvest` and to play BBC Radio 4 you would set `media_content_id` to `My Live Radio/BBC Radio 4`
|
||||
|
||||
|
||||
@ -27,7 +27,7 @@ The module communicates via Satel's open TCP protocol published on their website
|
||||
|
||||
## Setup
|
||||
|
||||
Please note that **ETHM-1 module is currently not supported**: it does not provide functionality used by this extension. At the moment only ETHM-1 Plus module is supported. That might change in the future, but no promisses are given.
|
||||
Please note that **ETHM-1 module is currently not supported**: it does not provide functionality used by this extension. At the moment only ETHM-1 Plus module is supported. That might change in the future, but no promises are given.
|
||||
|
||||
The library currently doesn't support encrypted connection to your alarm, so you need **to turn off encryption for integration protocol**. In Polish: "koduj integracje" must be unchecked. You will find this setting in your DloadX program.
|
||||
|
||||
|
||||
@ -16,7 +16,7 @@ a limited set of selectable options for the entity.
|
||||
|
||||
### Services
|
||||
|
||||
The Number entities registers the following services:
|
||||
The Select entities registers the following services:
|
||||
|
||||
| Service | Data | Description |
|
||||
| ------- | ---- | ----------- |
|
||||
|
||||
@ -83,6 +83,10 @@ device:
|
||||
description: The name of the device.
|
||||
required: false
|
||||
type: string
|
||||
suggested_area:
|
||||
description: 'Suggest an area if the device isn’t in one yet.'
|
||||
required: false
|
||||
type: string
|
||||
sw_version:
|
||||
description: The firmware version of the device.
|
||||
required: false
|
||||
|
||||
@ -60,7 +60,7 @@ display_options:
|
||||
pressure:
|
||||
description: Pressure
|
||||
name:
|
||||
description: Change the name of te sensor, for in the frontend.
|
||||
description: Change the name of the sensor, for in the frontend.
|
||||
required: false
|
||||
type: string
|
||||
is_hat_attached:
|
||||
|
||||
@ -98,7 +98,7 @@ The SMA WebConnect module supports a wide variety of sensors, but not all of the
|
||||
| power_l2 | W | Power for phase 2 |
|
||||
| power_l3 | W | Power for phase 3 |
|
||||
|
||||
### Batery Inverter
|
||||
### Battery Inverter
|
||||
|
||||
| name | Unit | Description |
|
||||
| --- | --- | --- |
|
||||
|
||||
@ -27,5 +27,5 @@ Assistant.
|
||||
To prevent being automatically logged out of your SmartHab mobile app, you
|
||||
might want to create a secondary user in the app's settings and grant it
|
||||
access to your home. You can then configure the integration using this account's
|
||||
credentials. This is also more secure, as this user should be less priviledged.
|
||||
credentials. This is also more secure, as this user should be less privileged.
|
||||
</div>
|
||||
|
||||
@ -25,6 +25,8 @@ notify:
|
||||
recipient: "YOUR_RECIPIENT"
|
||||
```
|
||||
|
||||
Check your e-mail provider configuration or help pages to get the correct SMTP settings.
|
||||
|
||||
{% configuration %}
|
||||
name:
|
||||
description: Setting the optional parameter `name` allows multiple notifiers to be created. The notifier will bind to the service `notify.NOTIFIER_NAME`.
|
||||
@ -78,27 +80,7 @@ debug:
|
||||
default: false
|
||||
{% endconfiguration %}
|
||||
|
||||
A sample configuration entry for Google Mail.
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
notify:
|
||||
- name: "NOTIFIER_NAME"
|
||||
platform: smtp
|
||||
server: "smtp.example.com"
|
||||
port: 587
|
||||
timeout: 15
|
||||
sender: "john@example.com"
|
||||
encryption: starttls
|
||||
username: "john@example.com"
|
||||
password: "thePassword"
|
||||
recipient:
|
||||
- "james@example.com"
|
||||
- "bob@example.com"
|
||||
sender_name: "My Home Assistant"
|
||||
```
|
||||
|
||||
Keep in mind that Google has some extra layers of protection which need special attention (Hint: 'Less secure apps'). If you have 2-step verification enabled on your Google account, you'll need to use [an application-specific password](https://support.google.com/mail/answer/185833?hl=en).
|
||||
### Usage
|
||||
|
||||
To use the SMTP notification, refer to it in an automation or script like in this example:
|
||||
|
||||
@ -190,11 +172,35 @@ burglar:
|
||||
</html>
|
||||
```
|
||||
|
||||
This platform is fragile and not able to catch all exceptions in a smart way because of the large number of possible configuration combinations.
|
||||
To learn more about how to use notifications in your automations, please see the [getting started with automation page](/getting-started/automation/).
|
||||
|
||||
A combination that will work properly is port 587 and STARTTLS. It's recommended to enable STARTTLS, if possible.
|
||||
## Specific E-Mail Provider Configuration
|
||||
|
||||
For Google Mail (smtp.gmail.com) an additional step in the setup process is needed. Google has some extra layers of protection
|
||||
which need special attention. By default, the usage by external applications, especially scripts, is limited. Visit the [Less secure apps](https://www.google.com/settings/security/lesssecureapps) page and enable it.
|
||||
Check below some configurations examples for specific e-mail providers.
|
||||
If you are in doubt about the SMTP settings required, check your e-mail provider configuration or help pages for more information about its specific SMTP configuration.
|
||||
|
||||
To use notifications, please see the [getting started with automation page](/getting-started/automation/).
|
||||
### Google Mail
|
||||
|
||||
A sample configuration entry for Google Mail.
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry for Google Mail.
|
||||
notify:
|
||||
- name: "NOTIFIER_NAME"
|
||||
platform: smtp
|
||||
server: "smtp.gmail.com"
|
||||
port: 587
|
||||
timeout: 15
|
||||
sender: "YOUR_USERNAME@gmail.com"
|
||||
encryption: starttls
|
||||
username: "YOUR_USERNAME@gmail.com"
|
||||
password: "YOUR_PASSWORD"
|
||||
recipient:
|
||||
- "RECIPIENT_1@example.com"
|
||||
- "RECIPIENT_N@example.com"
|
||||
sender_name: "SENDER_NAME"
|
||||
```
|
||||
|
||||
Keep in mind that Google has some extra layers of protection that need special attention. By default, the usage by external applications is limited so you will need to visit the [less secure apps](https://www.google.com/settings/security/lesssecureapps) page and enable it to be able to send e-mails. Be aware that Google will periodically turn it off if it is not used (no e-mail is sent).
|
||||
|
||||
To avoid having your e-mail notifications broken due to the less secure app's behavior, it is recommended that you enable 2-step verification on your Google account, and use [an application-specific password](https://support.google.com/mail/answer/185833?hl=en) in your notification configuration.
|
||||
|
||||
@ -270,14 +270,7 @@ sonos:
|
||||
- 192.0.2.27
|
||||
```
|
||||
|
||||
If your Home Assistant instance has multiple IP addresses, you can provide the IP address that should be used for Sonos auto-discovery. This is rarely needed since all addresses should be tried by default.
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry using Sonos discovery on a specific interface
|
||||
sonos:
|
||||
media_player:
|
||||
interface_addr: 192.0.2.1
|
||||
```
|
||||
If your Home Assistant instance has multiple IP addresses, you can enable the IP address that should be used for Sonos auto-discovery with the [Network](/integrations/network/) integration. This should only be necessary if the Sonos speakers are on a network segment not reachable from the default interface.
|
||||
|
||||
The Sonos speakers will attempt to connect back to Home Assistant to deliver change events. By default, Home Assistant will listen on port 1400 but will try the next 100 ports above 1400 if it is in use. You can change the IP address that Home Assistant advertises to Sonos speakers. This can help in NAT scenarios such as when _not_ using the Docker option `--net=host`:
|
||||
|
||||
|
||||
@ -28,7 +28,7 @@ The Synology DSM sensor platform provides access to various statistics from your
|
||||
|
||||
This sensor will wake up your Synology NAS if it's in hibernation mode.
|
||||
|
||||
You can change the scan interal within the configuration options (default is 15 min).
|
||||
You can change the scan interval within the configuration options (default is 15 min).
|
||||
|
||||
Having cameras or the Home mode toggle from [Surveillance Station](https://www.synology.com/en-us/surveillance) will fetch every 30 seconds. Disable those entities if you don't want your NAS to be fetch as frequently.
|
||||
|
||||
|
||||
@ -140,7 +140,7 @@ You can use the service `tado.set_water_heater_timer` to set your water heater t
|
||||
|
||||
### Service `tado.set_climate_temperature_offset`
|
||||
|
||||
You can use the service `tado.set_climate_temperature_offset` to set the temprature offset for Tado climate devices
|
||||
You can use the service `tado.set_climate_temperature_offset` to set the temperature offset for Tado climate devices.
|
||||
|
||||
| Service data attribute | Optional | Description |
|
||||
| ---------------------- | -------- | ---------------------------------------------------------------------- |
|
||||
@ -170,7 +170,7 @@ script:
|
||||
|
||||
{% raw %}
|
||||
```yaml
|
||||
# Example automation to set temprature offset based on another thermostat value
|
||||
# Example automation to set temperature offset based on another thermostat value
|
||||
automation:
|
||||
# Trigger if the state of either thermostat changes
|
||||
trigger:
|
||||
|
||||
@ -299,6 +299,21 @@ curl --header "Content-Type: application/json" \
|
||||
http://homeassistant.local:8123/api/webhook/my-super-secret-webhook-id
|
||||
```
|
||||
|
||||
### Turning an event into a binary sensor
|
||||
|
||||
You can use a trigger-based template entity to convert any event or other automation trigger into a binary sensor. The below configuration will turn on a binary sensor for 5 seconds when the automation trigger triggers.
|
||||
|
||||
```yaml
|
||||
template:
|
||||
trigger:
|
||||
platform: event
|
||||
event_type: my_event
|
||||
binary_sensor:
|
||||
- name: Event recently fired
|
||||
auto_off: 5
|
||||
state: "true"
|
||||
```
|
||||
|
||||
### Sun Angle
|
||||
|
||||
This example shows the sun angle in the frontend.
|
||||
|
||||
@ -50,4 +50,15 @@ This integration provides the following platforms:
|
||||
|
||||
Tesla options are set via **Configuration** -> **Integrations** -> **Tesla** -> **Options**.
|
||||
|
||||
* Seconds between scans - referred to below as the `scan_interval`.
|
||||
|
||||
* Wake cars on start - Whether to wake sleeping cars on Home Assistant startup. This allows a user to choose whether cars should continue to sleep (and not update information) or to wake up the cars potentially interrupting long term hibernation and increasing vampire drain.
|
||||
|
||||
## Potential Battery impacts
|
||||
|
||||
Here are some things to consider and understand when implementing the Tesla component and its potential effect on your car's battery.
|
||||
|
||||
- The `scan_interval` determines when to check if the car is awake and new information is available, but the Tesla integration will not wake up a sleeping car during this polling. By default, the polling will occur every 660 seconds. Polling a car too frequently can keep the car awake and drain the battery. Different firmware versions and measurements of Tesla cars can take from 11 to 15 minutes for sleep mode to occur. There is no official information on sleep mode timings so your mileage may vary and you should experiment with different polling times for an optimal experience.
|
||||
- The car will, however, be woken up when a command is actively sent to the car, such as door unlock or turning on the HVAC. It will then also fetch updated information while the car is awake based on the `scan_interval`.
|
||||
- The car can intentionally be woken up to fetch recent information by sending a harmless command, for example, a lock command. This can be used in an automation to, for example, ensure that updated information is available every morning. (Note that the command must be valid for that specific car model. So locking the frunk of a Model 3 will not wake up that car).
|
||||
- You can also toggle the `Update switch` on/off to disable polling of the vehicle completely via automations or the Lovelace UI.
|
||||
|
||||
@ -35,7 +35,6 @@ Go to [developer.tibber.com/settings/accesstoken](https://developer.tibber.com/s
|
||||
|
||||
Tibber can send a notification by calling the [`notify` service](/integrations/notify/). It will send a notification to all devices registered in the Tibber account.
|
||||
|
||||
The requirement is that you have setup the [`tibber` component](#setup).
|
||||
To use notifications, please see the [getting started with automation page](/getting-started/automation/).
|
||||
|
||||
### Send message
|
||||
@ -53,7 +52,6 @@ action:
|
||||
The `tibber` sensor provides the current electricity price if you are a [Tibber](https://tibber.com/) customer.
|
||||
If you have a Tibber Pulse it will also show the electricity consumption in real time.
|
||||
|
||||
The requirement is that you have setup the [`tibber` component](#setup). The sensor will show once the transfer date to tibber has been confirmed.
|
||||
|
||||
## Examples
|
||||
|
||||
|
||||
@ -70,7 +70,7 @@ max_accuracy:
|
||||
type: integer
|
||||
default: 0
|
||||
skip_accuracy_filter_on:
|
||||
description: Skip filter position by "max_accuracy filter" if any of specified attributes are pressent on the traccar message.
|
||||
description: Skip filter position by "max_accuracy filter" if any of specified attributes are present on the traccar message.
|
||||
required: false
|
||||
type: list
|
||||
monitored_conditions:
|
||||
|
||||
@ -74,3 +74,7 @@ Please make sure you have `autoconf` installed (`$ sudo apt-get install autoconf
|
||||
### Setting the `api_key`
|
||||
|
||||
Do not use the `api_key` variable in `configuration.yaml`. The API key is only needed once at initial setup and will be stored.
|
||||
|
||||
## Known limitations
|
||||
|
||||
- The TRÅDFRI Shortcut button sends no events to Home Assistant so it cannot be used to automate with; it does report battery status.
|
||||
|
||||
@ -25,7 +25,7 @@ ha_platforms:
|
||||
ha_dhcp: true
|
||||
---
|
||||
|
||||
The `tuya` integration is the main integration to integrate [Tuya Smart](https://www.tuya.com) related platforms, except the Zigbee hub. This includes devices linked with the Tuya, Smart Life, and Jinvoo Smart apps. You will need your account information (username, password and account country code) from one of these apps to discover and control devices which related to your account.
|
||||
The `tuya` integration is the main integration to integrate [Tuya Smart](https://www.tuya.com) related platforms, except the Zigbee and Bluetooth(BLE) hub. This includes devices linked with the Tuya, Smart Life, and Jinvoo Smart apps. You will need your account information (username, password and account country code) from one of these apps to discover and control devices which related to your account.
|
||||
|
||||
**Important**: Not all Tuya devices are supported by the `tuya API` used by this integration. For more details refer to [TuyaHA Library](https://github.com/PaulAnnekov/tuyaha).
|
||||
|
||||
|
||||
@ -22,6 +22,10 @@ Notes:
|
||||
- The string inputs for `Substring *` allow you to force the integration to use a particular route or avoid a particular route in its time travel calculation. These inputs are case insensitive matched against the description of the route.
|
||||
- When using the `Avoid Toll Roads?`, `Avoid Subscription Roads?` and `Avoid Ferries?` options be aware that Waze will sometimes still route you over toll roads or ferries if a valid vignette/subscription is assumed. Default behavior is that Waze will route you over roads having subscription options, so best is to set both `Avoid Toll Roads?` and `Avoid Subscription Roads?` or `Avoid Ferries?` if needed and experiment to ensure the desired outcome.
|
||||
|
||||
## Manual Polling
|
||||
|
||||
Some users will want to have more control over polling frequencies. To use more granular polling, disable automated polling in your config entry's System Options. To manually trigger a polling request, call the [`homeassistant.update_entity` service](/integrations/homeassistant/#service-homeassistantupdate_entity) as needed, either manually or via automations.
|
||||
|
||||
## Example using dynamic destination
|
||||
|
||||
Using the flexible option to set a sensor value to the `Destination`, you can setup a single Waze integration that will calculate travel time to multiple optional locations on demand.
|
||||
|
||||
@ -13,7 +13,7 @@ The `template` integrations creates weather provider that combines integrations
|
||||
|
||||
There are several powerful ways to use this integration, including localizing your weather provider information with local information from temperature, humidity, pressure sensors that you own.
|
||||
|
||||
Another use case could be using temperature and humidity from one weather plaform, with forecasts from a different one.
|
||||
Another use case could be using temperature and humidity from one weather platform, with forecasts from a different one.
|
||||
|
||||
|
||||
## Configuration
|
||||
|
||||
@ -54,7 +54,7 @@ Please read the linked sections for those devices for more information.
|
||||
|
||||
It is recommend to supply your Xiaomi cloud credentials during configuration
|
||||
to automatically connect to your devices. You need to specify the cloud server
|
||||
you used in the Xiaomi Home App (where you initialy setup the device). There are
|
||||
you used in the Xiaomi Home App (where you initially setup the device). There are
|
||||
6 servers: `cn`, `de`, `i2`, `ru`, `sg` and `us`; please see
|
||||
[this page](https://www.openhab.org/addons/bindings/miio/#country-servers) for
|
||||
the server to use for each country.
|
||||
@ -1216,7 +1216,7 @@ Allowed `params` for the `reset_consumable` command:
|
||||
|
||||
[RRCC](https://github.com/LazyT/rrcc) supports both rooted and non-rooted Vacuums and acts as a mostly fully featured replacement for Mi Home that works locally without the cloud. If you have installed the rooted firmware [Valetudo](https://github.com/Hypfer/Valetudo) you are able to SSH into your Vacuum and enable MQTT plus use map functions with no cloud requirement.
|
||||
|
||||
Using the map editor you are able to acquire the co-ordinates required for zoned clean up. Here is an example script for zoned clean up:
|
||||
Using the map editor you are able to acquire the coordinates required for zoned clean up. Here is an example script for zoned clean up:
|
||||
|
||||
```yaml
|
||||
vacuum_kitchen:
|
||||
@ -1241,7 +1241,7 @@ miiocli vacuum --ip <ip of the vacuum> --token <your vacuum token> get_room_mapp
|
||||
It will return the full mapping of room numbers to user-defined names as a list of (number,name) tuples.
|
||||
Alternatively, one can just test the clean_segment service with a number and see which room it cleans.
|
||||
|
||||
It seems to be the case that Numbers 1..15 are used to number the intitial segmentation done by the vacuum cleaner itself. Numbers 16 and upwards numbers rooms from the users manual editing.
|
||||
It seems to be the case that Numbers 1..15 are used to number the initial segmentation done by the vacuum cleaner itself. Numbers 16 and upwards numbers rooms from the users manual editing.
|
||||
|
||||
## Xiaomi Philips Light
|
||||
|
||||
|
||||
@ -204,6 +204,6 @@ Number 6 sends an image from a templated URL.
|
||||
|
||||
{% endraw %}
|
||||
|
||||
The possible source of a file is prioritized and only one will be picked up. `url_template` has the hightest priority; next is `url` then `path_template` and finally if none of them are defined `path` would be used. `path` will be used to eliminate file extension guessing for unknown URL downloads. Only the file extension will be left, as Home Assistant changes the filename to a random string for added privacy.
|
||||
The possible source of a file is prioritized and only one will be picked up. `url_template` has the highest priority; next is `url` then `path_template` and finally if none of them are defined `path` would be used. `path` will be used to eliminate file extension guessing for unknown URL downloads. Only the file extension will be left, as Home Assistant changes the filename to a random string for added privacy.
|
||||
|
||||
To find out more about notifications, please see the [getting started with automation page](/getting-started/automation/).
|
||||
|
||||
@ -339,7 +339,7 @@ To help resolve any kinks or compatibility problems, report bugs as issues with
|
||||
|
||||
There is no official compatibility list of supported devices for the simple reason that practically all devices Zigbee Home Automation that are fully compliant with the standards and specifications as set by the [Zigbee Alliance](https://zigbeealliance.org) should technically be compatible with this ZHA integration. The fact remains, however, that some hardware manufacturers do not always fully comply with each set specification, which can cause a few devices to only partially work or not work at all with ZHA, but developers can create workarounds for such issues via a solution for 'ZHA exception and deviation handling' that this implementation features. See that section for more information.
|
||||
|
||||
Tip to new users is that, while there is no official list of supported devices, some ZHA users take comfort that blakadder maintains an unofficial Zigbee Device Compatibility Repository which anyone can submit compatibility reports to, it can be found at [zigbee.blakadder.com](https://zigbee.blakadder.com) and currently contains independent compatibility lists and device pairing tips for several home automation gateway/bridge/hub softwares, including but not limited to open source Zigbee implementations such as; ZHA, Tasmota, Zigbee2MQTT, and ZiGate.
|
||||
Tip to new users is that, while there is no official list of supported devices, some ZHA users take comfort that blakadder maintains an unofficial Zigbee Device Compatibility Repository which anyone can submit compatibility reports to, it can be found at [zigbee.blakadder.com](https://zigbee.blakadder.com) and currently contains independent compatibility lists and device pairing tips for several home automation gateway/bridge/hub software, including but not limited to open source Zigbee implementations such as; ZHA, Tasmota, Zigbee2MQTT, and ZiGate.
|
||||
|
||||
### ZHA exception and deviation handling
|
||||
|
||||
|
||||
@ -615,7 +615,7 @@ Z-Wave JS keeps a database of all devices it supports, including any special tre
|
||||
|
||||
### I get a lot of sensor entities for my device that I'm probably never going to use
|
||||
|
||||
The integration will add as many useable entities for you as possible from the information it retrieves from your Z-Wave devices. Entities that you don't want/like, can be disabled within the Home Assistant interface.
|
||||
The integration will add as many usable entities for you as possible from the information it retrieves from your Z-Wave devices. Entities that you don't want/like, can be disabled within the Home Assistant interface.
|
||||
|
||||
### I renamed my devices in Z-Wave JS 2 MQTT but those names are not visible in Home Assistant
|
||||
|
||||
|
||||
@ -53,6 +53,7 @@ Alright, that's it! Enjoy the release!
|
||||
- [Release 2021.7.1 - July 8](#release-202171---july-8)
|
||||
- [Release 2021.7.2 - July 12](#release-202172---july-12)
|
||||
- [Release 2021.7.3 - July 16](#release-202173---july-16)
|
||||
- [Release 2021.7.4 - July 21](#release-202174---july-21)
|
||||
- [If you need help...](#if-you-need-help)
|
||||
- [Breaking Changes](#breaking-changes)
|
||||
- [All changes](#all-changes)
|
||||
@ -520,6 +521,58 @@ The following integrations are now available via the Home Assistant UI:
|
||||
[sma docs]: /integrations/sma/
|
||||
[zha docs]: /integrations/zha/
|
||||
|
||||
## Release 2021.7.4 - July 21
|
||||
|
||||
- Allow pymodbus to reconnect in running system (not startup) ([@janiversen] - [#53020]) ([modbus docs])
|
||||
- Fix groups reporting incorrect supported color modes ([@Kane610] - [#53088]) ([deconz docs])
|
||||
- Handle all WeMo ensure_long_press_virtual_device exceptions ([@esev] - [#53094]) ([wemo docs])
|
||||
- Fix remote rpi gpio input type ([@jgriff2] - [#53108]) ([remote_rpi_gpio docs])
|
||||
- More restrictive state updates of UniFi uptime sensor ([@Kane610] - [#53111]) ([unifi docs])
|
||||
- Bump simplisafe-python to 11.0.2 ([@bachya] - [#53121]) ([simplisafe docs])
|
||||
- Bump nexia to 0.9.10 to fix asair login ([@bdraco] - [#53122]) ([nexia docs])
|
||||
- Bump surepy to 0.7.0 ([@benleb] - [#53123]) ([surepetcare docs])
|
||||
- Upgrade pysonos to 0.0.53 ([@amelchio] - [#53137]) ([sonos docs])
|
||||
- Correctly detect is not home ([@balloob] - [#53279]) ([device_tracker docs])
|
||||
- Upgrade to async-upnp-client==0.19.1 ([@StevenLooman] - [#53288]) ([dlna_dmr docs]) ([ssdp docs]) ([upnp docs])
|
||||
- Fix homekit locks not being created from when setup from the UI ([@bdraco] - [#53301]) ([homekit docs])
|
||||
|
||||
[#53020]: https://github.com/home-assistant/core/pull/53020
|
||||
[#53088]: https://github.com/home-assistant/core/pull/53088
|
||||
[#53094]: https://github.com/home-assistant/core/pull/53094
|
||||
[#53108]: https://github.com/home-assistant/core/pull/53108
|
||||
[#53111]: https://github.com/home-assistant/core/pull/53111
|
||||
[#53121]: https://github.com/home-assistant/core/pull/53121
|
||||
[#53122]: https://github.com/home-assistant/core/pull/53122
|
||||
[#53123]: https://github.com/home-assistant/core/pull/53123
|
||||
[#53137]: https://github.com/home-assistant/core/pull/53137
|
||||
[#53279]: https://github.com/home-assistant/core/pull/53279
|
||||
[#53288]: https://github.com/home-assistant/core/pull/53288
|
||||
[#53301]: https://github.com/home-assistant/core/pull/53301
|
||||
[@Kane610]: https://github.com/Kane610
|
||||
[@StevenLooman]: https://github.com/StevenLooman
|
||||
[@amelchio]: https://github.com/amelchio
|
||||
[@bachya]: https://github.com/bachya
|
||||
[@balloob]: https://github.com/balloob
|
||||
[@bdraco]: https://github.com/bdraco
|
||||
[@benleb]: https://github.com/benleb
|
||||
[@esev]: https://github.com/esev
|
||||
[@janiversen]: https://github.com/janiversen
|
||||
[@jgriff2]: https://github.com/jgriff2
|
||||
[deconz docs]: /integrations/deconz/
|
||||
[device_tracker docs]: /integrations/device_tracker/
|
||||
[dlna_dmr docs]: /integrations/dlna_dmr/
|
||||
[homekit docs]: /integrations/homekit/
|
||||
[modbus docs]: /integrations/modbus/
|
||||
[nexia docs]: /integrations/nexia/
|
||||
[remote_rpi_gpio docs]: /integrations/remote_rpi_gpio/
|
||||
[simplisafe docs]: /integrations/simplisafe/
|
||||
[sonos docs]: /integrations/sonos/
|
||||
[ssdp docs]: /integrations/ssdp/
|
||||
[surepetcare docs]: /integrations/surepetcare/
|
||||
[unifi docs]: /integrations/unifi/
|
||||
[upnp docs]: /integrations/upnp/
|
||||
[wemo docs]: /integrations/wemo/
|
||||
|
||||
## If you need help...
|
||||
|
||||
...don't hesitate to use our very active [forums](https://community.home-assistant.io/) or join us for a little [chat](https://discord.gg/c5DvZ4e).
|
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Loading…
x
Reference in New Issue
Block a user