From 03d0d75ae1ef64d21e0bb390a54482aaf43dc05e Mon Sep 17 00:00:00 2001 From: Paulus Schoutsen Date: Sun, 25 Oct 2015 00:58:12 -0700 Subject: [PATCH] Component details pages added --- sass/custom/_paulus.scss | 26 ++++- sass/oscailte/base/_navigation.scss | 2 +- .../alarm_control_panel.manual.markdown | 8 +- .../_components/alarm_control_panel.markdown | 8 +- .../alarm_control_panel.mqtt.markdown | 8 +- source/_components/arduino.markdown | 8 +- source/_components/automation.markdown | 4 +- source/_components/browser.markdown | 6 +- source/_components/camera.foscam.markdown | 8 +- source/_components/camera.generic.markdown | 6 +- source/_components/configurator.markdown | 4 +- source/_components/conversation.markdown | 6 +- .../device_sun_light_trigger.markdown | 4 +- .../device_tracker.actiontec.markdown | 8 +- .../_components/device_tracker.aruba.markdown | 8 +- .../device_tracker.asuswrt.markdown | 8 +- .../_components/device_tracker.ddwrt.markdown | 8 +- .../device_tracker.geofancy.markdown | 8 +- .../_components/device_tracker.luci.markdown | 8 +- source/_components/device_tracker.markdown | 6 +- .../_components/device_tracker.mqtt.markdown | 6 +- .../device_tracker.netgear.markdown | 8 +- .../device_tracker.nmap_scanner.markdown | 8 +- .../device_tracker.owntracks.markdown | 8 +- .../_components/device_tracker.snmp.markdown | 8 +- .../device_tracker.thomson.markdown | 8 +- .../device_tracker.tomato.markdown | 8 +- .../device_tracker.tplink.markdown | 8 +- source/_components/discovery.markdown | 6 +- source/_components/downloader.markdown | 6 +- source/_components/group.markdown | 6 +- source/_components/history.markdown | 8 +- source/_components/ifttt.manything.markdown | 10 +- source/_components/ifttt.markdown | 6 +- source/_components/isy994.markdown | 4 +- source/_components/keyboard.markdown | 6 +- .../light.blinksticklight.markdown | 8 +- source/_components/light.hue.markdown | 8 +- .../_components/light.limitlessled.markdown | 8 +- source/_components/light.markdown | 4 +- source/_components/light.rfxtrx.markdown | 6 +- source/_components/light.tellstick.markdown | 8 +- source/_components/light.vera.markdown | 8 +- source/_components/light.wink.markdown | 6 +- source/_components/logbook.markdown | 6 +- source/_components/media_player.cast.markdown | 8 +- .../_components/media_player.denon.markdown | 8 +- .../_components/media_player.firetv.markdown | 8 +- .../_components/media_player.itunes.markdown | 8 +- source/_components/media_player.kodi.markdown | 8 +- source/_components/media_player.markdown | 4 +- source/_components/media_player.mpd.markdown | 8 +- source/_components/media_player.plex.markdown | 6 +- .../_components/media_player.sonos.markdown | 8 +- .../media_player.squeezebox.markdown | 8 +- source/_components/modbus.markdown | 6 +- source/_components/mqtt.markdown | 7 +- source/_components/notify.file.markdown | 10 +- source/_components/notify.instapush.markdown | 10 +- source/_components/notify.markdown | 4 +- source/_components/notify.nma.markdown | 10 +- source/_components/notify.pushbullet.markdown | 10 +- source/_components/notify.pushover.markdown | 10 +- source/_components/notify.slack.markdown | 10 +- source/_components/notify.smtp.markdown | 10 +- source/_components/notify.syslog.markdown | 10 +- source/_components/notify.telegram.markdown | 10 +- source/_components/notify.xmpp.markdown | 10 +- source/_components/rfxtrx.markdown | 6 +- source/_components/scene.markdown | 4 +- source/_components/script.markdown | 4 +- source/_components/sensor.arduino.markdown | 10 +- source/_components/sensor.arest.markdown | 8 +- source/_components/sensor.bitcoin.markdown | 8 +- .../sensor.command_sensor.markdown | 8 +- source/_components/sensor.cpuspeed.markdown | 8 +- source/_components/sensor.dht.markdown | 9 +- source/_components/sensor.efergy.markdown | 8 +- source/_components/sensor.forecast.markdown | 8 +- source/_components/sensor.glances.markdown | 8 +- source/_components/sensor.modbus.markdown | 8 +- source/_components/sensor.mqtt.markdown | 8 +- source/_components/sensor.mysensors.markdown | 8 +- .../sensor.openweathermap.markdown | 8 +- source/_components/sensor.rest.markdown | 8 +- source/_components/sensor.rfxtrx.markdown | 6 +- source/_components/sensor.rpi_gpio.markdown | 10 +- source/_components/sensor.sabnzbd.markdown | 8 +- .../sensor.swiss_public_transport.markdown | 8 +- .../_components/sensor.systemmonitor.markdown | 5 +- source/_components/sensor.tellstick.markdown | 8 +- source/_components/sensor.temper.markdown | 6 +- source/_components/sensor.time_date.markdown | 8 +- .../_components/sensor.transmission.markdown | 8 +- source/_components/sensor.vera.markdown | 8 +- source/_components/sensor.wink.markdown | 6 +- source/_components/sensor.worldclock.markdown | 8 +- source/_components/shell_command.markdown | 8 +- source/_components/simple_alarm.markdown | 6 +- source/_components/sun.markdown | 8 +- source/_components/switch.arduino.markdown | 10 +- source/_components/switch.arest.markdown | 8 +- .../switch.command_switch.markdown | 8 +- source/_components/switch.edimax.markdown | 8 +- source/_components/switch.hikvision.markdown | 10 +- source/_components/switch.markdown | 4 +- source/_components/switch.modbus.markdown | 8 +- source/_components/switch.mqtt.markdown | 8 +- source/_components/switch.rest.markdown | 8 +- source/_components/switch.rfxtrx.markdown | 6 +- source/_components/switch.rpi_gpio.markdown | 10 +- source/_components/switch.tellstick.markdown | 8 +- .../_components/switch.transmission.markdown | 8 +- source/_components/switch.vera.markdown | 8 +- source/_components/switch.wemo.markdown | 8 +- source/_components/switch.wink.markdown | 6 +- source/_components/tellstick.markdown | 8 +- .../thermostat.heat_control.markdown | 4 +- source/_components/thermostat.markdown | 4 +- source/_components/thermostat.nest.markdown | 8 +- .../thermostat.radiotherm.markdown | 8 +- source/_components/vera.markdown | 8 +- source/_components/verisure.markdown | 6 +- source/_components/wink.markdown | 8 +- source/_components/zone.markdown | 4 +- source/_components/zwave.markdown | 8 +- .../asides/component_navigation.html | 102 ++++++++++++++++++ source/_includes/custom/navigation.html | 2 +- source/_includes/site/sidebar.html | 12 ++- source/_layouts/component.html | 14 +++ 130 files changed, 610 insertions(+), 471 deletions(-) create mode 100644 source/_includes/asides/component_navigation.html create mode 100644 source/_layouts/component.html diff --git a/sass/custom/_paulus.scss b/sass/custom/_paulus.scss index 49b72efe3c9..47d94218c83 100644 --- a/sass/custom/_paulus.scss +++ b/sass/custom/_paulus.scss @@ -308,17 +308,26 @@ p.note { border-radius: 2px; box-shadow: rgba(0, 0, 0, 0.098) 0px 2px 4px, rgba(0, 0, 0, 0.098) 0px 0px 3px; padding: 8px; + text-align: center; .img-container { height: 50px; - text-align: center; margin-bottom: 8px; + font: 0/0 a; + + &:before { /* create a full-height inline block pseudo=element */ + content: ' '; + display: inline-block; + vertical-align: middle; /* vertical alignment of the inline element */ + height: 100%; + } img { max-width: 100%; max-height: 50px; box-shadow: none; border: none; + vertical-align: middle; } } @@ -337,3 +346,18 @@ p.note { } } } + +.aside-module { + .section { + margin-bottom: 16px; + } + + .brand-logo-container { + text-align: center; + height: 97px; + + img { + max-height: 97px; + } + } +} \ No newline at end of file diff --git a/sass/oscailte/base/_navigation.scss b/sass/oscailte/base/_navigation.scss index d043ff40514..ea581a0b4e9 100644 --- a/sass/oscailte/base/_navigation.scss +++ b/sass/oscailte/base/_navigation.scss @@ -14,7 +14,7 @@ body{ -webkit-animation: bugfix infinite 1s; } #toggle, .toggle { display: none; } .menu li { list-style: none; float:left; } -$menu-collapse: 790px; +$menu-collapse: 955px; // @media only screen and (max-width: $lap-end){ @media only screen and (max-width: $menu-collapse){ diff --git a/source/_components/alarm_control_panel.manual.markdown b/source/_components/alarm_control_panel.manual.markdown index 4196f4c0edd..ba32957c38d 100644 --- a/source/_components/alarm_control_panel.manual.markdown +++ b/source/_components/alarm_control_panel.manual.markdown @@ -1,16 +1,16 @@ --- -layout: page -title: "Manual alarm support" +layout: component +title: "Manual Alarm Control Panel" description: "Instructions how to integrate manual alarms into Home Assistant." date: 2015-10-13 19:10 -sidebar: false +sidebar: true comments: false sharing: true footer: true ha_category: Alarm Control Panel --- - + This platform enables you to set manual alarms in Home Assistant. ```yaml diff --git a/source/_components/alarm_control_panel.markdown b/source/_components/alarm_control_panel.markdown index d5aab4a6621..a3eeb57e6c8 100644 --- a/source/_components/alarm_control_panel.markdown +++ b/source/_components/alarm_control_panel.markdown @@ -1,15 +1,15 @@ --- -layout: page -title: "Alarm panel support" +layout: component +title: "Alarm panel" description: "Instructions how to integrate Alarm Control Panels into Home Assistant." date: 2015-10-13 19:10 -sidebar: false +sidebar: true comments: false sharing: true footer: true --- - + Home Assistant can give you an interface with is similar to a classic alarm system. There are several panels supported: - [Manual](/components/alarm_control_panel.manual.html) diff --git a/source/_components/alarm_control_panel.mqtt.markdown b/source/_components/alarm_control_panel.mqtt.markdown index 300be40c126..f852f047ea4 100644 --- a/source/_components/alarm_control_panel.mqtt.markdown +++ b/source/_components/alarm_control_panel.mqtt.markdown @@ -1,9 +1,9 @@ --- -layout: page -title: "MQTT alarm support" +layout: component +title: "MQTT Alarm Control Panel" description: "Instructions how to integrate MQTT alarms into Home Assistant." date: 2015-09-14 19:10 -sidebar: false +sidebar: true comments: false sharing: true footer: true @@ -11,7 +11,7 @@ logo: mqtt.png ha_category: "Alarm Control Panel" --- - + This platform enables the possibility to control an MQTT alarm. The alarm will only change state after receiving the a new state from `state_topic`. If these messages are published with RETAIN flag, the MQTT alarm will receive an instant state update after subscription and will start with correct state. Otherwise, diff --git a/source/_components/arduino.markdown b/source/_components/arduino.markdown index 891d7d37505..94b9bb5aba3 100644 --- a/source/_components/arduino.markdown +++ b/source/_components/arduino.markdown @@ -1,20 +1,16 @@ --- -layout: page +layout: component title: "Arduino" description: "Instructions how to setup an Arduino boards within Home Assistant." date: 2015-06-27 10:28 -sidebar: false +sidebar: true comments: false sharing: true footer: true logo: arduino.png ha_category: DIY -logo: arduino.png -ha_category: Hub --- - - 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. There are a lot of extensions (so called [shields](https://www.arduino.cc/en/Main/ArduinoShields)) available. Those shields can be plugged-in into the existing connectors and stacked on top of each other. This makes it possible to expand the capabilities of the Arduino boards. diff --git a/source/_components/automation.markdown b/source/_components/automation.markdown index 948ee2d8241..a4467083997 100644 --- a/source/_components/automation.markdown +++ b/source/_components/automation.markdown @@ -1,9 +1,9 @@ --- -layout: page +layout: component title: "Automation" description: "Instructions how to setup automation within Home Assistant." date: 2015-01-20 22:36 -sidebar: false +sidebar: true comments: false sharing: true footer: true diff --git a/source/_components/browser.markdown b/source/_components/browser.markdown index 6d9b5055461..0a31cfca145 100644 --- a/source/_components/browser.markdown +++ b/source/_components/browser.markdown @@ -1,16 +1,16 @@ --- -layout: page +layout: component title: "Browser" description: "Instructions how to setup the browser component with Home Assistant." date: 2015-01-24 14:39 -sidebar: false +sidebar: true comments: false sharing: true footer: true ha_category: Other --- - + The browser component provides a service to open urls in the default browser on the host machine. To load this component, add the following lines to your `configuration.yaml`: diff --git a/source/_components/camera.foscam.markdown b/source/_components/camera.foscam.markdown index 7ade3382127..9fd47c6a9fc 100644 --- a/source/_components/camera.foscam.markdown +++ b/source/_components/camera.foscam.markdown @@ -1,9 +1,9 @@ --- -layout: page -title: "Foscam IP camera support" +layout: component +title: "Foscam IP camera" description: "Instructions how to integrate Foscam IP cameras within Home Assistant." date: 2015-09-17 08:01 -sidebar: false +sidebar: true comments: false sharing: true footer: true @@ -11,7 +11,7 @@ logo: foscam.png ha_category: Camera --- - + The foscam platform allows you to watch the live stream of your [Foscam](http://www.foscam.com/) IP camera in Home Assistant. To enable your Foscam IP camera in your installation, add the following to your `configuration.yaml` file: diff --git a/source/_components/camera.generic.markdown b/source/_components/camera.generic.markdown index 6ab31c9a80b..63729d80ac2 100644 --- a/source/_components/camera.generic.markdown +++ b/source/_components/camera.generic.markdown @@ -1,15 +1,15 @@ --- -layout: page +layout: component title: "Generic IP Camera" description: "Instructions how to integrate IP cameras within Home Assistant." date: 2015-07-11 0:36 -sidebar: false +sidebar: true comments: false sharing: true footer: true ha_category: Camera --- - + This component allows you to integrate any IP camera into Home Assistant. It supports fetching images from a url with optional HTTP authentication. diff --git a/source/_components/configurator.markdown b/source/_components/configurator.markdown index 7e2ab437a2a..b633d970b24 100644 --- a/source/_components/configurator.markdown +++ b/source/_components/configurator.markdown @@ -1,9 +1,9 @@ --- -layout: page +layout: component title: "Configurator" description: "Instructions how to integrate the configurator in your components." date: 2015-03-15 00:51 -sidebar: false +sidebar: true comments: false sharing: true footer: true diff --git a/source/_components/conversation.markdown b/source/_components/conversation.markdown index da1f41b9baf..803b4062eb7 100644 --- a/source/_components/conversation.markdown +++ b/source/_components/conversation.markdown @@ -1,15 +1,15 @@ --- -layout: page +layout: component title: "Conversation" description: "Instructions how to have conversations with your Home Assistant." date: 2015-03-15 00:39 -sidebar: false +sidebar: true comments: false sharing: true footer: true --- - + The conversation component can process sentences into commands for Home Assistant. It is currently limited to parsing commands in the format `turn `. To enable the conversion option in your installation, add the following to your `configuration.yaml` file: diff --git a/source/_components/device_sun_light_trigger.markdown b/source/_components/device_sun_light_trigger.markdown index 3e62262cd3c..741580bc552 100644 --- a/source/_components/device_sun_light_trigger.markdown +++ b/source/_components/device_sun_light_trigger.markdown @@ -1,9 +1,9 @@ --- -layout: page +layout: component title: "Automating your lights" description: "Instructions how to automate your lights with Home Assistant." date: 2015-01-20 22:36 -sidebar: false +sidebar: true comments: false sharing: true footer: true diff --git a/source/_components/device_tracker.actiontec.markdown b/source/_components/device_tracker.actiontec.markdown index 561fd9820b5..818c82d9224 100644 --- a/source/_components/device_tracker.actiontec.markdown +++ b/source/_components/device_tracker.actiontec.markdown @@ -1,9 +1,9 @@ --- -layout: page -title: "Actiontec support" +layout: component +title: "Actiontec" description: "Instructions how to integrate Actiontec routers into Home Assistant." date: 2015-08-30 19:00 -sidebar: false +sidebar: true comments: false sharing: true footer: true @@ -11,7 +11,7 @@ logo: actiontec.png ha_category: Presence Detection --- - + This platform allows you to detect presence by looking at connected devices to an [Actiontec](http://www.actiontec.com/) device. Supported devices (tested): diff --git a/source/_components/device_tracker.aruba.markdown b/source/_components/device_tracker.aruba.markdown index f98cd55c1fa..56f11c2f43b 100644 --- a/source/_components/device_tracker.aruba.markdown +++ b/source/_components/device_tracker.aruba.markdown @@ -1,9 +1,9 @@ --- -layout: page -title: "Aruba support" +layout: component +title: "Aruba" description: "Instructions how to integrate Aruba routers into Home Assistant." date: 2015-08-31 08:45 -sidebar: false +sidebar: true comments: false sharing: true footer: true @@ -11,7 +11,7 @@ logo: aruba.png ha_category: Presence Detection --- - + This platform allows you to detect presence by looking at connected devices to an [Aruba Instant](http://www.arubanetworks.com/products/networking/aruba-instant/) device. Supported devices (tested): diff --git a/source/_components/device_tracker.asuswrt.markdown b/source/_components/device_tracker.asuswrt.markdown index fd8fb6bc884..21a090edefa 100644 --- a/source/_components/device_tracker.asuswrt.markdown +++ b/source/_components/device_tracker.asuswrt.markdown @@ -1,9 +1,9 @@ --- -layout: page -title: "ASUSWRT support" +layout: component +title: "ASUSWRT" description: "Instructions how to integrate ASUSWRT based routers into Home Assistant." date: 2015-08-06 19:00 -sidebar: false +sidebar: true comments: false sharing: true footer: true @@ -11,7 +11,7 @@ logo: asus.png ha_category: Presence Detection --- - + This platform offers presence detection by looking at connected devices to a [ASUSWRT](http://event.asus.com/2013/nw/ASUSWRT/) based router.

