mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-07-27 11:16:54 +00:00
Add 'ha_iot_class'
This commit is contained in:
Fabian Affolter
parent
ebc09dbefe
commit
067eb35afa
@ -10,6 +10,7 @@ footer: true
|
||||
logo: android_ip_webcam.png
|
||||
ha_category: Hub
|
||||
ha_release: "0.40"
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
The `android_ip_webcam` component turns an Android phone into a network camera with multiple viewing options.
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: android_ip_webcam.png
|
||||
ha_category: Binary Sensor
|
||||
ha_release: "0.40"
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: eight_sleep.png
|
||||
ha_category: Binary Sensor
|
||||
ha_release: "0.44"
|
||||
ha_iot_class: "Cloud Polling"
|
||||
---
|
||||
|
||||
|
||||
|
||||
@ -9,8 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: zigbee.png
|
||||
ha_category: Binary Sensor
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
To get your ZigBee binary sensors working with Home Assistant, follow the
|
||||
instructions for the general [ZigBee Home Automation
|
||||
component](/components/zha/).
|
||||
To get your ZigBee binary sensors working with Home Assistant, follow then instructions for the general [ZigBee Home Automationcomponent](/components/zha/).
|
||||
|
||||
@ -9,6 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: bus_scs.png
|
||||
ha_category: Cover
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
The SCSGate devices can control motorized covers connected to the BTicino MyHome system.
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: eight_sleep.png
|
||||
ha_category: Hub
|
||||
ha_release: "0.44"
|
||||
ha_iot_class: "Cloud Polling"
|
||||
---
|
||||
|
||||
The `eight_sleep` component allows Home Assistant to fetch data from your [Eight Sleep](https://eightsleep.com/) smart cover or mattress.
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
layout: page
|
||||
title: "EnOcean"
|
||||
description: "Connect EnOcean devices to home-assistant"
|
||||
description: "Connect EnOcean devices to Home Assistant"
|
||||
date: 2016-05-25 23:39
|
||||
sidebar: true
|
||||
comments: false
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: enocean.png
|
||||
ha_category: Hub
|
||||
ha_release: 0.21
|
||||
ha_iot_class: "Local Push"
|
||||
---
|
||||
|
||||
The [EnOcean](https://en.wikipedia.org/wiki/EnOcean) standard is supported by many different vendors. There are switches and sensors of many different kinds, and typically they employ energy harvesting to get power such that no batteries are unnecessary.
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: enocean.png
|
||||
ha_category: Light
|
||||
ha_release: 0.21
|
||||
ha_iot_class: "Local Push"
|
||||
---
|
||||
|
||||
An EnOcean light can take many forms. Currently only one type has been tested: Eltako FUD61 dimmer.
|
||||
|
||||
@ -10,7 +10,7 @@ footer: true
|
||||
logo: modbus.png
|
||||
ha_category: Hub
|
||||
ha_release: pre 0.7
|
||||
ha_iot_class: "Local Polling"
|
||||
ha_iot_class: "Local Push"
|
||||
---
|
||||
|
||||
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: nfandroidtv.png
|
||||
ha_category: Notifications
|
||||
ha_release: 0.32
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
|
||||
@ -22,9 +23,9 @@ To enable the notification platform, add the following to your `configuration.ya
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
notify:
|
||||
- platform: nfandroidtv
|
||||
name: Kitchen
|
||||
host: 192.168.1.12
|
||||
- platform: nfandroidtv
|
||||
name: Kitchen
|
||||
host: 192.168.1.12
|
||||
```
|
||||
|
||||
Configuration variables:
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: bus_scs.png
|
||||
ha_category: Hub
|
||||
ha_release: 0.13
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
The SCSGate component support the [SCSGate](https://translate.google.com/translate?hl=en&sl=it&tl=en&u=http%3A%2F%2Fguidopic.altervista.org%2Feibscsgt%2Finterface.html) device. This a homebrew device allows to interact with the MyHome system from BTicino/Legrande.
|
||||
@ -28,7 +29,7 @@ Configuration variables:
|
||||
|
||||
### {% linkable_title How to find the scs_id for your devices %}
|
||||
|
||||
The SCSGate component relies on the [scsgate](https://github.com/flavio/scsgate) python module.
|
||||
The SCSGate component relies on the [scsgate](https://github.com/flavio/scsgate) Python module.
|
||||
|
||||
This module provides also a command line tool called `scs-monitor`. This program can be used to find the IDs of your lights, switches and roller shutters and produce the YAML snippet to insert into your `configuration.yaml` file.
|
||||
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: amcrest.png
|
||||
ha_category: Sensor
|
||||
ha_release: 0.37
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
The `amcrest` sensor allows you to integrate your [Amcrest](https://amcrest.com/) IP camera in Home Assistant.
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: android_ip_webcam.png
|
||||
ha_category: Sensor
|
||||
ha_release: "0.40"
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
layout: page
|
||||
title: APCUPSd Sensor
|
||||
title: "APCUPSd Sensor"
|
||||
description: "Instructions on how to set up APCUPSd sensors within Home Assistant."
|
||||
date: 2016-02-10 18:28
|
||||
sidebar: true
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: apcupsd.png
|
||||
ha_release: 0.13
|
||||
ha_category: System Monitor
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
The `apcupsd` sensor platform allows you to monitor a UPS (battery backup) by using data from the [apcaccess](http://linux.die.net/man/8/apcaccess) command.
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: home-assistant.png
|
||||
ha_category: Sensor
|
||||
ha_release: 0.33
|
||||
ha_iot_class: "Local Push"
|
||||
---
|
||||
|
||||
The `api_stream` sensor platform shows how many clients are connected to the stream API
|
||||
|
||||
@ -9,6 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
ha_category: Sensor
|
||||
ha_release: 0.31
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
The `arwn` sensor platform is a client for the [Ambient Radio Weather Network](http://github.com/sdague/arwn) project. This collects weather station data and makes it available in an MQTT subtree.
|
||||
|
||||
@ -10,8 +10,9 @@ footer: true
|
||||
logo: blink.png
|
||||
ha_category: Sensor
|
||||
ha_release: "0.40"
|
||||
ha_iot_class: "Cloud Polling"
|
||||
---
|
||||
|
||||
<p class='note'>
|
||||
To get your Blink sensors working with Home Assistant, follow the instructions for the general [Blink component](/components/blink/).
|
||||
</p>
|
||||
</p>
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: bom.png
|
||||
ha_category: Weather
|
||||
ha_release: 0.29
|
||||
ha_iot_class: "Cloud Polling"
|
||||
---
|
||||
|
||||
The `bom` sensor platform uses the [Australian Bureau of Meteorology (BOM)](http://www.bom.gov.au) as a source for current (half-hourly) meteorological data.
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: broadlink.png
|
||||
ha_category: Sensor
|
||||
ha_release: 0.35
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: home-assistant.png
|
||||
ha_category: System Monitor
|
||||
ha_release: 0.44
|
||||
ha_iot_class: "depends"
|
||||
---
|
||||
|
||||
The `cert_expiry` sensor fetches information from a configured URL and displays the certificate expiry in days.
|
||||
|
||||
@ -12,6 +12,7 @@ ha_category: Weather
|
||||
featured: true
|
||||
ha_release: 0.30
|
||||
redirect_from: /components/sensor.forecast/
|
||||
ha_iot_class: "Cloud Polling"
|
||||
---
|
||||
|
||||
The `darksky` platform uses the [Dark Sky](https://darksky.net/) web service as a source for meteorological data for your location. The location is based on the `longitude` and `latitude` coordinates configured in your `configuration.yaml` file. The coordinates are auto-detected but to take advantage of the hyper-local weather reported by Dark Sky, you can refine them down to your exact home address. GPS coordinates can be found by using [Google Maps](https://www.google.com/maps) and clicking on your home or [Openstreetmap](http://www.openstreetmap.org/).
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
ha_category: System Monitor
|
||||
logo: dovado.png
|
||||
ha_release: 0.32
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
The `dovado` platform let you monitor your router from [Dovado](http://www.dovado.com/)
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: dweet.png
|
||||
ha_category: Sensor
|
||||
ha_release: "0.10"
|
||||
ha_iot_class: "Cloud Polling"
|
||||
---
|
||||
|
||||
The `dweet` sensor platform allows you to get details from your devices which are publishing their values to [Dweet.io](https://dweet.io/).
|
||||
|
||||
@ -19,18 +19,18 @@ All beacons that support the Eddystone protocol, have a temperature sensor and c
|
||||
## Requirements
|
||||
|
||||
As this platform uses `bluez` to scan for Bluetooth LE devices **a Linux OS with bluez installed** is required. In addition to that, the `libbluetooth` headers need to be installed:
|
||||
```shell
|
||||
|
||||
```bash
|
||||
$ sudo apt-get install libbluetooth-dev
|
||||
```
|
||||
|
||||
Scanning for Bluetooth LE devices also requires special permissions. To grant these to the python executable execute the following:
|
||||
```shell
|
||||
|
||||
```bash
|
||||
$ sudo apt-get install libcap2-bin
|
||||
$ sudo setcap 'cap_net_raw,cap_net_admin+eip' $(readlink -f $(which python3))
|
||||
```
|
||||
|
||||
## Configuration
|
||||
|
||||
To use your Eddystone beacon in your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
@ -42,16 +42,14 @@ sensor:
|
||||
living_room:
|
||||
namespace: "112233445566778899AA"
|
||||
instance: "000000000001"
|
||||
name: "Living Room" # optional
|
||||
kitchen:
|
||||
namespace: "112233445566778899AA"
|
||||
instance: "000000000002"
|
||||
name: "Kitchen" # optional
|
||||
```
|
||||
Configuration variables:
|
||||
- **bt_device_id** (*Optional*): The id of the bluetooth device that should be used for scanning (hci*X*). You can find the correct one using `hcitool dev` (default: 0).
|
||||
- **beacons** array (*Required*): The beacons that should be monitored.
|
||||
- **[entry]** (*Required*): Name of the beacon.
|
||||
- **namespace** (*Required*): Namespace ID of the beacon in hexadecimal notation. Must be exactly 20 characters (10 bytes) long.
|
||||
- **namespace** (*Required*): Instance ID of the beacon in hexadecimal notation. Must be exactly 12 characters (6 bytes) long.
|
||||
- **instance** (*Required*): Instance ID of the beacon in hexadecimal notation. Must be exactly 12 characters (6 bytes) long.
|
||||
- **name** (*Optional*): Friendly name of the beacon.
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: eight_sleep.png
|
||||
ha_category: Sensor
|
||||
ha_release: "0.44"
|
||||
ha_iot_class: "Cloud Polling"
|
||||
---
|
||||
|
||||
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: enocean.png
|
||||
ha_category: Sensor
|
||||
ha_release: 0.21
|
||||
ha_iot_class: "Local Push"
|
||||
---
|
||||
|
||||
|
||||
|
||||
@ -11,6 +11,7 @@ logo: fastdotcom.png
|
||||
ha_category: System Monitor
|
||||
featured: false
|
||||
ha_release: 0.26
|
||||
ha_iot_class: "Cloud Polling"
|
||||
---
|
||||
|
||||
The `fastdotcom` sensor component uses the [Fast.com](https://fast.com/) web service to measure network bandwidth performance.
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: fedex.png
|
||||
ha_category: Sensor
|
||||
ha_release: 0.39
|
||||
ha_iot_class: "Cloud Polling"
|
||||
---
|
||||
|
||||
The `fedex` platform allows one to track deliveries by [FedEx](http://www.fedex.com/). To use this sensor, you need a [FedEx Delivery Manager](https://www.fedex.com/us/delivery/) account.
|
||||
|
||||
@ -33,7 +33,6 @@ Jul 16 09:30:33 laptop019 gpsdctl[5305]: reached a running gpsd
|
||||
To check if your setup is working, connect to port 2947 on the host where `gpsd` is running with `telnet`. This may need adjustments to your firewall.
|
||||
|
||||
```bash
|
||||
|
||||
$ telnet localhost 2947
|
||||
Trying 127.0.0.1...
|
||||
Connected to localhost.
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: haveibeenpwned.png
|
||||
ha_category: Sensor
|
||||
ha_release: 0.31
|
||||
ha_iot_class: "Cloud Polling"
|
||||
---
|
||||
|
||||
The `haveibeenpwned` sensor platform creates sensors that check for breached email accounts on [haveibeenpwned](https://haveibeenpwned.com).
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: http.png
|
||||
ha_category: Sensor
|
||||
ha_release: pre 0.7
|
||||
ha_iot_class: "Local Push"
|
||||
---
|
||||
|
||||
The URL for a sensor looks like the example below:
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: influxdb.png
|
||||
ha_category: Sensor
|
||||
ha_release: 0.32
|
||||
ha_iot_class: "depends"
|
||||
---
|
||||
|
||||
The `influxdb` sensor allows you to use values from an [InfluxDB](https://influxdb.com/) database to populate a sensor state. This can be use to present statistic about home_assistant sensors if used with the `influxdb` history component. It can also be used with an external data source.
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: knx.png
|
||||
ha_category: DIY
|
||||
ha_release: 0.29
|
||||
ha_iot_class: "Local Push"
|
||||
---
|
||||
|
||||
The `knx` sensor platform allows you to monitor [KNX](http://www.knx.org) sensors.
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: metoffice.jpg
|
||||
ha_category: Weather
|
||||
ha_release: 0.42
|
||||
ha_iot_class: "Cloud Polling"
|
||||
---
|
||||
|
||||
The `metoffice` sensor platform uses the Met Office's [DataPoint API][datapoint] for weather data.
|
||||
|
||||
@ -9,6 +9,8 @@ sharing: true
|
||||
footer: true
|
||||
logo: ubiquiti.png
|
||||
ha_category: Sensor
|
||||
ha_iot_class: "Local Polling"
|
||||
ha_release: 0.32
|
||||
---
|
||||
|
||||
|
||||
@ -19,13 +21,10 @@ To add this platform to your installation, add the following to your `configurat
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
sensor:
|
||||
platform: mfi
|
||||
host: IP_ADDRESS
|
||||
port: PORT
|
||||
username: USERNAME
|
||||
password: PASSWORD
|
||||
ssl: true
|
||||
verify_ssl: true
|
||||
- platform: mfi
|
||||
host: IP_ADDRESS
|
||||
username: USERNAME
|
||||
password: PASSWORD
|
||||
```
|
||||
|
||||
Configuration variables:
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: mhz19_logo.png
|
||||
ha_category: Sensor
|
||||
ha_release: 0.27
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
The MH-Z19 is a small nondispersive infrared sensor that can measure CO2 level. High CO2 levels can lead to drowsiness, poor concentration, loss of attention or increased heart rate. The CO2 level outside is around 400ppm, but inside levels can reach between 1000 and 5000 ppm. High CO2 levels indicate that you should increase ventilation.
|
||||
@ -19,6 +20,7 @@ Check out the [Open Home Automation web site](https://www.open-homeautomation.co
|
||||
To use this sensor in your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
sensor:
|
||||
- platform: mhz19
|
||||
serial_device: /dev/tty.SLAB_USBtoUART
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: modbus.png
|
||||
ha_category: Sensor
|
||||
ha_release: pre 0.7
|
||||
ha_iot_class: "Local Push"
|
||||
---
|
||||
|
||||
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: neato.png
|
||||
ha_category: Sensor
|
||||
ha_release: 0.33
|
||||
ha_iot_class: "Cloud Polling"
|
||||
---
|
||||
|
||||
The `neato` sensor platform allows you to watch status and battery of your [Neato Botvac Connected](https://www.neatorobotics.com/robot-vacuum/botvac-connected-series/botvac-connected/).
|
||||
|
||||
@ -9,6 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: netatmo.png
|
||||
ha_category: Weather
|
||||
ha_iot_class: "Cloud Polling"
|
||||
---
|
||||
|
||||
### {% linkable_title Basic Configuration %}
|
||||
@ -28,14 +29,14 @@ To enable the Netatmo sensor, you first have to set up [netatmo](/components/net
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
sensor:
|
||||
platform: netatmo
|
||||
station: STATION_NAME
|
||||
modules:
|
||||
module_name1:
|
||||
- temperature
|
||||
module_name2:
|
||||
- temperature
|
||||
- battery_vp
|
||||
- platform: netatmo
|
||||
station: STATION_NAME
|
||||
modules:
|
||||
module_name1:
|
||||
- temperature
|
||||
module_name2:
|
||||
- temperature
|
||||
- battery_vp
|
||||
```
|
||||
|
||||
Configuration variables:
|
||||
|
||||
@ -10,7 +10,7 @@ footer: true
|
||||
logo: netdata.png
|
||||
ha_category: System Monitor
|
||||
ha_release: 0.35
|
||||
ha_iot_class: "Local Push"
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: nut.png
|
||||
ha_category: System Monitor
|
||||
ha_version: 0.34
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
The `nut` sensor platform allows you to monitor a UPS (battery backup) by using data from a [NUT](http://networkupstools.org/) (Network UPS Tools) server.
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: octoprint.png
|
||||
ha_category: Sensor
|
||||
ha_release: 0.19
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
|
||||
@ -22,6 +23,7 @@ You must have the [OctoPrint component](/components/octoprint/) configured to us
|
||||
To set it up, add the following information to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
sensor:
|
||||
- platform: octoprint
|
||||
name: OctoPrint
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: onewire.png
|
||||
ha_category: DIY
|
||||
ha_release: 0.12
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
The `onewire` platform supports sensors which are using the One wire (1-wire) bus for communication.
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: openevse.png
|
||||
ha_category: Sensor
|
||||
ha_release: "0.38"
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
|
||||
@ -28,7 +29,6 @@ sensor:
|
||||
|
||||
Configuration variables:
|
||||
|
||||
- **api_key** (*Required*): Your Sonarr API key, found in Settings > General in the Sonarr Web UI.
|
||||
- **host** (*Required*): The IP address or hostname of your charger
|
||||
- **monitored_variables** array (*Required*): Conditions to display on the frontend.
|
||||
- **status**: The status of the charger (i.e., "Connected", "Charging", etc.)
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: openweathermap.png
|
||||
ha_category: Weather
|
||||
ha_release: pre 0.7
|
||||
ha_iot_class: "Cloud Polling"
|
||||
---
|
||||
|
||||
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: plex.png
|
||||
ha_category: Media Player
|
||||
ha_release: 0.22
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
The `plex` sensor platform will monitor activity on a given [Plex Media Server](https://plex.tv/). It will create a sensor that shows the number of currently watching users as the state. If you click the sensor for more details it will show you who is watching what.
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: pocketcasts.png
|
||||
ha_category: Sensor
|
||||
ha_release: 0.39
|
||||
ha_iot_class: "Cloud Polling"
|
||||
---
|
||||
|
||||
To enable this sensor, add the following lines to your `configuration.yaml`:
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: pushbullet.png
|
||||
ha_category: Sensor
|
||||
ha_release: 0.44
|
||||
ha_iot_class: "Cloud Polling"
|
||||
---
|
||||
|
||||
The `pushbullet` sensor platform reads messages from [Pushbullet](https://www.pushbullet.com/), a free service to send information between your phones, browsers, and friends.
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: restful.png
|
||||
ha_category: Sensor
|
||||
ha_release: 0.7.4
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: rflink.png
|
||||
ha_category: Sensor
|
||||
ha_release: 0.38
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
The `rflink` component support devices that use [RFLink gateway firmware](http://www.nemcon.nl/blog2/), for example the [Nodo RFLink Gateway](https://www.nodo-shop.nl/nl/21-rflink-gateway). RFLink gateway is an Arduino firmware that allows two-way communication with a multitude of RF wireless devices using cheap hardware (Arduino + transceiver).
|
||||
@ -27,11 +28,10 @@ Assigning name to a sensor:
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
sensor:
|
||||
platform: rflink
|
||||
devices:
|
||||
# assign name to a sensor
|
||||
alectov1_0334_temp:
|
||||
name: Temperature Outside
|
||||
- platform: rflink
|
||||
devices:
|
||||
alectov1_0334_temp:
|
||||
name: Temperature Outside
|
||||
```
|
||||
|
||||
Configuration variables:
|
||||
|
||||
@ -9,6 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: rfxtrx.png
|
||||
ha_category: Sensor
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
The `rfxtrx` platform support sensors that communicate in the frequency range of 433.92 MHz.
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: ring.png
|
||||
ha_category: Sensor
|
||||
ha_release: "0.40"
|
||||
ha_iot_class: "Cloud Polling"
|
||||
---
|
||||
|
||||
To get your [Ring.com](https://ring.com/) binary sensors working within Home Assistant, please follow the instructions for the general [Ring component](/components/ring).
|
||||
@ -30,9 +31,6 @@ sensor:
|
||||
|
||||
Configuration variables:
|
||||
|
||||
- **username** (*Required*): The username for accessing your Ring account.
|
||||
- **password** (*Required*): The password for accessing your Ring account.
|
||||
- **scan_interval** (*Optional*): Defines the update interval of the sensor in seconds. The default is 30 seconds.
|
||||
- **monitored_conditions** array (*Required*): Conditions to display in the frontend. The following conditions can be monitored.
|
||||
- **battery**: Return the battery level from device
|
||||
- **last_activity**: Return the timestamp from the last event captured (ding/motion/on_demand) by the Ring doorbell camera
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: home-assistant.png
|
||||
ha_category: Sensor
|
||||
ha_release: 0.31
|
||||
ha_iot_class: "Cloud Polling"
|
||||
---
|
||||
|
||||
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: serial_pm.png
|
||||
ha_category: DIY
|
||||
ha_release: 0.26
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
Particulate matter sensors measure the amount of very small particles in the air. A short introduction how these sensors work can be found on [Open Home Automation](https://www.open-homeautomation.com/2016/07/19/measuring-air-quality/).
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: sonarr.png
|
||||
ha_category: Sensor
|
||||
ha_release: 0.34
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
|
||||
|
||||
@ -11,6 +11,7 @@ logo: speedtest.png
|
||||
ha_category: System Monitor
|
||||
featured: false
|
||||
ha_release: 0.13
|
||||
ha_iot_class: "Cloud Polling"
|
||||
---
|
||||
|
||||
The `speedtest` sensor component uses the [Speedtest.net](https://speedtest.net/) web service to measure network bandwidth performance.
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: supervisord.png
|
||||
ha_category: System Monitor
|
||||
ha_release: "0.20"
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
The `supervisord` platform allows you to track the states of [Supervisord](http://supervisord.org/).
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: tado.png
|
||||
ha_category: Sensor
|
||||
ha_release: 0.41
|
||||
ha_iot_class: "Cloud Polling"
|
||||
---
|
||||
|
||||
The `tado` sensor platform allow you to monitor your tado climate devices.
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: tcp_ip.png
|
||||
ha_category: Sensor
|
||||
ha_release: 0.14
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
The TCP component allows the integration of some services for which a specific Home Assistant component does not exist. If the service communicates over a TCP socket with a simple request/reply mechanism then the chances are that this component will allow integration with it.
|
||||
|
||||
@ -10,21 +10,18 @@ footer: true
|
||||
logo: ted.png
|
||||
ha_category: Sensor
|
||||
ha_release: 0.30
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
The `ted 5000` monitors electricity consumption/production by connecting to the
|
||||
[TED](http://www.theenergydetective.com/home) gateway, itself connected to one
|
||||
or several Measuring Transmitting Units (MTU).
|
||||
The platform creates up to two sensors per MTU, one for Wattage the other for
|
||||
Voltage. If you want to enable the ted5000 sensor, add the following lines to
|
||||
your `configuration.yaml`:
|
||||
The `ted 5000` monitors electricity consumption/production by connecting to the [TED](http://www.theenergydetective.com/home) gateway, itself connected to one or several Measuring Transmitting Units (MTU). The platform creates up to two sensors per MTU, one for Wattage the other for Voltage.
|
||||
|
||||
If you want to enable the ted5000 sensor, add the following lines to your `configuration.yaml`:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
sensor:
|
||||
platform: ted5000
|
||||
name: main
|
||||
host: 192.168.1.100
|
||||
port: 80
|
||||
- platform: ted5000
|
||||
host: 192.168.1.100
|
||||
```
|
||||
|
||||
Configuration variables:
|
||||
@ -34,6 +31,7 @@ Configuration variables:
|
||||
- **name** (*Optional*): Name of the ted gateway. Defaults to ted.
|
||||
|
||||
For each plugged MTU, using an index starting at 1, the platform creates 2 sensors:
|
||||
|
||||
```yaml
|
||||
sensor.<name>_mtu<MTU id>_power
|
||||
sensor.<name>_mtu<MTU id>_voltage
|
||||
|
||||
@ -9,7 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: telldus.png
|
||||
ha_category: Sensor
|
||||
featured: false
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
Integrates Telldus Live sensors into Home Assistant. See the [main component](/components/tellduslive/) for configuration instructions.
|
||||
|
||||
@ -9,6 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: telldus_tellstick.png
|
||||
ha_category: Sensor
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
|
||||
|
||||
@ -8,6 +8,8 @@ comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
ha_category: Sensor
|
||||
ha_iot_class: "Local Push"
|
||||
ha_release: pre 0.7
|
||||
---
|
||||
|
||||
This `temper` sensor platform allows you to get the current temperature from a TEMPer device.
|
||||
@ -20,8 +22,7 @@ sensor:
|
||||
- platform: temper
|
||||
```
|
||||
|
||||
|
||||
Configuration options for the a TCP Sensor:
|
||||
Configuration option:
|
||||
|
||||
- **name** (*Optional*): The name you would like to give the sensor in Home Assistant.
|
||||
- **scale** (*Optional*): The scale for the sensor.
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: torque.png
|
||||
ha_category: Transport
|
||||
ha_release: "0.10"
|
||||
ha_iot_class: "Cloud Polling"
|
||||
---
|
||||
|
||||
The `torque` platform will allow you to monitor [Torque](http://torque-bhp.com/) data relayed from a bluetooth OBD2 stick via the Torque mobile application.
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: twitch.png
|
||||
ha_category: Social
|
||||
ha_release: "0.10"
|
||||
ha_iot_class: "Cloud Polling"
|
||||
---
|
||||
|
||||
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: ups.png
|
||||
ha_category: Sensor
|
||||
ha_release: 0.39
|
||||
ha_iot_class: "Cloud Polling"
|
||||
---
|
||||
|
||||
The `ups` platform allows one to track deliveries by the [UPS](https://www.ups.com/). To use this sensor, you need a [My UPS Account](https://www.ups.com/mychoice).
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: usps.png
|
||||
ha_category: Sensor
|
||||
ha_release: 0.36
|
||||
ha_iot_class: "Cloud Polling"
|
||||
---
|
||||
|
||||
The `usps` platform allows one to track deliveries and inbound mail from the [US Postal Service (USPS)](https://www.usps.com/).
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: yr.png
|
||||
ha_category: Weather
|
||||
ha_release: 0.11
|
||||
ha_iot_class: "Cloud Polling"
|
||||
---
|
||||
|
||||
|
||||
|
||||
@ -9,8 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: zigbee.png
|
||||
ha_category: Sensor
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
To get your ZigBee sensors working with Home Assistant, follow the
|
||||
instructions for the general [ZigBee Home Automation
|
||||
component](/components/zha/).
|
||||
To get your ZigBee sensors working with Home Assistant, follow theminstructions for the general [ZigBee Home Automationmcomponent](/components/zha/).
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: zoneminder.png
|
||||
ha_category: Sensor
|
||||
ha_release: 0.31
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: android_ip_webcam.png
|
||||
ha_category: Switch
|
||||
ha_release: "0.40"
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: broadlink.png
|
||||
ha_category: Switch
|
||||
ha_release: 0.35
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
This `Broadlink` switch platform allow to you control Broadlink [devices](http://www.ibroadlink.com/rm/).
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: digitalloggers.png
|
||||
ha_category: Switch
|
||||
ha_release: 0.35
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
|
||||
@ -22,9 +23,6 @@ To use your digitalloggers switch in your installation, add the following to you
|
||||
switch:
|
||||
- platform: digitalloggers
|
||||
host: 192.168.1.43
|
||||
password: SuperSecret123!!
|
||||
name: FantasticRelayDevice
|
||||
|
||||
```
|
||||
|
||||
Configuration variables:
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: enocean.png
|
||||
ha_category: Switch
|
||||
ha_release: 0.21
|
||||
ha_iot_class: "Local Push"
|
||||
---
|
||||
|
||||
An EnOcean switch can take many forms. Currently only one type has been tested: Permundo PSC234
|
||||
|
||||
@ -9,6 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: ubiquiti.png
|
||||
ha_category: Switch
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: modbus.png
|
||||
ha_category: Switch
|
||||
ha_release: pre 0.7
|
||||
ha_iot_class: "Local Push"
|
||||
---
|
||||
|
||||
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: bus_scs.png
|
||||
ha_category: Switch
|
||||
ha_release: 0.13
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
The SCSGate device can control switches of the BTicino MyHome system.
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: ethernet.png
|
||||
ha_category: Switch
|
||||
ha_release: 0.16
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
The `wake_on_lan` (WOL) switch platform allows you to turn on a [WOL](https://en.wikipedia.org/wiki/Wake-on-LAN) enabled computer.
|
||||
|
||||
@ -9,8 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: zigbee.png
|
||||
ha_category: Switch
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
To get your ZigBee switches working with Home Assistant, follow the
|
||||
instructions for the general [ZigBee Home Automation
|
||||
component](/components/zha/).
|
||||
To get your ZigBee switches working with Home Assistant, follow theminstructions for the general [ZigBee Home Automation component](/components/zha/).
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: zoneminder.png
|
||||
ha_category: Switch
|
||||
ha_release: 0.31
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: bom.png
|
||||
ha_category: Weather
|
||||
ha_release: 0.36
|
||||
ha_iot_class: "Cloud Polling"
|
||||
---
|
||||
|
||||
The `bom` weather platform uses the [Australian Bureau of Meteorology (BOM)](http://www.bom.gov.au) as a source for current (half-hourly) meteorological data.
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: metoffice.jpg
|
||||
ha_category: Weather
|
||||
ha_release: 0.42
|
||||
ha_iot_class: "Cloud Polling"
|
||||
---
|
||||
|
||||
The `metoffice` weather platform uses the Met Office's [DataPoint API][datapoint] for weather data.
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: openweathermap.png
|
||||
ha_category: Weather
|
||||
ha_release: 0.32
|
||||
ha_iot_class: "Cloud Polling"
|
||||
---
|
||||
|
||||
The `openweathermap` weather platform uses [OpenWeatherMap](http://openweathermap.org/) as an source for current meteorological data for your location.
|
||||
|
||||
@ -10,11 +10,11 @@ footer: true
|
||||
logo: zigbee.png
|
||||
ha_category: Hub
|
||||
ha_release: 0.44
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
[ZigBee Home Automation](http://www.zigbee.org/zigbee-for-developers/applicationstandards/zigbeehomeautomation/)
|
||||
integration for Home Assistant allows you to connect many off-the-shelf ZigBee
|
||||
devices to Home Assistant, using a compatible ZigBee radio.
|
||||
integration for Home Assistant allows you to connect many off-the-shelf ZigBee devices to Home Assistant, using a compatible ZigBee radio.
|
||||
|
||||
There is currently support for the following device types within Home Assistant:
|
||||
|
||||
@ -42,6 +42,4 @@ Configuration variables:
|
||||
- **usb_path** (*Required*): Path to the serial device for the radio.
|
||||
- **database_path** (*Required*): Path to the database which will keep persistent network data.
|
||||
|
||||
|
||||
|
||||
To add new devices to the network, call the `permit` service on the `zha` domain, and then follow the device instructions.
|
||||
|
||||
@ -11,6 +11,7 @@ logo: zoneminder.png
|
||||
ha_category: Hub
|
||||
featured: false
|
||||
ha_release: 0.31
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
The ZoneMinder component sets up the integration with your [ZoneMinder](https://www.zoneminder.com) instance so that [cameras](/components/camera.zoneminder/), [sensors](/components/sensor.zoneminder/), and [switches](/components/switch.zoneminder) can use it.
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user