To get your Blink cameras working with Home Assistant, follow the instructions for the general [Blink component](/components/blink/). -
\ No newline at end of file + diff --git a/source/_components/camera.bloomsky.markdown b/source/_components/camera.bloomsky.markdown index 95a314cb1c..8661690eb6 100644 --- a/source/_components/camera.bloomsky.markdown +++ b/source/_components/camera.bloomsky.markdown @@ -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 ``` diff --git a/source/_components/camera.ffmpeg.markdown b/source/_components/camera.ffmpeg.markdown index 6f99665a3f..86e6355c8d 100644 --- a/source/_components/camera.ffmpeg.markdown +++ b/source/_components/camera.ffmpeg.markdown @@ -10,6 +10,7 @@ footer: true logo: ffmpeg.png ha_category: Camera ha_release: 0.26 +ha_iot_class: "Local Polling" --- diff --git a/source/_components/camera.foscam.markdown b/source/_components/camera.foscam.markdown index 9d24f5e844..ea90a82984 100644 --- a/source/_components/camera.foscam.markdown +++ b/source/_components/camera.foscam.markdown @@ -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: diff --git a/source/_components/camera.mjpeg.markdown b/source/_components/camera.mjpeg.markdown index 7e3dbdad55..a307590ca2 100644 --- a/source/_components/camera.mjpeg.markdown +++ b/source/_components/camera.mjpeg.markdown @@ -10,6 +10,7 @@ footer: true logo: camcorder.png ha_category: Camera ha_release: pre 0.7 +ha_iot_class: "depends" --- diff --git a/source/_components/camera.neato.markdown b/source/_components/camera.neato.markdown index 9954d924b5..f215a087a7 100644 --- a/source/_components/camera.neato.markdown +++ b/source/_components/camera.neato.markdown @@ -10,6 +10,7 @@ footer: true logo: neato.png ha_category: Camera ha_release: 0.42 +ha_iot_class: "Cloud Polling" --- diff --git a/source/_components/camera.netatmo.markdown b/source/_components/camera.netatmo.markdown index b569974d82..5ad8ebe38e 100644 --- a/source/_components/camera.netatmo.markdown +++ b/source/_components/camera.netatmo.markdown @@ -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: diff --git a/source/_components/camera.synology.markdown b/source/_components/camera.synology.markdown index 561f0d4160..d8b9d3f92c 100644 --- a/source/_components/camera.synology.markdown +++ b/source/_components/camera.synology.markdown @@ -10,6 +10,7 @@ footer: true logo: synology.png ha_category: Camera ha_release: 0.31 +ha_iot_class: "Local Polling" --- diff --git a/source/_components/camera.uvc.markdown b/source/_components/camera.uvc.markdown index 3587431d40..367f4472ca 100644 --- a/source/_components/camera.uvc.markdown +++ b/source/_components/camera.uvc.markdown @@ -10,6 +10,7 @@ footer: true logo: ubiquiti.png ha_category: Camera ha_release: 0.13 +ha_iot_class: "Local Polling" --- diff --git a/source/_components/camera.verisure.markdown b/source/_components/camera.verisure.markdown index 23c32cb914..e96a8725f7 100644 --- a/source/_components/camera.verisure.markdown +++ b/source/_components/camera.verisure.markdown @@ -10,6 +10,7 @@ footer: true logo: verisure.png ha_category: Camera ha_release: 0.31 +ha_iot_class: "Local Polling" --- diff --git a/source/_components/camera.zoneminder.markdown b/source/_components/camera.zoneminder.markdown index b0ad14b3db..d1fc230ecc 100644 --- a/source/_components/camera.zoneminder.markdown +++ b/source/_components/camera.zoneminder.markdown @@ -10,6 +10,7 @@ footer: true logo: zoneminder.png ha_category: Camera ha_release: 0.39 +ha_iot_class: "Local Polling" --- diff --git a/source/_components/climate.eq3btsmart.markdown b/source/_components/climate.eq3btsmart.markdown index 39915d9723..5b93fce6ff 100644 --- a/source/_components/climate.eq3btsmart.markdown +++ b/source/_components/climate.eq3btsmart.markdown @@ -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. diff --git a/source/_components/climate.generic_thermostat.markdown b/source/_components/climate.generic_thermostat.markdown index 9635689f5d..2184dc3b2c 100644 --- a/source/_components/climate.generic_thermostat.markdown +++ b/source/_components/climate.generic_thermostat.markdown @@ -10,6 +10,7 @@ footer: true logo: heat-control.png ha_category: Climate ha_release: pre 0.7 +ha_iot_class: "Local Polling" --- diff --git a/source/_components/climate.heatmiser.markdown b/source/_components/climate.heatmiser.markdown index ce68a92387..b772e9923b 100644 --- a/source/_components/climate.heatmiser.markdown +++ b/source/_components/climate.heatmiser.markdown @@ -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. diff --git a/source/_components/climate.honeywell.markdown b/source/_components/climate.honeywell.markdown index f57ecebc22..8a50fc5dd6 100644 --- a/source/_components/climate.honeywell.markdown +++ b/source/_components/climate.honeywell.markdown @@ -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 ```Scan interval is expressed in seconds. Omitting scan_interval may result in too-frequent polling and cause you to rate-limited by Honeywell. diff --git a/source/_components/climate.netatmo.markdown b/source/_components/climate.netatmo.markdown index 956cb50285..72c4f0de00 100644 --- a/source/_components/climate.netatmo.markdown +++ b/source/_components/climate.netatmo.markdown @@ -10,6 +10,7 @@ footer: true logo: netatmo.png ha_category: Climate ha_release: 0.31 +ha_iot_class: "Cloud Polling" --- diff --git a/source/_components/climate.oem.markdown b/source/_components/climate.oem.markdown index ff998539e8..c123b0e0f7 100644 --- a/source/_components/climate.oem.markdown +++ b/source/_components/climate.oem.markdown @@ -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/). diff --git a/source/_components/climate.proliphix.markdown b/source/_components/climate.proliphix.markdown index cc4e9e2078..d2c048762d 100644 --- a/source/_components/climate.proliphix.markdown +++ b/source/_components/climate.proliphix.markdown @@ -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. diff --git a/source/_components/climate.radiotherm.markdown b/source/_components/climate.radiotherm.markdown index 960f4a2645..f3cf3bd919 100644 --- a/source/_components/climate.radiotherm.markdown +++ b/source/_components/climate.radiotherm.markdown @@ -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: diff --git a/source/_components/climate.tado.markdown b/source/_components/climate.tado.markdown index 9df090db6c..c49a8ef4bd 100644 --- a/source/_components/climate.tado.markdown +++ b/source/_components/climate.tado.markdown @@ -10,6 +10,7 @@ footer: true logo: tado.png ha_category: Climate ha_release: 0.41 +ha_iot_class: "Cloud Polling" --- diff --git a/source/_components/cover.isy994.markdown b/source/_components/cover.isy994.markdown index fc9c114220..95aed3d3ba 100644 --- a/source/_components/cover.isy994.markdown +++ b/source/_components/cover.isy994.markdown @@ -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. diff --git a/source/_components/cover.rpi_gpio.markdown b/source/_components/cover.rpi_gpio.markdown index 4b19a8f55b..7b0fd775ac 100644 --- a/source/_components/cover.rpi_gpio.markdown +++ b/source/_components/cover.rpi_gpio.markdown @@ -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. diff --git a/source/_components/device_tracker.bbox.markdown b/source/_components/device_tracker.bbox.markdown index 0c067dc917..7a5cc91649 100644 --- a/source/_components/device_tracker.bbox.markdown +++ b/source/_components/device_tracker.bbox.markdown @@ -10,6 +10,7 @@ footer: true logo: bbox.png ha_category: Presence Detection ha_release: "0.31" +ha_iot_class: "Local Polling" --- diff --git a/source/_components/fan.isy994.markdown b/source/_components/fan.isy994.markdown index 6c1e7f1e07..6b9e55f289 100644 --- a/source/_components/fan.isy994.markdown +++ b/source/_components/fan.isy994.markdown @@ -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. diff --git a/source/_components/light.blinksticklight.markdown b/source/_components/light.blinksticklight.markdown index 2225a7cf46..9deab2be84 100644 --- a/source/_components/light.blinksticklight.markdown +++ b/source/_components/light.blinksticklight.markdown @@ -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: diff --git a/source/_components/light.hyperion.markdown b/source/_components/light.hyperion.markdown index 26a7c66736..4c25533665 100644 --- a/source/_components/light.hyperion.markdown +++ b/source/_components/light.hyperion.markdown @@ -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: diff --git a/source/_components/light.insteon_hub.markdown b/source/_components/light.insteon_hub.markdown index 0791c7c370..82c4df9aa5 100644 --- a/source/_components/light.insteon_hub.markdown +++ b/source/_components/light.insteon_hub.markdown @@ -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. diff --git a/source/_components/light.insteon_local.markdown b/source/_components/light.insteon_local.markdown index 87f8e0271a..14f91598c9 100644 --- a/source/_components/light.insteon_local.markdown +++ b/source/_components/light.insteon_local.markdown @@ -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 diff --git a/source/_components/light.insteon_plm.markdown b/source/_components/light.insteon_plm.markdown index 9a06948859..7c95d8dfe4 100644 --- a/source/_components/light.insteon_plm.markdown +++ b/source/_components/light.insteon_plm.markdown @@ -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. diff --git a/source/_components/light.isy994.markdown b/source/_components/light.isy994.markdown index 4a43240e72..8ae450edfc 100644 --- a/source/_components/light.isy994.markdown +++ b/source/_components/light.isy994.markdown @@ -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. diff --git a/source/_components/light.litejet.markdown b/source/_components/light.litejet.markdown index 422fe77f0c..d51cfd70c7 100644 --- a/source/_components/light.litejet.markdown +++ b/source/_components/light.litejet.markdown @@ -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/). diff --git a/source/_components/light.mystrom.markdown b/source/_components/light.mystrom.markdown index 1a41b8172d..ea1334c3f9 100644 --- a/source/_components/light.mystrom.markdown +++ b/source/_components/light.mystrom.markdown @@ -10,6 +10,7 @@ footer: true logo: mystrom.png ha_category: Light ha_release: 0.43 +ha_iot_class: "Local Polling" --- diff --git a/source/_components/light.piglow.markdown b/source/_components/light.piglow.markdown index efaff38edd..d261a81648 100644 --- a/source/_components/light.piglow.markdown +++ b/source/_components/light.piglow.markdown @@ -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 ``` diff --git a/source/_components/light.rflink.markdown b/source/_components/light.rflink.markdown index e596e1259b..705d7073c6 100644 --- a/source/_components/light.rflink.markdown +++ b/source/_components/light.rflink.markdown @@ -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. diff --git a/source/_components/light.rfxtrx.markdown b/source/_components/light.rfxtrx.markdown index 6f5b20f997..ee5c513fe8 100644 --- a/source/_components/light.rfxtrx.markdown +++ b/source/_components/light.rfxtrx.markdown @@ -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. diff --git a/source/_components/light.scsgate.markdown b/source/_components/light.scsgate.markdown index 5162abe217..5625b43cfb 100644 --- a/source/_components/light.scsgate.markdown +++ b/source/_components/light.scsgate.markdown @@ -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: diff --git a/source/_components/light.wink.markdown b/source/_components/light.wink.markdown index 1c9f721bd6..b5a76c090c 100644 --- a/source/_components/light.wink.markdown +++ b/source/_components/light.wink.markdown @@ -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/). diff --git a/source/_components/light.yeelight.markdown b/source/_components/light.yeelight.markdown index 94d600135c..056b6246da 100644 --- a/source/_components/light.yeelight.markdown +++ b/source/_components/light.yeelight.markdown @@ -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. diff --git a/source/_components/light.yeelightsunflower.markdown b/source/_components/light.yeelightsunflower.markdown index 324ee4b2e8..97d2a0a6d2 100644 --- a/source/_components/light.yeelightsunflower.markdown +++ b/source/_components/light.yeelightsunflower.markdown @@ -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. diff --git a/source/_components/light.zha.markdown b/source/_components/light.zha.markdown index fe71e06fc0..c3b0cc2d8b 100644 --- a/source/_components/light.zha.markdown +++ b/source/_components/light.zha.markdown @@ -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/). diff --git a/source/_components/lock.isy994.markdown b/source/_components/lock.isy994.markdown index 942cf7213b..04109b9cd6 100644 --- a/source/_components/lock.isy994.markdown +++ b/source/_components/lock.isy994.markdown @@ -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. diff --git a/source/_components/lock.verisure.markdown b/source/_components/lock.verisure.markdown index 61e901986e..2e72677179 100644 --- a/source/_components/lock.verisure.markdown +++ b/source/_components/lock.verisure.markdown @@ -10,6 +10,7 @@ footer: true logo: verisure.png ha_category: Lock ha_release: 0.13 +ha_iot_class: "Cloud Polling" --- diff --git a/source/_components/netatmo.markdown b/source/_components/netatmo.markdown index 286f0b78fe..e502e50e4f 100644 --- a/source/_components/netatmo.markdown +++ b/source/_components/netatmo.markdown @@ -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.
diff --git a/source/_components/raspihats.markdown b/source/_components/raspihats.markdown index 5e298c83be..3c1d33ed1e 100644 --- a/source/_components/raspihats.markdown +++ b/source/_components/raspihats.markdown @@ -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. diff --git a/source/_components/rpi_gpio.markdown b/source/_components/rpi_gpio.markdown index 18d2bab947..b0f2fdc370 100644 --- a/source/_components/rpi_gpio.markdown +++ b/source/_components/rpi_gpio.markdown @@ -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. diff --git a/source/_components/rpi_pfio.markdown b/source/_components/rpi_pfio.markdown index b9b8241aff..041693be58 100644 --- a/source/_components/rpi_pfio.markdown +++ b/source/_components/rpi_pfio.markdown @@ -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. diff --git a/source/_components/sensor.bbox.markdown b/source/_components/sensor.bbox.markdown index d88f988da8..ec3be264ac 100644 --- a/source/_components/sensor.bbox.markdown +++ b/source/_components/sensor.bbox.markdown @@ -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. diff --git a/source/_components/sensor.isy994.markdown b/source/_components/sensor.isy994.markdown index e449d7c54d..60913660ef 100644 --- a/source/_components/sensor.isy994.markdown +++ b/source/_components/sensor.isy994.markdown @@ -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. diff --git a/source/_components/sensor.pvoutput.markdown b/source/_components/sensor.pvoutput.markdown index dbdd7e8a9c..fe2d9b8e09 100644 --- a/source/_components/sensor.pvoutput.markdown +++ b/source/_components/sensor.pvoutput.markdown @@ -10,6 +10,7 @@ footer: true logo: pvoutput.png ha_category: Energy ha_release: 0.33 +ha_iot_class: "Cloud Polling" --- diff --git a/source/_components/sensor.verisure.markdown b/source/_components/sensor.verisure.markdown index 4435630d5b..75a4676365 100644 --- a/source/_components/sensor.verisure.markdown +++ b/source/_components/sensor.verisure.markdown @@ -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. diff --git a/source/_components/sensor.waqi.markdown b/source/_components/sensor.waqi.markdown index 30ac8d193a..ce920cfeff 100644 --- a/source/_components/sensor.waqi.markdown +++ b/source/_components/sensor.waqi.markdown @@ -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. diff --git a/source/_components/switch.bbb_gpio.markdown b/source/_components/switch.bbb_gpio.markdown index a77ac8560f..22feef16a6 100644 --- a/source/_components/switch.bbb_gpio.markdown +++ b/source/_components/switch.bbb_gpio.markdown @@ -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). diff --git a/source/_components/switch.isy994.markdown b/source/_components/switch.isy994.markdown index 124ee24c59..e5b4249dd6 100644 --- a/source/_components/switch.isy994.markdown +++ b/source/_components/switch.isy994.markdown @@ -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. diff --git a/source/_components/switch.raspihats.markdown b/source/_components/switch.raspihats.markdown index 0c13b8a168..674f2f99e4 100644 --- a/source/_components/switch.raspihats.markdown +++ b/source/_components/switch.raspihats.markdown @@ -10,6 +10,7 @@ footer: true logo: raspihats.png ha_category: Switch ha_release: 0.45 +ha_iot_class: "Local Push" --- diff --git a/source/_components/switch.rpi_gpio.markdown b/source/_components/switch.rpi_gpio.markdown index 691a1bd61d..639bcdc8a1 100644 --- a/source/_components/switch.rpi_gpio.markdown +++ b/source/_components/switch.rpi_gpio.markdown @@ -10,6 +10,7 @@ footer: true logo: raspberry-pi.png ha_category: Switch ha_release: pre 0.7 +ha_iot_class: "Local Push" --- diff --git a/source/_components/switch.rpi_pfio.markdown b/source/_components/switch.rpi_pfio.markdown index e5403e095d..d8e77e79fa 100644 --- a/source/_components/switch.rpi_pfio.markdown +++ b/source/_components/switch.rpi_pfio.markdown @@ -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. diff --git a/source/_components/switch.rpi_rf.markdown b/source/_components/switch.rpi_rf.markdown index 8a1d9c19b7..2d412034f5 100644 --- a/source/_components/switch.rpi_rf.markdown +++ b/source/_components/switch.rpi_rf.markdown @@ -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: diff --git a/source/_components/switch.verisure.markdown b/source/_components/switch.verisure.markdown index 9367b292cf..4169abe98d 100644 --- a/source/_components/switch.verisure.markdown +++ b/source/_components/switch.verisure.markdown @@ -9,6 +9,7 @@ sharing: true footer: true logo: verisure.png ha_category: Switch +ha_iot_class: "Cloud Polling" --- diff --git a/source/_components/tado.markdown b/source/_components/tado.markdown index 50f98e1909..34447a66d9 100644 --- a/source/_components/tado.markdown +++ b/source/_components/tado.markdown @@ -10,6 +10,7 @@ footer: true logo: tado.png ha_category: Hub ha_release: 0.41 +ha_iot_class: "Cloud Polling" --- diff --git a/source/_components/verisure.markdown b/source/_components/verisure.markdown index 5314204e59..3dccb534fe 100644 --- a/source/_components/verisure.markdown +++ b/source/_components/verisure.markdown @@ -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. diff --git a/source/_components/zabbix.markdown b/source/_components/zabbix.markdown index 80c8ea4487..0bc2fe72cb 100644 --- a/source/_components/zabbix.markdown +++ b/source/_components/zabbix.markdown @@ -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.