diff --git a/source/_components/device_tracker.ddwrt.markdown b/source/_components/device_tracker.ddwrt.markdown index 11c6f9a8a63..cd4f644c929 100644 --- a/source/_components/device_tracker.ddwrt.markdown +++ b/source/_components/device_tracker.ddwrt.markdown @@ -1,9 +1,9 @@ --- -layout: page -title: "DD-WRT support" +layout: component +title: "DD-WRT" description: "Instructions how to integrate DD-WRT based routers into Home Assistant." date: 2015-05-11 09:00 -sidebar: false +sidebar: true comments: false sharing: true footer: true @@ -11,7 +11,7 @@ logo: ddwrt.png ha_category: Presence Detection --- - + This platform offers presence detection by looking at connected devices to a [DD-WRT](http://www.dd-wrt.com/site/index) based router. To use a DD-WRRT router in your installation, add the following to your `configuration.yaml` file: diff --git a/source/_components/device_tracker.geofancy.markdown b/source/_components/device_tracker.geofancy.markdown index 3531d6a364f..5fb2cf14d95 100644 --- a/source/_components/device_tracker.geofancy.markdown +++ b/source/_components/device_tracker.geofancy.markdown @@ -1,9 +1,9 @@ --- -layout: page -title: "Geofancy device tracker" +layout: component +title: "Geofancy" description: "Instructions how to use Geofancy to track devices in Home Assistant." date: 2015-10-13 19:00 -sidebar: false +sidebar: true comments: false sharing: true footer: true @@ -11,7 +11,7 @@ logo: geofancy.png ha_category: Presence Detection --- - + This platform allows you to detect presence using [Geofancy](https://my.geofancy.com/). Geofancy allows users to track their location on iOS devices. To integrate Geofancy in Home Assistant, add the following section to your `configuration.yaml` file: diff --git a/source/_components/device_tracker.luci.markdown b/source/_components/device_tracker.luci.markdown index 7e11db5b12e..c9d69c698f0 100644 --- a/source/_components/device_tracker.luci.markdown +++ b/source/_components/device_tracker.luci.markdown @@ -1,9 +1,9 @@ --- -layout: page -title: "OpenWRT support" +layout: component +title: "OpenWRT" description: "Instructions how to integrate OpenWRT routers into Home Assistant." date: 2015-03-23 19:59 -sidebar: false +sidebar: true comments: false sharing: true footer: true @@ -11,7 +11,7 @@ logo: openwrt.png ha_category: Presence Detection --- - + Before this scanner can be used you have to install the luci RPC package on OpenWRT: opkg install luci-mod-rpc. ```yaml diff --git a/source/_components/device_tracker.markdown b/source/_components/device_tracker.markdown index 174c21ac9b1..c4b8ec82bc8 100644 --- a/source/_components/device_tracker.markdown +++ b/source/_components/device_tracker.markdown @@ -1,9 +1,9 @@ --- -layout: page -title: "Device tracking" +layout: component +title: "Device Tracker" description: "Instructions how to setup device tracking within Home Assistant." date: 2015-01-20 22:36 -sidebar: false +sidebar: true comments: false sharing: true footer: true diff --git a/source/_components/device_tracker.mqtt.markdown b/source/_components/device_tracker.mqtt.markdown index 4f64b9bd60d..b6619412fde 100644 --- a/source/_components/device_tracker.mqtt.markdown +++ b/source/_components/device_tracker.mqtt.markdown @@ -1,9 +1,9 @@ --- -layout: page +layout: component title: "MQTT device tracker" description: "Instructions how to use MQTT to track devices in Home Assistant." date: 2015-09-19 20:41 -sidebar: false +sidebar: true comments: false sharing: true footer: true @@ -11,7 +11,7 @@ logo: mqtt.png ha_category: Presence Detection --- - + This platform allows you to detect presence by monitoring an MQTT topic for new locations. To use this platform, you specify a unique topic for each device. diff --git a/source/_components/device_tracker.netgear.markdown b/source/_components/device_tracker.netgear.markdown index ecc0f59814d..a35a4c58509 100644 --- a/source/_components/device_tracker.netgear.markdown +++ b/source/_components/device_tracker.netgear.markdown @@ -1,9 +1,9 @@ --- -layout: page -title: "Netgear support" +layout: component +title: "Netgear" description: "Instructions how to integrate Netgear routers into Home Assistant." date: 2015-03-23 19:59 -sidebar: false +sidebar: true comments: false sharing: true footer: true @@ -11,7 +11,7 @@ logo: netgear.png ha_category: Presence Detection --- - + This platform allows you to detect presence by looking at connected devices to a [Netgear](http://www.netgear.com/) device. ```yaml diff --git a/source/_components/device_tracker.nmap_scanner.markdown b/source/_components/device_tracker.nmap_scanner.markdown index 9728a65f91e..1f0fe645b8c 100644 --- a/source/_components/device_tracker.nmap_scanner.markdown +++ b/source/_components/device_tracker.nmap_scanner.markdown @@ -1,16 +1,16 @@ --- -layout: page -title: "Nmap support" +layout: component +title: "Nmap" description: "Instructions how to integrate Nmap into Home Assistant." date: 2015-03-23 19:59 -sidebar: false +sidebar: true comments: false sharing: true footer: true ha_category: Presence Detection --- - + As an alternative to the router-based device tracking, it is possible to directly scan the network for devices by using Nmap. The IP addresses to scan can be specified in any format that Nmap understands, including the network-prefix notation (`192.168.1.1/24`) and the range notation (`192.168.1.1-255`). diff --git a/source/_components/device_tracker.owntracks.markdown b/source/_components/device_tracker.owntracks.markdown index 6099f7d7178..d4bb034173b 100644 --- a/source/_components/device_tracker.owntracks.markdown +++ b/source/_components/device_tracker.owntracks.markdown @@ -1,9 +1,9 @@ --- -layout: page -title: "Owntracks device tracker" +layout: component +title: "Owntracks" description: "Instructions how to use Owntracks to track devices in Home Assistant." date: 2015-09-22 07:00 -sidebar: false +sidebar: true comments: false sharing: true footer: true @@ -11,7 +11,7 @@ logo: owntracks.png ha_category: Presence Detection --- - + This platform allows you to detect presence using [Owntracks](http://owntracks.org/). OwnTracks allows users to track their location on Android and iOS phones and publish it to an MQTT broker. This platform will connect to the broker and monitor for new locations. diff --git a/source/_components/device_tracker.snmp.markdown b/source/_components/device_tracker.snmp.markdown index fe25f4b4a25..65d6f09c7a3 100644 --- a/source/_components/device_tracker.snmp.markdown +++ b/source/_components/device_tracker.snmp.markdown @@ -1,9 +1,9 @@ --- -layout: page -title: "Generic SNMP support" +layout: component +title: "SNMP" description: "Instructions how to integrate SNMP into Home Assistant." date: 2015-10-08 12:00 -sidebar: false +sidebar: true comments: false sharing: true footer: true @@ -11,7 +11,7 @@ logo: network-snmp.png ha_category: Presence Detection --- - + Most wifi-accesspoints (WAP) and wifi-routers (WRT) support the Simple Network Management Protocol (SNMP). This is a standardized method for monitoring/manageing network connected devices. SNMP uses a tree-like hierarchy where each node is an object. Many of these objects contain (live) lists of insances and metrics, like network interfaces, disks, and wifi registrations.

diff --git a/source/_components/device_tracker.thomson.markdown b/source/_components/device_tracker.thomson.markdown index 042db7f9d90..6d640b9deb9 100644 --- a/source/_components/device_tracker.thomson.markdown +++ b/source/_components/device_tracker.thomson.markdown @@ -1,9 +1,9 @@ --- -layout: page -title: "Thomson support" +layout: component +title: "Thomson" description: "Instructions how to integrate Thomson routers into Home Assistant." date: 2015-08-30 19:00 -sidebar: false +sidebar: true comments: false sharing: true footer: true @@ -11,7 +11,7 @@ logo: technicolor.png ha_category: Presence Detection --- - + Thomson produced networking equipment (under the brand name SpeedTouch) till 2010 and was then renamed to Technicolor. This platform allows you to detect presence by looking at connected devices to a [Thomson](http://www.technicolor.com) device. diff --git a/source/_components/device_tracker.tomato.markdown b/source/_components/device_tracker.tomato.markdown index 4204b0c1b34..886fd5ca88f 100644 --- a/source/_components/device_tracker.tomato.markdown +++ b/source/_components/device_tracker.tomato.markdown @@ -1,16 +1,16 @@ --- -layout: page -title: "Tomato support" +layout: component +title: "Tomato" description: "Instructions how to integrate Tomato routers into Home Assistant." date: 2015-03-23 19:59 -sidebar: false +sidebar: true comments: false sharing: true footer: true ha_category: Presence Detection --- - + Tomato requires an extra config variable called `http_id`. The value can be obtained by logging in to the Tomato admin interface and search for `http_id` in the page source code. ```yaml diff --git a/source/_components/device_tracker.tplink.markdown b/source/_components/device_tracker.tplink.markdown index 2bfd3fecdf1..5bae2e37865 100644 --- a/source/_components/device_tracker.tplink.markdown +++ b/source/_components/device_tracker.tplink.markdown @@ -1,9 +1,9 @@ --- -layout: page -title: "TP-Link support" +layout: component +title: "TP-Link" description: "Instructions how to integrate TP-Link routers into Home Assistant." date: 2015-06-22 10:30 -sidebar: false +sidebar: true comments: false sharing: true footer: true @@ -11,7 +11,7 @@ logo: tp-link.png ha_category: Presence Detection --- - + This platform allows you to detect presence by looking at connected devices to a [TP-Link](https://www.tp-link.com) device. This includes the ArcherC9 line. ```yaml diff --git a/source/_components/discovery.markdown b/source/_components/discovery.markdown index 0470fd8cbe9..bf0f9bc00f6 100644 --- a/source/_components/discovery.markdown +++ b/source/_components/discovery.markdown @@ -1,15 +1,15 @@ --- -layout: page +layout: component title: "Discovery" description: "Instructions how to setup Home Assistant to discover new devices." date: 2015-01-24 14:39 -sidebar: false +sidebar: true comments: false sharing: true footer: true --- - + Home Assistant can discover and automatically configure zeroconf/mDNS and uPnP devices on your network. Currently the `discovery` component can detect: * Google Chromecast diff --git a/source/_components/downloader.markdown b/source/_components/downloader.markdown index cbe326a5a2f..96e303c5235 100644 --- a/source/_components/downloader.markdown +++ b/source/_components/downloader.markdown @@ -1,16 +1,16 @@ --- -layout: page +layout: component title: "Downloader" description: "Instructions how to setup the downloader component with Home Assistant." date: 2015-01-24 14:39 -sidebar: false +sidebar: true comments: false sharing: true footer: true ha_category: Other --- - + The `downloader` component provides a service to download files. It will raise an error and not continue to set itself up when the download directory does not exist. To enable it, add the following lines to your `configuration.yaml`: diff --git a/source/_components/group.markdown b/source/_components/group.markdown index 7c1556ad4cf..a3bdfaea143 100644 --- a/source/_components/group.markdown +++ b/source/_components/group.markdown @@ -1,9 +1,9 @@ --- -layout: page -title: "Group support" +layout: component +title: "Group" description: "Instructions how to setup groups within Home Assistant." date: 2015-03-23 19:59 -sidebar: false +sidebar: true comments: false sharing: true footer: true diff --git a/source/_components/history.markdown b/source/_components/history.markdown index ef03866ef4e..ff13bf75c09 100644 --- a/source/_components/history.markdown +++ b/source/_components/history.markdown @@ -1,15 +1,15 @@ --- -layout: page -title: "History support" +layout: component +title: "History" description: "Instructions how to enable history support for Home Assistant." date: 2015-03-23 19:59 -sidebar: false +sidebar: true comments: false sharing: true footer: true --- - + This component will track everything that is going on within Home Assistant and allows the user to browse through it. To enable the history option in your installation, add the following to your `configuration.yaml` file: diff --git a/source/_components/ifttt.manything.markdown b/source/_components/ifttt.manything.markdown index 812fb262866..77a295be55b 100644 --- a/source/_components/ifttt.manything.markdown +++ b/source/_components/ifttt.manything.markdown @@ -1,14 +1,16 @@ --- -layout: page -title: "IFTTT - ManyThing Channel" +layout: component +title: "ManyThing" description: "Instructions how to setup ManyThing support with IFTTT." date: 2015-09-07 18:00 -sidebar: false +sidebar: true comments: false sharing: true footer: true +logo: manything.png +ha_category: Camera --- - + [Manything](https://manything.com) is a smart app that turns your iPhone, iPod, or iPad into a wifi camera for monitoring your home, your pets, anything! Comes with live streaming, motion activated alerts, cloud video recording, and more. diff --git a/source/_components/ifttt.markdown b/source/_components/ifttt.markdown index e390da00ff5..c0ca59cb3f9 100644 --- a/source/_components/ifttt.markdown +++ b/source/_components/ifttt.markdown @@ -1,16 +1,16 @@ --- -layout: page +layout: component title: "IFTTT" description: "Instructions how to setup IFTTT within Home Assistant." date: 2015-09-07 18:00 -sidebar: false +sidebar: true comments: false sharing: true footer: true logo: ifttt.png ha_category: Other --- - + [IFTTT](https://ifttt.com) is a web service that allows users to create chains of simple conditional statements, so called "recipes". With the ifttt component you can trigger recipes through the "maker" channel. See the [announcement blog post](/blog/2015/09/13/home-assistant-meets-ifttt/) for examples diff --git a/source/_components/isy994.markdown b/source/_components/isy994.markdown index 40b2ebe8a07..e8f3cbb1d5f 100644 --- a/source/_components/isy994.markdown +++ b/source/_components/isy994.markdown @@ -1,9 +1,9 @@ --- -layout: page +layout: component title: "ISY994 Controller" description: "Instructions how to setup the ISY994 controller within Home Assistant." date: 2015-01-20 22:36 -sidebar: false +sidebar: true comments: false sharing: true footer: true diff --git a/source/_components/keyboard.markdown b/source/_components/keyboard.markdown index d4dbd942286..6024c27c827 100644 --- a/source/_components/keyboard.markdown +++ b/source/_components/keyboard.markdown @@ -1,16 +1,16 @@ --- -layout: page +layout: component title: "Keyboard" description: "Instructions how to simulate key presses with Home Assistant." date: 2015-01-24 14:39 -sidebar: false +sidebar: true comments: false sharing: true footer: true ha_category: Other --- - + The `keyboard` component simulates key presses on the host machine. It currently offers the following Buttons as a Service (BaaS): * `keyboard/volume_up` diff --git a/source/_components/light.blinksticklight.markdown b/source/_components/light.blinksticklight.markdown index 6305a14662e..e1e1c186c7c 100644 --- a/source/_components/light.blinksticklight.markdown +++ b/source/_components/light.blinksticklight.markdown @@ -1,9 +1,9 @@ --- -layout: page -title: "Blinkstick support" +layout: component +title: "Blinkstick" description: "Instructions how to setup Blinkstick lights within Home Assistant." date: 2015-10-08 10:00 -sidebar: false +sidebar: true comments: false sharing: true footer: true @@ -11,7 +11,7 @@ logo: blinkstick.png ha_category: Light --- - + The blinkstick platform let you can control your [Blinkstick](https://www.blinkstick.com/) lights from within Home Assistant. To add blinkstick to your installation, add the following to your `configuration.yaml` file: diff --git a/source/_components/light.hue.markdown b/source/_components/light.hue.markdown index f7b8d3dcc51..7d08297894c 100644 --- a/source/_components/light.hue.markdown +++ b/source/_components/light.hue.markdown @@ -1,9 +1,9 @@ --- -layout: page -title: "Philips Hue support" +layout: component +title: "Philips Hue" description: "Instructions how to setup Philips Hue within Home Assistant." date: 2015-03-23 20:09 -sidebar: false +sidebar: true comments: false sharing: true footer: true @@ -11,7 +11,7 @@ logo: philips_hue.png ha_category: Light --- - + Philips Hue support is integrated into Home Assistant as a light platform. The preferred way to setup the Philips Hue platform is by enabling the [the discovery component]({{site_root}}/components/discovery.html). diff --git a/source/_components/light.limitlessled.markdown b/source/_components/light.limitlessled.markdown index 96c94b56563..2b0f7254682 100644 --- a/source/_components/light.limitlessled.markdown +++ b/source/_components/light.limitlessled.markdown @@ -1,16 +1,16 @@ --- -layout: page -title: "LimitlessLED support" +layout: component +title: "LimitlessLED" description: "Instructions how to setup LimitlessLED within Home Assistant." date: 2015-06-10 22:48 -sidebar: false +sidebar: true comments: false sharing: true footer: true ha_category: Light --- - + The limitlessled can control your [LimitlessLED](http://www.limitlessled.com/) lights from within Home Assistant. The lights are also known as EasyBulb, AppLight, AppLamp, MiLight, LEDme, dekolight or iLight. To add limitlessled to your installation, add the following to your `configuration.yaml` file: diff --git a/source/_components/light.markdown b/source/_components/light.markdown index 63435d0ef0f..0c3f44c2d1b 100644 --- a/source/_components/light.markdown +++ b/source/_components/light.markdown @@ -1,9 +1,9 @@ --- -layout: page +layout: component title: "Lights" description: "Instructions how to setup your lights with Home Assistant." date: 2015-01-24 14:39 -sidebar: false +sidebar: true comments: false sharing: true footer: true diff --git a/source/_components/light.rfxtrx.markdown b/source/_components/light.rfxtrx.markdown index c8f9c827730..e29e43bd8d7 100644 --- a/source/_components/light.rfxtrx.markdown +++ b/source/_components/light.rfxtrx.markdown @@ -1,9 +1,9 @@ --- -layout: page -title: "RFXtrx light support" +layout: component +title: "RFXtrx light" description: "Instructions how to integrate RFXtrx lights into Home Assistant." date: 2015-10-08 10:15 -sidebar: false +sidebar: true comments: false sharing: true footer: true diff --git a/source/_components/light.tellstick.markdown b/source/_components/light.tellstick.markdown index 5443fdfc6c8..ebda3cac136 100644 --- a/source/_components/light.tellstick.markdown +++ b/source/_components/light.tellstick.markdown @@ -1,9 +1,9 @@ --- -layout: page -title: "TellStick lights support" +layout: component +title: "TellStick lights" description: "Instructions how to integrate TellStick lights into Home Assistant." date: 2015-08-06 19:00 -sidebar: false +sidebar: true comments: false sharing: true footer: true @@ -11,7 +11,7 @@ logo: telldus_tellstick.png ha_category: Light --- - + This tellstick light platform allows you to control your [TellStick](http://www.telldus.se/products/tellstick) dimmers. To use your TellStick device in your installation, add the following to your `configuration.yaml` file: diff --git a/source/_components/light.vera.markdown b/source/_components/light.vera.markdown index 0a4d2cc38d9..bbf88b9090c 100644 --- a/source/_components/light.vera.markdown +++ b/source/_components/light.vera.markdown @@ -1,9 +1,9 @@ --- -layout: page -title: "Vera lights support" +layout: component +title: "Vera lights" description: "Instructions how to integrate Vera lights into Home Assistant." date: 2015-10-20 21:00 -sidebar: false +sidebar: true comments: false sharing: true footer: true @@ -11,7 +11,7 @@ logo: vera.png ha_category: Light --- - + This vera light platform allows you to control your [Vera](http://getvera.com/) lights. This platform is useful if you wish for switches connected to your Vera controller to appear as lights in Home Assistant. All switches will be added as a light unless you exclude them in the configuration file. diff --git a/source/_components/light.wink.markdown b/source/_components/light.wink.markdown index 7084a165d5c..2b90ef8196f 100644 --- a/source/_components/light.wink.markdown +++ b/source/_components/light.wink.markdown @@ -1,9 +1,9 @@ --- -layout: page +layout: component title: "Wink lights" description: "Instructions how to setup the Wink lights within Home Assistant." date: 2015-01-20 22:36 -sidebar: false +sidebar: true comments: false sharing: true footer: true @@ -11,7 +11,7 @@ logo: wink.png ha_category: Light --- - + The wink sensor platform allows you to use your [Wink](http://www.wink.com/) lights. The requirement is that you have setup your [Wink hub](/components/light.wink.html). diff --git a/source/_components/logbook.markdown b/source/_components/logbook.markdown index dd751c13655..c845dc2f2f9 100644 --- a/source/_components/logbook.markdown +++ b/source/_components/logbook.markdown @@ -1,9 +1,9 @@ --- -layout: page -title: "Logbook support" +layout: component +title: "Logbook" description: "Instructions how to enable the logbook component for Home Assistant." date: 2015-04-25 9:23 -sidebar: false +sidebar: true comments: false sharing: true footer: true diff --git a/source/_components/media_player.cast.markdown b/source/_components/media_player.cast.markdown index 8f586bccc9d..b0c478cc405 100644 --- a/source/_components/media_player.cast.markdown +++ b/source/_components/media_player.cast.markdown @@ -1,9 +1,9 @@ --- -layout: page -title: "Google Cast support" +layout: component +title: "Google Cast" description: "Instructions how to integrate Google Cast into Home Assistant." date: 2015-03-23 19:59 -sidebar: false +sidebar: true comments: false sharing: true footer: true @@ -11,7 +11,7 @@ logo: google_cast.png ha_category: Media Player --- - + Google Cast devices will be automatically discovered if you enable [the discovery component]({{site_root}}/components/discovery.html). There is a issue where Chromecasts can only be discovered if your device is connected to the same subnet as your Chromecast. Chromecast platform can also be forced to load by adding the following lines to your `configuration.yaml`: diff --git a/source/_components/media_player.denon.markdown b/source/_components/media_player.denon.markdown index d006c6fac7e..1b7890b98c0 100644 --- a/source/_components/media_player.denon.markdown +++ b/source/_components/media_player.denon.markdown @@ -1,9 +1,9 @@ --- -layout: page -title: "Denon Network Receivers support" +layout: component +title: "Denon Network Receivers" description: "Instructions how to integrate Denon Network Receivers into Home Assistant." date: 2015-09-08 09:00 -sidebar: false +sidebar: true comments: false sharing: true footer: true @@ -11,7 +11,7 @@ logo: denon.png ha_category: Media Player --- - + The denon platform allows you to control a [Denon Network Receivers](http://www.denon.co.uk/chg/product/compactsystems/networkmusicsystems/ceolpiccolo) from Home Assistant. Supported devices: diff --git a/source/_components/media_player.firetv.markdown b/source/_components/media_player.firetv.markdown index f1a285dbfa6..8f52a5582da 100644 --- a/source/_components/media_player.firetv.markdown +++ b/source/_components/media_player.firetv.markdown @@ -1,9 +1,9 @@ --- -layout: page -title: "FireTV support" +layout: component +title: "FireTV" description: "Instructions how to integrate Music Player Daemon into Home Assistant." date: 2015-10-23 18:00 -sidebar: false +sidebar: true comments: false sharing: true footer: true @@ -11,7 +11,7 @@ logo: firetv.png ha_category: Media Player --- - + The firetv platform allows you to control a [Amazon Fire TV/stick](http://www.amazon.com/Amazon-DV83YW-Fire-TV/dp/B00U3FPN4U). The python-firetv Python 2.x module with its helper script that exposes a HTTP server to fetch state and perform actions is used. diff --git a/source/_components/media_player.itunes.markdown b/source/_components/media_player.itunes.markdown index c98510c9a10..5e5c890353a 100644 --- a/source/_components/media_player.itunes.markdown +++ b/source/_components/media_player.itunes.markdown @@ -1,9 +1,9 @@ --- -layout: page -title: "iTunes support" +layout: component +title: "iTunes" description: "Instructions how to integrate iTunes into Home Assistant." date: 2015-06-22 11:00 -sidebar: false +sidebar: true comments: false sharing: true footer: true @@ -11,7 +11,7 @@ logo: itunes.png ha_category: Media Player --- - + The iTunes platform allows you to control [iTunes](http://apple.com/itunes/) from Home Assistant. It uses a 3rd party server that you run on your Mac called [itunes-api](https://github.com/maddox/itunes-api). Play, pause, or skip songs remotely on iTunes running on your Mac. In addition to controlling iTunes, your available AirPlay endpoints will be added as media players as well. You can then individually address them append turn them on, turn them off, or adjust their volume. diff --git a/source/_components/media_player.kodi.markdown b/source/_components/media_player.kodi.markdown index 8b141d8b88b..69ab0ead09d 100644 --- a/source/_components/media_player.kodi.markdown +++ b/source/_components/media_player.kodi.markdown @@ -1,9 +1,9 @@ --- -layout: page -title: "Kodi support" +layout: component +title: "Kodi" description: "Instructions how to integrate Kodi into Home Assistant." date: 2015-06-22 11:00 -sidebar: false +sidebar: true comments: false sharing: true footer: true @@ -11,7 +11,7 @@ logo: kodi.png ha_category: Media Player --- - + The kodi platform allows you to control a [Kodi](http://kodi.tv/) multimedia system from Home Assistant. To add Kodi to your installation, add the following to your `configuration.yaml` file: diff --git a/source/_components/media_player.markdown b/source/_components/media_player.markdown index 2b5cbf78c61..3f95f4c5156 100644 --- a/source/_components/media_player.markdown +++ b/source/_components/media_player.markdown @@ -1,9 +1,9 @@ --- -layout: page +layout: component title: "Media Player" description: "Instructions how to setup your media players with Home Assistant." date: 2015-01-24 14:39 -sidebar: false +sidebar: true comments: false sharing: true footer: true diff --git a/source/_components/media_player.mpd.markdown b/source/_components/media_player.mpd.markdown index cbdfe46d619..12632d19bf6 100644 --- a/source/_components/media_player.mpd.markdown +++ b/source/_components/media_player.mpd.markdown @@ -1,9 +1,9 @@ --- -layout: page -title: "Music Player Daemon support" +layout: component +title: "Music Player Daemon" description: "Instructions how to integrate Music Player Daemon into Home Assistant." date: 2015-06-02 08:00 -sidebar: false +sidebar: true comments: false sharing: true footer: true @@ -11,7 +11,7 @@ logo: mpd.png ha_category: Media Player --- - + The mpd platform allows you to control a [Music Player Daemon](http://www.musicpd.org/) from Home Assistant. Unfortunatly you will not be able to manipulate the playlist (add or delete songs) or add transitions between the songs. To add MPD to your installation, add the following to your `configuration.yaml` file: diff --git a/source/_components/media_player.plex.markdown b/source/_components/media_player.plex.markdown index 5ec12c87237..a4e037fc4b1 100644 --- a/source/_components/media_player.plex.markdown +++ b/source/_components/media_player.plex.markdown @@ -1,9 +1,9 @@ --- -layout: page +layout: component title: "Plex" description: "Instructions how to integrate Plex into Home Assistant." date: 2015-10-05 21:21 -sidebar: false +sidebar: true comments: false sharing: true footer: true @@ -11,7 +11,7 @@ logo: plex.png ha_category: Media Player --- - + The Plex platform allows you to connect a [Plex Media Server](https://plex.tv) to Home Assistant. It will allow you to control media playback and see the current playing item. To add Plex to your installation, add the following to your `configuration.yaml` file: diff --git a/source/_components/media_player.sonos.markdown b/source/_components/media_player.sonos.markdown index df185325959..7d1fcd90501 100644 --- a/source/_components/media_player.sonos.markdown +++ b/source/_components/media_player.sonos.markdown @@ -1,9 +1,9 @@ --- -layout: page -title: "Sonos support" +layout: component +title: "Sonos" description: "Instructions how to integrateSonos devices into Home Assistant." date: 2015-09-12 13:00 -sidebar: false +sidebar: true comments: false sharing: true footer: true @@ -11,7 +11,7 @@ logo: sonos.png ha_category: Media Player --- - + The sonos platform allows you to control your [Sonos](http://www.sonos.com) HiFi wireless speakers and audio components from Home Assistant. To add your Sonos components to your installation, add the following to your `configuration.yaml` file. It will perform auto-discovery of your connected speakers. diff --git a/source/_components/media_player.squeezebox.markdown b/source/_components/media_player.squeezebox.markdown index d8bab635d76..30dcf75bf76 100644 --- a/source/_components/media_player.squeezebox.markdown +++ b/source/_components/media_player.squeezebox.markdown @@ -1,9 +1,9 @@ --- -layout: page -title: "Logitech Squeezebox support" +layout: component +title: "Logitech Squeezebox" description: "Instructions how to integrate a Logitech Squeezebox into Home Assistant." date: 2015-08-09 11:00 -sidebar: false +sidebar: true comments: false sharing: true footer: true @@ -11,7 +11,7 @@ logo: logitech.png ha_category: Media Player --- - + The squeezebox platform allows you to control a [Logitech Squeezebox](https://en.wikipedia.org/wiki/Squeezebox_%28network_music_player%29) multimedia system from Home Assistant. To add your Squeezebox to your installation, add the following to your `configuration.yaml` file: diff --git a/source/_components/modbus.markdown b/source/_components/modbus.markdown index c2f7d9d7079..0d5b3da93e7 100644 --- a/source/_components/modbus.markdown +++ b/source/_components/modbus.markdown @@ -1,9 +1,9 @@ --- -layout: page +layout: component title: "Modbus" description: "Instructions how to integrate Modbus within Home Assistant." date: 2015-04-25 9:16 -sidebar: false +sidebar: true comments: false sharing: true footer: true @@ -11,7 +11,7 @@ logo: modbus.png ha_category: Hub --- - + [Modbus](http://www.modbus.org/) is a serial communication protocol to control PLCs (Programmable logic controller). It currently supports sensors and switches which can be controlled over serial, TCP, and UDP connections. To add modbus to your installation, add the following to your `configuration.yaml` file: diff --git a/source/_components/mqtt.markdown b/source/_components/mqtt.markdown index 6080ff9de3b..91318d5409e 100644 --- a/source/_components/mqtt.markdown +++ b/source/_components/mqtt.markdown @@ -1,14 +1,15 @@ --- -layout: page +layout: component title: "MQTT" description: "Instructions how to setup MQTT within Home Assistant." date: 2015-08-07 18:00 -sidebar: false +sidebar: true comments: false sharing: true footer: true +logo: mqtt.png --- - + MQTT (aka MQ Telemetry Transport) is a machine-to-machine or "Internet of Things" connectivity protocol on top of TCP/IP. It allows extremely lightweight publish/subscribe messaging transport. To integrate MQTT into Home Assistant, add the following section to your `configuration.yaml` file: diff --git a/source/_components/notify.file.markdown b/source/_components/notify.file.markdown index 5c1a46bd916..3c7cbab3a83 100644 --- a/source/_components/notify.file.markdown +++ b/source/_components/notify.file.markdown @@ -1,16 +1,16 @@ --- -layout: page -title: "File notification support" +layout: component +title: "File notification" description: "Instructions how to add file notifications to Home Assistant." date: 2015-06-22 10:00 -sidebar: false +sidebar: true comments: false sharing: true footer: true -ha_category: Notify +ha_category: Notifications --- - + The file platform allows you to store notifications from Home Assistant as a file. To enable file notifications in your installation, add the following to your `configuration.yaml` file: diff --git a/source/_components/notify.instapush.markdown b/source/_components/notify.instapush.markdown index 9c04e002cae..238d1bad05c 100644 --- a/source/_components/notify.instapush.markdown +++ b/source/_components/notify.instapush.markdown @@ -1,17 +1,17 @@ --- -layout: page -title: "Instapush notification support" +layout: component +title: "Instapush" description: "Instructions how to add Instapush notifications to Home Assistant." date: 2015-05-01 18:00 -sidebar: false +sidebar: true comments: false sharing: true footer: true logo: instapush.png -ha_category: Notify +ha_category: Notifications --- - + The instapush platform uses [Instapush](https://instapush.im) to delivery notifications from Home Assistant to your Android or iOS device. The Instapush [Getting Started page](https://instapush.im/home/start/) will guide through the process of creating the required items. diff --git a/source/_components/notify.markdown b/source/_components/notify.markdown index a0e04e4df7b..2d3faf9a5d0 100644 --- a/source/_components/notify.markdown +++ b/source/_components/notify.markdown @@ -1,9 +1,9 @@ --- -layout: page +layout: component title: "Notifications" description: "Instructions how to add user notifications to Home Assistant." date: 2015-01-20 22:36 -sidebar: false +sidebar: true comments: false sharing: true footer: true diff --git a/source/_components/notify.nma.markdown b/source/_components/notify.nma.markdown index 918cd87eeaa..69f1a4bff81 100644 --- a/source/_components/notify.nma.markdown +++ b/source/_components/notify.nma.markdown @@ -1,17 +1,17 @@ --- -layout: page -title: "Notify My Android (NMA) notification support" +layout: component +title: "Notify My Android" description: "Instructions how to add user notifications to Home Assistant." date: 2015-05-01 18:00 -sidebar: false +sidebar: true comments: false sharing: true footer: true logo: nma.png -ha_category: Notify +ha_category: Notifications --- - + The nma platform uses [Notify My Android (NMA)](http://www.notifymyandroid.com/) to delivery notifications from Home Assistant to your Android device. To add NMA to your installation, add the following to your `configuration.yaml` file: diff --git a/source/_components/notify.pushbullet.markdown b/source/_components/notify.pushbullet.markdown index 4ae29290b44..7b401698701 100644 --- a/source/_components/notify.pushbullet.markdown +++ b/source/_components/notify.pushbullet.markdown @@ -1,17 +1,17 @@ --- -layout: page -title: "PushBullet notification support" +layout: component +title: "PushBullet" description: "Instructions how to add user notifications to Home Assistant." date: 2015-01-20 22:36 -sidebar: false +sidebar: true comments: false sharing: true footer: true logo: pushbullet.png -ha_category: Notify +ha_category: Notifications --- - + Home Assistant currently supports the awesome [PushBullet](https://www.pushbullet.com/), a free service to send information between your phones, browsers and friends. To add PushBullet to your installation, add the following to your `configuration.yaml` file: diff --git a/source/_components/notify.pushover.markdown b/source/_components/notify.pushover.markdown index 22cf5d52120..0a76bf6e0c1 100644 --- a/source/_components/notify.pushover.markdown +++ b/source/_components/notify.pushover.markdown @@ -1,17 +1,17 @@ --- -layout: page -title: "Notifications" +layout: component +title: "PushOver" description: "Instructions how to add user notifications to Home Assistant." date: 2015-01-20 22:36 -sidebar: false +sidebar: true comments: false sharing: true footer: true logo: pushover.png -ha_category: Notify +ha_category: Notifications --- - + The [PushOver service](https://pushover.net/) is a platform for the notify component. This allows components to send messages to the user using PushOver. To use PushOver notifications, add the following to your `configuration.yaml` file: diff --git a/source/_components/notify.slack.markdown b/source/_components/notify.slack.markdown index 17a8c8dbe63..f4e75c5d621 100644 --- a/source/_components/notify.slack.markdown +++ b/source/_components/notify.slack.markdown @@ -1,17 +1,17 @@ --- -layout: page -title: "Slack notification support" +layout: component +title: "Slack" description: "Instructions how to add Slack notifications to Home Assistant." date: 2015-08-06 18:00 -sidebar: false +sidebar: true comments: false sharing: true footer: true logo: slack.png -ha_category: Notify +ha_category: Notifications --- - + The slack platform allows you to deliver notifications from Home Assistant to [Slack](https://slack.com/). You need to obtain the [Slack API token](https://api.slack.com/web?sudo=1) to be able to send notifications. diff --git a/source/_components/notify.smtp.markdown b/source/_components/notify.smtp.markdown index 29785ae8716..17ec4056024 100644 --- a/source/_components/notify.smtp.markdown +++ b/source/_components/notify.smtp.markdown @@ -1,17 +1,17 @@ --- -layout: page -title: "SMTP notification support" +layout: component +title: "SMTP" description: "Instructions how to add e-mail notifications to Home Assistant." date: 2015-06-03 18:00 -sidebar: false +sidebar: true comments: false sharing: true footer: true logo: smtp.png -ha_category: Notify +ha_category: Notifications --- - + The smtp platform allows you to deliver notifications from Home Assistant to an e-mail recipient. To enable notification by e-mail in your installation, add the following to your `configuration.yaml` file: diff --git a/source/_components/notify.syslog.markdown b/source/_components/notify.syslog.markdown index b1cedf3dea7..e4dc1e0bd8d 100644 --- a/source/_components/notify.syslog.markdown +++ b/source/_components/notify.syslog.markdown @@ -1,16 +1,16 @@ --- -layout: page -title: "Syslog notification support" +layout: component +title: "Syslog" description: "Instructions how to add syslog notifications to Home Assistant." date: 2015-06-09 16:00 -sidebar: false +sidebar: true comments: false sharing: true footer: true -ha_category: Notify +ha_category: Notifications --- - + The syslog platform allows you to deliver notifications from Home Assistant to the local syslog. To enable syslog notifications in your installation, add the following to your `configuration.yaml` file: diff --git a/source/_components/notify.telegram.markdown b/source/_components/notify.telegram.markdown index 30dccc2223e..4be8021609a 100644 --- a/source/_components/notify.telegram.markdown +++ b/source/_components/notify.telegram.markdown @@ -1,17 +1,17 @@ --- -layout: page -title: "Telegram notification support" +layout: component +title: "Telegram" description: "Instructions how to add Telegram notifications to Home Assistant." date: 2015-10-09 18:00 -sidebar: false +sidebar: true comments: false sharing: true footer: true logo: telegram.png -ha_category: Notify +ha_category: Notifications --- - + The telegram platform uses [Telegram](https://web.telegram.org) to delivery notifications from Home Assistant to your Android device, your Windows phone, or your iOS device. The requirement are: diff --git a/source/_components/notify.xmpp.markdown b/source/_components/notify.xmpp.markdown index 6750c66b80f..258c9b97be6 100644 --- a/source/_components/notify.xmpp.markdown +++ b/source/_components/notify.xmpp.markdown @@ -1,17 +1,17 @@ --- -layout: page -title: "Jabber (XMPP) notification support" +layout: component +title: "Jabber (XMPP)" description: "Instructions how to add Jabber (XMPP) notifications to Home Assistant." date: 2015-05-08 18:00 -sidebar: false +sidebar: true comments: false sharing: true footer: true logo: xmpp.png -ha_category: Notify +ha_category: Notifications --- - + The xmpp platform allows you to deliver notifications from Home Assistant to a [Jabber (XMPP)](http://xmpp.org) account. ```yaml diff --git a/source/_components/rfxtrx.markdown b/source/_components/rfxtrx.markdown index db240d6fcd4..c89aacf93be 100644 --- a/source/_components/rfxtrx.markdown +++ b/source/_components/rfxtrx.markdown @@ -1,9 +1,9 @@ --- -layout: page -title: "RFXtrx support" +layout: component +title: "RFXtrx" description: "Instructions how to integrate RFXtrx into Home Assistant." date: 2015-10-08 10:15 -sidebar: false +sidebar: true comments: false sharing: true footer: true diff --git a/source/_components/scene.markdown b/source/_components/scene.markdown index 20f20396c90..8dbb9bebbd2 100644 --- a/source/_components/scene.markdown +++ b/source/_components/scene.markdown @@ -1,9 +1,9 @@ --- -layout: page +layout: component title: "Scenes" description: "Instructions how to setup scenes within Home Assistant." date: 2015-03-23 19:59 -sidebar: false +sidebar: true comments: false sharing: true footer: true diff --git a/source/_components/script.markdown b/source/_components/script.markdown index 636179704a9..d183b10f38e 100644 --- a/source/_components/script.markdown +++ b/source/_components/script.markdown @@ -1,9 +1,9 @@ --- -layout: page +layout: component title: "Scripts" description: "Instructions how to setup scripts within Home Assistant." date: 2015-03-23 19:59 -sidebar: false +sidebar: true comments: false sharing: true footer: true diff --git a/source/_components/sensor.arduino.markdown b/source/_components/sensor.arduino.markdown index cb8b990bbe7..0691ab274be 100644 --- a/source/_components/sensor.arduino.markdown +++ b/source/_components/sensor.arduino.markdown @@ -1,17 +1,17 @@ --- -layout: page -title: "Arduino sensor support" +layout: component +title: "Arduino sensor" description: "Instructions how to integrate Arduino boards within Home Assistant." date: 2015-09-14 18:28 -sidebar: false +sidebar: true comments: false sharing: true footer: true logo: arduino.png -ha_category: Sensor +ha_category: DIY --- - + The arduino sensor platform allows allow you to get an numerical values from an analog input pin of an [Arduino](https://www.arduino.cc/) board. Usually the value is between 0 and 1024. To enable an Arduino sensor with Home Assistant, add the following section to your `configuration.yaml` file: diff --git a/source/_components/sensor.arest.markdown b/source/_components/sensor.arest.markdown index e90e5400e65..78f4dad758a 100644 --- a/source/_components/sensor.arest.markdown +++ b/source/_components/sensor.arest.markdown @@ -1,9 +1,9 @@ --- -layout: page -title: "aREST sensor support" +layout: component +title: "aREST sensor" description: "Instructions how to integrate aREST sensors within Home Assistant." date: 2015-09-07 18:15 -sidebar: false +sidebar: true comments: false sharing: true footer: true @@ -11,7 +11,7 @@ logo: arest.png ha_category: Sensor --- - + The arest sensor platform allows you to get all data from your devices (like Arduinos with a ethernet/wifi connection, the ESP8266, and the Raspberry Pi) running the [aREST](http://arest.io/) RESTful framework. To use your aREST enabled device in your installation, add the following to your `configuration.yaml` file: diff --git a/source/_components/sensor.bitcoin.markdown b/source/_components/sensor.bitcoin.markdown index 01f80ee89a8..efb232c67fe 100644 --- a/source/_components/sensor.bitcoin.markdown +++ b/source/_components/sensor.bitcoin.markdown @@ -1,9 +1,9 @@ --- -layout: page -title: "Bitcoin support" +layout: component +title: "Bitcoin" description: "Instructions how to integrate Bitcoin data within Home Assistant." date: 2015-05-08 17:15 -sidebar: false +sidebar: true comments: false sharing: true footer: true @@ -11,7 +11,7 @@ logo: bitcoin.png ha_category: Sensor --- - + The bitcoin platform displays various details about the [Bitcoin](https://bitcoin.org) network. If you have an online wallet from [Blockchain.info](https://blockchain.info/) the sensor is capable to show your current balance. diff --git a/source/_components/sensor.command_sensor.markdown b/source/_components/sensor.command_sensor.markdown index dbcfba335ff..8719dde1717 100644 --- a/source/_components/sensor.command_sensor.markdown +++ b/source/_components/sensor.command_sensor.markdown @@ -1,16 +1,16 @@ --- -layout: page -title: "Command line sensors support" +layout: component +title: "Command line sensors" description: "Instructions how to integrate commandline sensors into Home Assistant." date: 2015-09-13 10:10 -sidebar: false +sidebar: true comments: false sharing: true footer: true ha_category: Sensor --- - + A sensor platform that issues specific commands to get data. This might very well become our most powerful platform as it allows anyone to integrate any type of switch into Home Assistant that can be controlled from the command line, including calling other scripts! To enable it, add the following lines to your `configuration.yaml`: diff --git a/source/_components/sensor.cpuspeed.markdown b/source/_components/sensor.cpuspeed.markdown index f4ec5e9cd5a..96e04b4c57b 100644 --- a/source/_components/sensor.cpuspeed.markdown +++ b/source/_components/sensor.cpuspeed.markdown @@ -1,16 +1,16 @@ --- -layout: page -title: "Monitor CPU speed" +layout: component +title: "CPU speed" description: "Instructions how to integrate CPU speed within Home Assistant." date: 2015-10-15 11:00 -sidebar: false +sidebar: true comments: false sharing: true footer: true ha_category: Sensor --- - + The cpuspeed sensor platform to allow you to monitor the current CPU speed. To add this platform to your installation, add the following to your `configuration.yaml` file: diff --git a/source/_components/sensor.dht.markdown b/source/_components/sensor.dht.markdown index 8ca311c946e..b009154c5b5 100644 --- a/source/_components/sensor.dht.markdown +++ b/source/_components/sensor.dht.markdown @@ -1,17 +1,16 @@ --- -layout: page -title: "DHT support" +layout: component +title: "DHT" description: "Instructions how to integrate DHTxx sensors within Home Assistant." date: 2015-08-30 19:15 -sidebar: false +sidebar: true comments: false sharing: true footer: true -logo: dht.png ha_category: DIY --- - + The dht sensor platform allows you to get the current temperature and humidity from a DHT11, DHT22, or AM2302 device. To use your DHTxx sensor in your installation, add the following to your `configuration.yaml` file: diff --git a/source/_components/sensor.efergy.markdown b/source/_components/sensor.efergy.markdown index 658e0112c1e..8a61b44a3f2 100644 --- a/source/_components/sensor.efergy.markdown +++ b/source/_components/sensor.efergy.markdown @@ -1,9 +1,9 @@ --- -layout: page -title: "Efergy support" +layout: component +title: "Efergy" description: "Instructions how to integrate Efergy devices within Home Assistant." date: 2015-07-11 0:15 -sidebar: false +sidebar: true comments: false sharing: true footer: true @@ -11,7 +11,7 @@ logo: efergy.png ha_category: Sensor --- - + Integrate your [Efergy](https://efergy.com) meter information into Home Assistant. To get an app token, log in to your efergy account, go to the Settings page, click on App tokens, and click "Add token". ```yaml diff --git a/source/_components/sensor.forecast.markdown b/source/_components/sensor.forecast.markdown index 77dce37c55f..f7629baefd3 100644 --- a/source/_components/sensor.forecast.markdown +++ b/source/_components/sensor.forecast.markdown @@ -1,16 +1,16 @@ --- -layout: page -title: "Forecast.io support" +layout: component +title: "Forecast.io" description: "Instructions how to integrate Forecast.io within Home Assistant." date: 2015-04-25 9:06 -sidebar: false +sidebar: true comments: false sharing: true footer: true ha_category: Weather --- - + The forecast platform uses the [Forecast.io](https://forecast.io/) web service as a source for meteorological data for your location. The location is based on the Longitude and Latitude cooridinates configured in `configuration.yaml`. The cooridinates are auto detected but to take advantage of the hyper-local weather reported by forecast.io, you can refine them down to your exact home address. GPS cooridinates can be found by using Google Maps and clicking on your home. You need an API key which is free but requires a [registration](https://developer.forecast.io/register). You can make 1000 requests per day. This means that you could create approximately every 1.4 minute one. diff --git a/source/_components/sensor.glances.markdown b/source/_components/sensor.glances.markdown index 72938aaa817..48e9d90b5d7 100644 --- a/source/_components/sensor.glances.markdown +++ b/source/_components/sensor.glances.markdown @@ -1,9 +1,9 @@ --- -layout: page -title: "Glances sensor support" +layout: component +title: "Glances sensor" description: "Instructions how to integrate Glances sensors into Home Assistant." date: 2015-09-14 19:10 -sidebar: false +sidebar: true comments: false sharing: true footer: true @@ -11,7 +11,7 @@ logo: glances.png ha_category: Sensor --- - + The glances sensor platform is consuming the system information provided by the [Glances](https://github.com/nicolargo/glances) API. This enables one to track remote host and display their stats in Home Assistant. This sensors needs a running isntance of `glances` on the host: diff --git a/source/_components/sensor.modbus.markdown b/source/_components/sensor.modbus.markdown index 15afd25f661..cab6b00e9d4 100644 --- a/source/_components/sensor.modbus.markdown +++ b/source/_components/sensor.modbus.markdown @@ -1,9 +1,9 @@ --- -layout: page -title: "Modbus sensors support" +layout: component +title: "Modbus sensors" description: "Instructions how to integrate Modbus sensors into Home Assistant." date: 2015-08-30 23:38 -sidebar: false +sidebar: true comments: false sharing: true footer: true @@ -11,7 +11,7 @@ logo: modbus.png ha_category: Sensor --- - + The modbus sensor platform allows you to gather data from your [Modbus](http://www.modbus.org/) sensors. To use your Modbus sensors in your installation, add the following to your `configuration.yaml` file: diff --git a/source/_components/sensor.mqtt.markdown b/source/_components/sensor.mqtt.markdown index 44d3638b2cf..e291ea72a9f 100644 --- a/source/_components/sensor.mqtt.markdown +++ b/source/_components/sensor.mqtt.markdown @@ -1,9 +1,9 @@ --- -layout: page -title: "MQTT Sensor support" +layout: component +title: "MQTT Sensor" description: "Instructions how to integrate MQTT sensors within Home Assistant." date: 2015-05-30 23:21 -sidebar: false +sidebar: true comments: false sharing: true footer: true @@ -11,7 +11,7 @@ logo: mqtt.png ha_category: Sensor --- - + This MQTT sensor implementation uses the MQTT message payload as the sensor value. If messages in this state_topic are published with *RETAIN* flag, the sensor will receive an instant update with last known value. Otherwise, the initial state will be undefined. To use your MQTT sensor in your installation, add the following to your `configuration.yaml` file: diff --git a/source/_components/sensor.mysensors.markdown b/source/_components/sensor.mysensors.markdown index 219feaa6702..23c747a6835 100644 --- a/source/_components/sensor.mysensors.markdown +++ b/source/_components/sensor.mysensors.markdown @@ -1,9 +1,9 @@ --- -layout: page -title: "MySensors sensors support" +layout: component +title: "MySensors" description: "Instructions how to integrate MySensors sensors into Home Assistant." date: 2015-05-14 21:57 -sidebar: false +sidebar: true comments: false sharing: true footer: true @@ -11,7 +11,7 @@ logo: mysensors.png ha_category: Sensor --- - + The [MySensors](https://www.mysensors.org) project combines Arduino boards with NRF24L01 radio boards to build sensor networks. Integrate your Serial MYSensors Gateway by adding the following to your `configuration.yaml` file: diff --git a/source/_components/sensor.openweathermap.markdown b/source/_components/sensor.openweathermap.markdown index a114a2c5116..11b0dd5b541 100644 --- a/source/_components/sensor.openweathermap.markdown +++ b/source/_components/sensor.openweathermap.markdown @@ -1,9 +1,9 @@ --- -layout: page -title: "OpenWeatherMap support" +layout: component +title: "OpenWeatherMap" description: "Instructions how to integrate OpenWeatherMap within Home Assistant." date: 2015-04-25 9:06 -sidebar: false +sidebar: true comments: false sharing: true footer: true @@ -11,7 +11,7 @@ logo: openweathermap.png ha_category: Weather --- - + The openweathermap platform uses [OpenWeatherMap](http://openweathermap.org/) as an source for current meteorological data for your location. The `forecast` will show you the condition in 3 h. You need an API key which is free but requires a [registration](http://home.openweathermap.org/users/sign_up). diff --git a/source/_components/sensor.rest.markdown b/source/_components/sensor.rest.markdown index 09ba23477d9..c0b0f823457 100644 --- a/source/_components/sensor.rest.markdown +++ b/source/_components/sensor.rest.markdown @@ -1,16 +1,16 @@ --- -layout: page -title: "RESTful sensor support" +layout: component +title: "RESTful sensor" description: "Instructions how to integrate REST sensors into Home Assistant." date: 2015-09-14 19:10 -sidebar: false +sidebar: true comments: false sharing: true footer: true ha_category: Sensor --- - + The rest sensor platform is consuming a given endpoint which is exposed by a [RESTful API](https://en.wikipedia.org/wiki/Representational_state_transfer) of a device, an application, or a web service. The sensor has support for GET and POST requests. To enable this sensor, add the following lines to your `configuration.yaml` file for a GET request: diff --git a/source/_components/sensor.rfxtrx.markdown b/source/_components/sensor.rfxtrx.markdown index b16929b3645..858bf7caaeb 100644 --- a/source/_components/sensor.rfxtrx.markdown +++ b/source/_components/sensor.rfxtrx.markdown @@ -1,9 +1,9 @@ --- -layout: page -title: "RFXtrx sensors support" +layout: component +title: "RFXtrx sensors" description: "Instructions how to integrate RFXtrx sensors into Home Assistant." date: 2015-08-06 17:15 -sidebar: false +sidebar: true comments: false sharing: true footer: true diff --git a/source/_components/sensor.rpi_gpio.markdown b/source/_components/sensor.rpi_gpio.markdown index 26b905ac485..4d4ade557fa 100644 --- a/source/_components/sensor.rpi_gpio.markdown +++ b/source/_components/sensor.rpi_gpio.markdown @@ -1,17 +1,17 @@ --- -layout: page -title: "Raspberry PI GPIO sensor support" +layout: component +title: "Raspberry PI GPIO sensor" description: "Instructions how to integrate the GPIO sensor capability of a Raspberry PI into Home Assistant." date: 2015-08-30 19:00 -sidebar: false +sidebar: true comments: false sharing: true footer: true logo: raspberry-pi.png -ha_category: Sensor +ha_category: DIY --- - + The rpi_gpio sensor platform allows you to read sensor values of the GPIOs of your [Raspberry Pi](https://www.raspberrypi.org/). To use your Raspberry Pi's GPIO in your installation, add the following to your `configuration.yaml` file: diff --git a/source/_components/sensor.sabnzbd.markdown b/source/_components/sensor.sabnzbd.markdown index 37fd6279cf2..fa2718ff746 100644 --- a/source/_components/sensor.sabnzbd.markdown +++ b/source/_components/sensor.sabnzbd.markdown @@ -1,9 +1,9 @@ --- -layout: page -title: "SABnzbd support" +layout: component +title: "SABnzbd" description: "Instructions how to integrate SABnzbd within Home Assistant." date: 2015-03-23 19:59 -sidebar: false +sidebar: true comments: false sharing: true footer: true @@ -11,7 +11,7 @@ logo: sabnzbd.png ha_category: Sensor --- - + The sabnzbd platform will allow you to monitor your downloads with [SABnzbd](http://sabnzbd.org) from within Home Assistant and setup automation based on the information. To use sabnzbd with your installation, add the following to your `configuration.yaml` file: diff --git a/source/_components/sensor.swiss_public_transport.markdown b/source/_components/sensor.swiss_public_transport.markdown index fc336ebe577..f2ab2840d96 100644 --- a/source/_components/sensor.swiss_public_transport.markdown +++ b/source/_components/sensor.swiss_public_transport.markdown @@ -1,16 +1,16 @@ --- -layout: page -title: "Swiss Public Transport support" +layout: component +title: "Swiss Public Transport" description: "Instructions how to integrate timetable data for travelling in Switzerland within Home Assistant." date: 2015-06-02 21:45 -sidebar: false +sidebar: true comments: false sharing: true footer: true ha_category: Sensor --- - + The swiss public transport sensor will give you the next two departure times from a given location to another one in Switzerland. The [Stationboard](http://transport.opendata.ch/examples/stationboard.html) website can help to determine the exact name of the start and the end station. With the station names it's necessary to search for the ID of those stations: diff --git a/source/_components/sensor.systemmonitor.markdown b/source/_components/sensor.systemmonitor.markdown index a8030984fc7..3f82195384b 100644 --- a/source/_components/sensor.systemmonitor.markdown +++ b/source/_components/sensor.systemmonitor.markdown @@ -1,16 +1,15 @@ --- -layout: page +layout: component title: "Monitor server resources" description: "Instructions how to integrate server resources within Home Assistant." date: 2015-03-23 19:59 -sidebar: false +sidebar: true comments: false sharing: true footer: true ha_category: Sensor --- - The system monitoring sensor platform to allow you to monitor disk usage, memory usage, CPU usage, and running processes. This platform has superseded the process component which is now considered deprecated. To add this platform to your installation, add the following to your `configuration.yaml` file: diff --git a/source/_components/sensor.tellstick.markdown b/source/_components/sensor.tellstick.markdown index 7280e62969c..61c9a305142 100644 --- a/source/_components/sensor.tellstick.markdown +++ b/source/_components/sensor.tellstick.markdown @@ -1,9 +1,9 @@ --- -layout: page -title: "TellStick sensors support" +layout: component +title: "TellStick sensors" description: "Instructions how to integrate TellStick sensors into Home Assistant." date: 2015-08-06 19:00 -sidebar: false +sidebar: true comments: false sharing: true footer: true @@ -11,7 +11,7 @@ logo: telldus_tellstick.png ha_category: Sensor --- - + This tellstick sensor platform allows you to get current meteorological data from a [TellStick](http://www.telldus.se/products/tellstick) device. To use your TellStick device in your installation, add the following to your `configuration.yaml` file: diff --git a/source/_components/sensor.temper.markdown b/source/_components/sensor.temper.markdown index df1295abc10..1ea0a26b78c 100644 --- a/source/_components/sensor.temper.markdown +++ b/source/_components/sensor.temper.markdown @@ -1,9 +1,9 @@ --- -layout: page -title: "TEMPer sensors support" +layout: component +title: "TEMPer sensors" description: "Instructions how to integrate TEMPer sensors into Home Assistant." date: 2015-08-06 19:00 -sidebar: false +sidebar: true comments: false sharing: true footer: true diff --git a/source/_components/sensor.time_date.markdown b/source/_components/sensor.time_date.markdown index 85d463a0453..612bce17a13 100644 --- a/source/_components/sensor.time_date.markdown +++ b/source/_components/sensor.time_date.markdown @@ -1,16 +1,16 @@ --- -layout: page -title: "Time & Date support" +layout: component +title: "Time & Date" description: "Instructions how to integrate the time and the date within Home Assistant." date: 2015-05-08 17:15 -sidebar: false +sidebar: true comments: false sharing: true footer: true ha_category: Sensor --- - + The time and date platform simple displays the time in various formats, the date, or both. To enable this sensor in your installation, add the following to your `configuration.yaml` file: diff --git a/source/_components/sensor.transmission.markdown b/source/_components/sensor.transmission.markdown index 144f318e1df..69cb2f2d3d3 100644 --- a/source/_components/sensor.transmission.markdown +++ b/source/_components/sensor.transmission.markdown @@ -1,9 +1,9 @@ --- -layout: page -title: "Transmission support" +layout: component +title: "Transmission" description: "Instructions how to integrate Transmission within Home Assistant." date: 2015-04-25 9:06 -sidebar: false +sidebar: true comments: false sharing: true footer: true @@ -11,7 +11,7 @@ logo: transmission.png ha_category: Sensor --- - + The [Transmission](http://www.transmissionbt.com/) platform allows you to monitor your downloads from within Home Assistant and setup automation based on the information. ```yaml diff --git a/source/_components/sensor.vera.markdown b/source/_components/sensor.vera.markdown index c44536e194e..6b71a311835 100644 --- a/source/_components/sensor.vera.markdown +++ b/source/_components/sensor.vera.markdown @@ -1,9 +1,9 @@ --- -layout: page -title: "Vera sensors support" +layout: component +title: "Vera sensors" description: "Instructions how to integrate Vera sensors into Home Assistant." date: 2015-10-20 21:00 -sidebar: false +sidebar: true comments: false sharing: true footer: true @@ -11,7 +11,7 @@ logo: vera.png ha_category: Sensor --- - + This vera sensor platform allows you to get data from your [Vera](http://getvera.com/) sensors. To use your Vera sensor in your installation, add the following to your `configuration.yaml` file: diff --git a/source/_components/sensor.wink.markdown b/source/_components/sensor.wink.markdown index 57f73022d81..cd02e2d6cbd 100644 --- a/source/_components/sensor.wink.markdown +++ b/source/_components/sensor.wink.markdown @@ -1,9 +1,9 @@ --- -layout: page +layout: component title: "Wink sensors" description: "Instructions how to setup the Wink sensors within Home Assistant." date: 2015-01-20 22:36 -sidebar: false +sidebar: true comments: false sharing: true footer: true @@ -11,7 +11,7 @@ logo: wink.png ha_category: Sensor --- - + The wink sensor platform allows you to get data from your [Wink](http://www.wink.com/) sensors. The requirement is that you have setup your [Wink hub](/components/light.wink.html). diff --git a/source/_components/sensor.worldclock.markdown b/source/_components/sensor.worldclock.markdown index e0109630a8d..ef6c0f7a4ee 100644 --- a/source/_components/sensor.worldclock.markdown +++ b/source/_components/sensor.worldclock.markdown @@ -1,16 +1,16 @@ --- -layout: page -title: "Worldclock support" +layout: component +title: "Worldclock" description: "Instructions how to integrate a Worldclock within Home Assistant." date: 2015-10-02 11:15 -sidebar: false +sidebar: true comments: false sharing: true footer: true ha_category: Sensor --- - + The worldclock platform simple displays the current time in a different time zone To enable this sensor in your installation, add the following to your `configuration.yaml` file: diff --git a/source/_components/shell_command.markdown b/source/_components/shell_command.markdown index a52a8fbdf06..f0dd48e183f 100644 --- a/source/_components/shell_command.markdown +++ b/source/_components/shell_command.markdown @@ -1,16 +1,16 @@ --- -layout: page -title: "Shell command component" +layout: component +title: "Shell command" description: "Instructions how to integrate Shell commands into Home Assistant." date: 2015-10-13 19:10 -sidebar: false +sidebar: true comments: false sharing: true footer: true ha_category: Other --- - + This component can expose regular shell commands as services. ```yaml diff --git a/source/_components/simple_alarm.markdown b/source/_components/simple_alarm.markdown index 1144cc7d60b..aad2cfc914e 100644 --- a/source/_components/simple_alarm.markdown +++ b/source/_components/simple_alarm.markdown @@ -1,15 +1,15 @@ --- -layout: page +layout: component title: "Intruder Alerts" description: "Instructions how to receive intruder alerts from Home Assistant." date: 2015-01-20 22:36 -sidebar: false +sidebar: true comments: false sharing: true footer: true --- - + The component `simple_alarm` is capable of detecting intruders. It does so by checking if lights are being turned on while there is no one at home. When this happens it will turn the lights red, flash them for 30 seconds and send a message via [the notifiy component]({{site_root}}/components/notify.html). It will also flash a specific light when a known person comes home. This component depends on the components [device_tracker]({{site_root}}/components/device_tracker.html) and [light]({{site_root}}/components/light.html) being setup. diff --git a/source/_components/sun.markdown b/source/_components/sun.markdown index 572f461a94d..3dd6b29b5ff 100644 --- a/source/_components/sun.markdown +++ b/source/_components/sun.markdown @@ -1,16 +1,16 @@ --- -layout: page -title: "Tracking the Sun" +layout: component +title: "Sun" description: "Instructions how to track the sun within Home Assistant." date: 2015-01-24 14:39 -sidebar: false +sidebar: true comments: false sharing: true footer: true ha_category: Weather --- - + The `sun` component will use your current location to track if the sun is above or below the horizon. The sun can be used within automation as [a trigger with an optional offset to simulate dawn/dusk][automation-trigger]. diff --git a/source/_components/switch.arduino.markdown b/source/_components/switch.arduino.markdown index ce05d59322d..10b7a19185e 100644 --- a/source/_components/switch.arduino.markdown +++ b/source/_components/switch.arduino.markdown @@ -1,17 +1,17 @@ --- -layout: page -title: "Arduino switch support" +layout: component +title: "Arduino switch" description: "Instructions how to integrate Arduino boards within Home Assistant." date: 2015-09-14 18:28 -sidebar: false +sidebar: true comments: false sharing: true footer: true logo: arduino.png -ha_category: Switch +ha_category: DIY --- - + The arduino switch platform allows you to control the digital pins of your [Arduino](https://www.arduino.cc/) board. Support for switching pins is limited to high/on and low/off of the digital pins. PWM (pin 3,5,6,9,10, and 11 on an Arduino Uno) is not supported yet. To enable the Arduino pins with Home Assistant, add the following section to your `configuration.yaml` file: diff --git a/source/_components/switch.arest.markdown b/source/_components/switch.arest.markdown index 16d37df9877..37429a47120 100644 --- a/source/_components/switch.arest.markdown +++ b/source/_components/switch.arest.markdown @@ -1,9 +1,9 @@ --- -layout: page -title: "aREST switch support" +layout: component +title: "aREST switch" description: "Instructions how to integrate aREST switches within Home Assistant." date: 2015-09-11 23:15 -sidebar: false +sidebar: true comments: false sharing: true footer: true @@ -11,7 +11,7 @@ logo: arest.png ha_category: Switch --- - + 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. To use your aREST enabled device in your installation, add the following to your `configuration.yaml` file: diff --git a/source/_components/switch.command_switch.markdown b/source/_components/switch.command_switch.markdown index 6e540845915..afd11ba3a38 100644 --- a/source/_components/switch.command_switch.markdown +++ b/source/_components/switch.command_switch.markdown @@ -1,16 +1,16 @@ --- -layout: page -title: "Command line switches support" +layout: component +title: "Command line switches" description: "Instructions how to have a switch call command line commands." date: 2015-06-10 22:41 -sidebar: false +sidebar: true comments: false sharing: true footer: true ha_category: Switch --- - + A switch platform that issues specific commands when it is turned on and off. This might very well become our most platform as it allows anyone to integrate any type of switch into Home Assistant that can be controlled from the command line, including calling other scripts! To enable it, add the following lines to your `configuration.yaml`: diff --git a/source/_components/switch.edimax.markdown b/source/_components/switch.edimax.markdown index 3823d4dc2eb..cb93f2893ee 100644 --- a/source/_components/switch.edimax.markdown +++ b/source/_components/switch.edimax.markdown @@ -1,9 +1,9 @@ --- -layout: page -title: "Edimax switches support" +layout: component +title: "Edimax switches" description: "Instructions how to integrate Edimax switches into Home Assistant." date: 2015-06-10 22:54 -sidebar: false +sidebar: true comments: false sharing: true footer: true @@ -11,7 +11,7 @@ logo: edimax.png ha_category: Switch --- - + This edimax switch platform allows you to control the state of your [Edimax](http://www.edimax.com/edimax/merchandise/merchandise_list/data/edimax/global/home_automation_smart_plug/) switches. To use your Edimax switch in your installation, add the following to your `configuration.yaml` file: diff --git a/source/_components/switch.hikvision.markdown b/source/_components/switch.hikvision.markdown index a8923d17876..05f3d47d00f 100644 --- a/source/_components/switch.hikvision.markdown +++ b/source/_components/switch.hikvision.markdown @@ -1,17 +1,17 @@ --- -layout: page -title: "Hikvision camera support" +layout: component +title: "Hikvision camera" description: "Instructions how to integrate Hikvision camera's into Home Assistant." date: 2015-06-10 22:54 -sidebar: false +sidebar: true comments: false sharing: true footer: true logo: hikvision.png -ha_category: Switch +ha_category: Camera --- - + This hikvisioncam switch platform allows you to control your motion detection setting on your [Hikvision](http://www.hikvision.com/) camera.

diff --git a/source/_components/switch.markdown b/source/_components/switch.markdown index f017acc7ab4..85897e57f0a 100644 --- a/source/_components/switch.markdown +++ b/source/_components/switch.markdown @@ -1,9 +1,9 @@ --- -layout: page +layout: component title: "Switches" description: "Instructions how to setup your switches with Home Assistant." date: 2015-01-24 14:39 -sidebar: false +sidebar: true comments: false sharing: true footer: true diff --git a/source/_components/switch.modbus.markdown b/source/_components/switch.modbus.markdown index 981b9b0457b..ff8c2d269c6 100644 --- a/source/_components/switch.modbus.markdown +++ b/source/_components/switch.modbus.markdown @@ -1,9 +1,9 @@ --- -layout: page -title: "Modbus switch support" +layout: component +title: "Modbus switch" description: "Instructions how to integrate Modbus switches into Home Assistant." date: 2015-08-30 23:38 -sidebar: false +sidebar: true comments: false sharing: true footer: true @@ -11,7 +11,7 @@ logo: modbus.png ha_category: Switch --- - + The modbus switch platform allows you to control [Modbus](http://www.modbus.org/) switches. To use your Modbus switches in your installation, add the following to your `configuration.yaml` file: diff --git a/source/_components/switch.mqtt.markdown b/source/_components/switch.mqtt.markdown index 28649f17b77..26d81154b25 100644 --- a/source/_components/switch.mqtt.markdown +++ b/source/_components/switch.mqtt.markdown @@ -1,9 +1,9 @@ --- -layout: page -title: "MQTT switch support" +layout: component +title: "MQTT switch" description: "Instructions how to integrate MQTT switches into Home Assistant." date: 2015-08-30 23:38 -sidebar: false +sidebar: true comments: false sharing: true footer: true @@ -11,7 +11,7 @@ logo: mqtt.png ha_category: Switch --- - + In an ideal scenario, the MQTT device will have a state topic to publish state changes. If these messages are published with RETAIN flag, the MQTT switch will receive an instant state update after subscription and will start with correct state. Otherwise, the initial state of the switch will be false/off. diff --git a/source/_components/switch.rest.markdown b/source/_components/switch.rest.markdown index a133a76178c..2342d6f80dd 100644 --- a/source/_components/switch.rest.markdown +++ b/source/_components/switch.rest.markdown @@ -1,16 +1,16 @@ --- -layout: page -title: "RESTful switch support" +layout: component +title: "RESTful switch" description: "Instructions how to integrate REST switches into Home Assistant." date: 2015-09-14 19:10 -sidebar: false +sidebar: true comments: false sharing: true footer: true ha_category: Switch --- - + The rest switch platform allows you to control a given endpoint that supports a [RESTful API](https://en.wikipedia.org/wiki/Representational_state_transfer). The switch can get the state via GET and set the state via POST on a given REST resource. To enable this switch, add the following lines to your `configuration.yaml` file: diff --git a/source/_components/switch.rfxtrx.markdown b/source/_components/switch.rfxtrx.markdown index d6fae1f3391..46ba9b00b58 100644 --- a/source/_components/switch.rfxtrx.markdown +++ b/source/_components/switch.rfxtrx.markdown @@ -1,9 +1,9 @@ --- -layout: page -title: "RFXtrx switch support" +layout: component +title: "RFXtrx switch" description: "Instructions how to integrate RFXtrx switches into Home Assistant." date: 2015-10-08 10:15 -sidebar: false +sidebar: true comments: false sharing: true footer: true diff --git a/source/_components/switch.rpi_gpio.markdown b/source/_components/switch.rpi_gpio.markdown index 9a46f8c288c..30113a641d7 100644 --- a/source/_components/switch.rpi_gpio.markdown +++ b/source/_components/switch.rpi_gpio.markdown @@ -1,17 +1,17 @@ --- -layout: page -title: "Raspberry PI GPIO switch support" +layout: component +title: "Raspberry PI GPIO switch" description: "Instructions how to integrate the GPIO of a Raspberry PI into Home Assistant." date: 2015-08-07 14:00 -sidebar: false +sidebar: true comments: false sharing: true footer: true logo: raspberry-pi.png -ha_category: Switch +ha_category: DIY --- - + The rpi_gpio switch platform allows you to control the GPIOs of your [Raspberry Pi](https://www.raspberrypi.org/). To use your Raspberry Pi's GPIO in your installation, add the following to your `configuration.yaml` file: diff --git a/source/_components/switch.tellstick.markdown b/source/_components/switch.tellstick.markdown index 626afffccec..21f22f825a3 100644 --- a/source/_components/switch.tellstick.markdown +++ b/source/_components/switch.tellstick.markdown @@ -1,9 +1,9 @@ --- -layout: page -title: "TellStick switch support" +layout: component +title: "TellStick switch" description: "Instructions how to integrate TellStick switches into Home Assistant." date: 2015-08-06 19:00 -sidebar: false +sidebar: true comments: false sharing: true footer: true @@ -11,7 +11,7 @@ logo: telldus_tellstick.png ha_category: Switch --- - + This tellstick switch platform allows you to control [TellStick](http://www.telldus.se/products/tellstick) devices. To use your TellStick device in your installation, add the following to your `configuration.yaml` file: diff --git a/source/_components/switch.transmission.markdown b/source/_components/switch.transmission.markdown index f2cce07f6aa..37f7b054627 100644 --- a/source/_components/switch.transmission.markdown +++ b/source/_components/switch.transmission.markdown @@ -1,9 +1,9 @@ --- -layout: page -title: "Transmission switch support" +layout: component +title: "Transmission switch" description: "Instructions how to integrate Transmission within Home Assistant." date: 2015-06-02 09:00 -sidebar: false +sidebar: true comments: false sharing: true footer: true @@ -11,7 +11,7 @@ logo: transmission.png ha_category: Sensor --- - + The transmission platform allows you to control your [Transmission](http://www.transmissionbt.com/) client from within Home Assistant. The platform enables you switch to your 'Alternative Speed Limits' (aka 'Turtle mode') setting. To add Transmission to your installation, add the following to your `configuration.yaml` file: diff --git a/source/_components/switch.vera.markdown b/source/_components/switch.vera.markdown index 74fe6dd1475..418c48d91e8 100644 --- a/source/_components/switch.vera.markdown +++ b/source/_components/switch.vera.markdown @@ -1,9 +1,9 @@ --- -layout: page -title: "Vera switches support" +layout: component +title: "Vera switches" description: "Instructions how to integrate Vera switches into Home Assistant." date: 2015-10-20 21:00 -sidebar: false +sidebar: true comments: false sharing: true footer: true @@ -11,7 +11,7 @@ logo: vera.png ha_category: Switch --- - + This vera switch platform allows you to control your [Vera](http://getvera.com/) switches. To use your Vera switches in your installation, add the following to your `configuration.yaml` file: diff --git a/source/_components/switch.wemo.markdown b/source/_components/switch.wemo.markdown index d5878eec30e..4bb1359fe96 100644 --- a/source/_components/switch.wemo.markdown +++ b/source/_components/switch.wemo.markdown @@ -1,9 +1,9 @@ --- -layout: page -title: "Belkin WeMo switches support" +layout: component +title: "Belkin WeMo switches" description: "Instructions how to integrate Belkin WeMo switches into Home Assistant." date: 2015-03-23 19:59 -sidebar: false +sidebar: true comments: false sharing: true footer: true @@ -11,7 +11,7 @@ logo: belkin_wemo.png ha_category: Switch --- - + The wemo platform allows you to control your [Belkin WeMo](http://www.belkin.com/us/p/P-F7C027/) switches from within Home Assistant. They will be automatically discovered if the discovery component is enabled. diff --git a/source/_components/switch.wink.markdown b/source/_components/switch.wink.markdown index 94f97a8a016..478ed6341b6 100644 --- a/source/_components/switch.wink.markdown +++ b/source/_components/switch.wink.markdown @@ -1,9 +1,9 @@ --- -layout: page +layout: component title: "Wink switches" description: "Instructions how to setup the Wink switches within Home Assistant." date: 2015-01-20 22:36 -sidebar: false +sidebar: true comments: false sharing: true footer: true @@ -11,7 +11,7 @@ logo: wink.png ha_category: Switch --- - + The wink switch platform allows you to control your [Wink](http://www.wink.com/) switches. The requirement is that you have setup your [Wink hub](/components/light.wink.html). diff --git a/source/_components/tellstick.markdown b/source/_components/tellstick.markdown index 5b651ab1b6e..b2e88a8ae72 100644 --- a/source/_components/tellstick.markdown +++ b/source/_components/tellstick.markdown @@ -1,9 +1,9 @@ --- -layout: page -title: "TellStick component" +layout: component +title: "TellStick" description: "Instructions how to integrate your TellStick into Home Assistant." date: 2015-03-28 13:06 -sidebar: false +sidebar: true comments: false sharing: true footer: true @@ -11,7 +11,7 @@ logo: telldus_tellstick.png ha_category: Hub --- - + The tellstick component integrates [TellStick](http://www.telldus.se/products/tellstick) devices into Home Assistant. This integration allows users to add switches, lights, and sensors which are communicating with 433 Mhz. There are couple of vendors (Capidi Elro, Intertechno, Nexa, Proove, Sartano, and Viking) how are selling products which works with TellStick. For more details, please check the TellStick [compatibility list](http://telldus.se/products/compability). diff --git a/source/_components/thermostat.heat_control.markdown b/source/_components/thermostat.heat_control.markdown index de2fb4113e0..0f5b803d5a3 100644 --- a/source/_components/thermostat.heat_control.markdown +++ b/source/_components/thermostat.heat_control.markdown @@ -1,9 +1,9 @@ --- -layout: page +layout: component title: "Heat control" description: "Turn Home Assistant into a thermostat" date: 2015-03-23 19:59 -sidebar: false +sidebar: true comments: false sharing: true footer: true diff --git a/source/_components/thermostat.markdown b/source/_components/thermostat.markdown index dec13c5e938..cb41344c65d 100644 --- a/source/_components/thermostat.markdown +++ b/source/_components/thermostat.markdown @@ -1,9 +1,9 @@ --- -layout: page +layout: component title: "Adding thermostats" description: "Instructions how to setup thermostats tracking within Home Assistant." date: 2015-01-20 22:36 -sidebar: false +sidebar: true comments: false sharing: true footer: true diff --git a/source/_components/thermostat.nest.markdown b/source/_components/thermostat.nest.markdown index 6f347b41e75..54c0c50aedf 100644 --- a/source/_components/thermostat.nest.markdown +++ b/source/_components/thermostat.nest.markdown @@ -1,9 +1,9 @@ --- -layout: page -title: "Nest thermostat support" +layout: component +title: "Nest thermostat" description: "Instructions how to integrate Nest thermostats within Home Assistant." date: 2015-03-23 19:59 -sidebar: false +sidebar: true comments: false sharing: true footer: true @@ -11,7 +11,7 @@ logo: nest_thermostat.png ha_category: Thermostat --- - + The nest thermostat platform let you control a thermostat from [Nest](https://nest.com). To set it up, add the following information to your `configuration.yaml` file: diff --git a/source/_components/thermostat.radiotherm.markdown b/source/_components/thermostat.radiotherm.markdown index d2e8e77fe51..37e9ae1999d 100644 --- a/source/_components/thermostat.radiotherm.markdown +++ b/source/_components/thermostat.radiotherm.markdown @@ -1,9 +1,9 @@ --- -layout: page -title: "Radiotherm thermostat support" +layout: component +title: "Radiotherm thermostat" description: "Instructions how to integrate Radiotherm thermostats within Home Assistant." date: 2015-10-18 17:15 -sidebar: false +sidebar: true comments: false sharing: true footer: true @@ -11,7 +11,7 @@ logo: radiotherm.png ha_category: Thermostat --- - + The nest thermostat platform let you control a thermostat from [Radio Thermostat](http://www.radiothermostat.com/). The underlaying library supports: diff --git a/source/_components/vera.markdown b/source/_components/vera.markdown index 2d6ffc58a98..51a98d5ffd3 100644 --- a/source/_components/vera.markdown +++ b/source/_components/vera.markdown @@ -1,9 +1,9 @@ --- -layout: page -title: "Vera support" +layout: component +title: "Vera" description: "Instructions how to setup Vera hubs within Home Assistant." date: 2015-03-23 20:04 -sidebar: false +sidebar: true comments: false sharing: true footer: true @@ -11,7 +11,7 @@ logo: vera.png ha_category: Hub --- - + The [Vera](http://getvera.com) ecosystem is using Z-Wave for communication between the Vera controller and the devices. ## {% linkable_title Building on top of Vera %} diff --git a/source/_components/verisure.markdown b/source/_components/verisure.markdown index 4e29467b8b2..1624d84ca1f 100644 --- a/source/_components/verisure.markdown +++ b/source/_components/verisure.markdown @@ -1,9 +1,9 @@ --- -layout: page +layout: component title: "Verisure" description: "Instructions how to setup Verisure devices within Home Assistant." date: 2015-08-17 20:28 -sidebar: false +sidebar: true comments: false sharing: true footer: true @@ -11,7 +11,7 @@ logo: verisure.png ha_category: Hub --- - + Home Assistant has support to integrate your [Verisure](https://www.verisure.com/) devices. diff --git a/source/_components/wink.markdown b/source/_components/wink.markdown index 5bce06c41c8..93ec2dc4073 100644 --- a/source/_components/wink.markdown +++ b/source/_components/wink.markdown @@ -1,9 +1,9 @@ --- -layout: page -title: "Wink hub" +layout: component +title: "Wink" description: "Instructions how to setup the Wink hub within Home Assistant." date: 2015-01-20 22:36 -sidebar: false +sidebar: true comments: false sharing: true footer: true @@ -11,7 +11,7 @@ logo: wink.png ha_category: Hub --- - + [Wink](http://www.wink.com/) is a home automation hub that can control a whole wide range of devices on the market. Or, as they say in their own words:

Wink offers one, quick and simple way to connect people with the products they rely on every day in their home.
diff --git a/source/_components/zone.markdown b/source/_components/zone.markdown index b0fc01587d8..9b83803b442 100644 --- a/source/_components/zone.markdown +++ b/source/_components/zone.markdown @@ -1,9 +1,9 @@ --- -layout: page +layout: component title: "Zone" description: "Instructions how to setup zones within Home Assistant." date: 2015-10-04 09:23 -sidebar: false +sidebar: true comments: false sharing: true footer: true diff --git a/source/_components/zwave.markdown b/source/_components/zwave.markdown index 3b2ba53af40..99807c7889b 100644 --- a/source/_components/zwave.markdown +++ b/source/_components/zwave.markdown @@ -1,9 +1,9 @@ --- -layout: page -title: "Z-Wave support" +layout: component +title: "Z-Wave" description: "Instructions how to integrate your existing Z-Wave within Home Assistant." date: 2015-03-23 19:59 -sidebar: false +sidebar: true comments: false sharing: true footer: true @@ -16,7 +16,7 @@ Z-Wave support is currently broken as we're unable to compile Python Open Z-Wave.

- + [Z-Wave](http://www.z-wave.com/) support for Home Assistant is very new. We have started now by integrating only the sensors. diff --git a/source/_includes/asides/component_navigation.html b/source/_includes/asides/component_navigation.html new file mode 100644 index 00000000000..e61ff281e44 --- /dev/null +++ b/source/_includes/asides/component_navigation.html @@ -0,0 +1,102 @@ +{% assign components = site.components | sort: 'title' %} +
+
+ {% if page.logo %} + + {% endif %} +
+ + {% assign file_parts = page.url | split: '/' | last | split: '.' %} + {% if file_parts.size == 3 %} + {% assign is_platform = true %} + {% assign imp_name = file_parts[1] %} + {% assign parent_name = file_parts[0] %} + {% assign parent_url = parent_name | prepend: '/components/' | append: '.html' %} + {% assign parent_component = components | where: 'url', parent_url | first %} + {% else %} + {% assign is_platform = false %} + {% assign imp_name = file_parts | first %} + {% endif %} + + {% if is_platform and parent_name != 'sensor' %} +
+ This is a platform for + the {{parent_component.title}} component. +
+ + {% elsif is_platform == false and imp_name != 'ifttt' %} + + {% assign platforms_found = false %} + {% for component in components %} + {% if component.url != page.url %} + {% assign comp_imp_name = component.url | split: '/' | last | split: '.' | first %} + {% if comp_imp_name == imp_name %} + {% unless platforms_found %} + {% assign platforms_found = true %} +

Platforms

+ + {% endif %} + + {% endif %} + + + {% assign related_found = false %} + {% for component in components %} + {% if component.url != page.url %} + {% assign comp_file_parts = component.url | split: '/' | last | split: '.' %} + {% if comp_file_parts.size == 3 %} + {% assign comp_imp_name = comp_file_parts[1] %} + {% else %} + {% assign comp_imp_name = comp_file_parts | first %} + {% endif %} + + {% if comp_imp_name == imp_name %} + {% unless related_found %} + {% assign related_found = true %} +
+

Related components

+ +
+ {% endif %} + + + + {% if page.ha_category %} +
+

Category {{page.ha_category}}

+
    + {% for component in components %} + {% if component.ha_category == page.ha_category %} +
  • + {% if component.url == page.url %} + {{component.title}} + {% else %} + {{component.title}} + {% endif %} +
    • + {% endif %} + {% endfor %} +
+
+ {% endif %} +
diff --git a/source/_includes/custom/navigation.html b/source/_includes/custom/navigation.html index 677ddc19668..4d9eac4af00 100644 --- a/source/_includes/custom/navigation.html +++ b/source/_includes/custom/navigation.html @@ -8,9 +8,9 @@
  • Presence detection
  • Automation
  • Configuration cookbook
    • -
  • Component overview
    • +
  • Components
  • Developers
      diff --git a/source/_includes/site/sidebar.html b/source/_includes/site/sidebar.html index 477c03ab757..f14f78a5f85 100644 --- a/source/_includes/site/sidebar.html +++ b/source/_includes/site/sidebar.html @@ -1,7 +1,9 @@
      - - {% include asides/social.html %} - - {% include_array default_asides %} - + {% assign url_parts = page.url | split: '/' %} + {% if url_parts[1] == 'components' %} + {% include asides/component_navigation.html %} + {% else %} + {% include asides/social.html %} + {% include_array default_asides %} + {% endif %}
      diff --git a/source/_layouts/component.html b/source/_layouts/component.html new file mode 100644 index 00000000000..3f387fde493 --- /dev/null +++ b/source/_layouts/component.html @@ -0,0 +1,14 @@ +--- +layout: default +--- + +
      +
      +

      + {{ page.title }} +

      +
      +
      + + {{ content }} +