Add 'ha_iot_class'

This commit is contained in:
Fabian Affolter 2017-06-13 18:45:30 +02:00
parent b705dbaf4f
commit 11f21d9d96
No known key found for this signature in database
GPG Key ID: DDF3D6F44AAB1336
70 changed files with 148 additions and 96 deletions

View File

@ -10,6 +10,7 @@ footer: true
logo: verisure.png
ha_category: Alarm
ha_release: 0.7.3
ha_iot_class: "Cloud Polling"
---

View File

@ -11,6 +11,7 @@ logo: arduino.png
ha_category: DIY
featured: true
ha_release: pre 0.7
ha_iot_class: "Local Polling"
---
The [Arduino](https://www.arduino.cc/) device family are microcontroller boards that are often based on the ATmega328 chip. They come with digital input/output pins (some can be used as PWM outputs), analog inputs, and a USB connection. The equipment depends on the [type](https://www.arduino.cc/en/Main/Products) of board. The most common ones are the Arduino Uno and the Arduino Leonardo with 14 digital input/output pins and 6 analog input pins.
@ -48,6 +49,6 @@ A word of caution: The Arduino boards are not storing states. This means that wi
Add the user who is used to run Home Assistant to the groups to allow access to the serial port.
```bash
sudo usermod -a -G dialout,lock $USER
$ sudo usermod -a -G dialout,lock $USER
```

View File

@ -10,6 +10,7 @@ footer: true
logo: beaglebone-black.png
ha_category: DIY
ha_release: 0.36
ha_iot_class: "Local Push"
---
The `bbb_gpio` component is the base for all [BeagleBone Black](https://beagleboard.org/black) related GPIO platforms in Home Assistant. There is no setup needed for the component itself, for the platforms please check their corresponding pages.

View File

@ -10,6 +10,7 @@ footer: true
logo: beaglebone-black.png
ha_category: Binary Sensor
ha_release: 0.37
ha_iot_class: "Local Push"
---
The `bbb_gpio` binary sensor platform allows you to read sensor values of the GPIOs of your [BeagleBone Black](https://beagleboard.org/black).

View File

@ -15,4 +15,4 @@ ha_release: pre 0.7
The `isy994` platform allows you to get data from your [ISY994](https://www.universal-devices.com/residential/isy994i-series/) binary sensors from within Home Assistant.
They will be automatically discovered if the isy994 component is loaded.
They will be automatically discovered if the `isy994` component is loaded.

View File

@ -10,7 +10,7 @@ footer: true
logo: pilight.png
ha_category: Binary Sensor
ha_release: 0.44
ha_iot_class: Local Poll
ha_iot_class: "Local Polling"
---
This component implement the [pilight hub](https://github.com/home-assistant/home-assistant.github.io/source/_components/pilight.markdown) binary sensor functionality.

View File

@ -10,6 +10,7 @@ footer: true
logo: raspberry-pi.png
ha_category: Binary Sensor
ha_release: 0.45
ha_iot_class: "Local Push"
---
The `rpi_pfio` binary sensor platform allows you to read sensor values of the [PiFace Digital I/O](http://www.piface.org.uk/products/piface_digital/) .

View File

@ -9,6 +9,7 @@ sharing: true
footer: true
logo: amcrest.png
ha_category: Camera
ha_iot_class: "Local Polling"
ha_release: 0.34
---

View File

@ -10,6 +10,7 @@ footer: true
logo: axis.png
ha_category: Camera
ha_release: "0.45"
ha_iot_class: "Local Polling"
---
The `Axis` camera platform allows you to stream video from your [Axis](https://www.axis.com/) cameras.

View File

@ -10,8 +10,9 @@ footer: true
logo: blink.png
ha_category: Camera
ha_release: "0.40"
ha_iot_class: "Cloud Polling"
---
<p class='note'>
To get your Blink cameras working with Home Assistant, follow the instructions for the general [Blink component](/components/blink/).
</p>
</p>

View File

@ -10,6 +10,7 @@ footer: true
logo: bloomsky.png
ha_category: Camera
ha_release: 0.13
ha_iot_class: "Local Polling"
---
@ -20,5 +21,5 @@ To enable this camera in your installation, set up the [BloomSky component](/com
```yaml
# Example configuration.yaml entry
camera:
platform: bloomsky
- platform: bloomsky
```

View File

@ -10,6 +10,7 @@ footer: true
logo: ffmpeg.png
ha_category: Camera
ha_release: 0.26
ha_iot_class: "Local Polling"
---

View File

@ -9,6 +9,7 @@ sharing: true
footer: true
logo: foscam.png
ha_category: Camera
ha_iot_class: "Local Polling"
---
@ -19,10 +20,10 @@ To enable your Foscam IP camera in your installation, add the following to your
```yaml
# Example configuration.yaml entry
camera:
platform: foscam
ip: IP_ADDRESS
username: USERNAME
password: PASSWORD
- platform: foscam
ip: IP_ADDRESS
username: USERNAME
password: PASSWORD
```
Configuration variables:

View File

@ -10,6 +10,7 @@ footer: true
logo: camcorder.png
ha_category: Camera
ha_release: pre 0.7
ha_iot_class: "depends"
---

View File

@ -10,6 +10,7 @@ footer: true
logo: neato.png
ha_category: Camera
ha_release: 0.42
ha_iot_class: "Cloud Polling"
---

View File

@ -10,6 +10,7 @@ footer: true
logo: netatmo.png
ha_category: Camera
ha_release: 0.22
ha_iot_class: "Local Polling"
---
### {% linkable_title Basic Configuration %}
@ -25,7 +26,7 @@ If you want to select a specific camera, set discovery to False for [netatmo](/c
```yaml
# Example configuration.yaml entry
camera:
platform: netatmo
- platform: netatmo
```
Configuration variables:

View File

@ -10,6 +10,7 @@ footer: true
logo: synology.png
ha_category: Camera
ha_release: 0.31
ha_iot_class: "Local Polling"
---
 

View File

@ -10,6 +10,7 @@ footer: true
logo: ubiquiti.png
ha_category: Camera
ha_release: 0.13
ha_iot_class: "Local Polling"
---

View File

@ -10,6 +10,7 @@ footer: true
logo: verisure.png
ha_category: Camera
ha_release: 0.31
ha_iot_class: "Local Polling"
---

View File

@ -10,6 +10,7 @@ footer: true
logo: zoneminder.png
ha_category: Camera
ha_release: 0.39
ha_iot_class: "Local Polling"
---

View File

@ -9,7 +9,7 @@ sharing: true
footer: true
logo: eq3.gif
ha_category: Climate
ha_iot_class: "Local Poll"
ha_iot_class: "Local Polling"
---
The `eq3btsmart` climate platform allows you to integrate EQ3 Bluetooth Smart Thermostats.

View File

@ -10,6 +10,7 @@ footer: true
logo: heat-control.png
ha_category: Climate
ha_release: pre 0.7
ha_iot_class: "Local Polling"
---

View File

@ -10,24 +10,25 @@ footer: true
logo: heatmiser.png
ha_category: Climate
ha_release: "0.10"
ha_iot_class: "Local Polling"
---
The `heatmiser` climate platform let you control [Heatmiser DT/DT-E/PRT/PRT-E](http://www.heatmisershop.co.uk/heatmiser-slimline-programmable-room-thermostat/) thermostats from Heatmiser. The module itself is currently setup to work over a RS232 -> RS485 converter, therefore it connects over IP.
The `heatmiser` climate platform let you control [Heatmiser DT/DT-E/PRT/PRT-E](http://www.heatmisershop.co.uk/heatmiser-slimline-programmable-room-thermostat/) thermostats from Heatmiser. The module itself is currently setup to work over a RS232 -> RS485 converter, therefore it connects over IP.
Further work would be required to get this setup to connect over Wifi, but the HeatmiserV3 python module being used is a full implementation of the V3 protocol. If you would like to contribute to making this work over wifi, please contact @andylockran on github.
Further work would be required to get this setup to connect over Wifi, but the HeatmiserV3 python module being used is a full implementation of the V3 protocol.
To set it up, add the following information to your `configuration.yaml` file:
```yaml
climate:
platform: heatmiser
ipaddress: YOUR_IPADDRESS
port: YOUR_PORT
tstats:
- 1:
id: THERMOSTAT_ID
name: THERMOSTAT_NAME
- platform: heatmiser
ipaddress: YOUR_IPADDRESS
port: YOUR_PORT
tstats:
- 1:
id: THERMOSTAT_ID
name: THERMOSTAT_NAME
```
A single interface can handle up to 32 connected devices.

View File

@ -9,6 +9,8 @@ sharing: true
footer: true
logo: honeywell.png
ha_category: Climate
ha_release: pre 0.7
ha_iot_class: "Cloud Polling"
---
@ -18,10 +20,10 @@ To set it up, add the following information to your `configuration.yaml` file:
```yaml
climate:
platform: honeywell
username: YOUR_USERNAME
password: YOUR_PASSWORD
scan_interval: 600
- platform: honeywell
username: YOUR_USERNAME
password: YOUR_PASSWORD
scan_interval: 600
```
<p class='note'>
Scan interval is expressed in seconds. Omitting scan_interval may result in too-frequent polling and cause you to rate-limited by Honeywell.

View File

@ -10,6 +10,7 @@ footer: true
logo: netatmo.png
ha_category: Climate
ha_release: 0.31
ha_iot_class: "Cloud Polling"
---

View File

@ -10,6 +10,7 @@ footer: true
logo: oem.png
ha_category: Climate
ha_release: 0.39
ha_iot_class: "Local Polling"
---
This platform supports the ESP82666 based "WiFi MQTT Relay / Thermostat" sold by [OpenEnergyMonitor](https://shop.openenergymonitor.com/wifi-mqtt-relay-thermostat/). The underlying [library](http://oemthermostat.readthedocs.io/) only supports this single relay variant of the [original device](https://harizanov.com/2014/12/wifi-iot-3-channel-relay-board-with-mqtt-and-http-api-using-esp8266/).

View File

@ -10,6 +10,7 @@ footer: true
logo: proliphix.png
ha_category: Climate
ha_release: 0.11
ha_iot_class: "Local Polling"
---
@ -23,15 +24,15 @@ To set it up, add the following information to your `configuration.yaml` file:
```yaml
climate:
platform: proliphix
host: IP_ADDRESS
username: YOUR_USERNAME
password: YOUR_PASSWORD
- platform: proliphix
host: IP_ADDRESS
username: YOUR_USERNAME
password: YOUR_PASSWORD
```
Configuration variables:
- **host** (*Required*): Address of your thermostat, eg. 192.168.1.32
- **host** (*Required*): Address of your thermostat, eg. 192.168.1.32.
- **username** (*Required*): Username for the thermostat.
- **password** (*Required*): Password for the thermostat.

View File

@ -9,6 +9,7 @@ sharing: true
footer: true
logo: radiotherm.png
ha_category: Climate
ha_iot_class: "Local Polling"
---
@ -26,7 +27,7 @@ To set it up, add the following information to your `configuration.yaml` file:
```yaml
# Example configuration.yaml entry
climate:
platform: radiotherm
- platform: radiotherm
```
Configuration variables:

View File

@ -10,6 +10,7 @@ footer: true
logo: tado.png
ha_category: Climate
ha_release: 0.41
ha_iot_class: "Cloud Polling"
---

View File

@ -14,4 +14,4 @@ ha_iot_class: "Local Push"
The `isy994` platform allows you to get data from your [ISY994](https://www.universal-devices.com/residential/isy994i-series/) cover from within Home Assistant.
They will be automatically discovered if the isy994 component is loaded.
They will be automatically discovered if the `isy994` component is loaded.

View File

@ -10,6 +10,7 @@ footer: true
logo: raspberry-pi.png
ha_category: Cover
ha_release: 0.23
ha_iot_class: "Local Push"
---
The `rpi_gpio` cover platform allows you to use a Raspberry Pi to control your cover such as Garage doors.

View File

@ -10,6 +10,7 @@ footer: true
logo: bbox.png
ha_category: Presence Detection
ha_release: "0.31"
ha_iot_class: "Local Polling"
---

View File

@ -14,4 +14,4 @@ ha_iot_class: "Local Push"
The `isy994` platform allows you to get data from your [ISY994](https://www.universal-devices.com/residential/isy994i-series/) fan from within Home Assistant.
They will be automatically discovered if the isy994 component is loaded.
They will be automatically discovered if the `isy994` component is loaded.

View File

@ -10,6 +10,7 @@ footer: true
logo: blinkstick.png
ha_category: Light
ha_release: 0.7.5
ha_iot_class: "Local Polling"
---
@ -20,9 +21,9 @@ To add blinkstick to your installation, add the following to your `configuration
```yaml
# Example configuration.yaml entry
light:
platform: blinksticklight
serial: BS000795-1.1
name: Living Room
- platform: blinksticklight
serial: BS000795-1.1
name: Living Room
```
Configuration variables:

View File

@ -10,9 +10,10 @@ footer: true
logo: hyperion.png
ha_category: Light
ha_release: 0.7.6
ha_iot_class: "Local Polling"
---
This platform allows you to integrate your [Hyperion](https://hyperion-project.org/wiki) into Home Assistant. Hyperion is an open source Ambilight implementation which runs on many platforms.
The `hyperion` platform allows you to integrate your [Hyperion](https://hyperion-project.org/wiki) into Home Assistant. Hyperion is an open source Ambilight implementation which runs on many platforms.
To use your Hyperion light in your installation, add the following to your `configuration.yaml` file:

View File

@ -10,6 +10,7 @@ footer: true
logo: insteon.png
ha_category: Light
ha_release: 0.21
ha_iot_class: "Local Push"
---
The `insteon_hub` light component lets you control your lights connected to an [Insteon Hub](http://www.insteon.com/insteon-hub/) with Home Assistant.

View File

@ -10,6 +10,7 @@ footer: true
logo: insteon.png
ha_category: Light
ha_version: 0.36
ha_iot_class: "Local Push"
---
The `insteon_local` light component lets you control your lights connected to an [Insteon Hub](http://www.insteon.com/insteon-hub/) with Home Assistant.
@ -27,6 +28,7 @@ insteon_local:
```
To add lights (dimmers) to your set-up, add the platform to your light configuration:
```yaml
light:
- platform: insteon_local

View File

@ -13,10 +13,5 @@ ha_iot_class: "Local Push"
ha_version: 0.39
---
The `insteon_plm` light platform lets you control your sensors through
an INSTEON PowerLinc Modem (PLM) device connected directly to your system on a
USB or serial port. To add support, set up the primary [insteon_plm]
component.
[insteon_plm]: /components/insteon_plm/
The `insteon_plm` light platform lets you control your sensors through an INSTEON PowerLinc Modem (PLM) device connected directly to your system on an USB or serial port. To add support, set up the primary [insteon_plm](/components/insteon_plm/) component.

View File

@ -14,4 +14,4 @@ ha_iot_class: "Local Push"
The `isy994` platform allows you to get data from your [ISY994](https://www.universal-devices.com/residential/isy994i-series/) light from within Home Assistant.
They will be automatically discovered if the isy994 component is loaded.
They will be automatically discovered if the `isy994` component is loaded.

View File

@ -9,6 +9,7 @@ sharing: true
footer: true
ha_category: Light
ha_release: 0.32
ha_iot_class: "Local Polling"
---
To get your LiteJet lights working with Home Assistant, follow the instructions for the general [LiteJet component](/components/litejet/).

View File

@ -10,6 +10,7 @@ footer: true
logo: mystrom.png
ha_category: Light
ha_release: 0.43
ha_iot_class: "Local Polling"
---

View File

@ -10,6 +10,7 @@ footer: true
logo: raspberry-pi.png
ha_category: Light
ha_release: 0.37
ha_iot_class: "Local Polling"
---
@ -20,5 +21,5 @@ To add piglow to your installation, add the following to your `configuration.yam
```yaml
# Example configuration.yaml entry
light:
platform: piglow
- platform: piglow
```

View File

@ -10,6 +10,7 @@ footer: true
logo: rflink.png
ha_category: Light
ha_release: 0.38
ha_iot_class: "Assumed state"
---
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,13 +28,13 @@ Configuring a device as light with a nice name:
```yaml
# Example configuration.yaml entry
light:
platform: rflink
device_defaults:
fire_event: true
signal_repetitions: 2
devices:
newkaku_0000c6c2_1:
name: Living room
- platform: rflink
device_defaults:
fire_event: true
signal_repetitions: 2
devices:
newkaku_0000c6c2_1:
name: Living room
```
Configuration variables:
@ -64,17 +65,17 @@ Sometimes a light is controlled by multiple remotes, each remote has its own cod
```yaml
# Example configuration.yaml entry
light:
platform: rflink
devices:
newkaku_0000c6c2_1:
name: Living room
aliasses:
- newkaku_000000001_2
- kaku_000001_a
Ansluta_ce30_0:
name: Kitchen Under Counter Lights
Maclean_0d82_01:
name: Bedroom Lamp
- platform: rflink
devices:
newkaku_0000c6c2_1:
name: Living room
aliasses:
- newkaku_000000001_2
- kaku_000001_a
Ansluta_ce30_0:
name: Kitchen Under Counter Lights
Maclean_0d82_01:
name: Bedroom Lamp
```
Any on/off command from any allias ID updates the current state of the light. However when sending a command through the frontend only the primary ID is used.

View File

@ -10,6 +10,7 @@ footer: true
logo: rfxtrx.png
ha_category: Light
ha_release: 0.7.5
ha_iot_class: "Assumed State"
---
The `rfxtrx` platform support lights that communicate in the frequency range of 433.92 MHz.

View File

@ -10,6 +10,7 @@ footer: true
logo: bus_scs.png
ha_category: Light
ha_release: 0.13
ha_iot_class: "Local Polling"
---
The SCSGate device can control lights of the BTicino MyHome system.
@ -19,11 +20,11 @@ To enable SCSGate lights in your installation, add the following to your `config
```yaml
# Example configuration.yaml entry
light:
platform: scsgate
devices:
living_room:
name: Living Room
scs_id: XXXXX
- platform: scsgate
devices:
living_room:
name: Living Room
scs_id: XXXXX
```
Configuration variables:

View File

@ -14,7 +14,7 @@ ha_release: pre 0.7
---
The wink light platform allows you to use your [Wink](http://www.wink.com/) lights.
The `wink` light platform allows you to use your [Wink](http://www.wink.com/) lights.
The requirement is that you have setup [Wink](/components/wink/).

View File

@ -10,6 +10,7 @@ footer: true
logo: yeelight.png
ha_category: Light
ha_release: 0.32
ha_iot_class: "Local Polling"
---
The `yeelight` light platform allows you to control your Yeelight Wifi bulbs with Home Assistant.

View File

@ -9,6 +9,7 @@ sharing: true
footer: true
ha_category: Light
ha_release: 0.39
ha_iot_class: "Local Polling"
---
The `yeelightsunflower` light platform allows you to control your Yeelight Sunflower light bulbs with Home Assistant.

View File

@ -9,8 +9,7 @@ sharing: true
footer: true
logo: zigbee.png
ha_category: Light
ha_iot_class: "Local Polling"
---
To get your ZigBee lights working with Home Assistant, follow the
instructions for the general [ZigBee Home Automation
component](/components/zha/).
To get your ZigBee lights working with Home Assistant, follow the instructions for the general [ZigBee Home Automation component](/components/zha/).

View File

@ -14,4 +14,4 @@ ha_iot_class: "Local Push"
The `isy994` platform allows you to get data from your [ISY994](https://www.universal-devices.com/residential/isy994i-series/) lock from within Home Assistant.
They will be automatically discovered if the isy994 component is loaded.
They will be automatically discovered if the `isy994` component is loaded.

View File

@ -10,6 +10,7 @@ footer: true
logo: verisure.png
ha_category: Lock
ha_release: 0.13
ha_iot_class: "Cloud Polling"
---

View File

@ -10,6 +10,7 @@ footer: true
logo: netatmo.png
ha_category: Hub
ha_release: "0.20"
ha_iot_class: "Cloud Polling"
---
@ -28,15 +29,15 @@ netatmo:
Configuration variables:
- **api_key** (*Required*): The API key for your netatmo account.
- **secret_key** (*Required*): Your netatmo secret key
- **username** (*Required*): Username for the netatmo account.
- **password** (*Required*): Password for the netatmo account.
- **api_key** (*Required*): The API key for your Netatmo account.
- **secret_key** (*Required*): Your Netatmo secret key
- **username** (*Required*): Username for the Netatmo account.
- **password** (*Required*): Password for the Netatmo account.
- **discovery** (*Optional)*: Whether to discover Netatmo devices. Set it to False, if you want to choose which Netatmo device you want to add (default True).
### {% linkable_title Get API and Secret Key %}
To get your API credentials, you have to declare a new application in the [NetAtmo Developer Page](https://dev.netatmo.com/). Sign in using your username and password from your regular NetAtmo account.
To get your API credentials, you have to declare a new application in the [NetAtmo Developer Page](https://dev.netatmo.com/). Sign in using your username and password from your regular Netatmo account.
Click on 'Create an App' at the top of the page.
<p class='img'>

View File

@ -10,6 +10,7 @@ footer: true
logo: raspihats.png
ha_category: DIY
ha_release: 0.45
ha_iot_class: "Local Push"
---
The `raspihats` component is the base for all related Raspihats platforms in Home Assistant. There is no setup needed for the component itself, for the platforms please check their corresponding pages.

View File

@ -10,6 +10,7 @@ footer: true
logo: raspberry-pi.png
ha_category: DIY
ha_release: pre 0.7
ha_iot_class: "Local Push"
---
The `rpi_gpio` component is the base for all related GPIO platforms in Home Assistant. There is no setup needed for the component itself, for the platforms please check their corresponding pages.

View File

@ -10,6 +10,7 @@ footer: true
logo: raspberry-pi.png
ha_category: DIY
ha_release: 0.45
ha_iot_class: "Local Push"
---
The `rpi_pfio` component is the base for all related [PiFace Digital I/O (PFIO)](http://www.piface.org.uk/) platforms in Home Assistant. There is no setup needed for the component itself, for the platforms please check their corresponding pages.

View File

@ -10,6 +10,7 @@ footer: true
logo: bbox.png
ha_category: Sensor
ha_release: 0.31
ha_iot_class: "Local Push"
---
The `bbox` platform uses the [Bbox Modem Router](https://fr.wikipedia.org/wiki/Bbox/) from the French Internet provider Bouygues Telecom. Sensors are mainly bandwidth measures.

View File

@ -14,4 +14,4 @@ ha_iot_class: "Local Push"
The `isy994` platform allows you to get data from your [ISY994](https://www.universal-devices.com/residential/isy994i-series/) sensor from within Home Assistant.
They will be automatically discovered if the isy994 component is loaded.
They will be automatically discovered if the `isy994` component is loaded.

View File

@ -10,6 +10,7 @@ footer: true
logo: pvoutput.png
ha_category: Energy
ha_release: 0.33
ha_iot_class: "Cloud Polling"
---

View File

@ -9,7 +9,7 @@ sharing: true
footer: true
logo: verisure.png
ha_category: Sensor
featured: false
ha_iot_class: "Cloud Polling"
---
Integrates Verisure sensors into Home Assistant. See the [main component](/components/verisure/) for configuration instructions.

View File

@ -10,7 +10,7 @@ footer: true
logo: waqi.png
ha_category: Health
ha_release: 0.34
ha_iot_class: "Local Polling"
ha_iot_class: "Cloud Polling"
---
The `waqi` sensor platform will query [World Air Quality Index](http://aqicn.org) service to check AQI value for a specific set of locations. The resulting indexes will be added to the Home Assistant as sensor outputs.

View File

@ -10,6 +10,7 @@ footer: true
logo: beaglebone-black.png
ha_category: Switch
ha_release: 0.36
ha_iot_class: "Local Push"
---
The `bbb_gpio` switch platform allows you to control the GPIOs of your [BeagleBone Black](https://beagleboard.org/black).

View File

@ -14,4 +14,4 @@ ha_iot_class: "Local Push"
The `isy994` platform allows you to get data from your [ISY994](https://www.universal-devices.com/residential/isy994i-series/) switch from within Home Assistant.
They will be automatically discovered if the isy994 component is loaded.
They will be automatically discovered if the `isy994` component is loaded.

View File

@ -10,6 +10,7 @@ footer: true
logo: raspihats.png
ha_category: Switch
ha_release: 0.45
ha_iot_class: "Local Push"
---

View File

@ -10,6 +10,7 @@ footer: true
logo: raspberry-pi.png
ha_category: Switch
ha_release: pre 0.7
ha_iot_class: "Local Push"
---

View File

@ -10,6 +10,7 @@ footer: true
logo: raspberry-pi.png
ha_category: Switch
ha_release: 0.45
ha_iot_class: "Local Polling"
---
The `rpi_pfio` switch platform allows you to control the [PiFace Digital I/O](http://www.piface.org.uk/products/piface_digital/) module.

View File

@ -10,6 +10,7 @@ footer: true
logo: raspberry-pi.png
ha_category: Switch
ha_release: 0.19
ha_iot_class: "Assumed state"
---
@ -23,21 +24,21 @@ To enable, add the following to your `configuration.yaml`:
```yaml
# Example configuration.yaml entry
switch:
platform: rpi_rf
gpio: 17
switches:
bedroom_light:
code_on: 1234567
code_off: 1234568
ambilight:
pulselength: 200
code_on: 987654
code_off: 133742
living_room_light:
protocol: 5
code_on: 654321,565874,233555,149874
code_off: 654320,565873,233554,149873
signal_repetitions: 15
- platform: rpi_rf
gpio: 17
switches:
bedroom_light:
code_on: 1234567
code_off: 1234568
ambilight:
pulselength: 200
code_on: 987654
code_off: 133742
living_room_light:
protocol: 5
code_on: 654321,565874,233555,149874
code_off: 654320,565873,233554,149873
signal_repetitions: 15
```
Configuration variables:

View File

@ -9,6 +9,7 @@ sharing: true
footer: true
logo: verisure.png
ha_category: Switch
ha_iot_class: "Cloud Polling"
---

View File

@ -10,6 +10,7 @@ footer: true
logo: tado.png
ha_category: Hub
ha_release: 0.41
ha_iot_class: "Cloud Polling"
---

View File

@ -10,6 +10,7 @@ footer: true
logo: verisure.png
ha_category: Hub
ha_release: pre 0.7
ha_iot_class: "Cloud Polling"
---
Home Assistant has support to integrate your [Verisure](https://www.verisure.com/) devices.

View File

@ -11,6 +11,7 @@ logo: zabbix.png
ha_category: System Monitor
featured: false
ha_release: 0.37
ha_iot_class: "Local Polling"
---
The `zabbix` component is the main component to connect to a [Zabbix](http://www.zabbix.com/) monitoring instance via the Zabbix API.