mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-07-23 17:27:19 +00:00
Merge branch 'current' into next
This commit is contained in:
Paulus Schoutsen
commit
08729e457e
@ -28,4 +28,10 @@ Configuration variables:
|
||||
|
||||
<p class='note'>
|
||||
This add-on is not compatible when you installed Hass.io via the generic Linux installer.
|
||||
|
||||
If you're coming from Rasbian or similar, use `root` rather than `pi` when connecting via ssh or else you will get this error.
|
||||
|
||||
```bash
|
||||
Permission denied (publickey,keyboard-interactive)
|
||||
```
|
||||
</p>
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: mqtt.png
|
||||
ha_category: Alarm
|
||||
ha_release: 0.7.4
|
||||
ha_iot_class: depends
|
||||
---
|
||||
|
||||
The `mqtt` alarm panel platform enables the possibility to control MQTT capable alarm panels. The Alarm icon will change state after receiving a new state from `state_topic`. If these messages are published with *RETAIN* flag, the MQTT alarm panel will receive an instant state update after subscription and will start with the correct state. Otherwise, the initial state will be `unknown`.
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: verisure.png
|
||||
ha_category: Alarm
|
||||
ha_release: 0.7.3
|
||||
ha_iot_class: "Cloud Polling"
|
||||
---
|
||||
|
||||
|
||||
|
||||
@ -20,7 +20,7 @@ The Wink alarm platform allows you to control your [Wink](http://www.wink.com/)
|
||||
The requirement is that you have setup [Wink](/components/wink/).
|
||||
|
||||
|
||||
### Supported devices
|
||||
### {% linkable_title Supported devices %}
|
||||
|
||||
- Canary all-in-one security camera
|
||||
|
||||
|
||||
@ -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.
|
||||
|
||||
@ -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
|
||||
```
|
||||
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: arlo.png
|
||||
ha_category: Hub
|
||||
ha_release: 0.46
|
||||
ha_iot_class: "Cloud Polling"
|
||||
---
|
||||
|
||||
The `arlo` implementation allows you to integrate your [Arlo](https://arlo.netgear.com/) devices in Home Assistant.
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: axis.png
|
||||
ha_category: Hub
|
||||
ha_release: "0.45"
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
[Axis Communications](https://www.axis.com/) devices are surveillance cameras and other security related network connected hardware. Sensor API works with firmware 5.50 and newer.
|
||||
|
||||
@ -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.
|
||||
|
||||
@ -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: 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).
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: eight_sleep.png
|
||||
ha_category: Binary Sensor
|
||||
ha_release: "0.44"
|
||||
ha_iot_class: "Cloud Polling"
|
||||
---
|
||||
|
||||
|
||||
|
||||
@ -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.
|
||||
|
||||
@ -10,7 +10,7 @@ footer: true
|
||||
logo: mqtt.png
|
||||
ha_category: Binary Sensor
|
||||
ha_release: 0.9
|
||||
ha_iot_class: "Depends"
|
||||
ha_iot_class: "depends"
|
||||
---
|
||||
|
||||
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: nest.png
|
||||
ha_category: Binary Sensor
|
||||
ha_release: pre 0.7
|
||||
ha_iot_class: "Cloud Polling"
|
||||
---
|
||||
|
||||
|
||||
|
||||
@ -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.
|
||||
|
||||
@ -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/) .
|
||||
|
||||
@ -19,7 +19,7 @@ The Wink binary sensor platform allows you to get data from your [Wink](http://w
|
||||
The requirement is that you have setup [Wink](/components/wink/).
|
||||
|
||||
|
||||
### Supported Binary sensor devices
|
||||
### {% linkable_title Supported Binary sensor devices %}
|
||||
|
||||
- Smoke and CO detectors (No Wink hub required for Nest)
|
||||
- Window/Door sensors
|
||||
|
||||
@ -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/).
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: blink.png
|
||||
ha_category: Hub
|
||||
ha_release: "0.40"
|
||||
ha_iot_class: "Cloud Polling"
|
||||
---
|
||||
|
||||
The `blink` component lets you view camera images and motion events from [Blink](http://blinkforhome.com) camera and security systems.
|
||||
|
||||
@ -9,6 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: amcrest.png
|
||||
ha_category: Camera
|
||||
ha_iot_class: "Local Polling"
|
||||
ha_release: 0.34
|
||||
---
|
||||
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: arlo.png
|
||||
ha_category: Camera
|
||||
ha_release: 0.46
|
||||
ha_iot_class: "Cloud Polling"
|
||||
---
|
||||
|
||||
To get your [Arlo](https://arlo.netgear.com/) cameras working within Home Assistant, please follow the instructions for the general [Arlo component](/components/arlo).
|
||||
|
||||
@ -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.
|
||||
|
||||
@ -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>
|
||||
|
||||
@ -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
|
||||
```
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: ffmpeg.png
|
||||
ha_category: Camera
|
||||
ha_release: 0.26
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
|
||||
|
||||
@ -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:
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: camcorder.png
|
||||
ha_category: Camera
|
||||
ha_release: pre 0.7
|
||||
ha_iot_class: "depends"
|
||||
---
|
||||
|
||||
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: mqtt.png
|
||||
ha_category: Camera
|
||||
ha_release: 0.43
|
||||
ha_iot_class: depends
|
||||
---
|
||||
|
||||
The `mqtt` camera platform allows you to integrate the content of an image file sent through MQTT into Home Assistant as a camera. Everytime a message under the `topic` in the configuration is received, the image displayed in Home Assistant will also be updated.
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: neato.png
|
||||
ha_category: Camera
|
||||
ha_release: 0.42
|
||||
ha_iot_class: "Cloud Polling"
|
||||
---
|
||||
|
||||
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: nest.png
|
||||
ha_category: Camera
|
||||
ha_release: 0.34
|
||||
ha_iot_class: "Cloud Polling"
|
||||
---
|
||||
|
||||
The `nest` platform allows you to watch the live stream of your [Nest](https://nest.com/camera/meet-nest-cam/) camera in Home Assistant.
|
||||
|
||||
@ -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:
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: synology.png
|
||||
ha_category: Camera
|
||||
ha_release: 0.31
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: ubiquiti.png
|
||||
ha_category: Camera
|
||||
ha_release: 0.13
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: verisure.png
|
||||
ha_category: Camera
|
||||
ha_release: 0.31
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: zoneminder.png
|
||||
ha_category: Camera
|
||||
ha_release: 0.39
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
|
||||
|
||||
@ -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.
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: heat-control.png
|
||||
ha_category: Climate
|
||||
ha_release: pre 0.7
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
|
||||
|
||||
@ -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.
|
||||
|
||||
@ -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.
|
||||
|
||||
@ -9,6 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: nest.png
|
||||
ha_category: Climate
|
||||
ha_iot_class: "Cloud Polling"
|
||||
---
|
||||
|
||||
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: netatmo.png
|
||||
ha_category: Climate
|
||||
ha_release: 0.31
|
||||
ha_iot_class: "Cloud Polling"
|
||||
---
|
||||
|
||||
|
||||
|
||||
@ -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/).
|
||||
|
||||
@ -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.
|
||||
|
||||
|
||||
@ -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:
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: tado.png
|
||||
ha_category: Climate
|
||||
ha_release: 0.41
|
||||
ha_iot_class: "Cloud Polling"
|
||||
---
|
||||
|
||||
|
||||
|
||||
@ -19,7 +19,7 @@ The Wink climate platform allows you to get data from your [Wink](http://www.win
|
||||
The requirement is that you have setup [Wink](/components/wink/).
|
||||
|
||||
|
||||
### Supported climate devices:
|
||||
### {% linkable_title Supported climate devices %}
|
||||
|
||||
- Nest (No wink hub required)
|
||||
- Ecobee (No wink hub required)
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: z-wave.png
|
||||
ha_category: Climate
|
||||
ha_release: 0.17
|
||||
ha_iot_class: "Local Push"
|
||||
---
|
||||
|
||||
|
||||
@ -25,7 +26,7 @@ To enable the climate component for your Z-Wave network, add the following to yo
|
||||
|
||||
```yaml
|
||||
climate:
|
||||
platform: zwave
|
||||
- platform: zwave
|
||||
```
|
||||
|
||||
Once enabled, any Z-Wave climate devices will be available to Home Assistant. Multiple entities may be created. The following entities are created for a Remotec ZXT-120.
|
||||
|
||||
@ -15,7 +15,7 @@ ha_category: "Voice"
|
||||
The conversation component can process sentences into commands for Home Assistant. It is currently limited to parsing commands in the format `turn <Friendly Name> <on/off>`.
|
||||
|
||||
|
||||
To enable the conversion option in your installation, add the following to your `configuration.yaml` file:
|
||||
To enable the conversation option in your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: garadget.png
|
||||
ha_category: Cover
|
||||
ha_release: 0.32
|
||||
ha_iot_class: "Cloud Polling"
|
||||
---
|
||||
|
||||
|
||||
|
||||
@ -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.
|
||||
|
||||
@ -9,6 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: lutron.png
|
||||
ha_category: Cover
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
To get your Lutron Caseta covers working with Home Assistant, follow the instructions for the general [Lutron Caseta component](/components/lutron_caseta/).
|
||||
|
||||
@ -9,6 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: mqtt.png
|
||||
ha_category: Cover
|
||||
ha_iot_class: "depends"
|
||||
ha_release: 0.18
|
||||
---
|
||||
|
||||
|
||||
@ -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.
|
||||
|
||||
@ -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: wink.png
|
||||
ha_category: Cover
|
||||
ha_release: 0.13
|
||||
ha_iot_class: "Cloud Polling"
|
||||
---
|
||||
|
||||
Wink cover/garage door functionality depends on the product you're using. With GoControl/Linear Home Assistant can open, close, and view state. Chamberlain is currently limited to view only. Meaning Home Assistant will only show the current state of the door and control has been disabled (by Chamberlain). If you have a Chamberlain garage door, and would like to control it via Home Assistant, please contact Chamberlain and request that they re-enabled third-party control.
|
||||
@ -21,7 +22,7 @@ The following quote is from Wink.
|
||||
The requirement is that you have setup [Wink](/components/wink/).
|
||||
|
||||
|
||||
### Supported cover devices
|
||||
### {% linkable_title Supported cover devices %}
|
||||
|
||||
- Bali window treatments
|
||||
- Lutron shades
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: z-wave.png
|
||||
ha_category: Cover
|
||||
ha_release: 0.23
|
||||
ha_iot_class: "Local Push"
|
||||
---
|
||||
|
||||
Z-Wave garage doors, blinds, and roller shutters are supported as cover in Home Assistant.
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: bbox.png
|
||||
ha_category: Presence Detection
|
||||
ha_release: "0.31"
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
|
||||
|
||||
@ -9,6 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: mqtt.png
|
||||
ha_category: Presence Detection
|
||||
ha_iot_class: depends
|
||||
---
|
||||
|
||||
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: mqtt.png
|
||||
ha_category: Presence Detection
|
||||
ha_version: 0.44
|
||||
ha_iot_class: depends
|
||||
---
|
||||
|
||||
|
||||
|
||||
@ -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.
|
||||
|
||||
@ -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.
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: wink.png
|
||||
ha_category: Fan
|
||||
ha_release: 0.36
|
||||
ha_iot_class: "Cloud Polling"
|
||||
---
|
||||
|
||||
|
||||
@ -18,7 +19,7 @@ The Wink fan platform allows you to control your [Wink](http://www.wink.com/) fa
|
||||
The requirement is that you have setup [Wink](/components/wink/).
|
||||
|
||||
|
||||
### Supported fan devices
|
||||
### {% linkable_title Supported fan devices %}
|
||||
|
||||
- Gardinier
|
||||
|
||||
|
||||
@ -8,7 +8,9 @@ comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: z-wave.png
|
||||
ha_release: 0.38
|
||||
ha_category: Fan
|
||||
ha_iot_class: "Local Push"
|
||||
---
|
||||
|
||||
To get your Z-Wave fans working with Home Assistant, follow the instructions for the general [Z-Wave component](/components/zwave/).
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: ifttt.png
|
||||
ha_category: Automation
|
||||
featured: true
|
||||
ha_iot_class: "Cloud Push"
|
||||
---
|
||||
|
||||
[IFTTT](https://ifttt.com) is a web service that allows users to create chains of simple conditional statements, so called "Applets". With the IFTTT component you can trigger applets through the **"Maker"** channel. See the [announcement blog post](/blog/2015/09/13/home-assistant-meets-ifttt/) for examples how to use it.
|
||||
|
||||
@ -12,6 +12,7 @@ ha_category: Image Processing
|
||||
featured: false
|
||||
ha_release: 0.45
|
||||
og_image: /images/screenshots/ssocr.png
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
The `seven_segments` image processing platform allows you to read physical seven segments displays through Home Assistant. [`ssocr`](https://www.unix-ag.uni-kl.de/~auerswal/ssocr/) is used to extract the value shown on the display which is observed by a [camera](/components/camera/). `ssocr` need to be available on your system. Check the installation instruction for Fedora below or use `$ sudo apt-get install ssocr` on a Debian-based system:
|
||||
|
||||
@ -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:
|
||||
|
||||
@ -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.
|
||||
|
||||
@ -42,7 +42,7 @@ Configuration variables:
|
||||
|
||||
The Hue API allows you to group lights. Home Assistant also supports grouping of entities natively, but sometimes it can be usefull to use Hue Groups to group light bulbs. By doing so, Home Assistant only needs to send one API call to change the state of all the bulbs in those groups instead of one call for every light in the group. This causes all the bulbs to change state simultaniously.
|
||||
|
||||
These Hue Groups can be a `Luminaire`, `Lightsource`, `LightGroup` or `Room`. The `Luminaire` and `Lightsource` can't be created manually since the Hue bridge manages these automatically based on the discovered bulbs. The `Room` and `LightGroup` can be created manually trough the API, or the mobile app. A bulb can only exist in one `Room`, but can exist in multiple `LightGroup`. The `LightGroup` can be usefull to link certain bulbs together since.
|
||||
These Hue Groups can be a `Luminaire`, `Lightsource`, `LightGroup` or `Room`. The `Luminaire` and `Lightsource` can't be created manually since the Hue bridge manages these automatically based on the discovered bulbs. The `Room` and `LightGroup` can be created manually through the API, or the mobile app. A bulb can only exist in one `Room`, but can exist in multiple `LightGroup`. The `LightGroup` can be usefull to link certain bulbs together since.
|
||||
|
||||
The 2nd generation Hue app only allows to create a `Room`. You need to use the first generation app or the API to create a `LightGroup`.
|
||||
|
||||
|
||||
@ -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:
|
||||
|
||||
|
||||
@ -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.
|
||||
|
||||
@ -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
|
||||
|
||||
@ -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.
|
||||
|
||||
|
||||
@ -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.
|
||||
|
||||
@ -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/).
|
||||
|
||||
@ -9,6 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: lutron.png
|
||||
ha_category: Light
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
To get your Lutron lights working with Home Assistant, follow the instructions for the general [Lutron component](/components/lutron/).
|
||||
|
||||
@ -9,6 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: lutron.png
|
||||
ha_category: Light
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
To get your Lutron Caseta lights working with Home Assistant, follow the instructions for the general [Lutron Caseta component](/components/lutron_caseta/).
|
||||
|
||||
@ -63,7 +63,7 @@ Turns one or multiple lights off.
|
||||
|
||||
| Service data attribute | Optional | Description |
|
||||
| ---------------------- | -------- | ----------- |
|
||||
| `entity_id` | no | String or list of strings that point at `entity_id`s of lights. Else targets all.
|
||||
| `entity_id` | yes | String or list of strings that point at `entity_id`s of lights. Else targets all.
|
||||
| `transition` | yes | Integer that represents the time the light should take to transition to the new state in seconds.
|
||||
|
||||
### {% linkable_title Service `light.toggle` %}
|
||||
|
||||
@ -9,6 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: mqtt.png
|
||||
ha_category: Light
|
||||
ha_iot_class: depends
|
||||
---
|
||||
|
||||
The `mqtt` light platform lets you control your MQTT enabled lights. It supports setting brightness, color temperature, effects, flashing, on/off, RGB colors, transitions, XY colors and white values.
|
||||
|
||||
@ -9,7 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: mqtt.png
|
||||
ha_category: Light
|
||||
ha_iot_class: "Local Push"
|
||||
ha_iot_class: depends
|
||||
ha_release: 0.26
|
||||
---
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: mqtt.png
|
||||
ha_category: Light
|
||||
ha_iot_class: "Local Push"
|
||||
ha_iot_class: depends
|
||||
ha_release: 0.33
|
||||
---
|
||||
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: mystrom.png
|
||||
ha_category: Light
|
||||
ha_release: 0.43
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
|
||||
|
||||
@ -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
|
||||
```
|
||||
|
||||
@ -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.
|
||||
|
||||
@ -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.
|
||||
|
||||
@ -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:
|
||||
|
||||
@ -9,7 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
ha_category: Light
|
||||
ha_iot_class: "Local Polling"
|
||||
featured: false
|
||||
ha_logo: tikteck.png
|
||||
ha_release: 0.36
|
||||
---
|
||||
|
||||
|
||||
@ -9,15 +9,17 @@ sharing: true
|
||||
footer: true
|
||||
logo: wink.png
|
||||
ha_category: Light
|
||||
ha_iot_class: "Cloud Polling"
|
||||
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/).
|
||||
|
||||
|
||||
### Supported light devices
|
||||
### {% linkable_title Supported light devices %}
|
||||
|
||||
- Z-wave switches with dimming
|
||||
- Hue
|
||||
|
||||
@ -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.
|
||||
|
||||
@ -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.
|
||||
|
||||
@ -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/).
|
||||
|
||||
@ -9,6 +9,8 @@ sharing: true
|
||||
footer: true
|
||||
logo: z-wave.png
|
||||
ha_category: Light
|
||||
ha_release: pre 0.7
|
||||
ha_iot_class: "Local Push"
|
||||
---
|
||||
|
||||
To get your Z-Wave lights working with Home Assistant, follow the instructions for the general [Z-Wave component](/components/zwave/).
|
||||
|
||||
@ -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.
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: verisure.png
|
||||
ha_category: Lock
|
||||
ha_release: 0.13
|
||||
ha_iot_class: "Cloud Polling"
|
||||
---
|
||||
|
||||
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: wink.png
|
||||
ha_category: Lock
|
||||
ha_release: 0.9
|
||||
ha_iot_class: "Cloud Polling"
|
||||
---
|
||||
|
||||
|
||||
|
||||
@ -10,6 +10,7 @@ footer: true
|
||||
logo: z-wave.png
|
||||
ha_category: Lock
|
||||
ha_release: 0.19
|
||||
ha_iot_class: "Local Push"
|
||||
---
|
||||
|
||||
To get your Z-Wave locks working with Home Assistant, follow the instructions for the general [Z-Wave component](/components/zwave/).
|
||||
|
||||
@ -11,6 +11,7 @@ logo: lutron.png
|
||||
ha_category: Hub
|
||||
featured: False
|
||||
ha_release: 0.37
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
[Lutron](http://www.lutron.com/) is an American lighting control company. They have several lines of home automation devices that manage light switches/dimmers, occupancy sensors, HVAC controls, etc. The `lutron` component in Home Assistant is responsible for communicating with the main hub for these systems.
|
||||
|
||||
@ -11,11 +11,13 @@ logo: lutron.png
|
||||
ha_category: Hub
|
||||
featured: False
|
||||
ha_release: 0.41
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
[Lutron](http://www.lutron.com/) is an American lighting control company. They have several lines of home automation devices that manage light switches/dimmers, occupancy sensors, HVAC controls, etc. The `lutron_caseta` component in Home Assistant is responsible for communicating with the Lutron SmartBridge for these systems. Both 'pro' and 'standard' models are supported.
|
||||
[Lutron](http://www.lutron.com/) is an American lighting control company. They have several lines of home automation devices that manage light switches/dimmers, occupancy sensors, HVAC controls, etc. The `lutron_caseta` component in Home Assistant is responsible for communicating with the Lutron SmartBridge for these systems. Both 'pro' and 'standard' models are supported.
|
||||
|
||||
This component only supports the Caseta line of products. The current supported Caseta devices are:
|
||||
|
||||
- Dimmers as Home Assistant lights
|
||||
- Wall switches as Home Assistant switches
|
||||
- Serena shades as Home Assistant covers
|
||||
|
||||
@ -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"
|
||||
---
|
||||
|
||||
|
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Loading…
x
Reference in New Issue
Block a user