mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-07-22 16:56:50 +00:00
Merge remote-tracking branch 'origin/master' into next
Conflicts: source/getting-started/automation.markdown
This commit is contained in:
commit
de586c5433
@ -159,6 +159,10 @@ article.post, article.page, article.listing {
|
||||
text-decoration: none;
|
||||
}
|
||||
}
|
||||
|
||||
.frontpage a {
|
||||
text-decoration: none;
|
||||
}
|
||||
}
|
||||
|
||||
p.note {
|
||||
|
@ -9,6 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: alarmdotcom.png
|
||||
ha_category: Alarm
|
||||
ha_release: 0.11
|
||||
---
|
||||
|
||||
The `alarmdotcom` platform is consuming the information provided by a [Alarm.com](https://www.alarm.com/).
|
||||
|
@ -8,6 +8,7 @@ comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
ha_category: Alarm
|
||||
ha_release: 0.7.6
|
||||
---
|
||||
|
||||
|
||||
|
@ -9,6 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: apcupsd.png
|
||||
ha_category: Hub
|
||||
ha_release: 0.13
|
||||
---
|
||||
|
||||
[APCUPSd](http://www.apcupsd.org/) status information can be integrated into Home Assistant when the Network Information Server (NIS) [is configured](http://www.apcupsd.org/manual/manual.html#nis-server-client-configuration-using-the-net-driver) is enabled on the APC device.
|
||||
|
@ -9,6 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: apcupsd.png
|
||||
ha_category: Binary Sensor
|
||||
ha_release: 0.13
|
||||
---
|
||||
|
||||
In addition to the [APCUPSd Sensor](/components/sensor.apcupsd/) devices, you may also create a device which is simply "on" when the UPS status is online and "off" at all other times.
|
||||
|
@ -10,6 +10,7 @@ footer: true
|
||||
logo: arest.png
|
||||
ha_category: Binary Sensor
|
||||
ha_iot_class: "Local Polling"
|
||||
ha_release: 0.9
|
||||
---
|
||||
|
||||
|
||||
|
@ -9,6 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: bloomsky.png
|
||||
ha_category: Binary Sensor
|
||||
ha_release: 0.14
|
||||
---
|
||||
|
||||
The `bloomsky` binary sensor platform allows you to get data from your BloomSky device.
|
||||
|
@ -9,6 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: command_line.png
|
||||
ha_category: Binary Sensor
|
||||
ha_release: 0.12
|
||||
---
|
||||
|
||||
|
||||
|
@ -9,6 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: mqtt.png
|
||||
ha_category: Binary Sensor
|
||||
ha_release: 0.9
|
||||
---
|
||||
|
||||
|
||||
|
@ -9,7 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: mysensors.png
|
||||
ha_category: Binary Sensor
|
||||
featured: false
|
||||
ha_release: 0.14
|
||||
---
|
||||
|
||||
Integrates MySensors binary sensors into Home Assistant. See the [main component] for configuration instructions.
|
||||
|
@ -10,6 +10,7 @@ footer: true
|
||||
logo: networx.png
|
||||
ha_category: Binary Sensor
|
||||
ha_iot_class: "Local Push"
|
||||
ha_release: 0.14
|
||||
---
|
||||
|
||||
The `nx584` platform provides integration with GE, Caddx, Interlogix (and other brands) alarm panels that support the NX584 interface module (or have it built in). Supported panels include NX4/6/8/8E. Actual integration is done through [pynx584](http://github.com/kk7ds/pynx584) which is required for this to work.
|
||||
@ -48,4 +49,4 @@ binary_sensor:
|
||||
2: opening
|
||||
4: motion
|
||||
6: moisture
|
||||
```
|
||||
```
|
||||
|
@ -8,6 +8,7 @@ comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
ha_category: Binary Sensor
|
||||
ha_release: 0.10
|
||||
---
|
||||
|
||||
|
||||
|
@ -8,6 +8,7 @@ comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
ha_category: Binary Sensor
|
||||
ha_release: 0.14
|
||||
---
|
||||
|
||||
The TCP Binary Sensor is a type of [TCP Sensor](/components/sensor.tcp/) which is either "off" or "on". In order to use this sensor type, in addition to the configuration for the TCP Sensor, you must supply a `value_on` value to represent what is returned when the device is turned on.
|
||||
|
@ -9,6 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: wink.png
|
||||
ha_category: Binary Sensor
|
||||
ha_release: 0.14
|
||||
---
|
||||
|
||||
|
||||
|
@ -9,6 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: z-wave.png
|
||||
ha_category: Binary Sensor
|
||||
ha_release: 0.14
|
||||
---
|
||||
|
||||
To get your Z-Wave binary sensors working with Home Assistant, follow the instructions for the general [Z-Wave component](/components/zwave/).
|
||||
|
@ -10,6 +10,7 @@ footer: true
|
||||
logo: raspberry-pi.png
|
||||
ha_category: Camera
|
||||
ha_iot_class: "Local Polling"
|
||||
ha_release: 0.17
|
||||
---
|
||||
|
||||
|
||||
|
@ -9,6 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: ubiquiti.png
|
||||
ha_category: Camera
|
||||
ha_release: 0.13
|
||||
---
|
||||
|
||||
|
||||
|
@ -9,6 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: aruba.png
|
||||
ha_category: Presence Detection
|
||||
ha_release: 0.7
|
||||
---
|
||||
|
||||
|
||||
|
@ -10,6 +10,7 @@ footer: true
|
||||
logo: bluetooth.png
|
||||
ha_category: Presence Detection
|
||||
ha_iot_class: "Local Poll"
|
||||
ha_release: 0.18
|
||||
---
|
||||
|
||||
This tracker discovers new devices on boot and tracks bluetooth devices periodically based on interval_seconds value. Devices discovered are stored with 'bt_' as the prefix for device mac in `known_devices.yaml`.
|
||||
|
@ -9,6 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: avm.png
|
||||
ha_category: Presence Detection
|
||||
ha_release: 0.10
|
||||
---
|
||||
|
||||
|
||||
|
@ -9,6 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: icloud.png
|
||||
ha_category: Presence Detection
|
||||
ha_release: 0.10
|
||||
---
|
||||
|
||||
|
||||
|
@ -24,6 +24,7 @@ device_tracker:
|
||||
host: YOUR_ROUTER_IP
|
||||
username: YOUR_ADMIN_USERNAME
|
||||
password: YOUR_ADMIN_PASSWORD
|
||||
port: YOUR_ROUTER_PORT
|
||||
```
|
||||
|
||||
Configuration variables:
|
||||
@ -31,5 +32,6 @@ Configuration variables:
|
||||
- **host** (*Required*): The IP address of your router, e.g. 192.168.1.1.
|
||||
- **username** (*Required*: The username of an user with administrative privileges, usually *admin*.
|
||||
- **password** (*Required*): The password for your given admin account.
|
||||
- **port** (*Optional*): The port your router communicates with (defaults to 5000, but 80 is also known to be used on some models)
|
||||
|
||||
See the [device tracker component page](/components/device_tracker/) for instructions how to configure the people to be tracked.
|
||||
|
@ -9,6 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: network-snmp.png
|
||||
ha_category: Presence Detection
|
||||
ha_release: 0.7.5
|
||||
---
|
||||
|
||||
|
||||
|
@ -9,6 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: openwrt.png
|
||||
ha_category: Presence Detection
|
||||
ha_release: 0.7.6
|
||||
---
|
||||
|
||||
_This is one of the two ways we support OpenWRT. If you encounter problems, try [luci](/components/device_tracker.luci/)._
|
||||
|
@ -9,6 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: ubiquiti.png
|
||||
ha_category: Presence Detection
|
||||
ha_release: 0.14
|
||||
---
|
||||
|
||||
|
||||
|
@ -9,6 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: rss.gif
|
||||
ha_category: Other
|
||||
ha_release: 0.18
|
||||
---
|
||||
|
||||
Add an RSS/Atom feed reader that polls feeds every hour and sends new entries into the event bus.
|
||||
@ -26,3 +27,25 @@ feedreader:
|
||||
Configuration variables:
|
||||
|
||||
- **urls** (*Required*): List of URLS for your feeds.
|
||||
|
||||
Feedreader events can be used out of the box to trigger automation actions, e.g.:
|
||||
|
||||
```yaml
|
||||
automation:
|
||||
- alias: Trigger action when new element(s) in RSS feed
|
||||
trigger:
|
||||
platform: event
|
||||
event_type: feedreader
|
||||
action:
|
||||
service: script.turn_on
|
||||
entity_id: script.my_action
|
||||
```
|
||||
|
||||
For more advanced use cases, a custom component registering to the `feedreader` event type could be used instead:
|
||||
|
||||
```python
|
||||
EVENT_FEEDREADER = "feedreader"
|
||||
hass.bus.listen(EVENT_FEEDREADER, event_listener)
|
||||
```
|
||||
|
||||
To get started developing custom components, please refer to the [developers](/developers) documentation
|
||||
|
@ -9,6 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: mqtt.png
|
||||
ha_category: Garage Door
|
||||
ha_release: 0.18
|
||||
---
|
||||
|
||||
|
||||
|
@ -9,6 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: wink.png
|
||||
ha_category: Garage Door
|
||||
ha_release: 0.13
|
||||
---
|
||||
|
||||
Wink garage door functionality is currently limited to view only. Wink garage doors will still show the current state of the door, but control has been disabled for third parties. 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.
|
||||
|
@ -9,6 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo:
|
||||
ha_category: History
|
||||
ha_release: 0.13
|
||||
---
|
||||
|
||||
The `graphite` component records all events and state changes and feeds the data to a [graphite](http://graphite.wikidot.com/) instance.
|
||||
|
@ -10,6 +10,7 @@ footer: true
|
||||
logo: influxdb.png
|
||||
ha_category: "History"
|
||||
featured: true
|
||||
ha_release: 0.9
|
||||
---
|
||||
|
||||
The `influxdb` component makes it possible to transfer all state changes to an external [InfluxDB](https://influxdb.com/) database. For more details, [see the blog post on InfluxDB](/blog/2015/12/07/influxdb-and-grafana/).
|
||||
|
@ -9,6 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: home-assistant.png
|
||||
ha_category: Automation
|
||||
ha_release: 0.13
|
||||
---
|
||||
|
||||
The `input_select` component allows the user to define a list of values that can be selected via the frontend and can be used within conditions of automation. When a user selectes a new item, a state transition event is generated. This state event can be used in an `automation` trigger.
|
||||
|
@ -9,6 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: home-assistant.png
|
||||
ha_category: Automation
|
||||
ha_release: 0.16
|
||||
---
|
||||
|
||||
The `input_slider` component allows the user to define values that can be controlled via the frontend and can be used within conditions of automation. Changes to the slider generate state events. These state events can be utilized as `automation` triggers as well.
|
||||
|
@ -28,7 +28,7 @@ keyboard:
|
||||
|
||||
## {% linkable_title Dependencies %}
|
||||
|
||||
You may need to install platform-specific [dependencies for PyUserInput](https://github.com/SavinaRoja/PyUserInput#dependencies) in order to use the keyboard component. In most cases this can be done by running:
|
||||
You may need to install platform-specific [dependencies for PyUserInput](https://github.com/PyUserInput/PyUserInput#dependencies) in order to use the keyboard component. In most cases this can be done by running:
|
||||
|
||||
```bash
|
||||
$ pip3 install [package name]
|
||||
|
@ -9,6 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: blinkstick.png
|
||||
ha_category: Light
|
||||
ha_release: 0.7.5
|
||||
---
|
||||
|
||||
|
||||
|
@ -8,6 +8,7 @@ comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
ha_category: Light
|
||||
ha_release: 0.7.6
|
||||
---
|
||||
|
||||
This platform allows you to integrate your [Hyperion](https://github.com/tvdzwan/hyperion/wiki) into Home Assistant.
|
||||
|
@ -10,6 +10,7 @@ footer: true
|
||||
logo: lifx.png
|
||||
ha_category: Light
|
||||
ha_iot_class: "Local Push"
|
||||
ha_release: 0.12
|
||||
---
|
||||
|
||||
The `lifx` platform allows you to integrate your [LIFX](http://www.lifx.com) into Home Assistant.
|
||||
|
@ -10,6 +10,7 @@ footer: true
|
||||
logo: mysensors.png
|
||||
ha_category: Light
|
||||
featured: false
|
||||
ha_release: 0.13
|
||||
---
|
||||
|
||||
Integrates MySensors lights into Home Assistant. See the [main component] for configuration instructions.
|
||||
|
@ -8,6 +8,7 @@ comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
ha_category: Light
|
||||
ha_release: 0.7.5
|
||||
---
|
||||
|
||||
The `rfxtrx` platform support lights that communicate in the frequency range of 433.92 MHz.
|
||||
|
@ -9,6 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: bus_scs.png
|
||||
ha_category: Light
|
||||
ha_release: 0.13
|
||||
---
|
||||
|
||||
The SCSGate device can control lights of the BTicino MyHome system.
|
||||
|
@ -10,6 +10,7 @@ footer: true
|
||||
logo: belkin_wemo.png
|
||||
ha_category: Light
|
||||
ha_iot_class: "Local Polling"
|
||||
ha_release: 0.14
|
||||
---
|
||||
|
||||
|
||||
|
@ -9,6 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: mqtt.png
|
||||
ha_category: Lock
|
||||
ha_release: 0.15
|
||||
---
|
||||
|
||||
The `mqtt` lock platform let you control your MQTT enabled locks.
|
||||
|
@ -9,6 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: verisure.png
|
||||
ha_category: Lock
|
||||
ha_release: 0.13
|
||||
---
|
||||
|
||||
|
||||
|
@ -9,6 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: wink.png
|
||||
ha_category: Lock
|
||||
ha_release: 0.9
|
||||
---
|
||||
|
||||
|
||||
|
@ -9,6 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: firetv.png
|
||||
ha_category: Media Player
|
||||
ha_release: 0.7.6
|
||||
---
|
||||
|
||||
|
||||
|
@ -9,6 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: onkyo.png
|
||||
ha_category: Media Player
|
||||
ha_release: 0.17
|
||||
---
|
||||
|
||||
|
||||
|
@ -10,6 +10,7 @@ footer: true
|
||||
logo: panasonic.png
|
||||
ha_category: Media Player
|
||||
featured: false
|
||||
ha_release: 0.17
|
||||
---
|
||||
|
||||
The `panasonic_viera` platform allows you to control a Panasonic Viera TV.
|
||||
|
@ -10,6 +10,7 @@ footer: true
|
||||
logo: samsung.png
|
||||
ha_category: Media Player
|
||||
featured: false
|
||||
ha_release: 0.13
|
||||
---
|
||||
|
||||
The `samsungtv` platform allows you to control a [Samsung Smart TV](http://www.samsung.com/uk/consumer/tv-audio-video/televisions/).
|
||||
@ -35,6 +36,7 @@ Configuration variables:
|
||||
Currently known supported models:
|
||||
|
||||
- C7700
|
||||
- D7000
|
||||
- D8000
|
||||
- ES5500
|
||||
- ES6800
|
||||
|
@ -10,6 +10,7 @@ footer: true
|
||||
logo:
|
||||
ha_category: Media Player
|
||||
featured: false
|
||||
ha_release: 0.13
|
||||
---
|
||||
|
||||
The `snapcast` platform allows you to control [SnapCast](https://github.com/badaix/snapcast) from Home Assistant.
|
||||
|
@ -10,6 +10,7 @@ footer: true
|
||||
logo: webos.png
|
||||
ha_category: Media Player
|
||||
ha_iot_class: "Local Poll"
|
||||
ha_release: 0.18
|
||||
---
|
||||
|
||||
The `webostv` platform allows you to control a LG WebOS Smart TV.
|
||||
|
@ -9,6 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: yamaha.png
|
||||
ha_category: Media Player
|
||||
ha_release: 0.16
|
||||
---
|
||||
|
||||
The `yamaha` platform allows you to control [Yamaha Network Receivers](http://usa.yamaha.com/products/audio-visual/av-receivers-amps/rx) from Home Assistant.
|
||||
|
@ -9,6 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: mqtt.png
|
||||
ha_category: Other
|
||||
ha_release: 0.11
|
||||
---
|
||||
|
||||
The `mqtt_eventstream` components connects two Home Assistant instances via MQTT.
|
||||
|
@ -9,6 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: command_line.png
|
||||
ha_category: Notifications
|
||||
ha_release: 0.14
|
||||
---
|
||||
|
||||
The `command_line` platform allows you to use external tools for notifications from Home Assistant. The message will be passed in as STDIN.
|
||||
|
@ -9,6 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: free_mobile.png
|
||||
ha_category: Notifications
|
||||
ha_release: 0.11
|
||||
---
|
||||
|
||||
The `free_mobile` platform is using the French mobile operator [Free Mobile](http://mobile.free.fr/) to send SMS to your own cell phone.
|
||||
|
@ -9,6 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: gntp.png
|
||||
ha_category: Notifications
|
||||
ha_release: 0.16
|
||||
---
|
||||
|
||||
|
||||
|
@ -9,6 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: message_bird.png
|
||||
ha_category: Notifications
|
||||
ha_release: 0.16
|
||||
---
|
||||
|
||||
The `MessageBird` notification platform sends notifications as SMS messages using [MessageBird](https://www.messagebird.com/) to your mobile phone.
|
||||
|
@ -8,6 +8,7 @@ comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
ha_category: Notifications
|
||||
ha_release: 0.13
|
||||
---
|
||||
|
||||
|
||||
|
@ -9,6 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: telegram.png
|
||||
ha_category: Notifications
|
||||
ha_release: 0.7.5
|
||||
---
|
||||
|
||||
|
||||
|
@ -9,12 +9,13 @@ sharing: true
|
||||
footer: true
|
||||
logo: twitter.png
|
||||
ha_category: Notifications
|
||||
ha_release: 0.12
|
||||
---
|
||||
|
||||
|
||||
The `twitter` platform uses [Twitter](https://twitter.com) to delivery notifications from Home Assistant.
|
||||
|
||||
Go to [Twitter Apps](https://apps.twitter.com/app/new) and create an application. Visit "Keys and Access Tokens" of the application to get the details ("Consumer Key", "Consumer Secret", and "Access Token Secret" which needs to be generated).
|
||||
Go to [Twitter Apps](https://apps.twitter.com/app/new) and create an application. Visit "Keys and Access Tokens" of the application to get the details ("Consumer Key", "Consumer Secret", "Access Token" and "Access Token Secret" which needs to be generated).
|
||||
|
||||
To add Twitter to your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
@ -25,6 +26,7 @@ notify:
|
||||
platform: twitter
|
||||
consumer_key: ABCDEFGHJKLMNOPQRSTUVXYZ
|
||||
consumer_secret: ABCDEFGHJKLMNOPQRSTUVXYZ
|
||||
access_token: ABCDEFGHJKLMNOPQRSTUVXYZ
|
||||
access_token_secret: ABCDEFGHJKLMNOPQRSTUVXYZ
|
||||
```
|
||||
|
||||
@ -33,6 +35,7 @@ Configuration variables:
|
||||
- **name** (*Optional*): Setting the optional parameter `name` allows multiple notifiers to be created. The default value is `notify`. The notifier will bind to the service `notify.NOTIFIER_NAME`.
|
||||
- **consumer_key** (*Required*): Your "Consumer Key" (API Key) for the application.
|
||||
- **consumer_secret** (*Required*): Your "Consumer Secret" (API Secret) for the application.
|
||||
- **access_token** (*Required*): Your "Access Token" for the application.
|
||||
- **access_token_secret** (*Required*): Your "Access Token Secret" for the application.
|
||||
|
||||
To use notifications, please see the [getting started with automation page](/getting-started/automation/).
|
||||
|
@ -10,6 +10,7 @@ footer: true
|
||||
logo: webos.png
|
||||
ha_category: Notifications
|
||||
ha_iot_class: "Local Poll"
|
||||
ha_release: 0.18
|
||||
---
|
||||
|
||||
The `webostv` platform allows you to send notifications to a LG WebOS Smart TV.
|
||||
|
@ -9,6 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: home-assistant.png
|
||||
ha_category: Organization
|
||||
ha_release: 0.13
|
||||
---
|
||||
|
||||
The `proximity` component allows you to monitor the proximity of devices to a particular [zone](/components/zone/) and the direction of travel. The result is an entity created in Home Assistant which maintains the proximity data.
|
||||
|
@ -9,6 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: command_line.png
|
||||
ha_category: Rollershutter
|
||||
ha_release: 0.14
|
||||
---
|
||||
A rollershutter platform that issues specific commands when it is moved up, down and stopped. This might very well become our most powerful platform as it allows anyone to integrate any type of rollershutter into Home Assistant that can be controlled from the command line, including calling other scripts!
|
||||
|
||||
|
@ -9,6 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: mqtt.png
|
||||
ha_category: Rollershutter
|
||||
ha_release: 0.9
|
||||
---
|
||||
|
||||
|
||||
|
@ -9,6 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: hunter-douglas-powerview.png
|
||||
ha_category: Rollershutter
|
||||
ha_release: 0.15
|
||||
---
|
||||
|
||||
Implements the [Hunter Douglas PowerView](http://www.hunterdouglas.com/operating-systems/powerview-motorization/support) platform scene control. It queries the PowerView Hub and Home Assistant displays them as scenes.
|
||||
|
@ -9,6 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: bus_scs.png
|
||||
ha_category: Hub
|
||||
ha_release: 0.13
|
||||
---
|
||||
|
||||
The SCSGate component support the [SCSGate](https://translate.google.com/translate?hl=en&sl=it&tl=en&u=http%3A%2F%2Fguidopic.altervista.org%2Feibscsgt%2Finterface.html) device. This a homebrew device allows to interact with the MyHome system from BTicino/Legrande.
|
||||
|
@ -8,6 +8,7 @@ comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
ha_category: DIY
|
||||
ha_release: 0.7
|
||||
---
|
||||
|
||||
|
||||
|
@ -9,6 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: dweet.png
|
||||
ha_category: Sensor
|
||||
ha_release: 0.10
|
||||
---
|
||||
|
||||
The `dweet` sensor platform allows you to get details from your devices which are publishing their values to [Dweet.io](https://dweet.io/).
|
||||
|
@ -9,6 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: eliq.png
|
||||
ha_category: Sensor
|
||||
ha_release: 0.10
|
||||
---
|
||||
|
||||
|
||||
|
@ -10,6 +10,7 @@ footer: true
|
||||
logo: 'gtfs.png'
|
||||
ha_category: Sensor
|
||||
ha_iot_class: "Local Polling"
|
||||
ha_release: 0.17
|
||||
---
|
||||
|
||||
|
||||
|
@ -9,6 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: loop.png
|
||||
ha_category: Sensor
|
||||
ha_release: 0.17
|
||||
---
|
||||
|
||||
|
||||
|
@ -9,6 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: mqtt.png
|
||||
ha_category: Sensor
|
||||
ha_release: 0.7
|
||||
---
|
||||
|
||||
|
||||
|
@ -10,6 +10,7 @@ footer: true
|
||||
logo: neurio.png
|
||||
ha_category: Sensor
|
||||
ha_iot_class: "Cloud Polling"
|
||||
ha_release: 0.14
|
||||
---
|
||||
|
||||
|
||||
|
@ -9,6 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
ha_category: Sensor
|
||||
ha_iot_class: "Local Polling"
|
||||
ha_release: 0.17
|
||||
---
|
||||
|
||||
The `NZBGet` platform will allow you to monitor your downloads with [NZBGet](http://NZBGet.net) from within Home Assistant and setup automation based on the information.
|
||||
|
@ -8,6 +8,7 @@ comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
ha_category: Sensor
|
||||
ha_release: 0.12
|
||||
---
|
||||
|
||||
The `onewire` platform supports sensors which are using the One wire (1-wire) bus for communication.
|
||||
|
@ -10,6 +10,7 @@ footer: true
|
||||
logo: speedtest.png
|
||||
ha_category: Sensor
|
||||
featured: false
|
||||
ha_release: 0.13
|
||||
---
|
||||
|
||||
The `speedtest` sensor component uses the [Speedtest.net](https://speedtest.net/) web service to measure network bandwidth performance.
|
||||
|
@ -2,13 +2,15 @@
|
||||
layout: page
|
||||
title: "Steam"
|
||||
description: "Instructions on how to set up Steam sensors in Home Assistant."
|
||||
date: 2015-12-19 09:00
|
||||
date: 2016-04-30 09:00
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: steam.png
|
||||
ha_category: Sensor
|
||||
ha_iot_class: "Cloud Polling"
|
||||
ha_release: 0.14
|
||||
---
|
||||
|
||||
|
||||
|
@ -8,6 +8,7 @@ comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
ha_category: Sensor
|
||||
ha_release: 0.14
|
||||
---
|
||||
|
||||
The TCP component allows the integration of some services for which a specific Home Assistant component does not exist. If the service communicates over a TCP socket with a simple request/reply mechanism then the chances are that this component will allow integration with it.
|
||||
|
@ -8,6 +8,7 @@ comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
ha_category: Sensor
|
||||
ha_release: 0.12
|
||||
---
|
||||
|
||||
The `template` platform supports sensors which breaks out `state_attributes` from other entities.
|
||||
|
@ -10,6 +10,7 @@ footer: true
|
||||
logo: thinkingcleaner.png
|
||||
ha_category: Sensor
|
||||
ha_iot_class: "Local Poll"
|
||||
ha_release: 0.18
|
||||
---
|
||||
|
||||
The `ThinkingCleaner` sensor platform simple displays information about your [ThinkingCleaner](http://www.thinkingcleaner.com) addon.
|
||||
|
@ -9,6 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: torque.png
|
||||
ha_category: Sensor
|
||||
ha_release: 0.10
|
||||
---
|
||||
|
||||
The `torque` platform will allow you to monitor [Torque](http://torque-bhp.com/) data relayed from a bluetooth OBD2 stick via the Torque mobile application.
|
||||
|
@ -9,6 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: twitch.png
|
||||
ha_category: Sensor
|
||||
ha_release: 0.10
|
||||
---
|
||||
|
||||
|
||||
|
@ -10,6 +10,7 @@ footer: true
|
||||
logo: uber.png
|
||||
ha_category: Sensor
|
||||
ha_iot_class: "Cloud Polling"
|
||||
ha_release: 0.16
|
||||
---
|
||||
|
||||
|
||||
|
@ -9,6 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: yr.png
|
||||
ha_category: Weather
|
||||
ha_release: 0.11
|
||||
---
|
||||
|
||||
|
||||
|
@ -9,6 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: splunk.png
|
||||
ha_category: "History"
|
||||
ha_release: 0.13
|
||||
---
|
||||
|
||||
The `splunk` component makes it possible to log all state changes to an external [Splunk](http://splunk.com/) database using Splunk's HTTP Event Collector feature. You can either use this alone, or with the HomeAssistant for Splunk [app](https://github.com/miniconfig/splunk-homeassistant). Since the HEC feature is new to Splunk, you will need to use at least version 6.3.
|
||||
|
@ -8,6 +8,7 @@ comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
ha_category: "History"
|
||||
ha_release: 0.12
|
||||
---
|
||||
|
||||
The `statsd` component makes it possible to transfer all state changes to an external [StatsD](https://github.com/etsy/statsd) instance.
|
||||
|
@ -10,6 +10,7 @@ footer: true
|
||||
logo: arest.png
|
||||
ha_category: Switch
|
||||
ha_iot_class: "Local Polling"
|
||||
ha_release: 0.16
|
||||
---
|
||||
|
||||
The `arest` switch platform allows you to toggle pins of your devices (like Arduino boards with a ethernet/wifi connection, ESP8266 based devices, and the Raspberry Pi) running the [aREST](http://arest.io/) RESTful framework.
|
||||
|
@ -10,6 +10,7 @@ footer: true
|
||||
logo: dlink.png
|
||||
ha_category: Switch
|
||||
ha_iot_class: "Local Polling"
|
||||
ha_release: 0.14
|
||||
---
|
||||
|
||||
|
||||
|
@ -9,6 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: mqtt.png
|
||||
ha_category: Switch
|
||||
ha_release: 0.7
|
||||
---
|
||||
|
||||
The `mqtt` switch platform let you control your MQTT enabled light.
|
||||
|
@ -9,6 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: pulseaudio.png
|
||||
ha_category: Switch
|
||||
ha_release: 0.16
|
||||
---
|
||||
|
||||
|
||||
|
@ -8,6 +8,7 @@ comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
ha_category: Switch
|
||||
ha_release: 0.7.6
|
||||
---
|
||||
|
||||
|
||||
|
@ -8,6 +8,7 @@ comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
ha_category: Switch
|
||||
ha_release: 0.7.5
|
||||
---
|
||||
|
||||
The `rfxtrx` platform support switches that communicate in the frequency range of 433.92 MHz.
|
||||
|
@ -9,6 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: bus_scs.png
|
||||
ha_category: Switch
|
||||
ha_release: 0.13
|
||||
---
|
||||
|
||||
The SCSGate device can control switches of the BTicino MyHome system.
|
||||
|
@ -8,6 +8,7 @@ comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
ha_category: Switch
|
||||
ha_release: 0.13
|
||||
---
|
||||
|
||||
The `template` platform creates switches that combine components.
|
||||
|
@ -10,6 +10,7 @@ footer: true
|
||||
logo: thinkingcleaner.png
|
||||
ha_category: Switch
|
||||
ha_iot_class: "Local Poll"
|
||||
ha_release: 0.18
|
||||
---
|
||||
|
||||
The `ThinkingCleaner` switch platform allows you to control your [ThinkingCleaner](http://www.thinkingcleaner.com) addon.
|
||||
@ -22,4 +23,4 @@ switch:
|
||||
- platform: thinkingcleaner
|
||||
```
|
||||
|
||||
This will automatically add switches for each Thinking Cleaner in your network.
|
||||
This will automatically add switches for each Thinking Cleaner in your network.
|
||||
|
@ -9,6 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: ethernet.png
|
||||
ha_category: Switch
|
||||
ha_release: 0.16
|
||||
---
|
||||
|
||||
The `wake_on_lan` (WOL) switch platform allows you to turn on a [WOL](https://en.wikipedia.org/wiki/Wake-on-LAN) enabled computer.
|
||||
|
@ -10,6 +10,7 @@ footer: true
|
||||
logo: telldus.png
|
||||
ha_category: Hub
|
||||
featured: false
|
||||
ha_release: 0.11
|
||||
---
|
||||
|
||||
The `tellduslive` component let you connect to [Telldus Live](https://live.telldus.com). It's cloud platform that connects to your Tellstick connected gear at home.
|
||||
|
@ -9,6 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: ecobee.png
|
||||
ha_category: Thermostat
|
||||
ha_release: 0.9
|
||||
---
|
||||
|
||||
To get your Ecobee thermostats working with Home Assistant, follow the instructions for the general [Ecobee component](/components/ecobee/).
|
||||
|
@ -9,6 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: heatmiser.png
|
||||
ha_category: Thermostat
|
||||
ha_release: 0.10
|
||||
---
|
||||
|
||||
|
||||
|
@ -9,6 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: homematic.png
|
||||
ha_category: Thermostat
|
||||
ha_release: 0.9
|
||||
---
|
||||
|
||||
|
||||
|
@ -9,6 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: proliphix.png
|
||||
ha_category: Thermostat
|
||||
ha_release: 0.11
|
||||
---
|
||||
|
||||
|
||||
|
@ -9,6 +9,7 @@ sharing: true
|
||||
footer: true
|
||||
logo: z-wave.png
|
||||
ha_category: Thermostat
|
||||
ha_release: 0.17
|
||||
---
|
||||
|
||||
To get your Z-Wave thermostat working with Home Assistant, follow the instructions for the general [Z-Wave component](/components/zwave/).
|
||||
|
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