Add HA release

2025-07-23 17:27:19 +00:00 · 2016-04-30 16:39:23 +02:00 · 2016-04-30 16:39:23 +02:00 · d8681f5333
commit d8681f5333
parent c28be4afe0
54 changed files with 55 additions and 3 deletions
--- a/source/_components/apcupsd.markdown
+++ b/source/_components/apcupsd.markdown
@ -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.
--- a/source/_components/binary_sensor.apcupsd.markdown
+++ b/source/_components/binary_sensor.apcupsd.markdown
@ -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.
--- a/source/_components/binary_sensor.bloomsky.markdown
+++ b/source/_components/binary_sensor.bloomsky.markdown
@ -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.
--- a/source/_components/binary_sensor.command_line.markdown
+++ b/source/_components/binary_sensor.command_line.markdown
@ -9,6 +9,7 @@ sharing: true
 footer: true
 logo: command_line.png
 ha_category: Binary Sensor
+ha_release: 0.12
 ---


--- a/source/_components/binary_sensor.mysensors.markdown
+++ b/source/_components/binary_sensor.mysensors.markdown
@ -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.
--- a/source/_components/binary_sensor.nx584.markdown
+++ b/source/_components/binary_sensor.nx584.markdown
@ -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.
--- a/source/_components/binary_sensor.tcp.markdown
+++ b/source/_components/binary_sensor.tcp.markdown
@ -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.
--- a/source/_components/binary_sensor.wink.markdown
+++ b/source/_components/binary_sensor.wink.markdown
@ -9,6 +9,7 @@ sharing: true
 footer: true
 logo: wink.png
 ha_category: Binary Sensor
+ha_release: 0.14
 ---


--- a/source/_components/binary_sensor.zwave.markdown
+++ b/source/_components/binary_sensor.zwave.markdown
@ -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/).
--- a/source/_components/camera.uvc.markdown
+++ b/source/_components/camera.uvc.markdown
@ -9,6 +9,7 @@ sharing: true
 footer: true
 logo: ubiquiti.png
 ha_category: Camera
+ha_release: 0.13
 ---


--- a/source/_components/device_tracker.unifi.markdown
+++ b/source/_components/device_tracker.unifi.markdown
@ -9,6 +9,7 @@ sharing: true
 footer: true
 logo: ubiquiti.png
 ha_category: Presence Detection
+ha_release: 0.14
 ---


--- a/source/_components/garage_door.wink.markdown
+++ b/source/_components/garage_door.wink.markdown
@ -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.
--- a/source/_components/graphite.markdown
+++ b/source/_components/graphite.markdown
@ -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.
--- a/source/_components/input_select.markdown
+++ b/source/_components/input_select.markdown
@ -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. 
--- a/source/_components/input_slider.markdown
+++ b/source/_components/input_slider.markdown
@ -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. 
--- a/source/_components/light.lifx.markdown
+++ b/source/_components/light.lifx.markdown
@ -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.
--- a/source/_components/light.mysensors.markdown
+++ b/source/_components/light.mysensors.markdown
@ -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.
--- a/source/_components/light.scsgate.markdown
+++ b/source/_components/light.scsgate.markdown
@ -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.
--- a/source/_components/light.wemo.markdown
+++ b/source/_components/light.wemo.markdown
@ -10,6 +10,7 @@ footer: true
 logo: belkin_wemo.png
 ha_category: Light
 ha_iot_class: "Local Polling"
+ha_release: 0.14
 ---


--- a/source/_components/lock.mqtt.markdown
+++ b/source/_components/lock.mqtt.markdown
@ -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.
--- a/source/_components/lock.verisure.markdown
+++ b/source/_components/lock.verisure.markdown
@ -9,6 +9,7 @@ sharing: true
 footer: true
 logo: verisure.png
 ha_category: Lock
+ha_release: 0.13
 ---


--- a/source/_components/media_player.panasonic_viera.markdown
+++ b/source/_components/media_player.panasonic_viera.markdown
@ -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.
--- a/source/_components/media_player.samsungtv.markdown
+++ b/source/_components/media_player.samsungtv.markdown
@ -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/).
--- a/source/_components/media_player.snapcast.markdown
+++ b/source/_components/media_player.snapcast.markdown
@ -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.
--- a/source/_components/media_player.webostv.markdown
+++ b/source/_components/media_player.webostv.markdown
@ -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.
--- a/source/_components/media_player.yamaha.markdown
+++ b/source/_components/media_player.yamaha.markdown
@ -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.
--- a/source/_components/notify.command_line.markdown
+++ b/source/_components/notify.command_line.markdown
@ -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.
--- a/source/_components/notify.gntp.markdown
+++ b/source/_components/notify.gntp.markdown
@ -9,6 +9,7 @@ sharing: true
 footer: true
 logo: gntp.png
 ha_category: Notifications
+ha_release: 0.16
 ---


