mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-07-27 19:26:50 +00:00
Merge branch 'rc' into current
This commit is contained in:
Paulus Schoutsen
commit
78cc14bd77
@ -139,9 +139,9 @@ social:
|
||||
|
||||
# Home Assistant release details
|
||||
current_major_version: 0
|
||||
current_minor_version: 71
|
||||
current_minor_version: 72
|
||||
current_patch_version: 0
|
||||
date_released: 2018-06-08
|
||||
date_released: 2018-06-22
|
||||
|
||||
# Either # or the anchor link to latest release notes in the blog post.
|
||||
# Must be prefixed with a # and have double quotes around it.
|
||||
|
||||
@ -69,6 +69,10 @@ qos:
|
||||
required: false
|
||||
type: integer
|
||||
default: 0
|
||||
unique_id:
|
||||
description: "An ID that uniquely identifies this sensor. If two sensors have the same unique ID, Home Assistant will raise an exception."
|
||||
required: false
|
||||
type: string
|
||||
device_class:
|
||||
description: "The [type/class](/components/binary_sensor/) of the sensor to set the icon in the frontend."
|
||||
required: false
|
||||
|
||||
@ -28,22 +28,24 @@ The buttons will give you feedback with its built-in LED:
|
||||
- white then green: Pattern was submitted successfully
|
||||
- white then red: There is a problem with the communication
|
||||
|
||||
To use your myStrom WiFi Button in your installation, add the following to your `configuration.yaml` file:
|
||||
### {% linkable_title Setup of myStrom Buttons %}
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
binary_sensor:
|
||||
- platform: mystrom
|
||||
You need to configure every button to make it work with Home Assistant. First connect the Wifi Buttons to your wireless network. Once a button is connected you have three minutes to set the actions for the push patterns if the button is not charging. The fastest way is to use `curl`. Check the [documentation](https://mystrom.ch/wp-content/uploads/REST_API_WBP.txt) of the WiFi Button for further details about the implementation (`http://` is replaced by `get://` or `post://`). `action` is the name of the corresponding push pattern (see above).
|
||||
|
||||
The endpoint that is receiving the data is `http://[IP address Home Assistant]:8123/api/mystrom`. If you have set an [`api_password`](/components/http/) then this needs to be included in the URL.
|
||||
|
||||
With `api_password:`
|
||||
|
||||
```
|
||||
$ curl -d "[action]=get://[IP address Home Assistant]:8123/api/mystrom?api_password%3D[api_password]%26[action]%3D[ID of the button]" \
|
||||
http://[IP address of the button]/api/v1/device/[MAC address of the button]
|
||||
```
|
||||
|
||||
### {% linkable_title Setup of the myStrom Buttons %}
|
||||
|
||||
You need to configure every button to make it work with Home Assistant. First connect the Wifi Buttons to your wireless network. Once a button is connected you have three minutes to set the actions for the push patterns. The fastest way is to use `curl`. Check the [documentation](https://mystrom.ch/wp-content/uploads/REST_API_WBP.txt) of the WiFi Button for further details about the implementation (`http://` is replaced by `get://` or `post://`). `action` is the name of the corresponding push pattern (see above).
|
||||
|
||||
The endpoint that is receiving the data is `[IP address Home Assistant]:8123/api/mystrom`.
|
||||
Without `api_password`:
|
||||
|
||||
```bash
|
||||
$ curl -d "[action]=get://[IP address Home Assistant]:8123/api/mystrom?[action]%3D[ID of the button]" http://[IP address of the button]/api/v1/device/[MAC address of the button]
|
||||
$ curl -d "[action]=get://[IP address Home Assistant]:8123/api/mystrom?[action]%3D[ID of the button]" \
|
||||
http://[IP address of the button]/api/v1/device/[MAC address of the button]
|
||||
{
|
||||
"[MAC address of the button]": {
|
||||
"type": "button",
|
||||
@ -52,7 +54,7 @@ $ curl -d "[action]=get://[IP address Home Assistant]:8123/api/mystrom?[action]%
|
||||
"meshroot": false,
|
||||
"charge": true,
|
||||
"voltage": 4.292,
|
||||
"fw_version": "2.26",
|
||||
"fw_version": "2.56",
|
||||
"single": "get://[IP address Home Assistant]:8123/api/mystrom?single=[id of the button]",
|
||||
"double": "",
|
||||
"long": "",
|
||||
@ -67,6 +69,26 @@ A complete command to set the URL for a double click could look like the example
|
||||
$ curl -d "double=get://192.168.1.3:8123/api/mystrom?double%3DButton1" http://192.168.1.12/api/v1/device/4D5F5D5CD553
|
||||
```
|
||||
|
||||
With an `api_password`:
|
||||
|
||||
```bash
|
||||
curl -d "double=get://192.168.1.3:8123/api/mystrom?api_password%3Dapi_password%26double%3DButton1" http://192.168.1.12/api/v1/device/4D5F5D5CD553
|
||||
```
|
||||
|
||||
The command-line tool [`mystrom`](https://github.com/fabaff/python-mystrom) is a helper to configure myStrom buttons.
|
||||
|
||||
If you have set [`login_attempts_threshold`](/components/http/) and forget to include the `api_password` for an action and that action is triggered then after the threshold is reached will the button no longer work because it is banned. See [IP filtering and banning](/components/http/#ip-filtering-and-banning) about how to revert the banning.
|
||||
|
||||
## {% linkable_title Configuration %}
|
||||
|
||||
To use your myStrom WiFi Button in your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
binary_sensor:
|
||||
- platform: mystrom
|
||||
```
|
||||
|
||||
<p class='note'>
|
||||
The firmware version 2.26 doesn't support TLS/SSL. This means that you are only able to use the WiFi Buttons if you are using plain-text communication between Home Assistant and the clients/entities.
|
||||
The firmware version 2.56 doesn't support TLS/SSL. This means that you are only able to use the WiFi Buttons if you are using plain-text communication between Home Assistant and the clients/entities.
|
||||
</p>
|
||||
|
||||
@ -10,7 +10,7 @@ footer: true
|
||||
logo: nest.png
|
||||
ha_category: Binary Sensor
|
||||
ha_release: pre 0.7
|
||||
ha_iot_class: "Cloud Polling"
|
||||
ha_iot_class: "Cloud Push"
|
||||
---
|
||||
|
||||
|
||||
|
||||
35
source/_components/binary_sensor.uptimerobot.markdown
Normal file
35
source/_components/binary_sensor.uptimerobot.markdown
Normal file
@ -0,0 +1,35 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Uptime Robot"
|
||||
description: "Instructions on how to set up Uptime Robot within Home Assistant."
|
||||
date: 2018-05-29 21:00
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: uptimerobot.png
|
||||
ha_category: Binary Sensor
|
||||
ha_release: "0.72"
|
||||
ha_iot_class: "Cloud Polling"
|
||||
---
|
||||
|
||||
The `uptimerobot` binary_sensor platform allows you get the status for all of your monitors from your account on [Uptime Robot.]( https://uptimerobot.com)
|
||||
|
||||
## Example for `configuration.yaml` :
|
||||
|
||||
```yaml
|
||||
binary_sensor:
|
||||
- platform: uptimerobot
|
||||
api_key: u432898-d2507e493b31217e6c64fd35
|
||||
```
|
||||
|
||||
{% configuration %}
|
||||
api_key:
|
||||
description: Your Uptime Robot API key.
|
||||
required: true
|
||||
type: string
|
||||
{% endconfiguration %}
|
||||
|
||||
All the data will be fetch from [Uptime Robot](https://uptimerobot.com).
|
||||
|
||||
To get your API key, go to [My Settings](https://uptimerobot.com/dashboard#mySettings) on the Uptime Robot website, at the bottom you will find your "Main API Key".
|
||||
48
source/_components/binary_sensor.wirelesstag.markdown
Normal file
48
source/_components/binary_sensor.wirelesstag.markdown
Normal file
@ -0,0 +1,48 @@
|
||||
---
|
||||
layout: page
|
||||
title: "WirelessTag Binary Sensor"
|
||||
description: "Instructions on how to integrate Wireless Tags sensors within Home Assistant."
|
||||
date: 2018-03-26 21:49
|
||||
comments: false
|
||||
sidebar: true
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: wirelesstag.png
|
||||
ha_category: Binary Sensor
|
||||
ha_iot_class: "Local Push and Cloud Polling"
|
||||
ha_release: 0.68
|
||||
---
|
||||
|
||||
To get your [wirelesstag.net](http://wirelesstag.net) binary sensors working within Home Assistant, please follow the instructions for the general [WirelessTag component](/components/wirelesstag).
|
||||
|
||||
To enable tags set up with your [wirelesstag.net](http://wirelesstag.net) account, add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
binary_sensor:
|
||||
- platform: wirelesstag
|
||||
monitored_conditions:
|
||||
- presence
|
||||
- door
|
||||
- low_battery
|
||||
```
|
||||
|
||||
{% configuration %}
|
||||
monitored_conditions:
|
||||
description: The conditions types to monitor; valid values are specified below
|
||||
required: true
|
||||
type: list
|
||||
{% endconfiguration %}
|
||||
|
||||
The following conditions can be monitored:
|
||||
|
||||
* (`presence`): On means in range, Off means out of range.
|
||||
* (`motion`): On when a movement was detected, Off when clear.
|
||||
* (`door`): On when a door is open, Off when the door is closed.
|
||||
* (`cold`): On means temperature become too cold, Off means normal.
|
||||
* (`heat`): On means hot, Off means normal.
|
||||
* (`dry`): On means too dry (humidity), Off means normal.
|
||||
* (`wet`): On means too wet (humidity), Off means normal.
|
||||
* (`light`): On means light detected, Off means no light.
|
||||
* (`moisture`): On means moisture detected (wet), Off means no moisture (dry).
|
||||
* (`low_battery`): On means tag battery is low, Off means normal.
|
||||
@ -10,7 +10,7 @@ footer: true
|
||||
logo: nest.png
|
||||
ha_category: Camera
|
||||
ha_release: 0.34
|
||||
ha_iot_class: "Cloud Polling"
|
||||
ha_iot_class: "Cloud Poll"
|
||||
---
|
||||
|
||||
The `nest` platform allows you to watch the live stream of your [Nest](https://nest.com/camera/meet-nest-cam/) camera in Home Assistant.
|
||||
|
||||
86
source/_components/camera.xiaomi.markdown
Normal file
86
source/_components/camera.xiaomi.markdown
Normal file
@ -0,0 +1,86 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Xiaomi Cameras"
|
||||
description: "Instructions on how to integrate a video feed (via FFmpeg) as a camera within Home Assistant."
|
||||
date: 2018-06-20 13:00
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: xiaomi.png
|
||||
ha_category: Camera
|
||||
ha_release: 0.72
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
The `Xiaomi` camera platform allows you to utilize Xiaomi Cameras within Home Assistant.
|
||||
|
||||
To successfully implement this platform, the Home Assistant host should be capable of multiple simultaneous reads. For every concurrent Home Assistant user, a connection will be made to the camera every 10 seconds. This should normally not be a problem.
|
||||
|
||||
## {% linkable_title Preparing the Device %}
|
||||
|
||||
### {% linkable_title Installing Alternative Firmware %}
|
||||
|
||||
In order to integrate the camera with Home Assistant, it is necessary to install a custom firmware on the device. Instructions for doing so can be found for each models.
|
||||
|
||||
* [Yi 720p](https://github.com/fritz-smh/yi-hack)
|
||||
* [Yi Home 17CN / 27US / 47US / 1080p Home / Dome / 1080p Dome](https://github.com/shadow-1/yi-hack-v3)
|
||||
* [Xiaofang 1080p Camera](https://github.com/samtap/fang-hacks)
|
||||
|
||||
Once installed, please ensure that you have enabled FTP.
|
||||
|
||||
<p class='note warning'>
|
||||
Currently, version 0.1.4-beta2 of the custom firmware is the highest supported. Firmwares higher than this version use [Pure-FTPd](https://www.pureftpd.org/project/pure-ftpd), which has a bug that prevents FFmpeg from correctly rendering video files.
|
||||
</p>
|
||||
|
||||
<p class='note warning'>
|
||||
Hassbian users: don't forget to install ffmpeg support on your platform, otherwise, you'll not see video.
|
||||
</p>
|
||||
|
||||
<p class='note warning'>
|
||||
The live stream writing by the camera is not an supported format when the hass reads through FTP for Yi 720p and Xiaofang Cameras, so this component retrives the video which was saved 1 minute earlier.
|
||||
</p>
|
||||
|
||||
<p class='note warning'>
|
||||
If you enabled RTSP server, you can connect to your camera via other Home Assistant camera platforms. However, this RTSP server disables the ability to use the supremely-useful Mi Home app. In order to maintain both Home Assistant compatibility _and_ the native app, this platform retrieves videos via FTP.
|
||||
</p>
|
||||
|
||||
## {% linkable_title Configuring the Platform %}
|
||||
|
||||
To enable the platform, add the following lines to your`configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
camera:
|
||||
- platform: xiaomi
|
||||
name: Camera
|
||||
host: '192.168.1.100'
|
||||
model: 'yi'
|
||||
password: my_password_123
|
||||
```
|
||||
|
||||
Configuration variables:
|
||||
|
||||
- **name** (*Required*): A human-friendly name for the camera.
|
||||
- **host** (*Required*): The IP address or hostname of the camera.
|
||||
- **model** (*Required*): The model of Xiaomi Camera, currently supporting yi and xiaofang.
|
||||
- **password** (*Required*): The password to the FTP server on the camera (from above), can be any string as the current firmware doesn't allow setting ftp passwords.
|
||||
- **path** (*Optional*): The path to the raw MP4 files. Defaults to `/tmp/sd/record`.
|
||||
- **username** (*Optional*): The user that can access the FTP server. Defaults to `root`.
|
||||
- **ffmpeg_arguments** (*Optional*): Extra options to pass to `ffmpeg` (e.g., image quality or video filter options).
|
||||
|
||||
## {% linkable_title Image quality %}
|
||||
|
||||
Any option supported by [`ffmpeg` camera](/components/camera.ffmpeg/) can be utilized via the `ffmpeg_arguments` configuration parameter.
|
||||
|
||||
One particularly useful adjustment deals with video size. Since Yi videos are fairly large (especially on the 1080p cameras), the following configuration will bring them down to a manageable size:
|
||||
|
||||
```yaml
|
||||
camera:
|
||||
- platform: xiaomi
|
||||
name: My Camera
|
||||
host: '192.168.1.100'
|
||||
model: 'xiaofang'
|
||||
password: my_password_123
|
||||
path: /home/camera/feed
|
||||
ffmpeg_arguments: '-vf scale=800:450'
|
||||
```
|
||||
@ -12,31 +12,27 @@ ha_category: Media Player
|
||||
featured: true
|
||||
ha_release: pre 0.7
|
||||
ha_iot_class: "Local Polling"
|
||||
redirect_from: /components/media_player.cast/
|
||||
---
|
||||
|
||||
|
||||
Google Cast devices like Android TVs and Chromecasts will be automatically discovered if you enable [the discovery component]({{site_root}}/components/discovery/). There is an issue where Chromecasts can only be discovered if your device is connected to the same subnet as your Chromecast.
|
||||
Google Cast devices like Android TVs and Chromecasts will be automatically discovered if you enable [the discovery component]({{site_root}}/components/discovery/). If you don't have the discovery component enabled, you can enable the Cast component by going to the Integrations page inside the config panel.
|
||||
|
||||
## {% linkable_title Advanced use %}
|
||||
|
||||
The Cast component has some extra configuration options available for advanced users. You will still need to create a config entry to initialize the Cast component.
|
||||
|
||||
For example, Cast devices can only be discovered if they are on the same subnet as Home Assistant. If this is not the case, you want to configure the IP address of the Cast device directly:
|
||||
|
||||
The Chromecast platform can also be forced to load by adding the following lines to your `configuration.yaml`:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
media_player:
|
||||
- platform: cast
|
||||
cast:
|
||||
media_player:
|
||||
- host: 192.168.1.10
|
||||
```
|
||||
|
||||
Configuration variables:
|
||||
|
||||
- **host** (*Optional*): Use only if you don't want to scan for devices.
|
||||
- **ignore_cec** (*Optional*) A list of Chromecasts that should ignore CEC data for determining the active input. [See the upstream documentation for more information.](https://github.com/balloob/pychromecast#ignoring-cec-data)
|
||||
|
||||
## {% linkable_title Example %}
|
||||
|
||||
By setting `host:` you can specify the Chromecast to use.
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
media_player:
|
||||
- platform: cast
|
||||
host: 192.168.1.10
|
||||
```
|
||||
@ -174,6 +174,14 @@ aux_state_template:
|
||||
description: A template to render the value received on the `aux_state_topic` with.
|
||||
required: false
|
||||
type: template
|
||||
min_temp:
|
||||
description: Minimum set point available
|
||||
type: number
|
||||
required: false
|
||||
max_temp:
|
||||
description: Maximum set point available
|
||||
type: number
|
||||
required: false
|
||||
{% endconfiguration %}
|
||||
|
||||
#### {% linkable_title Optimistic mode %}
|
||||
|
||||
@ -9,7 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: nest.png
|
||||
ha_category: Climate
|
||||
ha_iot_class: "Cloud Polling"
|
||||
ha_iot_class: "Cloud Push"
|
||||
---
|
||||
|
||||
|
||||
|
||||
45
source/_components/climate.zhong_hong.markdown
Normal file
45
source/_components/climate.zhong_hong.markdown
Normal file
@ -0,0 +1,45 @@
|
||||
---
|
||||
layout: page
|
||||
title: "ZhongHong Thermostats Controller"
|
||||
description: "Instructions on how to integrate ZhongHong Support thermostats within Home Assistant."
|
||||
date: 2018-06-20 08:30
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: zhong_hong.png
|
||||
ha_category: Climate
|
||||
ha_release: "0.72"
|
||||
ha_iot_class: "Local Push"
|
||||
---
|
||||
|
||||
|
||||
The `zhong_hong` climate platform lets you control [Zhonghong HVAC Gateway Controller](http://zhonghongtech.cn/v1/product.shtml/) thermostats through Home Assistant.
|
||||
|
||||
To set it up, add the following information to your configuration.yaml file:
|
||||
|
||||
```yaml
|
||||
climate:
|
||||
- platform: zhong_hong
|
||||
host: GATEWAY_IP
|
||||
```
|
||||
|
||||
{% configuration %}
|
||||
host:
|
||||
description: The IP address of your controller.
|
||||
required: true
|
||||
type: string
|
||||
port:
|
||||
description: The port of your controller.
|
||||
required: false
|
||||
default: 9999
|
||||
type: int
|
||||
gateway_address:
|
||||
description: The gateway address for the gateway (Settings in the controller itself).
|
||||
required: false
|
||||
default: 1
|
||||
type: int
|
||||
|
||||
{% endconfiguration %}
|
||||
|
||||
When Gateway is found, All HVAC devices will be configured automatically.
|
||||
67
source/_components/device_tracker.freebox.markdown
Normal file
67
source/_components/device_tracker.freebox.markdown
Normal file
@ -0,0 +1,67 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Freebox"
|
||||
description: "Instructions on how to integrate Freebox routers into Home Assistant."
|
||||
date: 2018-05-16 23:00
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: freebox.svg
|
||||
ha_category: Presence Detection
|
||||
ha_release: "0.70"
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
|
||||
The `freebox` platform offers presence detection by keeping track of the
|
||||
devices connected to a [Freebox](http://www.free.fr/) router.
|
||||
|
||||
### {% linkable_title Configuration %}
|
||||
|
||||
If you have enabled the [discovery component](/components/discovery/),
|
||||
your Freebox should be detected automatically. Otherwise, you can set it
|
||||
up manually in your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
device_tracker:
|
||||
- platform: freebox
|
||||
host: foobar.fbox.fr
|
||||
port: 1234
|
||||
```
|
||||
|
||||
{% configuration %}
|
||||
host:
|
||||
description: The url of the Freebox.
|
||||
required: true
|
||||
type: string
|
||||
port:
|
||||
description: The https port the Freebox is listening on.
|
||||
required: true
|
||||
type: string
|
||||
{% endconfiguration %}
|
||||
|
||||
You can find out your Freebox host and port by opening
|
||||
[this address](http://mafreebox.freebox.fr/api_version) in your browser. The
|
||||
returned json should contain an api_domain (`host`) and a https_port (`port`).
|
||||
|
||||
### {% linkable_title Initial setup %}
|
||||
|
||||
The first time Home Assistant will connect to your Freebox, you will need to
|
||||
authorize it by pressing the right button on the facade of the Freebox when
|
||||
prompted to do so.
|
||||
|
||||
### {% linkable_title Notes %}
|
||||
|
||||
Note that the Freebox waits for some time before marking a device as
|
||||
inactive, meaning that there will be a small delay (1 or 2 minutes)
|
||||
between the time you disconnect a device and the time it will appear
|
||||
as "away" in Home Assistant. You should take this into account when specifying
|
||||
the `consider_home` parameter.
|
||||
On the contrary, the Freebox immediately reports devices newly connected, so
|
||||
they should appear as "home" almost instantly, as soon as Home Assistant
|
||||
refreshes the devices states.
|
||||
|
||||
See the [device tracker component page](/components/device_tracker/) for
|
||||
instructions how to configure the devices to be tracked.
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Facebox"
|
||||
description: "Detect and recognise faces with Facebox."
|
||||
description: "Detect and recognize faces with Facebox."
|
||||
date: 2018-05-03 00:00
|
||||
sidebar: true
|
||||
comments: false
|
||||
@ -13,14 +13,21 @@ featured: false
|
||||
ha_release: 0.70
|
||||
---
|
||||
|
||||
The `facebox` image processing platform allows you to detect and recognise faces in a camera image using [Facebox](https://machinebox.io/docs/facebox). The state of the entity is the number of faces detected, and recognised faces are listed in the `matched_faces` attribute. Facebox runs in a Docker container, and it is recommended that you run this container on a machine with a minimum of 2 GB RAM. On your machine with Docker, run the Facebox container with:
|
||||
```
|
||||
The `facebox` image processing platform allows you to detect and recognize faces in a camera image using [Facebox](https://machinebox.io/docs/facebox). The state of the entity is the number of faces detected, and recognized faces are listed in the `matched_faces` attribute. An `image_processing.detect_face` event is fired for each recognized face, and the event `data` provides the `confidence` of recognition, the `name` of the person, the `image_id` of the image associated with the match, the `bounding_box` that contains the face in the image, and the `entity_id` that processing was performed on.
|
||||
|
||||
## {% linkable_title Setup %}
|
||||
|
||||
Facebox runs in a Docker container and it is recommended that you run this container on a machine with a minimum of 2 GB RAM. On your machine with Docker, run the Facebox container with:
|
||||
|
||||
```bash
|
||||
MB_KEY="INSERT-YOUR-KEY-HERE"
|
||||
|
||||
sudo docker run --name=facebox --restart=always -p 8080:8080 -e "MB_KEY=$MB_KEY" machinebox/facebox
|
||||
```
|
||||
|
||||
If you only require face detection (number of faces) you can disable face recognition by adding ```-e "MB_FACEBOX_DISABLE_RECOGNITION=true"``` to the `docker run` command.
|
||||
If you only require face detection (number of faces) you can disable face recognition by adding `-e "MB_FACEBOX_DISABLE_RECOGNITION=true"` to the `docker run` command.
|
||||
|
||||
## {% linkable_title Configuration %}
|
||||
|
||||
To enable this platform in your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
@ -58,3 +65,28 @@ source:
|
||||
required: false
|
||||
type: string
|
||||
{% endconfiguration %}
|
||||
|
||||
## {% linkable_title Automations %}
|
||||
|
||||
Use the `image_processing.detect_face` events to trigger automations, and breakout the `trigger.event.data` using a [data_template](https://www.home-assistant.io/docs/automation/templating/). The following example automation sends a notification when Ringo Star is recognized:
|
||||
|
||||
{% raw %}
|
||||
```yaml
|
||||
- id: '12345'
|
||||
alias: Ringo Starr recognised
|
||||
trigger:
|
||||
platform: event
|
||||
event_type: image_processing.detect_face
|
||||
event_data:
|
||||
name: 'Ringo_Starr'
|
||||
action:
|
||||
service: notify.platform
|
||||
data_template:
|
||||
message: Ringo_Starr recognised with probability {{ trigger.event.data.confidence }}
|
||||
title: Door-cam notification
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
## {% linkable_title Optimising resources %}
|
||||
|
||||
[Image processing components](https://www.home-assistant.io/components/image_processing/) process the image from a camera at a fixed period given by the `scan_interval`. This leads to excessive processing if the image on the camera hasn't changed, as the default `scan_interval` is 10 seconds. You can override this by adding to your config `scan_interval: 10000` (setting the interval to 10,000 seconds), and then call the `image_processing.scan` service when you actually want to perform processing.
|
||||
|
||||
@ -37,6 +37,14 @@ insteon_plm:
|
||||
subcat: SUBCATEGORY
|
||||
firmware: FIRMWARE
|
||||
product_key: PRODUCT_KEY
|
||||
x10_devices:
|
||||
- housecode: HOUSECODE
|
||||
unitcode: UNITCODE
|
||||
platform: PLATFORM
|
||||
steps: STEPS
|
||||
x10_all_units_off: HOUSECODE
|
||||
x10_all_lights_on: HOUSECODE
|
||||
x10_all_lights_off: HOUSECODE
|
||||
```
|
||||
Configuration variables:
|
||||
- **port** (*Required*): The port for your device, e.g., `/dev/ttyUSB0`
|
||||
@ -48,6 +56,22 @@ Configuration variables:
|
||||
of 0x00 - 0xff
|
||||
- *FIRMWARE* and *PRODUCT_KEY* are more advanced options and will typically
|
||||
not be used.
|
||||
- **x10_devices** (*Optional*): Define X10 devices to control or respond to
|
||||
- *HOUSECODE* is the X10 housecode values a - p
|
||||
- *UNITCODE* is the X10 unit code values 1 - 16
|
||||
- *PLATFORM* is the Home Assistant Platform to associate the device with.
|
||||
The following platforms are supported
|
||||
- binary_sensor: Used for on/off devices or keypad buttons that are read only.
|
||||
- light: Used for dimmable X10 devices
|
||||
- switch: Used for On/Off X10 devices
|
||||
- *STEPS* is the number of dim/bright steps the device supports. Used for
|
||||
dimmable X10 devices only. Default value is 22.
|
||||
- **x10_all_units_off** (*Optional*): Creates an binary_sensor that responds
|
||||
to the X10 standard command for All Units Off.
|
||||
- **x10_all_lights_on** (*Optional*): Creates an binary_sensor that responds
|
||||
to the X10 standard command for All Lights On
|
||||
- **x10_all_lights_off** (*Optional*): Creates an binary_sensor that responds
|
||||
to the X10 standard command for All Lights Off
|
||||
|
||||
### {% linkable_title Autodiscovery %}
|
||||
|
||||
|
||||
@ -51,6 +51,11 @@ access_token:
|
||||
description: Any random string. This is used to ensure that only those devices which you have configured can authenticate to Home Assistant to change a device state.
|
||||
required: true
|
||||
type: string
|
||||
api_host:
|
||||
description: Override the IP address/host (and port number) of Home Assistant that the Konnected device(s) will use to communicate sensor state updates. If omitted, this is defaulted to the value of `base_url` in the `http` component. If you've set `base_url` to an external hostname, then you'll want to set this value back to your _local_ IP address and port (e.g. `http://192.168.1.101:8123`).
|
||||
required: false
|
||||
type: url
|
||||
default: value of `base_url`
|
||||
devices:
|
||||
description: A list of Konnected devices that you have on your network.
|
||||
required: true
|
||||
|
||||
39
source/_components/lock.kiwi.markdown
Normal file
39
source/_components/lock.kiwi.markdown
Normal file
@ -0,0 +1,39 @@
|
||||
---
|
||||
layout: page
|
||||
title: "KIWI Lock"
|
||||
description: "Instructions on how to integrate KIWI Smart Lock and Smart Entry."
|
||||
date: 2018-05-16 13:37
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: kiwi.png
|
||||
ha_category: Lock
|
||||
featured: false
|
||||
ha_release: 0.72
|
||||
ha_iot_class: "Cloud Polling"
|
||||
---
|
||||
|
||||
The `KIWI` platform allows you to open your KIWI Smart Locks and Smart Entry Devices.
|
||||
All you need to get started is a KIWI account. Register at [the KIWI website](https://kiwi.ki/login/).
|
||||
|
||||
## {% linkable_title Configuration %}
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
lock:
|
||||
- platform: kiwi
|
||||
username: mail@example.com
|
||||
password: mySecretPassword
|
||||
```
|
||||
|
||||
{% configuration %}
|
||||
username:
|
||||
required: true
|
||||
description: The username of your KIWI account.
|
||||
type: string
|
||||
password:
|
||||
required: true
|
||||
description: The password of your KIWI account.
|
||||
type: string
|
||||
{% endconfiguration %}
|
||||
@ -11,15 +11,16 @@ logo: home-assistant.png
|
||||
ha_category: "Utility"
|
||||
---
|
||||
|
||||
The logger component lets you define the level of logging activities in Home Assistant.
|
||||
The `logger` component lets you define the level of logging activities in Home Assistant.
|
||||
|
||||
To enable the logger in your installation, add the following to your `configuration.yaml` file:
|
||||
To enable the `logger` component in your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
To have a full log and log everything only this entry is needed (without any qualifier):
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
logger:
|
||||
```
|
||||
To log all messages and ignore events lower than critical for specified components.
|
||||
|
||||
To log all messages and ignore events lower than critical for specified components:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
@ -30,7 +31,7 @@ logger:
|
||||
homeassistant.components.camera: critical
|
||||
```
|
||||
|
||||
To ignore all messages lower than critical and log event for specified components.
|
||||
To ignore all messages lower than critical and log event for specified components:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
@ -43,7 +44,25 @@ logger:
|
||||
homeassistant.components.camera: critical
|
||||
```
|
||||
|
||||
Possible log severities are:
|
||||
{% configuration %}
|
||||
default:
|
||||
description: Default log level.
|
||||
required: false
|
||||
type: '[log_level](#log-levels)'
|
||||
default: debug
|
||||
logs:
|
||||
description: List of components and their log level.
|
||||
required: false
|
||||
type: map
|
||||
keys:
|
||||
'<component_namespace>':
|
||||
description: Logger namespace of the component.
|
||||
type: '[log_level](#log-levels)'
|
||||
{% endconfiguration %}
|
||||
|
||||
### {% linkable_title Log Levels %}
|
||||
|
||||
Possible log severity levels are:
|
||||
|
||||
- critical
|
||||
- fatal
|
||||
@ -53,11 +72,26 @@ Possible log severities are:
|
||||
- info
|
||||
- debug
|
||||
- notset
|
||||
|
||||
|
||||
## {% linkable_title Services %}
|
||||
|
||||
### {% linkable_title Service `set_default_level` %}
|
||||
|
||||
You can alter the default log level (for components without a specified log
|
||||
level) using the service `logger.set_default_level`.
|
||||
|
||||
An example call might look like this:
|
||||
|
||||
```yaml
|
||||
service: logger.set_default_level
|
||||
data:
|
||||
level: info
|
||||
```
|
||||
|
||||
### {% linkable_title Service `set_level` %}
|
||||
|
||||
You can alter log level for one or several components using the service
|
||||
``logger.set_level``. It accepts the same format as ``logs`` in the configuration.
|
||||
`logger.set_level`. It accepts the same format as `logs` in the configuration.
|
||||
|
||||
An example call might look like this:
|
||||
|
||||
@ -68,7 +102,9 @@ data:
|
||||
homeassistant.components.media_player.yamaha: debug
|
||||
```
|
||||
|
||||
The log information are stored in the [configuration directory](/docs/configuration/) as `home-assistant.log` and you can read it with the command-line tool `cat` or follow it dynamically with `tail -f`.
|
||||
The log information are stored in the [configuration directory](/docs/configuration/)
|
||||
as `home-assistant.log` and you can read it with the command-line tool `cat` or
|
||||
follow it dynamically with `tail -f`.
|
||||
|
||||
If you are a Hassbian user you can use the example below:
|
||||
|
||||
@ -76,7 +112,8 @@ If you are a Hassbian user you can use the example below:
|
||||
$ tail -f /home/homeassistant/.homeassistant/home-assistant.log
|
||||
```
|
||||
|
||||
If you are a Hass.io user you can use the example below, whenlogged in through the ssh addon:
|
||||
If you are a Hass.io user, you can use the example below, when logged in through
|
||||
the [SSH add-on](/addons/ssh/):
|
||||
|
||||
```bash
|
||||
$ tail -f /config/home-assistant.log
|
||||
|
||||
63
source/_components/media_player.epson.markdown
Normal file
63
source/_components/media_player.epson.markdown
Normal file
@ -0,0 +1,63 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Epson"
|
||||
description: "Instructions on how to integrate Epson projector into Home Assistant."
|
||||
date: 2018-06-13 15:00
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: epson.png
|
||||
ha_category: Media Player
|
||||
ha_release: 0.72
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
The `epson` platform allows you to control a Epson projector from Home Assistant.
|
||||
|
||||
To add Epson to your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
media_player:
|
||||
- platform: epson
|
||||
host: 192.168.0.123
|
||||
```
|
||||
|
||||
{% configuration %}
|
||||
host:
|
||||
description: The host name or address of the Epson projector
|
||||
required: true
|
||||
type: string
|
||||
port:
|
||||
description: The HTTP port number.
|
||||
required: false
|
||||
type: int
|
||||
default: 80
|
||||
name:
|
||||
description: The name of the device used in the frontend.
|
||||
required: false
|
||||
type: string
|
||||
default: 'EPSON Projector'
|
||||
ssl:
|
||||
description: Enable SSL. **Feature not tested.**
|
||||
required: false
|
||||
type: bool
|
||||
default: false
|
||||
{% endconfiguration %}
|
||||
|
||||
Supported features of Epson projector:
|
||||
- turn on/off
|
||||
- set input
|
||||
- set/get color mode
|
||||
- increase/decrease volume
|
||||
- mute/unmute audio
|
||||
- send next/previous track
|
||||
|
||||
Supported devices:
|
||||
- Epson projectors supporting ESC/VP21 protocol.
|
||||
|
||||
Tested devices:
|
||||
- Epson EH-TW5350
|
||||
|
||||
To make this module work you need to connect your projector to your LAN. The best is to use iProjection app by Epson to test if it is working.
|
||||
45
source/_components/media_player.horizon.markdown
Normal file
45
source/_components/media_player.horizon.markdown
Normal file
@ -0,0 +1,45 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Horizon HD Recorder"
|
||||
description: "Instructions how to integrate the Unitymedia Horizon HD Recorder into Home Assistant."
|
||||
date: 2018-05-02 20:00
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: unitymedia.png
|
||||
ha_category: Media Player
|
||||
ha_iot_class: "Local Polling"
|
||||
ha_release: 0.72
|
||||
---
|
||||
|
||||
The `horizon` component allows you to control a [Unitymedia](https://www.unitymedia.de) Horizon HD Recorder from Home Assistant.
|
||||
|
||||
To add a Horizon HD Recorder to your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
media_player:
|
||||
- platform: horizon
|
||||
host: 192.168.0.127
|
||||
```
|
||||
|
||||
{% configuration %}
|
||||
host:
|
||||
description: The hostname or address of the device.
|
||||
required: true
|
||||
type: string
|
||||
port:
|
||||
description: The port of the device to connect to.
|
||||
required: false
|
||||
type: int
|
||||
name:
|
||||
description: The name of the device used in the frontend.
|
||||
required: false
|
||||
type: string
|
||||
{% endconfiguration %}
|
||||
|
||||
|
||||
#### {% linkable_title Preparation of the Horizon HD Recorder %}
|
||||
|
||||
The Home Networking ("Heimnetzwerk") service needs to be enabled at the settings menu of the Horizon receiver. Once you have set up the Media Library ("Medienbibliothek"), we can determine whether the device is turned on or off. Without this, the component will fail to start.
|
||||
@ -56,7 +56,16 @@ Available services: `turn_on`, `turn_off`, `toggle`, `volume_up`, `volume_down`,
|
||||
| `entity_id` | yes | Target a specific media player. Defaults to all. |
|
||||
| `source` | no | Name of the source to switch to. Platform dependent. |
|
||||
|
||||
#### {% linkable_title Service `media_player.shuffle_set` %}
|
||||
#### {% linkable_title Service `media_player/select_sound_mode` %}
|
||||
|
||||
Currently only supported on [Denon AVR](/components/media_player.denonavr/) and [Songpal](/components/media_player.songpal/).
|
||||
|
||||
| Service data attribute | Optional | Description |
|
||||
| ---------------------- | -------- | ---------------------------------------------------- |
|
||||
| `entity_id` | no | Target a specific media player. For example `media_player.marantz`|
|
||||
| `sound_mode` | no | Name of the sound mode to switch to. Platform dependent.|
|
||||
|
||||
#### {% linkable_title Service `media_player/shuffle_set` %}
|
||||
|
||||
Currently only supported on [Spotify](/components/media_player.spotify/), [MPD](/components/media_player.mpd/), [Kodi](/components/media_player.kodi/), [Squeezebox](/components/media_player.squeezebox/) and [Universal](/components/media_player.universal/).
|
||||
|
||||
|
||||
@ -10,7 +10,7 @@ footer: true
|
||||
logo: nest.png
|
||||
ha_category: Hub
|
||||
featured: true
|
||||
ha_iot_class: "Cloud Polling"
|
||||
ha_iot_class: "Cloud Push"
|
||||
---
|
||||
|
||||
The Nest component is the main component to integrate all [Nest](https://nest.com/) related platforms. To connect Nest, you will have to [sign up for a developer account](https://developers.nest.com/products) and get a `client_id` and `client_secret`.
|
||||
|
||||
39
source/_components/netgear_lte.markdown
Normal file
39
source/_components/netgear_lte.markdown
Normal file
@ -0,0 +1,39 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Netgear LTE"
|
||||
description: "Instructions on how to integrate your Netgear LTE modem within Home Assistant."
|
||||
date: 2018-06-06 23:00
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: netgear.png
|
||||
ha_release: 0.72
|
||||
ha_category: Other
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
The Netgear LTE integration for Home Assistant allows you to observe and control [Netgear LTE modems](https://www.netgear.com/home/products/mobile-broadband/lte-modems/default.aspx), currently only tested with LB2120.
|
||||
|
||||
The integration provides:
|
||||
* a notify service that will send an SMS
|
||||
* a sensor with the number of unread SMS messages in the inbox
|
||||
* a sensor with data usage
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
netgear_lte:
|
||||
- host: IP_ADDRESS
|
||||
password: SECRET
|
||||
```
|
||||
|
||||
{% configuration %}
|
||||
host:
|
||||
description: The IP address of the modem web interface.
|
||||
required: true
|
||||
type: string
|
||||
password:
|
||||
description: The password used for the modem web interface.
|
||||
required: true
|
||||
type: string
|
||||
{% endconfiguration %}
|
||||
41
source/_components/notify.netgear_lte.markdown
Normal file
41
source/_components/notify.netgear_lte.markdown
Normal file
@ -0,0 +1,41 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Netgear LTE Notify"
|
||||
description: "Instructions on how to add Netgear LTE notifications to Home Assistant."
|
||||
date: 2018-06-06 23:00
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: netgear.png
|
||||
ha_category: Notifications
|
||||
ha_release: 0.72
|
||||
---
|
||||
|
||||
The `netgear_lte` platform allows you to use a Netgear LTE modem for notifications from Home Assistant. The message will be sent as an SMS text message.
|
||||
|
||||
This requires you to have set up the [Netgear LTE component](/components/netgear_lte/).
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
notify:
|
||||
- platform: netgear_lte
|
||||
name: sms
|
||||
target: "+15105550123"
|
||||
```
|
||||
|
||||
{% configuration %}
|
||||
target:
|
||||
description: The phone number of a default recipient or a list with multiple recipients.
|
||||
required: true
|
||||
type: string, list
|
||||
name:
|
||||
description: Setting the optional parameter `name` allows multiple notifiers to be created.
|
||||
required: false
|
||||
default: notify
|
||||
type: string
|
||||
host:
|
||||
description: The modem to use. Not needed if you only have one.
|
||||
required: false
|
||||
type: string
|
||||
{% endconfiguration %}
|
||||
@ -15,17 +15,19 @@ ha_iot_class: "Local Polling"
|
||||
|
||||
The `mitemp_bt` sensor platform allows one to monitor room temperature and humidity. The [Xiaomi Mijia BLE Temperature and Humidity sensor with LCD](https://www.amazon.com/Temperature-Humidity-Xiaomi-Bluetooth-Screen-Remote/dp/B079L6N6PC) is a small Bluetooth Low Energy device that monitors the room temperature and humidity. As only a single BLE device can be polled at the same time, the library employs locking to make sure this is the case.
|
||||
|
||||
# Installation
|
||||
## {% linkable_title Installation %}
|
||||
|
||||
Depending on the operating system you're running, you have to configure the proper Bluetooth backend on your system:
|
||||
|
||||
- On [Hass.io](/hassio/installation/): Not yet supported.
|
||||
- On [Hass.io](/hassio/installation/): mitemp_bt will work out of the box.
|
||||
- On a [generic Docker installation](https://www.home-assistant.io/docs/installation/docker/): Works out of the box with `--net=host` and properly configured Bluetooth on the host.
|
||||
- On other Linux systems:
|
||||
- Preferred solution: Install the `bluepy` and `btlewrap` library (via pip). When using a virtual environment, make sure to use install the library in the right one.
|
||||
- Fallback solution: Install `btlewrap` library (via pip) and `gatttool` via your package manager. Depending on the distribution, the package name might be: `bluez`, `bluetooth`, `bluez-deprecated`
|
||||
- Windows and MacOS are currently not supported by the btlewrap library.
|
||||
|
||||
# Configuration
|
||||
## {% linkable_title Configuration %}
|
||||
|
||||
Start a scan to determine the MAC addresses of the sensor:
|
||||
|
||||
```bash
|
||||
@ -43,10 +45,8 @@ $ bluetoothctl
|
||||
Discovery started
|
||||
[CHG] Controller XX:XX:XX:XX:XX:XX Discovering: yes
|
||||
[NEW] Device 4C:65:A8:D2:31:7F MJ_HT_V1
|
||||
|
||||
```
|
||||
|
||||
|
||||
Check for `MJ_HT_V1` or similar entries, those are your sensor.
|
||||
|
||||
To use your Mi Temperature and Humidity sensor in your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
@ -10,7 +10,7 @@ footer: true
|
||||
logo: nest.png
|
||||
ha_category: Sensor
|
||||
ha_release: pre 0.7
|
||||
ha_iot_class: "Cloud Polling"
|
||||
ha_iot_class: "Cloud Push"
|
||||
---
|
||||
|
||||
|
||||
@ -47,8 +47,9 @@ The following conditions are available by device:
|
||||
- target
|
||||
- hvac\_state: The currently active state of the HVAC system, `heating`, `cooling`, or `off`.
|
||||
- Nest Protect:
|
||||
- co\_status
|
||||
- smoke\_status
|
||||
- battery\_health
|
||||
- co\_status: `Ok`, `Warning`, or `Emergency`
|
||||
- smoke\_status: `Ok`, `Warning`, or `Emergency`
|
||||
- battery\_health: `Ok` or `Replace`
|
||||
- color\_status: `gray`, `green`, `yellow`, or `red`. Indicates device status by color in the Nest app UI. It is an aggregate condition for battery+smoke+CO states, and reflects the actual color indicators displayed in the Nest app.
|
||||
- Nest Camera: none
|
||||
|
||||
|
||||
43
source/_components/sensor.netgear_lte.markdown
Normal file
43
source/_components/sensor.netgear_lte.markdown
Normal file
@ -0,0 +1,43 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Netgear LTE Sensor"
|
||||
description: "Instructions on how to integrate Netgear LTE sensors into Home Assistant."
|
||||
date: 2018-06-06 23:00
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: netgear.png
|
||||
ha_release: 0.72
|
||||
ha_category: Sensor
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
The `netgear_lte` sensor platform allows you to monitor your Netgear LTE modem.
|
||||
|
||||
This requires you to have set up the [Netgear LTE component](/components/netgear_lte/).
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
sensor:
|
||||
- platform: netgear_lte
|
||||
sensors:
|
||||
- sms
|
||||
- usage
|
||||
```
|
||||
|
||||
{% configuration %}
|
||||
sensors:
|
||||
description: Sensor types to create.
|
||||
required: true
|
||||
type: list
|
||||
keys:
|
||||
sms:
|
||||
description: Number of unread SMS messages in the modem inbox.
|
||||
usage:
|
||||
description: Amount of data transferred.
|
||||
host:
|
||||
description: The modem to use. Not needed if you only have one.
|
||||
required: false
|
||||
type: string
|
||||
{% endconfiguration %}
|
||||
46
source/_components/sensor.nsw_fuel_station.markdown
Normal file
46
source/_components/sensor.nsw_fuel_station.markdown
Normal file
@ -0,0 +1,46 @@
|
||||
---
|
||||
layout: page
|
||||
title: "NSW Fuel Station Price Sensor"
|
||||
description: "Instructions on how to integrate NSW fuel station prices into Home Assistant."
|
||||
date: 2018-06-02 18:00
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
ha_category: Fuel
|
||||
ha_release: 0.72
|
||||
ha_iot_class: "Cloud Polling"
|
||||
---
|
||||
|
||||
The `nsw_fuel_station` sensor platform uses the [NSW Fuel Check App](https://www.fuelcheck.nsw.gov.au/app) data as a source for current fuel price data.
|
||||
|
||||
## {% linkable_title Setup %}
|
||||
|
||||
To get the station ID for any NSW fuel station you will need to:
|
||||
|
||||
- Visit the [Fuel Check App](https://www.fuelcheck.nsw.gov.au/app).
|
||||
- Open the developer console of your browser (for Chrome, click View -> Developer -> Developer Tools). Click the "Network" tab in the developer console.
|
||||
- In the Fuel Check App, search for your postcode or click "Fuel Near Me".
|
||||
- In the developer console, you should see a request to `/FuelCheckApp/v1/fuel/prices/bylocation`. Open this request and preview the response. Find the station you wish to add, and copy down the `ServiceStationID` field.
|
||||
|
||||
## {% linkable_title Configuration %}
|
||||
|
||||
To add the NSW fuel station price sensor to your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
sensor:
|
||||
- platform: nsw_fuel_station
|
||||
station_id: 291
|
||||
```
|
||||
|
||||
{% configuration %}
|
||||
station_id:
|
||||
description: The ID of the station to track
|
||||
required: true
|
||||
type: string
|
||||
fuel_types:
|
||||
description: A list of fuel types to track for the station. Must be one of `["E10", "U91", "E85", "P95", "P98", "DL", "PDL", "B20", "LPG", "CNG", "EV"]`. Descriptions of fuel types can be found [here](https://www.fuelcheck.nsw.gov.au/App/Home/FuelTypes).
|
||||
required: false
|
||||
default: "`['E10', 'U91']`"
|
||||
type: list
|
||||
{% endconfiguration %}
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Pi-Hole Sensor"
|
||||
description: "Instructions on how to integrate REST sensors into Home Assistant."
|
||||
title: "Pi-hole Sensor"
|
||||
description: "Instructions on how to integrate Pi-hole sensors into Home Assistant."
|
||||
date: 2016-09-03 16:30
|
||||
sidebar: true
|
||||
comments: false
|
||||
@ -14,7 +14,9 @@ ha_release: 0.28
|
||||
---
|
||||
|
||||
|
||||
The `pi_hole` sensor platform is displaying the statistical summary of a [Pi-Hole](https://pi-hole.net/) system.
|
||||
The `pi_hole` sensor platform is displaying the statistical summary of a [Pi-hole](https://pi-hole.net/) system.
|
||||
|
||||
## {% linkable_title Configuration %}
|
||||
|
||||
To enable this sensor, add the following lines to your `configuration.yaml` file for a GET request:
|
||||
|
||||
@ -24,18 +26,52 @@ sensor:
|
||||
- platform: pi_hole
|
||||
```
|
||||
|
||||
Configuration variables:
|
||||
{% configuration %}
|
||||
host:
|
||||
description: IP address of the host where Pi-hole is running.
|
||||
required: false
|
||||
type: string
|
||||
default: localhost
|
||||
location:
|
||||
description: The installation location of the Pi-hole API.
|
||||
required: false
|
||||
type: string
|
||||
default: admin
|
||||
ssl:
|
||||
description: "If `true`, use SSL/TLS to connect to the Pi-Hole system."
|
||||
required: false
|
||||
type: boolean
|
||||
default: false
|
||||
verify_ssl:
|
||||
description: Verify the certification of the system.
|
||||
required: false
|
||||
type: boolean
|
||||
default: true
|
||||
monitored_conditions:
|
||||
description: Defines the stats to monitor as sensors.
|
||||
required: false
|
||||
type: string
|
||||
default: all
|
||||
keys:
|
||||
ads_blocked_today:
|
||||
description: Total number of blocked ads today.
|
||||
ads_percentage_today:
|
||||
description: Percentage of blocked ads.
|
||||
dns_queries_today:
|
||||
description: Total number of DNS queries handled by Pi-hole today.
|
||||
domains_being_blocked:
|
||||
description: Total number of domains blocked by Pi-hole.
|
||||
queries_cached:
|
||||
description: Total number of cache queries on the last 24 hours.
|
||||
queries_forwarded:
|
||||
description: Total number of forwarded queries on the last 24 hours.
|
||||
unique_clients:
|
||||
description: Total number of unique clients on the last 24 hours.
|
||||
unique_domains:
|
||||
description: Total number of unique domains on the last 24 hours.
|
||||
clients_ever_seen:
|
||||
description: Total number of seen clients.
|
||||
{% endconfiguration %}
|
||||
|
||||
This sensor platform was not made by Pi-hole LLC or the Pi-hole community. They didn't provide support, feedback, testing or helped in any way while it was created. This is third party, may not if Pi-hole is breaking their API with the latest release, not official, not developed, not supported and not endorsed Pi-hole LLC or the Pi-hole community. The trademark `Pi-hole` and the logo is used here to describe the platform and only to describe. `Pi-hole` is a registered trademark of Pi-hole LLC.
|
||||
|
||||
- **host** (*Optional*): The IP address of the Pi-Hole system. Defaults to `localhost`.
|
||||
- **location** (*Optional*): The installation location of the Pi-Hole API. Defaults to `admin`.
|
||||
- **ssl** (*Optional*): If `true`, use SSL/TLS to connect to the Pi-Hole system. Defaults to `False`.
|
||||
- **verify_ssl** (*Optional*): Verify the certification of the system. Default to `True`.
|
||||
- **monitored_conditions** (*Optional*): Defines the stats to monitor as sensors.
|
||||
- **ads_blocked_today**: Total number of blocked ads today.
|
||||
- **ads_percentage_today**: Percentage of blocked ads.
|
||||
- **dns_queries_today**: Total number of DNS queries handled by Pi-Hole today.
|
||||
- **domains_being_blocked**: Total number of domains blocked by Pi-Hole.
|
||||
- **queries_cached**: Total number of cache queries on the last 24 hours.
|
||||
- **queries_forwarded**: Total number of forwarded queries on the last 24 hours.
|
||||
- **unique_clients**: Total number of unique clients on the last 24 hours.
|
||||
- **unique_domains**: Total number of unique domains on the last 24 hours.
|
||||
|
||||
@ -29,6 +29,8 @@ where:
|
||||
- **P** = the [phase](https://en.wikipedia.org/wiki/Phase_(waves)) offset to add to the periodic contribution, in units of degrees
|
||||
- **N(s)** = the random [Gaussian noise](https://en.wikipedia.org/wiki/Gaussian_noise) with spread **s**
|
||||
|
||||
The output will be limited to 3 decimals.
|
||||
|
||||
## {% linkable_title Configuration %}
|
||||
|
||||
To add a simulated sensor to your installation, add the following to your `configuration.yaml` file:
|
||||
@ -79,6 +81,11 @@ spread:
|
||||
required: false
|
||||
default: None
|
||||
type: float
|
||||
relative_to_epoch:
|
||||
description: Whether to simulate from epoch time (00:00:00, 1970-01-01), or relative to when the sensor was started.
|
||||
required: false
|
||||
default: true
|
||||
type: boolean
|
||||
{% endconfiguration %}
|
||||
|
||||
## {% linkable_title Example %}
|
||||
@ -94,4 +101,5 @@ sensor:
|
||||
mean: 50
|
||||
spread: 10
|
||||
seed: 999
|
||||
relative_to_epoch: false
|
||||
```
|
||||
|
||||
41
source/_components/sensor.wirelesstag.markdown
Normal file
41
source/_components/sensor.wirelesstag.markdown
Normal file
@ -0,0 +1,41 @@
|
||||
---
|
||||
layout: page
|
||||
title: "WirelessTag Sensor"
|
||||
description: "Instructions on how to integrate your Wireless Tags sensors within Home Assistant."
|
||||
date: 2018-03-26 21:50
|
||||
comments: false
|
||||
sidebar: true
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: wirelesstag.png
|
||||
ha_category: Sensor
|
||||
ha_iot_class: "Local Push and Cloud Polling"
|
||||
ha_release: 0.68
|
||||
---
|
||||
|
||||
To get your [wirelesstag.net](http://wirelesstag.net) sensors working within Home Assistant, please follow the instructions for the general [WirelessTag component](/components/wirelesstag).
|
||||
|
||||
To enable tags set up with your [wirelesstag.net](http://wirelesstag.net) account, add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
sensor:
|
||||
- platform: wirelesstag
|
||||
monitored_conditions:
|
||||
- temperature
|
||||
- humidity
|
||||
```
|
||||
|
||||
{% configuration %}
|
||||
monitored_conditions:
|
||||
description: The metrics types to monitor; valid values are specified below
|
||||
required: true
|
||||
type: list
|
||||
{% endconfiguration %}
|
||||
|
||||
The following metrics can be monitored:
|
||||
|
||||
* (`temperature`): Value is in Celsius or Fahrenheit (according to your settings at Tag Manager).
|
||||
* (`humidity`): Humidity level in %.
|
||||
* (`moisture`): Water level/soil moisture in % (applicable for Water Tag only).
|
||||
* (`light`): Brightness in lux (if supported by tag).
|
||||
@ -12,48 +12,16 @@ ha_category: Media Player
|
||||
featured: true
|
||||
ha_release: 0.7.3
|
||||
ha_iot_class: "Local Polling"
|
||||
redirect_from: /components/media_player.sonos/
|
||||
---
|
||||
|
||||
The `sonos` platform allows you to control your [Sonos](http://www.sonos.com) HiFi wireless speakers and audio components from Home Assistant. By default it supports auto-discovery provided by Home Assistant, and you don't need to add anything to your `configuration.yaml`. Alternatively, there are some manual configuration options, listed as follows:
|
||||
The `sonos` component allows you to control your [Sonos](http://www.sonos.com) HiFi wireless speakers and audio components from Home Assistant. By default it supports auto-discovery provided by Home Assistant, and you don't need to add anything to your `configuration.yaml`.
|
||||
|
||||
To add your Sonos components to your installation, add the following to your `configuration.yaml` file. It will perform Sonos auto-discovery of your connected speakers.
|
||||
If you don't have the discovery component enabled, you can configure the Sonos component by going to the integrations page inside the config panel.
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry using Sonos discovery
|
||||
media_player:
|
||||
- platform: sonos
|
||||
```
|
||||
## {% linkable_title Services %}
|
||||
|
||||
|
||||
If you have multiple network devices, you can provide the IP address of the device that should be used for Sonos auto-discovery.
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry using Sonos discovery on a specific interface
|
||||
media_player:
|
||||
- platform: sonos
|
||||
interface_addr: 192.0.2.1
|
||||
```
|
||||
|
||||
You can also specify one or more hosts to connect to if they cannot be found with Sonos auto-discovery.
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry with manually specified addresses
|
||||
media_player:
|
||||
- platform: sonos
|
||||
hosts: 192.0.2.25
|
||||
```
|
||||
|
||||
or, for multiple hosts:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry with manually specified addresses
|
||||
media_player:
|
||||
- platform: sonos
|
||||
hosts:
|
||||
- 192.0.2.25
|
||||
- 192.0.2.26
|
||||
- 192.0.2.27
|
||||
```
|
||||
Sonos makes various services available to allow configuring groups. They are currently registered under the media player component.
|
||||
|
||||
### {% linkable_title Service `sonos_snapshot` %}
|
||||
|
||||
@ -93,7 +61,7 @@ Remove one or more speakers from a group of speakers. If no `entity_id` is provi
|
||||
### {% linkable_title Service `sonos_set_sleep_timer` %}
|
||||
|
||||
Sets a timer that will turn off a speaker by tapering the volume down to 0 after a certain amount of time. Protip: If you set the sleep_time value to 0, then the speaker will immediately start tapering the volume down.
|
||||
|
||||
|
||||
| Service data attribute | Optional | Description |
|
||||
| ---------------------- | -------- | ----------- |
|
||||
| `entity_id` | no | String or list of `entity_id`s that will have their timers set. Must be a coordinator speaker.
|
||||
@ -102,7 +70,7 @@ Sets a timer that will turn off a speaker by tapering the volume down to 0 after
|
||||
### {% linkable_title Service `sonos_clear_sleep_timer` %}
|
||||
|
||||
Clear the sleep timer on a speaker, if one is set.
|
||||
|
||||
|
||||
| Service data attribute | Optional | Description |
|
||||
| ---------------------- | -------- | ----------- |
|
||||
| `entity_id` | no | String or list of `entity_id`s that will have their timers cleared. Must be a coordinator speaker.
|
||||
@ -110,7 +78,7 @@ Clear the sleep timer on a speaker, if one is set.
|
||||
### {% linkable_title Service `sonos_update_alarm` %}
|
||||
|
||||
Update an existing Sonos alarm.
|
||||
|
||||
|
||||
| Service data attribute | Optional | Description |
|
||||
| ---------------------- | -------- | ----------- |
|
||||
| `entity_id` | no | String or list of `entity_id`s that will have their timers cleared. Must be a coordinator speaker.
|
||||
@ -118,16 +86,51 @@ Update an existing Sonos alarm.
|
||||
| `time` | yes | Time to set the alarm.
|
||||
| `volume` | yes | Float for volume level.
|
||||
| `enabled` | yes | Boolean for whether or not to enable this alarm.
|
||||
| `include_linked_zones` | yes | Boolean that defines if the alarm also plays on grouped players.
|
||||
| `include_linked_zones` | yes | Boolean that defines if the alarm also plays on grouped players.
|
||||
|
||||
### {% linkable_title Service `sonos_set_option` %}
|
||||
|
||||
Set Sonos speaker options.
|
||||
|
||||
Night Sound and Speech Enhancement modes are only supported on Sonos PLAYBAR and PLAYBASE speakers when playing from the TV source. Other speaker types will ignore these options.
|
||||
|
||||
|
||||
| Service data attribute | Optional | Description |
|
||||
| ---------------------- | -------- | ----------- |
|
||||
| `entity_id` | no | String or list of `entity_id`s that will have their options set.
|
||||
| `night_sound` | yes | Boolean to control Night Sound mode.
|
||||
| `speech_enhance` | yes | Boolean to control Speech Enhancement mode.
|
||||
|
||||
|
||||
## {% linkable_title Advanced use %}
|
||||
|
||||
For advancved uses, there are some manual configuration options available.
|
||||
|
||||
If you have multiple network devices, you can provide the IP address of the device that should be used for Sonos auto-discovery.
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry using Sonos discovery on a specific interface
|
||||
sonos:
|
||||
media_player:
|
||||
interface_addr: 192.0.2.1
|
||||
```
|
||||
|
||||
You can also specify one or more hosts to connect to if they cannot be found with Sonos auto-discovery.
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry with manually specified addresses
|
||||
sonos:
|
||||
media_player:
|
||||
hosts: 192.0.2.25
|
||||
```
|
||||
|
||||
or, for multiple hosts:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry with manually specified addresses
|
||||
sonos:
|
||||
media_player:
|
||||
hosts:
|
||||
- 192.0.2.25
|
||||
- 192.0.2.26
|
||||
- 192.0.2.27
|
||||
```
|
||||
45
source/_components/switch.wirelesstag.markdown
Normal file
45
source/_components/switch.wirelesstag.markdown
Normal file
@ -0,0 +1,45 @@
|
||||
---
|
||||
layout: page
|
||||
title: "WirelessTag Switch"
|
||||
description: "Instructions on how to integrate your Wireless Tags sensors within Home Assistant."
|
||||
date: 2018-03-26 21:52
|
||||
comments: false
|
||||
sidebar: true
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: wirelesstag.png
|
||||
ha_category: Switch
|
||||
ha_iot_class: "Local Push and Cloud Polling"
|
||||
ha_release: 0.68
|
||||
---
|
||||
|
||||
To get your [wirelesstag.net](http://wirelesstag.net) switches working within Home Assistant, please follow the instructions for the general [WirelessTag component](/components/wirelesstag).
|
||||
|
||||
To enable tags set up with your [wirelesstag.net](http://wirelesstag.net) account, add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
switch:
|
||||
- platform: wirelesstag
|
||||
monitored_conditions:
|
||||
- motion
|
||||
- humidity
|
||||
```
|
||||
|
||||
{% configuration %}
|
||||
monitored_conditions:
|
||||
description: The metrics types to control; valid values are specified below
|
||||
required: true
|
||||
type: list
|
||||
{% endconfiguration %}
|
||||
|
||||
The following metrics can be controlled:
|
||||
|
||||
* (`temperature`): Control arm/disarm temperature monitoring.
|
||||
* (`humidity`): Control arm/disarm humidity monitoring.
|
||||
* (`motion`): Control arm/disarm motion and door open/close events monitoring.
|
||||
* (`light`): Control monitoring of light changes.
|
||||
* (`moisture`): Control monitoring of water level/soil moisture for water sensor.
|
||||
|
||||
Arm/Disarm of motion switch is required to receive motion and door binary sensors events.
|
||||
Others are only needed if you want to receive push notifications from tags on a specific range of changes in temperature, humidity, light or moisture.
|
||||
104
source/_components/watson_iot.markdown
Normal file
104
source/_components/watson_iot.markdown
Normal file
@ -0,0 +1,104 @@
|
||||
---
|
||||
layout: page
|
||||
title: "IBM Watson IoT Platform"
|
||||
description: "Record events in the IBM Watson IoT Platform."
|
||||
date: 2018-04-03 22:09
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: ibm.png
|
||||
ha_category: History
|
||||
ha_release: 0.72
|
||||
---
|
||||
|
||||
The `watson_iot` component enables you to link the devices in Home Assistant
|
||||
with an [IBM Watson IoT Platform instance](https://www.ibm.com/us-en/marketplace/internet-of-things-cloud).
|
||||
|
||||
## {% linkable_title Configuration %}
|
||||
|
||||
To use this component, you first need to register a gateway device type and then
|
||||
a gateway device in your IoT platform instance. For instructions on how to do
|
||||
this check the [official documentation](https://console.bluemix.net/docs/services/IoT/gateways/dashboard.html#IoT_connectGateway)
|
||||
which provides the details on doing this. After you register the gateway device
|
||||
for your home-assistant you'll need 4 pieces of information:
|
||||
- Organization ID
|
||||
- Gateway device Type
|
||||
- Gateway device ID
|
||||
- Authentication Token
|
||||
|
||||
With this basic information you can configure the component:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry:
|
||||
watson_iot:
|
||||
organization: 'organization_id'
|
||||
type: 'device_type'
|
||||
id: 'device_id'
|
||||
token: 'auth_token'
|
||||
```
|
||||
|
||||
{% configuration %}
|
||||
organization:
|
||||
description: The Organization ID for your Watson IoT Platform instance
|
||||
required: true
|
||||
type: string
|
||||
type:
|
||||
description: The device type for the gateway device to use
|
||||
required: true
|
||||
type: string
|
||||
id:
|
||||
description: The device id for the gateway device to use
|
||||
required: true
|
||||
type: string
|
||||
token:
|
||||
description: The authentication token for the gateway device
|
||||
required: true
|
||||
type: string
|
||||
exclude:
|
||||
description: Configure which components should be excluded from recording to Watson IoT Platform.
|
||||
required: false
|
||||
type: map
|
||||
keys:
|
||||
entities:
|
||||
description: The list of entity ids to be excluded from recording to Watson IoT Platform.
|
||||
required: false
|
||||
type: list
|
||||
domains:
|
||||
description: The list of domains to be excluded from recording to Watson IoT Platform.
|
||||
required: false
|
||||
type: list
|
||||
include:
|
||||
description: Configure which components should be included in recordings to Watson IoT Platform. If set, all other entities will not be recorded to Watson IoT Platform. Values set by the **blacklist** option will prevail.
|
||||
required: false
|
||||
type: map
|
||||
keys:
|
||||
entities:
|
||||
description: The list of entity ids to be included from recordings to Watson IoT Platform.
|
||||
required: false
|
||||
type: list
|
||||
domains:
|
||||
description: The list of domains to be included from recordings to Watson IoT Platform.
|
||||
required: false
|
||||
type: list
|
||||
{% endconfiguration %}
|
||||
|
||||
|
||||
## {% linkable_title Examples %}
|
||||
|
||||
### {% linkable_title Full configuration %}
|
||||
|
||||
```yaml
|
||||
watson_iot:
|
||||
|
||||
exclude:
|
||||
entities:
|
||||
- entity.id1
|
||||
- entity.id2
|
||||
domains:
|
||||
- automation
|
||||
include:
|
||||
entities:
|
||||
- entity.id3
|
||||
- entity.id4
|
||||
```
|
||||
44
source/_components/weather.ipma.markdown
Normal file
44
source/_components/weather.ipma.markdown
Normal file
@ -0,0 +1,44 @@
|
||||
---
|
||||
layout: page
|
||||
title: "IPMA"
|
||||
description: "Instructions on how to integrate Instituto Português do Mar e Atmosfera weather conditions into Home Assistant."
|
||||
date: 2018-05-31 17:00
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: ipma.png
|
||||
ha_category: Weather
|
||||
ha_release: 0.72
|
||||
ha_iot_class: "Cloud Polling"
|
||||
---
|
||||
|
||||
The `ipma` weather platform uses the [Instituto Português do Mar e Atmosfera](http://www.ipma.pt) as a source for current and forecast meteorological data.
|
||||
|
||||
## {% linkable_title Configuration %}
|
||||
|
||||
To add the IPMA weather platform to your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
weather:
|
||||
- platform: ipma
|
||||
```
|
||||
|
||||
{% configuration %}
|
||||
name:
|
||||
description: The name you would like to give to the weather station.
|
||||
required: false
|
||||
default: The name of the used station
|
||||
type: string
|
||||
latitude:
|
||||
description: Latitude of the location for which you want weather information.
|
||||
required: false
|
||||
default: Home Assistant global latitude configuration
|
||||
type: string
|
||||
longitude:
|
||||
description: Longitude of the location for which you want weather information.
|
||||
required: false
|
||||
default: Home Assistant global longitude configuration
|
||||
type: string
|
||||
{% endconfiguration %}
|
||||
@ -32,6 +32,7 @@ Configuration variables:
|
||||
|
||||
- **api_key** (*Required*): Your API key for http://openweathermap.org/.
|
||||
- **name** (*Optional*): Name to use in the frontend.
|
||||
- **mode** (*Optional*): Can specify `hourly` or `daily`. Select `hourly` for a three-hour forecast or `daily` for daily forecast. Defaults to `hourly`.
|
||||
- **latitude** (*Optional*): Latitude of the location to display the weather. Defaults to the latitude in your `configuration.yaml` file.
|
||||
- **longitude** (*Optional*): Longitude of the location to display the weather. Defaults to the longitude in your `configuration.yaml` file.
|
||||
|
||||
|
||||
47
source/_components/wirelesstag.markdown
Normal file
47
source/_components/wirelesstag.markdown
Normal file
@ -0,0 +1,47 @@
|
||||
---
|
||||
layout: page
|
||||
title: "WirelessTag"
|
||||
description: "Instructions on how to integrate your Wireless Tags sensors within Home Assistant."
|
||||
date: 2018-03-26 21:32
|
||||
comments: false
|
||||
sidebar: true
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: wirelesstag.png
|
||||
ha_category: Hub
|
||||
ha_iot_class: "Local Push and Cloud Polling"
|
||||
ha_release: 0.68
|
||||
---
|
||||
|
||||
The `wirelesstag` implementation allows you to integrate your [wirelesstag.net](http://wirelesstag.net) sensors tags in Home Assistant.
|
||||
|
||||
To enable tags set up with your [wirelesstag.net](http://wirelesstag.net) account, add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
wirelesstag:
|
||||
username: you@example.com
|
||||
password: secret
|
||||
```
|
||||
|
||||
{% configuration %}
|
||||
username:
|
||||
description: Username for your [wirelesstag.net](http://wirelesstag.net) account.
|
||||
required: true
|
||||
type: string
|
||||
password:
|
||||
description: Password for your [wirelesstag.net](http://wirelesstag.net) account.
|
||||
required: true
|
||||
type: string
|
||||
{% endconfiguration %}
|
||||
|
||||
Finish your configuration by visiting the [WirelessTag binary sensor](/components/binary_sensor.wirelesstag/), [WirelessTag sensor](/components/sensor.wirelesstag/), or [WirelessTag switch](/components/switch.wirelesstag/) documentation.
|
||||
|
||||
<p class='note'>
|
||||
To enable local push notifications from the Tags Manager, you need to add the IP address of the Tags Manager into whitelist in `http` component; i.e., add it to `trusted_networks`. See the [HTTP](/components/http/) for details.
|
||||
Additionally, you need add at least one [WirelessTag binary sensor](/components/binary_sensor.wirelesstag/) in config to start receiving local push notifications.
|
||||
</p>
|
||||
|
||||
<p class='note warning'>
|
||||
Tags Manager supports local push notifications for `http` schema only. So if your hass uses `https`, local push notifications are disabled and data is received via cloud polling.
|
||||
</p>
|
||||
502
source/_posts/2018-06-22-release-72.markdown
Normal file
502
source/_posts/2018-06-22-release-72.markdown
Normal file
@ -0,0 +1,502 @@
|
||||
---
|
||||
layout: post
|
||||
title: "0.72: Lovelace UI, KIWI Doorlocks, Wireless Tags, Insteon X10."
|
||||
description: "This release will blow you away. Click with caution."
|
||||
date: 2018-06-22 00:01:00
|
||||
date_formatted: "June 22, 2018"
|
||||
author: Paulus Schoutsen
|
||||
author_twitter: balloob
|
||||
comments: true
|
||||
categories: Release-Notes
|
||||
og_image: /images/blog/2018-06-release-0.72/lovelace.png
|
||||
---
|
||||
|
||||
I am super excited about this release as it brings some great examples of how we are refining the system to become more customizable and, at the same time, user friendly. The first thing that I am really excited about is a new experimental user interface that we call Lovelace. Check [this awesome rundown](https://gist.github.com/ciotlosm/9508388876edf92c4c1f3579e740fbd5) of all the features by [@ciotlosm]. The TL;DR: a faster, more customizable and more extensible UI with the same look and feel as the old one.
|
||||
|
||||
Be aware, this _is_ experimental, so things will change. However, we felt like we didn't want to keep this away from you any longer. Check the [Lovelace UI docs](https://developers.home-assistant.io/docs/en/lovelace_index.html) on how to get started. Make sure to share your creations!
|
||||
|
||||
Thanks to all the people that have been hanging out in the #beta channel on [Discord](https://discord.gg/c5DvZ4e) helping development, finding and squashing bugs and making suggestions. Especially thanks to [@c727] for all his development work and [@arsaboo] for being the first guinea pig.
|
||||
|
||||
<p class='img'>
|
||||
<img
|
||||
src='/images/blog/2018-06-release-0.72/lovelace.png'
|
||||
alt='Example user interface created using Lovelace.'
|
||||
>
|
||||
Example user interface created using Lovelace ([source](https://gist.github.com/ciotlosm/9508388876edf92c4c1f3579e740fbd5#file-ui-lovelace-yaml))
|
||||
</p>
|
||||
|
||||
Another change is that Nest, Sonos and Cast will now have to be configured using a config entry. Config entries can be created via the integrations page in the config panel. This is a concept that we have been developing for a couple of months now and it's our goal to eventually use this as the way to configure all components.
|
||||
|
||||
<p class='img'>
|
||||
<img
|
||||
src='/images/blog/2018-06-release-0.72/config_entry.png'
|
||||
alt='Screenshot of a browser showing a dialog to link a Nest account to Home Assistant.'
|
||||
>
|
||||
Screenshot of the Nest config entry.
|
||||
</p>
|
||||
|
||||
And as if this releases even needs more cool stuff, the Insteon integration now supports X10 thanks to [@teharris1]. It was a frequent requested feature from the Insteon community.
|
||||
|
||||
And finally, we'll be extending the open beta for Home Assistant Cloud until the first of September.
|
||||
|
||||
Enjoy this release and have a good weekend all!
|
||||
|
||||
## {% linkable_title New Platforms %}
|
||||
|
||||
- Weather Platform - IPMA ([@dgomes] - [#14716]) ([weather.ipma docs]) (new-platform)
|
||||
- Add Freebox device tracker ([@stilllman] - [#12727]) ([device_tracker.freebox docs]) (new-platform)
|
||||
- Add IBM Watson IoT Platform component ([@mtreinish] - [#13664]) ([watson_iot docs]) (new-platform)
|
||||
- Wireless tags platform ([@sergeymaysak] - [#13495]) ([wirelesstag docs]) ([binary_sensor.wirelesstag docs]) ([sensor.wirelesstag docs]) ([switch.wirelesstag docs]) (new-platform)
|
||||
- Add netgear_lte component ([@amelchio] - [#14687]) ([netgear_lte docs]) ([notify docs]) ([sensor.netgear_lte docs]) (new-platform)
|
||||
- Add Uptime Robot sensor ([@ludeeus] - [#14631]) ([binary_sensor.uptimerobot docs]) (new-platform)
|
||||
- Add support for the Unitymedia Horizon HD Recorder ([@benleb] - [#14275]) ([media_player.horizon docs]) (new-platform)
|
||||
- Add support for KIWI Door Locks ([@c7h] - [#14485]) ([lock.kiwi docs]) (new-platform)
|
||||
- Epson projector support ([@pszafer] - [#14841]) ([media_player.epson docs]) (new-platform)
|
||||
- Add sensor.nsw_fuel_station component ([@nickw444] - [#14757]) ([sensor.nsw_fuel_station docs]) (new-platform)
|
||||
- Add support for ZhongHong HVAC Controllers ([@crhan] - [#14552]) ([climate.zhong_hong docs]) (new-platform)
|
||||
- Xiaomi Cameras - multiple models ([@vaidyasr] - [#14244]) ([camera.xiaomi docs]) (new-platform)
|
||||
|
||||
## {% linkable_title 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). The release notes have comments enabled but it's preferred if you use the former communication channels. Thanks.
|
||||
|
||||
## {% linkable_title Reporting Issues %}
|
||||
|
||||
Experiencing issues introduced by this release? Please report them in our [issue tracker](https://github.com/home-assistant/home-assistant/issues). Make sure to fill in all fields of the issue template.
|
||||
|
||||
<!--more-->
|
||||
## {% linkable_title Breaking Changes %}
|
||||
|
||||
- For developers of custom panel: Remove ability to register panels directly with the frontend component. Register with custom panel component instead. ([@balloob] - [#14805]) ([frontend docs]) (breaking change)
|
||||
- Rename Hive hub friendly name to include "Hive" name ([@SteveEdson] - [#14747]) ([sensor.hive docs]) (breaking change)
|
||||
- Homematic: RotaryHandleSensorIP states will now report open, tilt, closed ([@hanzoh] - [#14885]) ([sensor.homematic docs]) (breaking change)
|
||||
- Add support for multiple Doorbird stations ([@oblogic7] - [#13994]) ([doorbird docs]) ([camera.doorbird docs]) ([switch.doorbird docs]) (breaking change)
|
||||
- AirVisual: The radius configuration parameter no longer does anything and has been removed. This won't negatively impact any existing integrations. Second, this PR will modify the unique IDs for each sensor to correctly include the locale. New unique IDs will now include _us_ and _cn_ ([@bachya] - [#14943]) ([sensor.airvisual docs]) (breaking change)
|
||||
- Sonos and Cast are now configured via config entries. Go to the integrations tab in config panel to set it up. ([@balloob] - [#14955]) ([media_player docs]) ([sonos docs]) ([media_player.sonos docs]) (breaking change)
|
||||
- Eight Sleep add REM type, Update async syntax, Catch API quirks ([@mezz64] - [#14937]) ([eight_sleep docs]) ([binary_sensor.eight_sleep docs]) ([sensor.eight_sleep docs]) (breaking change)
|
||||
- Fix energy meter for HS110 v2 users. Not a breaking change unless you are using a custom component ([@rytilahti] - [#15001]) ([light.tplink docs]) ([switch.tplink docs]) (breaking change) (beta fix)
|
||||
|
||||
## {% linkable_title Beta Fixes %}
|
||||
|
||||
- Remove load power attribute for channel USB ([@syssi] - [#14996]) ([switch.xiaomi_miio docs]) (beta fix)
|
||||
- Switch to own packaged version of spotipy ([@andrey-git] - [#14997]) ([media_player.spotify docs]) (beta fix)
|
||||
- Bump pyhs100 version ([@rytilahti] - [#15001]) ([light.tplink docs]) ([switch.tplink docs]) (breaking change) (beta fix)
|
||||
- Add experimental UI backend ([@balloob] - [#15002]) ([frontend docs]) (beta fix)
|
||||
- Fix panel URL authentication for Hass.io ([@pvizeli] - [#15024]) ([hassio docs]) (beta fix)
|
||||
- Fix linode I/O in state property ([@MartinHjelmare] - [#15010]) ([binary_sensor.linode docs]) ([switch.linode docs]) (beta fix)
|
||||
- Upgrade aiohttp to 3.3.2 ([@fabaff] - [#15025]) (beta fix)
|
||||
- Make zone entries work without radius ([@balloob] - [#15032]) ([zone docs]) (beta fix)
|
||||
- Bugfix empty entity lists ([@pvizeli] - [#15035]) (beta fix)
|
||||
- Rename experimental UI to lovelace ([@balloob] - [#15065]) ([frontend docs]) (beta fix)
|
||||
- X10 ([@teharris1] - [#14741]) ([insteon_plm docs]) ([switch.insteon_plm docs]) (beta fix)
|
||||
- Fix MQTT Light with RGB and Brightness ([@thinkl33t] - [#15053]) ([light.mqtt docs]) (beta fix)
|
||||
- Update Neato Library And Reduce Cloud Calls ([@dshokouhi] - [#15072]) ([neato docs]) ([camera.neato docs]) ([switch.neato docs]) ([vacuum.neato docs]) (beta fix)
|
||||
|
||||
## {% linkable_title All changes %}
|
||||
|
||||
- Weather Platform - IPMA ([@dgomes] - [#14716]) ([weather.ipma docs]) (new-platform)
|
||||
- Add additional 86sw model identifier of the LAN protocol V2 ([@syssi] - [#14799]) ([xiaomi_aqara docs]) ([binary_sensor.xiaomi_aqara docs])
|
||||
- Allow Kodi live streams to be recognized as paused ([@quthla] - [#14623]) ([media_player.kodi docs])
|
||||
- Update syntax ([@fabaff] - [#14812]) ([sensor.moon docs])
|
||||
- Use pihole module to get data ([@fabaff] - [#14809]) ([sensor.pi_hole docs])
|
||||
- Bump python-miio version (Closes: #13749) ([@syssi] - [#14796]) ([device_tracker docs]) ([fan.xiaomi_miio docs]) ([light.xiaomi_miio docs]) ([remote.xiaomi_miio docs]) ([sensor.xiaomi_miio docs]) ([switch.xiaomi_miio docs]) ([vacuum.xiaomi_miio docs])
|
||||
- Further cleanup frontend ([@balloob] - [#14805]) ([frontend docs]) (breaking change)
|
||||
- netatmo api is now in pip as pyatmo ([@jabesq] - [#14824]) ([netatmo docs]) ([binary_sensor.netatmo docs]) ([camera.netatmo docs]) ([climate.netatmo docs]) ([sensor.netatmo docs])
|
||||
- Action parameter doesn't longer have to be the first parameter ([@GruberMischa] - [#14815]) ([binary_sensor.mystrom docs])
|
||||
- Fixes an issue in Xiaomi TV platform that would some TVs not sleep correctly ([@simse] - [#14829]) ([media_player.xiaomi_tv docs])
|
||||
- Improved Fritz!Box thermostat support ([@thomaskr] - [#14789]) ([climate.fritzbox docs])
|
||||
- Add Freebox device tracker ([@stilllman] - [#12727]) ([device_tracker.freebox docs]) (new-platform)
|
||||
- Migrate entity registry to using websocket ([@balloob] - [#14830]) ([config docs])
|
||||
- Route themes and translations over websocket ([@balloob] - [#14828]) ([frontend docs]) ([websocket_api docs])
|
||||
- Feature/gearbest library update (Closes: #14813) ([@HerrHofrat] - [#14833]) ([sensor.gearbest docs])
|
||||
- Ignore the mistaken long_both_click event of the 86sw (Closes: #14802) ([@syssi] - [#14808]) ([binary_sensor.xiaomi_aqara docs])
|
||||
- Fix non awaited test ([@balloob] - [#14854])
|
||||
- Update Hue flow title ([@balloob] - [#14852]) ([hue docs])
|
||||
- Upgrade Mastodon.py to 1.3.0 ([@fabaff] - [#14858])
|
||||
- Improvements to LIFX reliability ([@amelchio] - [#14848]) ([light.lifx docs])
|
||||
- Add general sound mode support ([@starkillerOG] - [#14729]) ([media_player docs])
|
||||
- Add IBM Watson IoT Platform component ([@mtreinish] - [#13664]) ([watson_iot docs]) (new-platform)
|
||||
- Upgrade aiohttp to 3.3.0 ([@fabaff] - [#14766])
|
||||
- Add min_temp and max_temp to MQTT climate device ([@PhilRW] - [#14690]) ([climate.mqtt docs])
|
||||
- Store config entry id in entity registry ([@balloob] - [#14851])
|
||||
- Catch ConnectionError (fixes #14241) ([@fabaff] - [#14748]) ([media_player.yamaha docs])
|
||||
- Don't run unnecessary methods in executor pool ([@balloob] - [#14853])
|
||||
- Wireless tags platform ([@sergeymaysak] - [#13495]) ([wirelesstag docs]) ([binary_sensor.wirelesstag docs]) ([sensor.wirelesstag docs]) ([switch.wirelesstag docs]) (new-platform)
|
||||
- Fix door/window sensor support of the Xiaomi Aqara LAN protocol V2 (Closes: #14775) ([@syssi] - [#14777]) ([binary_sensor.xiaomi_aqara docs])
|
||||
- zha: handle "step_with_on_off" cluster command in LevelListener. ([@Adminiuga] - [#14756]) ([binary_sensor.zha docs])
|
||||
- Rename Hive hub friendly name ([@SteveEdson] - [#14747]) ([sensor.hive docs]) (breaking change)
|
||||
- Add set_default_level to logger ([@dale3h] - [#14703]) ([logger docs])
|
||||
- Fix unit conversion ([@dgomes] - [#14730]) ([climate.generic_thermostat docs]) ([climate.sensibo docs]) ([climate.tado docs])
|
||||
- Disable volume control for Onkyo when unavailable (Closes: #14774) ([@snikch] - [#14863]) ([media_player.onkyo docs])
|
||||
- Add netgear_lte component ([@amelchio] - [#14687]) ([netgear_lte docs]) ([notify docs]) ([sensor.netgear_lte docs]) (new-platform)
|
||||
- Add support for new hass.io panel ([@balloob] - [#14873]) ([hassio docs]) ([panel_custom docs])
|
||||
- Add color_status sensor for Nest Protect ([@awarecan] - [#14868]) ([sensor.nest docs])
|
||||
- UVC camera platform handling unavailable NVR or cameras better ([@exxamalte] - [#14864]) ([camera.uvc docs])
|
||||
- Samsung TV can't turn off after idle period ([@ejel] - [#14587]) ([media_player.samsungtv docs])
|
||||
- Discover Qubino ZMHTDx smart meter switches ([@turbokongen] - [#14884]) ([zwave docs])
|
||||
- Add missing mapping of RotaryHandleSensorIP states ([@hanzoh] - [#14885]) ([sensor.homematic docs]) (breaking change)
|
||||
- Add entity registry support to media_player.snapcast ([@jedi7] - [#14895]) ([media_player.snapcast docs])
|
||||
- Allow different identifiers for the CPU temperature (fixes #10104) ([@fabaff] - [#14898]) ([sensor.glances docs])
|
||||
- Make RainMachine async ([@bachya] - [#14879]) ([rainmachine docs]) ([binary_sensor.rainmachine docs]) ([sensor.rainmachine docs]) ([switch.rainmachine docs])
|
||||
- Add Uptime Robot sensor ([@ludeeus] - [#14631]) ([binary_sensor.uptimerobot docs]) (new-platform)
|
||||
- Upgrade python_opendata_transport to 0.1.3 ([@fabaff] - [#14905]) ([sensor.swiss_public_transport docs])
|
||||
- Upgrade psutil to 5.4.6 ([@fabaff] - [#14892]) ([sensor.systemmonitor docs])
|
||||
- Upgrade sendgrid to 5.4.0 ([@fabaff] - [#14891]) ([notify docs])
|
||||
- Upgrade python-mystrom to 0.4.4 ([@fabaff] - [#14889]) ([light.mystrom docs]) ([switch.mystrom docs])
|
||||
- Upgrade pylast to 2.3.0 ([@fabaff] - [#14888]) ([sensor.lastfm docs])
|
||||
- Added daily and hourly modes to Openweathermap ([@sgttrs] - [#14875]) ([weather.openweathermap docs])
|
||||
- Bump to denonavr 0.7.3 ([@klada] - [#14907]) ([media_player.denonavr docs])
|
||||
- Add api_host option to Konnected config ([@heythisisnate] - [#14896]) ([konnected docs])
|
||||
- Add support for the Unitymedia Horizon HD Recorder ([@benleb] - [#14275]) ([media_player.horizon docs]) (new-platform)
|
||||
- Add support for multiple Doorbird stations ([@oblogic7] - [#13994]) ([doorbird docs]) ([camera.doorbird docs]) ([switch.doorbird docs]) (breaking change)
|
||||
- Update mqtt_eventstream.py ([@molobrakos] - [#14923]) ([mqtt_eventstream docs])
|
||||
- Upgrade python-nest, add security_state sensor, nest.set_mode service set ETA as well ([@awarecan] - [#14901]) ([nest docs]) ([sensor.nest docs])
|
||||
- Add more test cases for samsungtv ([@ejel] - [#14900])
|
||||
- Refactored Arlo component and enhanced Arlo API queries and times ([@tchellomello] - [#14823]) ([arlo docs]) ([alarm_control_panel.arlo docs]) ([camera.arlo docs]) ([sensor.arlo docs])
|
||||
- Use cv.time_period instead of cv.time_period_str ([@awarecan] - [#14938]) ([nest docs])
|
||||
- Add support for KIWI Door Locks ([@c7h] - [#14485]) ([lock.kiwi docs]) (new-platform)
|
||||
- Fix snapcast uuid to be more unique ([@jedi7] - [#14925]) ([media_player.snapcast docs])
|
||||
- pytradfri 5.5.1: Improved 3rd party bulb support ([@Hate-Usernames] - [#14887]) ([tradfri docs]) ([light.tradfri docs])
|
||||
- Epson projector support ([@pszafer] - [#14841]) ([media_player.epson docs]) (new-platform)
|
||||
- Add scan_interval to RainMachine ([@bachya] - [#14945]) ([rainmachine docs])
|
||||
- Myq update from 0.0.8 to 0.0.11 ([@arraylabs] - [#14947]) ([cover.myq docs])
|
||||
- Upgrade pylint to 1.9.2 ([@scop] - [#14916])
|
||||
- Update python-wink to 1.8.0 ([@vickyg3] - [#14894]) ([wink docs])
|
||||
- Add unique_id for mqtt binary sensor ([@ciotlosm] - [#14929]) ([binary_sensor.mqtt docs])
|
||||
- Make Yi platform async ([@bachya] - [#14944]) ([camera.yi docs])
|
||||
- Nest config flow ([@balloob] - [#14921]) ([nest docs])
|
||||
- Fix Facebox face data parsing ([@robmarkcole] - [#14951]) ([image_processing.facebox docs])
|
||||
- Add sensor.nsw_fuel_station component ([@nickw444] - [#14757]) ([sensor.nsw_fuel_station docs]) (new-platform)
|
||||
- Make AirVisual platform async + other adjustments ([@bachya] - [#14943]) ([sensor.airvisual docs]) (breaking change)
|
||||
- Add support for ZhongHong HVAC Controllers ([@crhan] - [#14552]) ([climate.zhong_hong docs]) (new-platform)
|
||||
- Fix tests ([@balloob] - [#14959])
|
||||
- add relative time option to simulated sensors ([@Shou] - [#14038]) ([sensor.simulated docs])
|
||||
- Add config entry for Sonos + Cast ([@balloob] - [#14955]) ([media_player docs]) ([sonos docs]) ([media_player.sonos docs]) (breaking change)
|
||||
- Fix smappee component - "Error on device update" ([@bachya] - [#14883]) ([sensor.smappee docs])
|
||||
- Adhere to scan_interval in platforms when setup via config entry ([@balloob] - [#14969])
|
||||
- Add Calendar API endpoint to get events ([@titilambert] - [#14702]) ([calendar docs]) ([calendar.caldav docs])
|
||||
- Add calendar panel, add tests ([@balloob] - [#14973]) ([calendar docs])
|
||||
- Xiaomi Cameras - multiple models ([@vaidyasr] - [#14244]) ([camera.xiaomi docs]) (new-platform)
|
||||
- Fix binary_sensor.skybell state update when there are no events ([@trisk] - [#14927]) ([binary_sensor.skybell docs]) ([sensor.skybell docs])
|
||||
- Deconz make groups configurable ([@Kane610] - [#14704]) ([deconz docs]) ([light.deconz docs])
|
||||
- Show notification when user configures Nest client_id/secret ([@balloob] - [#14970]) ([hue docs]) ([nest docs])
|
||||
- Eight Sleep add REM type, Update async syntax, Catch API quirks ([@mezz64] - [#14937]) ([eight_sleep docs]) ([binary_sensor.eight_sleep docs]) ([sensor.eight_sleep docs]) (breaking change)
|
||||
- Return ISO formated datetime in forecast ([@c727] - [#14975]) ([weather.ecobee docs])
|
||||
- Remove inline pylint disables for messages disabled in pylintrc ([@scop] - [#14978])
|
||||
- Add availability to Rflink entities. ([@aequitas] - [#14977]) ([rflink docs])
|
||||
- Upgrade ring_doorbell to 0.2.1 to fix oauth issues ([@tchellomello] - [#14984]) ([ring docs])
|
||||
- Fix extended package support ([@cdce8p] - [#14980])
|
||||
- Upgraded PyArlo to 0.1.7 ([@tchellomello] - [#14987]) ([arlo docs])
|
||||
- Upgraded python-amcrest to 1.2.3 ([@tchellomello] - [#14988]) ([amcrest docs])
|
||||
- Upgraded RainCloudy to version 0.0.5 ([@tchellomello] - [#14986]) ([raincloud docs])
|
||||
- Do not mount deps folder when running in virtual env ([@balloob] - [#14993])
|
||||
- Refactoring camera component to use async/await syntax. ([@awarecan] - [#14990]) ([camera docs])
|
||||
- Remove load power attribute for channel USB ([@syssi] - [#14996]) ([switch.xiaomi_miio docs]) (beta fix)
|
||||
- Switch to own packaged version of spotipy ([@andrey-git] - [#14997]) ([media_player.spotify docs]) (beta fix)
|
||||
- Bump pyhs100 version ([@rytilahti] - [#15001]) ([light.tplink docs]) ([switch.tplink docs]) (breaking change) (beta fix)
|
||||
- Add experimental UI backend ([@balloob] - [#15002]) ([frontend docs]) (beta fix)
|
||||
- Fix panel URL authentication for Hass.io ([@pvizeli] - [#15024]) ([hassio docs]) (beta fix)
|
||||
- Fix linode I/O in state property ([@MartinHjelmare] - [#15010]) ([binary_sensor.linode docs]) ([switch.linode docs]) (beta fix)
|
||||
- Upgrade aiohttp to 3.3.2 ([@fabaff] - [#15025]) (beta fix)
|
||||
- Make zone entries work without radius ([@balloob] - [#15032]) ([zone docs]) (beta fix)
|
||||
- Bugfix empty entity lists ([@pvizeli] - [#15035]) (beta fix)
|
||||
- Rename experimental UI to lovelace ([@balloob] - [#15065]) ([frontend docs]) (beta fix)
|
||||
- X10 ([@teharris1] - [#14741]) ([insteon_plm docs]) ([switch.insteon_plm docs]) (beta fix)
|
||||
- Fix MQTT Light with RGB and Brightness ([@thinkl33t] - [#15053]) ([light.mqtt docs]) (beta fix)
|
||||
- Update Neato Library And Reduce Cloud Calls ([@dshokouhi] - [#15072]) ([neato docs]) ([camera.neato docs]) ([switch.neato docs]) ([vacuum.neato docs]) (beta fix)
|
||||
|
||||
[#12727]: https://github.com/home-assistant/home-assistant/pull/12727
|
||||
[#13495]: https://github.com/home-assistant/home-assistant/pull/13495
|
||||
[#13664]: https://github.com/home-assistant/home-assistant/pull/13664
|
||||
[#13994]: https://github.com/home-assistant/home-assistant/pull/13994
|
||||
[#14038]: https://github.com/home-assistant/home-assistant/pull/14038
|
||||
[#14244]: https://github.com/home-assistant/home-assistant/pull/14244
|
||||
[#14275]: https://github.com/home-assistant/home-assistant/pull/14275
|
||||
[#14485]: https://github.com/home-assistant/home-assistant/pull/14485
|
||||
[#14552]: https://github.com/home-assistant/home-assistant/pull/14552
|
||||
[#14587]: https://github.com/home-assistant/home-assistant/pull/14587
|
||||
[#14623]: https://github.com/home-assistant/home-assistant/pull/14623
|
||||
[#14631]: https://github.com/home-assistant/home-assistant/pull/14631
|
||||
[#14687]: https://github.com/home-assistant/home-assistant/pull/14687
|
||||
[#14690]: https://github.com/home-assistant/home-assistant/pull/14690
|
||||
[#14702]: https://github.com/home-assistant/home-assistant/pull/14702
|
||||
[#14703]: https://github.com/home-assistant/home-assistant/pull/14703
|
||||
[#14704]: https://github.com/home-assistant/home-assistant/pull/14704
|
||||
[#14716]: https://github.com/home-assistant/home-assistant/pull/14716
|
||||
[#14729]: https://github.com/home-assistant/home-assistant/pull/14729
|
||||
[#14730]: https://github.com/home-assistant/home-assistant/pull/14730
|
||||
[#14741]: https://github.com/home-assistant/home-assistant/pull/14741
|
||||
[#14747]: https://github.com/home-assistant/home-assistant/pull/14747
|
||||
[#14748]: https://github.com/home-assistant/home-assistant/pull/14748
|
||||
[#14756]: https://github.com/home-assistant/home-assistant/pull/14756
|
||||
[#14757]: https://github.com/home-assistant/home-assistant/pull/14757
|
||||
[#14766]: https://github.com/home-assistant/home-assistant/pull/14766
|
||||
[#14777]: https://github.com/home-assistant/home-assistant/pull/14777
|
||||
[#14789]: https://github.com/home-assistant/home-assistant/pull/14789
|
||||
[#14796]: https://github.com/home-assistant/home-assistant/pull/14796
|
||||
[#14799]: https://github.com/home-assistant/home-assistant/pull/14799
|
||||
[#14805]: https://github.com/home-assistant/home-assistant/pull/14805
|
||||
[#14808]: https://github.com/home-assistant/home-assistant/pull/14808
|
||||
[#14809]: https://github.com/home-assistant/home-assistant/pull/14809
|
||||
[#14812]: https://github.com/home-assistant/home-assistant/pull/14812
|
||||
[#14815]: https://github.com/home-assistant/home-assistant/pull/14815
|
||||
[#14823]: https://github.com/home-assistant/home-assistant/pull/14823
|
||||
[#14824]: https://github.com/home-assistant/home-assistant/pull/14824
|
||||
[#14828]: https://github.com/home-assistant/home-assistant/pull/14828
|
||||
[#14829]: https://github.com/home-assistant/home-assistant/pull/14829
|
||||
[#14830]: https://github.com/home-assistant/home-assistant/pull/14830
|
||||
[#14833]: https://github.com/home-assistant/home-assistant/pull/14833
|
||||
[#14841]: https://github.com/home-assistant/home-assistant/pull/14841
|
||||
[#14848]: https://github.com/home-assistant/home-assistant/pull/14848
|
||||
[#14851]: https://github.com/home-assistant/home-assistant/pull/14851
|
||||
[#14852]: https://github.com/home-assistant/home-assistant/pull/14852
|
||||
[#14853]: https://github.com/home-assistant/home-assistant/pull/14853
|
||||
[#14854]: https://github.com/home-assistant/home-assistant/pull/14854
|
||||
[#14858]: https://github.com/home-assistant/home-assistant/pull/14858
|
||||
[#14863]: https://github.com/home-assistant/home-assistant/pull/14863
|
||||
[#14864]: https://github.com/home-assistant/home-assistant/pull/14864
|
||||
[#14868]: https://github.com/home-assistant/home-assistant/pull/14868
|
||||
[#14873]: https://github.com/home-assistant/home-assistant/pull/14873
|
||||
[#14875]: https://github.com/home-assistant/home-assistant/pull/14875
|
||||
[#14879]: https://github.com/home-assistant/home-assistant/pull/14879
|
||||
[#14883]: https://github.com/home-assistant/home-assistant/pull/14883
|
||||
[#14884]: https://github.com/home-assistant/home-assistant/pull/14884
|
||||
[#14885]: https://github.com/home-assistant/home-assistant/pull/14885
|
||||
[#14887]: https://github.com/home-assistant/home-assistant/pull/14887
|
||||
[#14888]: https://github.com/home-assistant/home-assistant/pull/14888
|
||||
[#14889]: https://github.com/home-assistant/home-assistant/pull/14889
|
||||
[#14891]: https://github.com/home-assistant/home-assistant/pull/14891
|
||||
[#14892]: https://github.com/home-assistant/home-assistant/pull/14892
|
||||
[#14894]: https://github.com/home-assistant/home-assistant/pull/14894
|
||||
[#14895]: https://github.com/home-assistant/home-assistant/pull/14895
|
||||
[#14896]: https://github.com/home-assistant/home-assistant/pull/14896
|
||||
[#14898]: https://github.com/home-assistant/home-assistant/pull/14898
|
||||
[#14900]: https://github.com/home-assistant/home-assistant/pull/14900
|
||||
[#14901]: https://github.com/home-assistant/home-assistant/pull/14901
|
||||
[#14905]: https://github.com/home-assistant/home-assistant/pull/14905
|
||||
[#14907]: https://github.com/home-assistant/home-assistant/pull/14907
|
||||
[#14916]: https://github.com/home-assistant/home-assistant/pull/14916
|
||||
[#14921]: https://github.com/home-assistant/home-assistant/pull/14921
|
||||
[#14923]: https://github.com/home-assistant/home-assistant/pull/14923
|
||||
[#14925]: https://github.com/home-assistant/home-assistant/pull/14925
|
||||
[#14927]: https://github.com/home-assistant/home-assistant/pull/14927
|
||||
[#14929]: https://github.com/home-assistant/home-assistant/pull/14929
|
||||
[#14937]: https://github.com/home-assistant/home-assistant/pull/14937
|
||||
[#14938]: https://github.com/home-assistant/home-assistant/pull/14938
|
||||
[#14943]: https://github.com/home-assistant/home-assistant/pull/14943
|
||||
[#14944]: https://github.com/home-assistant/home-assistant/pull/14944
|
||||
[#14945]: https://github.com/home-assistant/home-assistant/pull/14945
|
||||
[#14947]: https://github.com/home-assistant/home-assistant/pull/14947
|
||||
[#14951]: https://github.com/home-assistant/home-assistant/pull/14951
|
||||
[#14955]: https://github.com/home-assistant/home-assistant/pull/14955
|
||||
[#14959]: https://github.com/home-assistant/home-assistant/pull/14959
|
||||
[#14969]: https://github.com/home-assistant/home-assistant/pull/14969
|
||||
[#14970]: https://github.com/home-assistant/home-assistant/pull/14970
|
||||
[#14973]: https://github.com/home-assistant/home-assistant/pull/14973
|
||||
[#14975]: https://github.com/home-assistant/home-assistant/pull/14975
|
||||
[#14977]: https://github.com/home-assistant/home-assistant/pull/14977
|
||||
[#14978]: https://github.com/home-assistant/home-assistant/pull/14978
|
||||
[#14980]: https://github.com/home-assistant/home-assistant/pull/14980
|
||||
[#14984]: https://github.com/home-assistant/home-assistant/pull/14984
|
||||
[#14986]: https://github.com/home-assistant/home-assistant/pull/14986
|
||||
[#14987]: https://github.com/home-assistant/home-assistant/pull/14987
|
||||
[#14988]: https://github.com/home-assistant/home-assistant/pull/14988
|
||||
[#14990]: https://github.com/home-assistant/home-assistant/pull/14990
|
||||
[#14993]: https://github.com/home-assistant/home-assistant/pull/14993
|
||||
[#14996]: https://github.com/home-assistant/home-assistant/pull/14996
|
||||
[#14997]: https://github.com/home-assistant/home-assistant/pull/14997
|
||||
[#15001]: https://github.com/home-assistant/home-assistant/pull/15001
|
||||
[#15002]: https://github.com/home-assistant/home-assistant/pull/15002
|
||||
[#15010]: https://github.com/home-assistant/home-assistant/pull/15010
|
||||
[#15024]: https://github.com/home-assistant/home-assistant/pull/15024
|
||||
[#15025]: https://github.com/home-assistant/home-assistant/pull/15025
|
||||
[#15032]: https://github.com/home-assistant/home-assistant/pull/15032
|
||||
[#15035]: https://github.com/home-assistant/home-assistant/pull/15035
|
||||
[#15053]: https://github.com/home-assistant/home-assistant/pull/15053
|
||||
[#15065]: https://github.com/home-assistant/home-assistant/pull/15065
|
||||
[#15072]: https://github.com/home-assistant/home-assistant/pull/15072
|
||||
[@Adminiuga]: https://github.com/Adminiuga
|
||||
[@GruberMischa]: https://github.com/GruberMischa
|
||||
[@Hate-Usernames]: https://github.com/Hate-Usernames
|
||||
[@HerrHofrat]: https://github.com/HerrHofrat
|
||||
[@Kane610]: https://github.com/Kane610
|
||||
[@MartinHjelmare]: https://github.com/MartinHjelmare
|
||||
[@PhilRW]: https://github.com/PhilRW
|
||||
[@Shou]: https://github.com/Shou
|
||||
[@SteveEdson]: https://github.com/SteveEdson
|
||||
[@aequitas]: https://github.com/aequitas
|
||||
[@amelchio]: https://github.com/amelchio
|
||||
[@arsaboo]: https://github.com/arsaboo
|
||||
[@andrey-git]: https://github.com/andrey-git
|
||||
[@arraylabs]: https://github.com/arraylabs
|
||||
[@awarecan]: https://github.com/awarecan
|
||||
[@bachya]: https://github.com/bachya
|
||||
[@balloob]: https://github.com/balloob
|
||||
[@benleb]: https://github.com/benleb
|
||||
[@c727]: https://github.com/c727
|
||||
[@c7h]: https://github.com/c7h
|
||||
[@cdce8p]: https://github.com/cdce8p
|
||||
[@ciotlosm]: https://github.com/ciotlosm
|
||||
[@crhan]: https://github.com/crhan
|
||||
[@dale3h]: https://github.com/dale3h
|
||||
[@dgomes]: https://github.com/dgomes
|
||||
[@dshokouhi]: https://github.com/dshokouhi
|
||||
[@ejel]: https://github.com/ejel
|
||||
[@exxamalte]: https://github.com/exxamalte
|
||||
[@fabaff]: https://github.com/fabaff
|
||||
[@hanzoh]: https://github.com/hanzoh
|
||||
[@heythisisnate]: https://github.com/heythisisnate
|
||||
[@jabesq]: https://github.com/jabesq
|
||||
[@jedi7]: https://github.com/jedi7
|
||||
[@klada]: https://github.com/klada
|
||||
[@ludeeus]: https://github.com/ludeeus
|
||||
[@mezz64]: https://github.com/mezz64
|
||||
[@molobrakos]: https://github.com/molobrakos
|
||||
[@mtreinish]: https://github.com/mtreinish
|
||||
[@nickw444]: https://github.com/nickw444
|
||||
[@oblogic7]: https://github.com/oblogic7
|
||||
[@pszafer]: https://github.com/pszafer
|
||||
[@pvizeli]: https://github.com/pvizeli
|
||||
[@quthla]: https://github.com/quthla
|
||||
[@robmarkcole]: https://github.com/robmarkcole
|
||||
[@rytilahti]: https://github.com/rytilahti
|
||||
[@scop]: https://github.com/scop
|
||||
[@sergeymaysak]: https://github.com/sergeymaysak
|
||||
[@sgttrs]: https://github.com/sgttrs
|
||||
[@simse]: https://github.com/simse
|
||||
[@snikch]: https://github.com/snikch
|
||||
[@starkillerOG]: https://github.com/starkillerOG
|
||||
[@stilllman]: https://github.com/stilllman
|
||||
[@syssi]: https://github.com/syssi
|
||||
[@tchellomello]: https://github.com/tchellomello
|
||||
[@teharris1]: https://github.com/teharris1
|
||||
[@thinkl33t]: https://github.com/thinkl33t
|
||||
[@thomaskr]: https://github.com/thomaskr
|
||||
[@titilambert]: https://github.com/titilambert
|
||||
[@trisk]: https://github.com/trisk
|
||||
[@turbokongen]: https://github.com/turbokongen
|
||||
[@vaidyasr]: https://github.com/vaidyasr
|
||||
[@vickyg3]: https://github.com/vickyg3
|
||||
[alarm_control_panel.arlo docs]: /components/alarm_control_panel.arlo/
|
||||
[amcrest docs]: /components/amcrest/
|
||||
[arlo docs]: /components/arlo/
|
||||
[binary_sensor.eight_sleep docs]: /components/binary_sensor.eight_sleep/
|
||||
[binary_sensor.linode docs]: /components/binary_sensor.linode/
|
||||
[binary_sensor.mqtt docs]: /components/binary_sensor.mqtt/
|
||||
[binary_sensor.mystrom docs]: /components/binary_sensor.mystrom/
|
||||
[binary_sensor.netatmo docs]: /components/binary_sensor.netatmo/
|
||||
[binary_sensor.rainmachine docs]: /components/binary_sensor.rainmachine/
|
||||
[binary_sensor.skybell docs]: /components/binary_sensor.skybell/
|
||||
[binary_sensor.uptimerobot docs]: /components/binary_sensor.uptimerobot/
|
||||
[binary_sensor.wirelesstag docs]: /components/binary_sensor.wirelesstag/
|
||||
[binary_sensor.xiaomi_aqara docs]: /components/binary_sensor.xiaomi_aqara/
|
||||
[binary_sensor.zha docs]: /components/binary_sensor.zha/
|
||||
[calendar docs]: /components/calendar/
|
||||
[calendar.caldav docs]: /components/calendar.caldav/
|
||||
[camera docs]: /components/camera/
|
||||
[camera.arlo docs]: /components/camera.arlo/
|
||||
[camera.doorbird docs]: /components/camera.doorbird/
|
||||
[camera.neato docs]: /components/camera.neato/
|
||||
[camera.netatmo docs]: /components/camera.netatmo/
|
||||
[camera.uvc docs]: /components/camera.uvc/
|
||||
[camera.xiaomi docs]: /components/camera.xiaomi/
|
||||
[camera.yi docs]: /components/camera.yi/
|
||||
[climate.fritzbox docs]: /components/climate.fritzbox/
|
||||
[climate.generic_thermostat docs]: /components/climate.generic_thermostat/
|
||||
[climate.mqtt docs]: /components/climate.mqtt/
|
||||
[climate.netatmo docs]: /components/climate.netatmo/
|
||||
[climate.sensibo docs]: /components/climate.sensibo/
|
||||
[climate.tado docs]: /components/climate.tado/
|
||||
[climate.zhong_hong docs]: /components/climate.zhong_hong/
|
||||
[config docs]: /components/config/
|
||||
[cover.myq docs]: /components/cover.myq/
|
||||
[deconz docs]: /components/deconz/
|
||||
[device_tracker docs]: /components/device_tracker/
|
||||
[device_tracker.freebox docs]: /components/device_tracker.freebox/
|
||||
[doorbird docs]: /components/doorbird/
|
||||
[eight_sleep docs]: /components/eight_sleep/
|
||||
[fan.xiaomi_miio docs]: /components/fan.xiaomi_miio/
|
||||
[frontend docs]: /components/frontend/
|
||||
[hassio docs]: /components/hassio/
|
||||
[hue docs]: /components/hue/
|
||||
[image_processing.facebox docs]: /components/image_processing.facebox/
|
||||
[insteon_plm docs]: /components/insteon_plm/
|
||||
[konnected docs]: /components/konnected/
|
||||
[light.deconz docs]: /components/light.deconz/
|
||||
[light.lifx docs]: /components/light.lifx/
|
||||
[light.mqtt docs]: /components/light.mqtt/
|
||||
[light.mystrom docs]: /components/light.mystrom/
|
||||
[light.tplink docs]: /components/light.tplink/
|
||||
[light.tradfri docs]: /components/light.tradfri/
|
||||
[light.xiaomi_miio docs]: /components/light.xiaomi_miio/
|
||||
[lock.kiwi docs]: /components/lock.kiwi/
|
||||
[logger docs]: /components/logger/
|
||||
[media_player docs]: /components/media_player/
|
||||
[media_player.denonavr docs]: /components/media_player.denonavr/
|
||||
[media_player.epson docs]: /components/media_player.epson/
|
||||
[media_player.horizon docs]: /components/media_player.horizon/
|
||||
[media_player.kodi docs]: /components/media_player.kodi/
|
||||
[media_player.onkyo docs]: /components/media_player.onkyo/
|
||||
[media_player.samsungtv docs]: /components/media_player.samsungtv/
|
||||
[media_player.snapcast docs]: /components/media_player.snapcast/
|
||||
[media_player.sonos docs]: /components/media_player.sonos/
|
||||
[media_player.spotify docs]: /components/media_player.spotify/
|
||||
[media_player.xiaomi_tv docs]: /components/media_player.xiaomi_tv/
|
||||
[media_player.yamaha docs]: /components/media_player.yamaha/
|
||||
[mqtt_eventstream docs]: /components/mqtt_eventstream/
|
||||
[neato docs]: /components/neato/
|
||||
[nest docs]: /components/nest/
|
||||
[netatmo docs]: /components/netatmo/
|
||||
[netgear_lte docs]: /components/netgear_lte/
|
||||
[notify docs]: /components/notify/
|
||||
[panel_custom docs]: /components/panel_custom/
|
||||
[raincloud docs]: /components/raincloud/
|
||||
[rainmachine docs]: /components/rainmachine/
|
||||
[remote.xiaomi_miio docs]: /components/remote.xiaomi_miio/
|
||||
[rflink docs]: /components/rflink/
|
||||
[ring docs]: /components/ring/
|
||||
[sensor.airvisual docs]: /components/sensor.airvisual/
|
||||
[sensor.arlo docs]: /components/sensor.arlo/
|
||||
[sensor.eight_sleep docs]: /components/sensor.eight_sleep/
|
||||
[sensor.gearbest docs]: /components/sensor.gearbest/
|
||||
[sensor.glances docs]: /components/sensor.glances/
|
||||
[sensor.hive docs]: /components/sensor.hive/
|
||||
[sensor.homematic docs]: /components/sensor.homematic/
|
||||
[sensor.lastfm docs]: /components/sensor.lastfm/
|
||||
[sensor.moon docs]: /components/sensor.moon/
|
||||
[sensor.nest docs]: /components/sensor.nest/
|
||||
[sensor.netatmo docs]: /components/sensor.netatmo/
|
||||
[sensor.netgear_lte docs]: /components/sensor.netgear_lte/
|
||||
[sensor.nsw_fuel_station docs]: /components/sensor.nsw_fuel_station/
|
||||
[sensor.pi_hole docs]: /components/sensor.pi_hole/
|
||||
[sensor.rainmachine docs]: /components/sensor.rainmachine/
|
||||
[sensor.simulated docs]: /components/sensor.simulated/
|
||||
[sensor.skybell docs]: /components/sensor.skybell/
|
||||
[sensor.smappee docs]: /components/sensor.smappee/
|
||||
[sensor.swiss_public_transport docs]: /components/sensor.swiss_public_transport/
|
||||
[sensor.systemmonitor docs]: /components/sensor.systemmonitor/
|
||||
[sensor.wirelesstag docs]: /components/sensor.wirelesstag/
|
||||
[sensor.xiaomi_miio docs]: /components/sensor.xiaomi_miio/
|
||||
[sonos docs]: /components/sonos/
|
||||
[switch.doorbird docs]: /components/switch.doorbird/
|
||||
[switch.insteon_plm docs]: /components/switch.insteon_plm/
|
||||
[switch.linode docs]: /components/switch.linode/
|
||||
[switch.mystrom docs]: /components/switch.mystrom/
|
||||
[switch.neato docs]: /components/switch.neato/
|
||||
[switch.rainmachine docs]: /components/switch.rainmachine/
|
||||
[switch.tplink docs]: /components/switch.tplink/
|
||||
[switch.wirelesstag docs]: /components/switch.wirelesstag/
|
||||
[switch.xiaomi_miio docs]: /components/switch.xiaomi_miio/
|
||||
[tradfri docs]: /components/tradfri/
|
||||
[vacuum.neato docs]: /components/vacuum.neato/
|
||||
[vacuum.xiaomi_miio docs]: /components/vacuum.xiaomi_miio/
|
||||
[watson_iot docs]: /components/watson_iot/
|
||||
[weather.ecobee docs]: /components/weather.ecobee/
|
||||
[weather.ipma docs]: /components/weather.ipma/
|
||||
[weather.openweathermap docs]: /components/weather.openweathermap/
|
||||
[websocket_api docs]: /components/websocket_api/
|
||||
[wink docs]: /components/wink/
|
||||
[wirelesstag docs]: /components/wirelesstag/
|
||||
[xiaomi_aqara docs]: /components/xiaomi_aqara/
|
||||
[zone docs]: /components/zone/
|
||||
[zwave docs]: /components/zwave/
|
||||
34
source/components/switch.linode.markdown
Normal file
34
source/components/switch.linode.markdown
Normal file
@ -0,0 +1,34 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Linode Switch"
|
||||
description: "Instructions on how to set up Linode switch within Home Assistant."
|
||||
date: 2017-10-20 08:00
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
ha_category: System Monitor
|
||||
logo: linode.png
|
||||
ha_release: 0.57
|
||||
ha_iot_class: "Cloud Polling"
|
||||
---
|
||||
|
||||
The `linode` switch platform allows you to turn your Linode nodes on and off.
|
||||
|
||||
Add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
switch:
|
||||
- platform: linode
|
||||
nodes:
|
||||
- 'myvpsname'
|
||||
```
|
||||
|
||||
{% configuration linode %}
|
||||
nodes:
|
||||
description: List of VPSs you want to control.
|
||||
required: true
|
||||
type: string
|
||||
{% endconfiguration %}
|
||||
|
||||
BIN
source/images/blog/2018-06-release-0.72/config_entry.png
Normal file
BIN
source/images/blog/2018-06-release-0.72/config_entry.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 23 KiB |
BIN
source/images/blog/2018-06-release-0.72/lovelace.png
Normal file
BIN
source/images/blog/2018-06-release-0.72/lovelace.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 126 KiB |
BIN
source/images/supported_brands/epson.png
Normal file
BIN
source/images/supported_brands/epson.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 11 KiB |
45
source/images/supported_brands/freebox.svg
Normal file
45
source/images/supported_brands/freebox.svg
Normal file
@ -0,0 +1,45 @@
|
||||
<?xml version="1.0" encoding="utf-8"?>
|
||||
<!-- Generator: Adobe Illustrator 13.0.0, SVG Export Plug-In . SVG Version: 6.00 Build 14948) -->
|
||||
<!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
|
||||
<svg version="1.1" id="Calque_1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px"
|
||||
width="1718.317px" height="333.639px" viewBox="0 0 1718.317 333.639" enable-background="new 0 0 1718.317 333.639"
|
||||
xml:space="preserve">
|
||||
<path fill="#C70119" d="M1094.17,134.662c0,36.376-72.879,106.899-146.345,106.899c-27.478,0-36.438-14.043-36.438-27.124
|
||||
c0-35.738,72.867-102.115,146.936-102.115C1085.801,112.322,1094.17,122.537,1094.17,134.662z M1015.915,1.915L1011.138,0
|
||||
c-10.748,1.915-27.478,3.83-38.226,5.107c-17.324,1.915-33.448,3.505-45.995,4.146l-1.792,5.744l28.072,9.253l-78.842,167.847
|
||||
c-3.588,7.66-7.175,15.638-7.175,23.614c0,23.297,31.66,34.145,71.086,34.145c94.382,0,203.687-59.032,203.687-110.089
|
||||
c0-24.252-19.711-40.526-67.503-40.526c-53.758,0-102.735,26.164-134.986,45.95l-1.197-0.635L1015.915,1.915z"/>
|
||||
<path fill="#C70119" d="M1197.572,196.568c0-35.104,31.653-89.033,111.699-89.033c51.368,0,67.495,22.338,67.495,44.997
|
||||
c0,32.866-32.85,89.029-109.903,89.029C1214.299,241.562,1197.572,220.501,1197.572,196.568z M1149.785,185.717
|
||||
c0,38.613,45.995,64.14,117.673,64.14c85.415,0,157.096-40.843,157.096-85.838c0-36.697-45.396-64.777-114.688-64.777
|
||||
C1223.259,99.242,1149.785,139.768,1149.785,185.717z"/>
|
||||
<path fill="#C70119" d="M1553.463,188.27l-40.624,30.635c-16.715,12.444-48.974,30.952-72.871,30.952
|
||||
c-22.098,0-31.656-8.614-31.656-16.592c0-9.894,13.741-18.189,29.864-21.382l6.577,2.234c-0.603,1.595-1.201,3.191-1.201,4.471
|
||||
c0,4.465,5.979,7.657,15.533,7.657c16.123,0,32.255-8.298,47.787-18.827l41.215-28.719l-15.533-28.402
|
||||
c-7.762-13.718-19.12-25.527-37.627-25.527c-20.313,0-33.455,11.168-41.218,20.103l-11.351-3.191
|
||||
c10.149-18.19,34.646-42.44,74.663-42.44c26.288,0,38.828,12.125,47.186,25.528l17.328,28.399l29.266-20.744
|
||||
c22.7-15.632,49.58-32.228,81.831-32.228c15.532,0,25.686,6.381,25.686,14.358c0,10.85-15.525,18.51-28.667,22.023l-4.777-1.597
|
||||
c-2.391-5.109-4.781-9.257-19.716-9.257c-20.31,0-37.031,10.212-51.962,20.421l-25.693,18.19l21.511,38.613
|
||||
c5.372,10.212,10.748,22.338,30.459,22.338c24.492,0,36.438-14.042,48.985-22.976l9.558,3.825
|
||||
c-16.733,15.002-43.006,44.357-81.239,44.357c-28.072,0-38.233-16.914-45.988-30.951L1553.463,188.27z"/>
|
||||
<path fill="#C70119" d="M211.905,125.501l-7.231,12.728h-65.607L38.544,328.044l-36.731,5.595L0,331.775l92.713-193.546H38.544
|
||||
l6.605-12.728h52.978c19.266-34.486,34.91-60.268,90.295-85.128c16.252-7.446,41.55-14.909,64.421-14.909
|
||||
c12.037,0,24.681,2.492,24.681,9.944c0,4.342-6.024,14.917-16.862,14.917c-11.433,0-24.07-6.218-37.913-6.218
|
||||
c-36.73,0-47.574,21.127-55.995,38.833l-21.066,42.562H211.905"/>
|
||||
<path fill="#C70119" d="M219.294,146.83c15.047-11.509,61.403-41.648,90.897-41.648c15.048,0,24.7,3.436,24.7,11.822
|
||||
c0,3.413-2.424,9.309-6.038,16.156l-22.879,42.546h1.211c16.252-15.838,72.844-70.524,110.765-70.524
|
||||
c12.645,0,18.656,3.733,18.656,10.575c0,7.146-6.619,22.984-25.275,22.984c-7.231,0-15.044-1.247-22.271-1.247
|
||||
c-41.537,0-84.279,60.275-104.146,91.956l-10.838,19.891c-1.203,2.168-10.831,2.479-21.677,2.479
|
||||
c-7.823,0-19.251-2.805-19.251-5.594c0-0.922,0.604-1.865,1.191-2.792l47.56-85.745c3.015-4.975,7.231-13.669,7.231-18.324
|
||||
c0-3.421-3.614-8.075-11.438-8.075c-16.262,0-40.937,14.598-50.567,20.818L219.294,146.83"/>
|
||||
<path fill="#C70119" d="M612.157,207.716c-39.732,22.678-83.694,40.378-136.658,40.378c-55.389,0-74.057-21.114-74.057-41.931
|
||||
c0-49.715,86.094-104.692,173.375-104.692c27.105,0,59.002,4.967,59.002,22.05c0,42.25-114.981,56.853-179.397,59.956
|
||||
c-3.616,8.075-4.806,15.844-4.806,23.927c0,15.538,21.063,23.924,49.345,23.924c34.932,0,70.458-11.813,104.766-28.89
|
||||
L612.157,207.716 M585.665,124.768c0-8.069-9.044-13.367-24.693-13.367c-46.344,0-93.904,43.504-103.545,64.002
|
||||
C512.812,173.532,585.665,158.629,585.665,124.768"/>
|
||||
<path fill="#C70119" d="M840.965,207.716c-39.737,22.678-83.669,40.378-136.661,40.378c-55.374,0-74.043-21.114-74.043-41.931
|
||||
c0-49.715,86.11-104.692,173.392-104.692c27.075,0,58.97,4.967,58.97,22.05c0,42.25-114.965,56.853-179.367,59.956
|
||||
c-3.614,8.075-4.835,15.844-4.835,23.927c0,15.538,21.079,23.924,49.375,23.924c34.9,0,70.428-11.813,104.747-28.89L840.965,207.716
|
||||
M814.47,124.768c0-8.069-9.018-13.367-24.669-13.367c-46.356,0-93.916,43.504-103.541,64.002
|
||||
C741.629,173.532,814.47,158.629,814.47,124.768"/>
|
||||
</svg>
|
||||
|
After Width: | Height: | Size: 4.4 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 240 KiB After Width: | Height: | Size: 11 KiB |
BIN
source/images/supported_brands/ibm.png
Normal file
BIN
source/images/supported_brands/ibm.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 2.0 KiB |
BIN
source/images/supported_brands/ipma.png
Normal file
BIN
source/images/supported_brands/ipma.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 6.2 KiB |
BIN
source/images/supported_brands/kiwi.png
Normal file
BIN
source/images/supported_brands/kiwi.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 34 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 20 KiB After Width: | Height: | Size: 9.5 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 32 KiB After Width: | Height: | Size: 4.4 KiB |
BIN
source/images/supported_brands/unitymedia.png
Normal file
BIN
source/images/supported_brands/unitymedia.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 12 KiB |
BIN
source/images/supported_brands/uptimerobot.png
Normal file
BIN
source/images/supported_brands/uptimerobot.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 4.5 KiB |
BIN
source/images/supported_brands/wirelesstag.png
Normal file
BIN
source/images/supported_brands/wirelesstag.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 26 KiB |
BIN
source/images/supported_brands/zhong_hong.png
Normal file
BIN
source/images/supported_brands/zhong_hong.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 3.4 KiB |
Loading…
x
Reference in New Issue
Block a user