--- a/source/_components/notify.message_bird.markdown
+++ b/source/_components/notify.message_bird.markdown
@ -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.
--- a/source/_components/notify.rest.markdown
+++ b/source/_components/notify.rest.markdown
@ -8,6 +8,7 @@ comments: false
 sharing: true
 footer: true
 ha_category: Notifications
+ha_release: 0.13
 ---


--- a/source/_components/notify.twitter.markdown
+++ b/source/_components/notify.twitter.markdown
@ -9,7 +9,7 @@ sharing: true
 footer: true
 logo: twitter.png
 ha_category: Notifications
-ha_release: 0.16
+ha_release: 0.12
 ---


--- a/source/_components/notify.webostv.markdown
+++ b/source/_components/notify.webostv.markdown
@ -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.
--- a/source/_components/proximity.markdown
+++ b/source/_components/proximity.markdown
@ -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.
--- a/source/_components/rollershutter.command_line.markdown
+++ b/source/_components/rollershutter.command_line.markdown
@ -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!

--- a/source/_components/scene.hunterdouglas_powerview.markdown
+++ b/source/_components/scene.hunterdouglas_powerview.markdown
@ -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.
--- a/source/_components/scsgate.markdown
+++ b/source/_components/scsgate.markdown
@ -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.
--- a/source/_components/sensor.loop_energy.markdown
+++ b/source/_components/sensor.loop_energy.markdown
@ -9,6 +9,7 @@ sharing: true
 footer: true
 logo: loop.png
 ha_category: Sensor
+ha_release: 0.17
 ---


--- a/source/_components/sensor.neurio_energy.markdown
+++ b/source/_components/sensor.neurio_energy.markdown
@ -10,6 +10,7 @@ footer: true
 logo: neurio.png
 ha_category: Sensor
 ha_iot_class: "Cloud Polling"
+ha_release: 0.14
 ---


--- a/source/_components/sensor.nzbget.markdown
+++ b/source/_components/sensor.nzbget.markdown
@ -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.
--- a/source/_components/sensor.onewire.markdown
+++ b/source/_components/sensor.onewire.markdown
@ -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.
--- a/source/_components/sensor.speedtest.markdown
+++ b/source/_components/sensor.speedtest.markdown
@ -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.
--- a/source/_components/sensor.tcp.markdown
+++ b/source/_components/sensor.tcp.markdown
@ -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.
--- a/source/_components/sensor.template.markdown
+++ b/source/_components/sensor.template.markdown
@ -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.
--- a/source/_components/sensor.uber.markdown
+++ b/source/_components/sensor.uber.markdown
@ -10,6 +10,7 @@ footer: true
 logo: uber.png
 ha_category: Sensor
 ha_iot_class: "Cloud Polling"
+ha_release: 0.16
 ---


--- a/source/_components/splunk.markdown
+++ b/source/_components/splunk.markdown
@ -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.
--- a/source/_components/statsd.markdown
+++ b/source/_components/statsd.markdown
@ -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.
--- a/source/_components/switch.dlink.markdown
+++ b/source/_components/switch.dlink.markdown
@ -10,6 +10,7 @@ footer: true
 logo: dlink.png
 ha_category: Switch
 ha_iot_class: "Local Polling"
+ha_release: 0.14
 ---


--- a/source/_components/switch.pulseaudio_loopback.markdown
+++ b/source/_components/switch.pulseaudio_loopback.markdown
@ -9,6 +9,7 @@ sharing: true
 footer: true
 logo: pulseaudio.png
 ha_category: Switch
+ha_release: 0.16
 ---


--- a/source/_components/switch.scsgate.markdown
+++ b/source/_components/switch.scsgate.markdown
@ -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.
--- a/source/_components/switch.template.markdown
+++ b/source/_components/switch.template.markdown
@ -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.
--- a/source/_components/switch.wake_on_lan.markdown
+++ b/source/_components/switch.wake_on_lan.markdown
@ -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.
--- a/source/_components/thermostat.zwave.markdown
+++ b/source/_components/thermostat.zwave.markdown
@ -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/).
--- a/source/_components/weblink.markdown
+++ b/source/_components/weblink.markdown
@ -9,6 +9,7 @@ sharing: true
 footer: true
 logo: 
 ha_category: Other
+ha_release: 0.13
 ---

 The `weblink` component allows you to display links in the Home Assistant frontend.
--- a/source/_components/zigbee.markdown
+++ b/source/_components/zigbee.markdown
@ -9,6 +9,7 @@ sharing: true
 footer: true
 logo: zigbee.png
 ha_category: DIY
+ha_release: 0.12
 ---

 [ZigBee](http://www.zigbee.org/what-is-zigbee/) integration for Home Assistant allows you to utilise modules such as the [XBee](http://www.digi.com/lp/xbee) as wireless General Purpose Input/Output (GPIO) devices. The component requires a local ZigBee device to be connected over a serial port. Through this it will send and receive commands to and from other devices on the ZigBee mesh network.