mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-07-23 17:27:19 +00:00
Replaces all redirected URLs in all content (#10484)
This commit is contained in:
Franck Nijhof
Paulus Schoutsen
parent
d4972e56c1
commit
45b5279c3b
@ -19,7 +19,7 @@ tellstick:
|
||||
port: [50800, 50801]
|
||||
```
|
||||
|
||||
To add [lights](/components/light.tellstick/), [sensors](/components/sensor.tellstick/) and [switches](/components/switch.tellstick/) you follow the guidelines for each type individually that is [described for Home Assistant](/components/tellstick/)
|
||||
To add [lights](/components/tellstick#light), [sensors](/components/tellstick#sensor) and [switches](/components/tellstick#switch) you follow the guidelines for each type individually that is [described for Home Assistant](/components/tellstick/)
|
||||
|
||||
The add-on will also enable you to interact with the `tdtool` via a Home Assistant services call, see example below for self-learning device.
|
||||
|
||||
|
||||
@ -81,7 +81,7 @@ panel_display:
|
||||
default: false
|
||||
type: boolean
|
||||
zones:
|
||||
description: "AlarmDecoder has no way to tell us which zones are actually in use, so each zone must be configured in Home Assistant. For each zone, at least a name must be given. For more information on the available zone types, take a look at the [Binary Sensor](/components/binary_sensor.alarmdecoder/) docs. *Note: If no zones are specified, Home Assistant will not load any binary_sensor integrations.*"
|
||||
description: "AlarmDecoder has no way to tell us which zones are actually in use, so each zone must be configured in Home Assistant. For each zone, at least a name must be given. For more information on the available zone types, take a look at the [Binary Sensor](/components/alarmdecoder) docs. *Note: If no zones are specified, Home Assistant will not load any binary_sensor integrations.*"
|
||||
required: false
|
||||
type: list
|
||||
keys:
|
||||
|
||||
@ -185,7 +185,7 @@ binary_sensor:
|
||||
|
||||
## Camera
|
||||
|
||||
The `android_ip_webcam` integration adds a camera by default if you choose not to use the integration but still want to see the video feed then the [`mjpeg` camera](/components/camera.mjpeg/) platform can be used.
|
||||
The `android_ip_webcam` integration adds a camera by default if you choose not to use the integration but still want to see the video feed then the [`mjpeg` camera](/components/mjpeg) platform can be used.
|
||||
|
||||
## Configuration
|
||||
|
||||
|
||||
@ -10,7 +10,7 @@ ha_iot_class: Local Push
|
||||
ha_release: 0.49
|
||||
---
|
||||
|
||||
The `apple_tv` platform allows you to control an Apple TV (3rd and 4th generation). See the [remote platform](/components/remote.apple_tv/) if you want to send remote control buttons, e.g., arrow keys.
|
||||
The `apple_tv` platform allows you to control an Apple TV (3rd and 4th generation). See the [remote platform](/components/apple_tv#remote) if you want to send remote control buttons, e.g., arrow keys.
|
||||
|
||||
There is currently support for the following device types within Home Assistant:
|
||||
|
||||
|
||||
@ -47,7 +47,7 @@ scan_interval:
|
||||
|
||||
It is recommended to create a dedicated user on Arlo website to be used within Home Assistant and then share your Arlo cameras.
|
||||
|
||||
Finish its configuration by visiting the [Arlo sensor page](/components/sensor.arlo/) or [Arlo camera page](/components/camera.arlo/) or [Arlo control panel page](/components/alarm_control_panel.arlo/). Arlo also has a service call `arlo.update` that can be manually called to force an update prior to the regular scheduled interval.
|
||||
Finish its configuration by visiting the [Arlo sensor page](/components/arlo#sensor) or [Arlo camera page](/components/arlo#camera) or [Arlo control panel page](/components/arlo). Arlo also has a service call `arlo.update` that can be manually called to force an update prior to the regular scheduled interval.
|
||||
|
||||
The Arlo integration also provides a camera service to enable/disable the motion detection sensor. The example below enables the motion detection every time the Home Assistant service starts.
|
||||
|
||||
@ -128,7 +128,7 @@ Setting Arlo to a custom mode (mapped to `home_mode_name` in `configuration.yaml
|
||||
|
||||
You can also completely disarm the Arlo base station by calling the `alarm_control_panel.alarm_disarm` service, and trigger the alarm by calling the `alarm_control_panel.alarm_trigger` service.
|
||||
|
||||
More examples and configuration options can be found on the [Manual Alarm Control page](/components/alarm_control_panel.manual/#examples).
|
||||
More examples and configuration options can be found on the [Manual Alarm Control page](/components/manual#examples).
|
||||
|
||||
## Camera
|
||||
|
||||
|
||||
@ -118,7 +118,7 @@ In this section you find some real-life examples of how to use this sensor.
|
||||
|
||||
### aREST sensor
|
||||
|
||||
Instead of using an [aREST](/components/binary_sensor.arest/) binary sensor,
|
||||
Instead of using an [aREST](/components/arest#binary-sensor) binary sensor,
|
||||
you could retrieve the value of a device supporting
|
||||
aREST directly with a REST binary sensor.
|
||||
|
||||
|
||||
@ -47,4 +47,4 @@ proxy_params:
|
||||
type: string
|
||||
{% endconfiguration %}
|
||||
|
||||
To get your `chat_id` and `api_key` follow the instructions [here](/components/notify.telegram/).
|
||||
To get your `chat_id` and `api_key` follow the instructions [here](/components/telegram).
|
||||
|
||||
@ -204,7 +204,7 @@ slots:
|
||||
type: string
|
||||
{% endconfiguration %}
|
||||
|
||||
Information about how to install on Windows can be found [here](/components/sensor.broadlink/#microsoft-windows-installation).
|
||||
Information about how to install on Windows can be found [here](/components/broadlink#sensor#microsoft-windows-installation).
|
||||
|
||||
### How to obtain IR/RF packets?
|
||||
|
||||
|
||||
@ -112,7 +112,7 @@ binary_sensor:
|
||||
payload_off: "fail"
|
||||
```
|
||||
|
||||
Consider to use the [`ping` sensor ](/components/binary_sensor.ping/) as an alternative to the samples above.
|
||||
Consider to use the [`ping` sensor ](/components/ping#binary-sensor) as an alternative to the samples above.
|
||||
|
||||
### Check if a system service is running
|
||||
|
||||
|
||||
@ -47,4 +47,4 @@ A few notes for platform: denon
|
||||
- Play and pause are supported, toggling is not possible.
|
||||
- Seeking cannot be implemented as the UI sends absolute positions. Only seeking via simulated button presses is possible.
|
||||
|
||||
[Denon AVR]: /components/media_player.denonavr/
|
||||
[Denon AVR]: /components/denonavr/
|
||||
|
||||
@ -94,4 +94,4 @@ A few notes:
|
||||
- To remotely power on Marantz receivers with Home Assistant, the Auto-Standby feature must be enabled in the receiver's settings.
|
||||
- Sound mode: The command to set a specific sound mode is different from the value of the current sound mode reported by the receiver (sound_mode_raw). There is a key-value structure (sound_mode_dict) that matches the raw sound mode to one of the possible commands to set a sound mode (for instance {'MUSIC':['PLII MUSIC']}. If you get a "Not able to match sound mode" warning, please open an issue on the [denonavr library](https://github.com/scarface-4711/denonavr), stating which raw sound mode could not be matched so it can be added to the matching dictionary. You can find the current raw sound mode under "Development Tools/States" in the front panel.
|
||||
|
||||
[Denon]: /components/media_player.denon/
|
||||
[Denon]: /components/denon
|
||||
|
||||
@ -41,7 +41,7 @@ only_direct:
|
||||
default: false
|
||||
{% endconfiguration %}
|
||||
|
||||
This sensor stores a lot of attributes which can be accessed by other sensors, e.g., a [template sensor](/components/sensor.template/).
|
||||
This sensor stores a lot of attributes which can be accessed by other sensors, e.g., a [template sensor](/components/template).
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
|
||||
@ -12,30 +12,30 @@ Home Assistant can discover and automatically configure [zeroconf](https://en.wi
|
||||
|
||||
* [Apple TV](/components/apple_tv/)
|
||||
* [Belkin WeMo switches](/components/wemo/)
|
||||
* [Bluesound speakers](/components/media_player.bluesound/)
|
||||
* [Bose Soundtouch speakers](/components/media_player.soundtouch/)
|
||||
* [Denon network receivers](/components/media_player.denonavr/)
|
||||
* [DirecTV receivers](/components/media_player.directv/)
|
||||
* [DLNA DMR enabled devices](/components/media_player.dlna_dmr/)
|
||||
* [Enigma2 media player](/components/media_player.enigma2/)
|
||||
* [Frontier Silicon internet radios](/components/media_player.frontier_silicon/)
|
||||
* [Google Cast](/components/media_player.cast/)
|
||||
* [Linn / Openhome](/components/media_player.openhome/)
|
||||
* [Logitech Harmony Hub](/components/remote.harmony/)
|
||||
* [Logitech media server (Squeezebox)](/components/media_player.squeezebox/)
|
||||
* [Netgear routers](/components/device_tracker.netgear/)
|
||||
* [Panasonic Viera](/components/media_player.panasonic_viera/)
|
||||
* [Philips Hue](/components/light.hue/)
|
||||
* [Plex media server](/components/media_player.plex/)
|
||||
* [Roku media player](/components/media_player.roku/)
|
||||
* [SABnzbd downloader](/components/sensor.sabnzbd/)
|
||||
* [Samsung SyncThru Printer](/components/sensor.syncthru/)
|
||||
* [Samsung TVs](/components/media_player.samsungtv/)
|
||||
* [Sonos speakers](/components/media_player.sonos/)
|
||||
* [Bluesound speakers](/components/bluesound)
|
||||
* [Bose Soundtouch speakers](/components/soundtouch)
|
||||
* [Denon network receivers](/components/denonavr/)
|
||||
* [DirecTV receivers](/components/directv)
|
||||
* [DLNA DMR enabled devices](/components/dlna_dmr)
|
||||
* [Enigma2 media player](/components/enigma2)
|
||||
* [Frontier Silicon internet radios](/components/frontier_silicon)
|
||||
* [Google Cast](/components/cast)
|
||||
* [Linn / Openhome](/components/openhome)
|
||||
* [Logitech Harmony Hub](/components/harmony)
|
||||
* [Logitech media server (Squeezebox)](/components/squeezebox)
|
||||
* [Netgear routers](/components/netgear)
|
||||
* [Panasonic Viera](/components/panasonic_viera)
|
||||
* [Philips Hue](/components/hue)
|
||||
* [Plex media server](/components/plex#media-player)
|
||||
* [Roku media player](/components/roku#media-player)
|
||||
* [SABnzbd downloader](/components/sabnzbd)
|
||||
* [Samsung SyncThru Printer](/components/syncthru)
|
||||
* [Samsung TVs](/components/samsungtv)
|
||||
* [Sonos speakers](/components/sonos)
|
||||
* [Telldus Live](/components/tellduslive/)
|
||||
* [Wink](/components/wink/)
|
||||
* [Yamaha media player](/components/media_player.yamaha/)
|
||||
* [Yeelight Sunflower bulb](/components/light.yeelightsunflower/)
|
||||
* [Yamaha media player](/components/yamaha)
|
||||
* [Yeelight Sunflower bulb](/components/yeelightsunflower/)
|
||||
* [Xiaomi Gateway (Aqara)](/components/xiaomi_aqara/)
|
||||
|
||||
It will be able to add Google Chromecasts and Belkin WeMo switches automatically,
|
||||
|
||||
@ -75,7 +75,7 @@ The `ecovacs` vacuum platform allows you to monitor and control your Ecovacs Dee
|
||||
|
||||
The remaining lifespan of components on your Deebot vacuum will be reported as attributes on the vacuum entity. The value will be a whole number representing the percentage of life remaining.
|
||||
|
||||
Here's an example of how to extract the filter's lifespan to its own sensor using a [template sensor](/components/sensor.template/):
|
||||
Here's an example of how to extract the filter's lifespan to its own sensor using a [template sensor](/components/template):
|
||||
|
||||
{% raw %}
|
||||
```yaml
|
||||
|
||||
@ -42,7 +42,7 @@ name:
|
||||
|
||||
## Power consumption sensor
|
||||
|
||||
Starting with [version 2 of the firmware](https://www.edimax.com/edimax/download/download/data/edimax/global/download/), the Edimax switches can also report the current and accumulated daily power consumption in their state objects. Use a [template sensor](/components/sensor.template/) to extract their values:
|
||||
Starting with [version 2 of the firmware](https://www.edimax.com/edimax/download/download/data/edimax/global/download/), the Edimax switches can also report the current and accumulated daily power consumption in their state objects. Use a [template sensor](/components/template) to extract their values:
|
||||
|
||||
{% raw %}
|
||||
```yaml
|
||||
|
||||
@ -104,7 +104,7 @@ panic_type:
|
||||
default: Police
|
||||
type: string
|
||||
zones:
|
||||
description: "Envisalink boards have no way to tell us which zones are actually in use, so each zone must be configured in Home Assistant. For each zone, at least a name must be given. For more information on the available zone types, take a look at the [Binary Sensor](/components/binary_sensor.envisalink/) docs. *Note: If no zones are specified, Home Assistant will not load any binary_sensor components.*"
|
||||
description: "Envisalink boards have no way to tell us which zones are actually in use, so each zone must be configured in Home Assistant. For each zone, at least a name must be given. For more information on the available zone types, take a look at the [Binary Sensor](/components/envisalink) docs. *Note: If no zones are specified, Home Assistant will not load any binary_sensor components.*"
|
||||
required: false
|
||||
type: integer
|
||||
keys:
|
||||
|
||||
@ -13,7 +13,7 @@ The `fastdotcom` integration uses the [Fast.com](https://fast.com/) web service
|
||||
|
||||
<div class='note'>
|
||||
|
||||
Currently fast.com only supports measuring download bandwidth. If you want to measure bandwidth metrics other then download such as ping and upload, utilize the [speedtest](/components/sensor.speedtest) component.
|
||||
Currently fast.com only supports measuring download bandwidth. If you want to measure bandwidth metrics other then download such as ping and upload, utilize the [speedtest](/components/speedtestdotnet) component.
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
@ -89,7 +89,7 @@ Event data:
|
||||
- **click_type**: The type of click. Possible values are `single`, `double` and `hold`.
|
||||
- **queued_time**: The amount of time this event was queued on the button, in seconds.
|
||||
|
||||
To help detect and debug flic button clicks, you can use this automation that send a notification on very click type of every button. This example uses the [HTML5 push notification platform](/components/notify.html5/). Visit the [notification integration page](/components/notify/) for more information on setting up notifications.
|
||||
To help detect and debug flic button clicks, you can use this automation that send a notification on very click type of every button. This example uses the [HTML5 push notification platform](/components/html5). Visit the [notification integration page](/components/notify/) for more information on setting up notifications.
|
||||
|
||||
```yaml
|
||||
automation:
|
||||
|
||||
@ -18,7 +18,7 @@ There is currently support for the following device types within Home Assistant:
|
||||
- [Binary Sensor](#binary-sensor)
|
||||
- [Switch](#switch)
|
||||
|
||||
Currently, only relays and ports configured to be digital inputs are supported in Home Assistant. For IR support, please use the [iTach remote platform](/components/remote.itach/), but note that it will likely not function concurrently on the same GC100 due to limitations in the TCP socket server implementation used by Global Caché.
|
||||
Currently, only relays and ports configured to be digital inputs are supported in Home Assistant. For IR support, please use the [iTach remote platform](/components/itach), but note that it will likely not function concurrently on the same GC100 due to limitations in the TCP socket server implementation used by Global Caché.
|
||||
|
||||
## Configuration
|
||||
|
||||
|
||||
@ -189,7 +189,7 @@ This does *not* affect the entities in Home Assistant. They all use their own co
|
||||
|
||||
### Reading attributes of entities
|
||||
|
||||
Most devices have, besides their state, additional attributes like their battery state or valve position. These can be accessed using templates in automations, or even as their own entities using the [template sensor](/components/sensor.template/) component. Here's an example of a template sensor that exposes the valve state of a thermostat.
|
||||
Most devices have, besides their state, additional attributes like their battery state or valve position. These can be accessed using templates in automations, or even as their own entities using the [template sensor](/components/template) component. Here's an example of a template sensor that exposes the valve state of a thermostat.
|
||||
|
||||
```yaml
|
||||
sensor:
|
||||
|
||||
@ -98,7 +98,7 @@ To set both the date and time in the same call, use `date` and `time` together,
|
||||
|
||||
The following example shows the usage of the `input_datetime` as a trigger in an
|
||||
automation (note that you will need a
|
||||
[time sensor](/components/sensor.time_date/) elsewhere in your configuration):
|
||||
[time sensor](/components/time_date) elsewhere in your configuration):
|
||||
|
||||
{% raw %}
|
||||
```yaml
|
||||
|
||||
@ -48,7 +48,7 @@ The default name of the location attributes is `lat` and `long` to avoid showing
|
||||
|
||||
### Show position on map with camera platform
|
||||
|
||||
The [generic camera platform](/components/camera.mjpeg/) offers
|
||||
The [generic camera platform](/components/mjpeg) offers
|
||||
the possibility to show the location of the ISS on OpenStreetMap.
|
||||
|
||||
{% raw %}
|
||||
|
||||
@ -71,7 +71,7 @@ devices:
|
||||
required: true
|
||||
type: string
|
||||
binary_sensors:
|
||||
description: A list of binary sensors connected to the device. See [Konnected Binary Sensor](/components/binary_sensor.konnected/) for configuration variables.
|
||||
description: A list of binary sensors connected to the device. See [Konnected Binary Sensor](/components/konnected#binary-sensor) for configuration variables.
|
||||
required: false
|
||||
type: list
|
||||
keys:
|
||||
@ -117,7 +117,7 @@ devices:
|
||||
required: false
|
||||
default: not set (device default is 3 minutes)
|
||||
switches:
|
||||
description: A list of actuators (on/off switches) connected to the device. See [Konnected Switch](/components/switch.konnected/) for configuration variables.
|
||||
description: A list of actuators (on/off switches) connected to the device. See [Konnected Switch](/components/konnected#switch) for configuration variables.
|
||||
required: false
|
||||
type: list
|
||||
keys:
|
||||
|
||||
@ -37,7 +37,7 @@ These are the steps to take:
|
||||
* Check all permission boxes
|
||||
* Hit Save
|
||||
4. You should be directed to your [Notification Apps list](https://developer.lametric.com/applications/sources), click on "Home Assistant", copy your client ID and client Secret and paste into the Home Assistant configuration block in the previous section.
|
||||
5. Set up some notifications in Home Assistant by following the instructions on the [Lametric Notify](/components/notify.lametric) page.
|
||||
5. Set up some notifications in Home Assistant by following the instructions on the [Lametric Notify](/components/lametric) page.
|
||||
6. Save all configuration files and restart Home Assistant.
|
||||
|
||||
## Notifications
|
||||
|
||||
@ -8,7 +8,7 @@ ha_iot_class: Local Polling
|
||||
ha_release: "0.20"
|
||||
---
|
||||
|
||||
The `lg_netcast` platform allows you to control a LG Smart TV running NetCast 3.0 (LG Smart TV models released in 2012) and NetCast 4.0 (LG Smart TV models released in 2013). For the new LG WebOS TV's use the [webostv](/components/media_player.webostv) platform.
|
||||
The `lg_netcast` platform allows you to control a LG Smart TV running NetCast 3.0 (LG Smart TV models released in 2012) and NetCast 4.0 (LG Smart TV models released in 2013). For the new LG WebOS TV's use the [webostv](/components/webostv#media-player) platform.
|
||||
|
||||
To add a LG TV to your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
|
||||
@ -648,7 +648,7 @@ light:
|
||||
|
||||
- [ESPHome](https://esphome.io) implements the JSON schema for MQTT based installs and supports [MQTT discovery](/docs/mqtt/discovery/).
|
||||
|
||||
- [AiLight](https://github.com/stelgenhof/AiLight) is a custom firmware for the Ai-Thinker (and equivalent) RGBW WiFi light bulbs that has an ESP8266 onboard and controlled by the MY9291 LED driver. It implements the [MQTT JSON light](/components/light.mqtt_json/) platform and supports ON/OFF, RGBW colours, brightness, colour temperature, flashing and transitions. Also it includes [MQTT Auto Discovery](/docs/mqtt/discovery/)) and the MQTT Last Will and Testament is enabled as well.
|
||||
- [AiLight](https://github.com/stelgenhof/AiLight) is a custom firmware for the Ai-Thinker (and equivalent) RGBW WiFi light bulbs that has an ESP8266 onboard and controlled by the MY9291 LED driver. It implements the [MQTT JSON light](/components/light.mqtt) platform and supports ON/OFF, RGBW colours, brightness, colour temperature, flashing and transitions. Also it includes [MQTT Auto Discovery](/docs/mqtt/discovery/)) and the MQTT Last Will and Testament is enabled as well.
|
||||
|
||||
## Template schema
|
||||
|
||||
|
||||
@ -56,7 +56,7 @@ locations:
|
||||
type: list
|
||||
{% endconfiguration %}
|
||||
|
||||
To explore the data available within the `data` attribute of a sensor use the `dev-template` tool on the Home-assistant frontend. `data` contains a list of monitored sites, where the number of monitored sites are given by the `sites` attribute. If a sensor has four sites, access the fourth site by indexing the list of sites using data[3]. Each site is a dictionary with multiple fields, with entries for the `latitude` and `longitude` of that site, a `pollution_status`, `site_code`, `site_name` and `site_type`. The field `number_of_pollutants` states how many pollutants are monitored (of the possible six) and the field `pollutants` returns a list with data for each pollutant. To access the first pollutant in the list for site zero use `attributes.data[0].pollutants[0]`. Each entry in `pollutants` is a dictionary with fields for the pollutant `code`, `description`, `index`, `quality` and a `summary`. [Template sensors](/components/sensor.template/) can then be added to display these attributes, for example:
|
||||
To explore the data available within the `data` attribute of a sensor use the `dev-template` tool on the Home-assistant frontend. `data` contains a list of monitored sites, where the number of monitored sites are given by the `sites` attribute. If a sensor has four sites, access the fourth site by indexing the list of sites using data[3]. Each site is a dictionary with multiple fields, with entries for the `latitude` and `longitude` of that site, a `pollution_status`, `site_code`, `site_name` and `site_type`. The field `number_of_pollutants` states how many pollutants are monitored (of the possible six) and the field `pollutants` returns a list with data for each pollutant. To access the first pollutant in the list for site zero use `attributes.data[0].pollutants[0]`. Each entry in `pollutants` is a dictionary with fields for the pollutant `code`, `description`, `index`, `quality` and a `summary`. [Template sensors](/components/template) can then be added to display these attributes, for example:
|
||||
|
||||
```yaml
|
||||
# Example template sensors
|
||||
|
||||
@ -7,7 +7,7 @@ ha_category:
|
||||
ha_release: "0.50"
|
||||
---
|
||||
|
||||
The `mqtt` platform extends the [manual alarm](/components/alarm_control_panel.manual/) by adding support for MQTT control of the alarm by a remote device. It can be used to create external keypads which simply change the state of the manual alarm in Home Assistant.
|
||||
The `mqtt` platform extends the [manual alarm](/components/manual) by adding support for MQTT control of the alarm by a remote device. It can be used to create external keypads which simply change the state of the manual alarm in Home Assistant.
|
||||
|
||||
It's essentially the opposite of the [MQTT Alarm Panel](/components/alarm_control_panel.mqtt/) which allows Home Assistant to observe an existing, fully-featured alarm where all of the alarm logic is embedded in that physical device.
|
||||
|
||||
@ -106,7 +106,7 @@ armed_home/armed_away/armed_night/disarmed/triggered:
|
||||
type: integer
|
||||
{% endconfiguration %}
|
||||
|
||||
See the documentation for the [manual alarm platform](/components/alarm_control_panel.manual/) for a description.
|
||||
See the documentation for the [manual alarm platform](/components/manual) for a description.
|
||||
|
||||
Additionally, the following MQTT configuration variables are also available.
|
||||
|
||||
@ -173,7 +173,7 @@ alarm_control_panel:
|
||||
pending_time: 0
|
||||
```
|
||||
|
||||
Refer to the [Manual Alarm Control page](/components/alarm_control_panel.manual/#examples) for more real-life examples on how to use this panel.
|
||||
Refer to the [Manual Alarm Control page](/components/manual#examples) for more real-life examples on how to use this panel.
|
||||
|
||||
## MQTT Control
|
||||
|
||||
|
||||
@ -57,7 +57,7 @@ Available services: `turn_on`, `turn_off`, `toggle`, `volume_up`, `volume_down`,
|
||||
|
||||
#### Service `media_player.select_sound_mode`
|
||||
|
||||
Currently only supported on [Denon AVR](/components/media_player.denonavr/) and [Songpal](/components/media_player.songpal/).
|
||||
Currently only supported on [Denon AVR](/components/denonavr/) and [Songpal](/components/songpal).
|
||||
|
||||
| Service data attribute | Optional | Description |
|
||||
| ---------------------- | -------- | ---------------------------------------------------- |
|
||||
@ -66,7 +66,7 @@ Currently only supported on [Denon AVR](/components/media_player.denonavr/) and
|
||||
|
||||
#### Service `media_player.shuffle_set`
|
||||
|
||||
Currently only supported on [Spotify](/components/media_player.spotify/), [MPD](/components/media_player.mpd/), [Kodi](/components/media_player.kodi/), [Squeezebox](/components/media_player.squeezebox/) and [Universal](/components/media_player.universal/).
|
||||
Currently only supported on [Spotify](/components/spotify), [MPD](/components/mpd), [Kodi](/components/kodi), [Squeezebox](/components/squeezebox) and [Universal](/components/universal).
|
||||
|
||||
| Service data attribute | Optional | Description |
|
||||
| ---------------------- | -------- | ---------------------------------------------------- |
|
||||
|
||||
@ -9,9 +9,9 @@ ha_release: 0.31
|
||||
ha_qa_scale: internal
|
||||
---
|
||||
|
||||
The `min_max` sensor platform consumes the state from other sensors to determine the minimum, maximum, latest (last) and the mean of the collected states. The sensor will always show you the lowest/highest/latest value which was received from all monitored sensors. If you have spikes in your values, it's recommended to filter/equalize your values with a [statistics sensor](/components/sensor.statistics/) first.
|
||||
The `min_max` sensor platform consumes the state from other sensors to determine the minimum, maximum, latest (last) and the mean of the collected states. The sensor will always show you the lowest/highest/latest value which was received from all monitored sensors. If you have spikes in your values, it's recommended to filter/equalize your values with a [statistics sensor](/components/statistics) first.
|
||||
|
||||
This sensor is an alternative to the [template sensor](/components/sensor.template/)'s `value_template:` to get the average of multiple sensors.
|
||||
This sensor is an alternative to the [template sensor](/components/template)'s `value_template:` to get the average of multiple sensors.
|
||||
|
||||
{% raw %}
|
||||
```yaml
|
||||
|
||||
@ -200,7 +200,7 @@ curl -G -X GET http://IP_ADDRESS/relay -d 'state=1'
|
||||
|
||||
### Get the current power consumption
|
||||
|
||||
The switch is measuring the current power consumption. To expose this as a sensor use a [`template` sensor](/components/sensor.template/).
|
||||
The switch is measuring the current power consumption. To expose this as a sensor use a [`template` sensor](/components/template).
|
||||
|
||||
{% raw %}
|
||||
```yaml
|
||||
|
||||
@ -87,7 +87,7 @@ That's it. You can copy and paste your new `client id` and `client secret` in yo
|
||||
|
||||
### Webhooks
|
||||
|
||||
The Welcome and Presence cameras can send instant events to Home Assistant by using webhooks. There are different types of events, each with slightly different data attached. To enable the webhooks add `webhooks: true` to your configuration. It is also required to have your camera enabled in Home Assistant. You can do this either by manually setting up the [platform](/components/camera.netatmo/) or by enabeling [discovery](/components/netatmo/#discovery).
|
||||
The Welcome and Presence cameras can send instant events to Home Assistant by using webhooks. There are different types of events, each with slightly different data attached. To enable the webhooks add `webhooks: true` to your configuration. It is also required to have your camera enabled in Home Assistant. You can do this either by manually setting up the [platform](/components/netatmo#camera) or by enabeling [discovery](/components/netatmo/#discovery).
|
||||
|
||||
To be able to receive events from Netatmo, your Home Assistant instance needs to be accessible from the web ([Hass.io instructions](/addons/duckdns/)) and you need to have the base_url configured for the HTTP integration ([docs](/components/http/#base_url)).
|
||||
|
||||
|
||||
@ -58,7 +58,7 @@ longitude:
|
||||
|
||||
<div class='note'>
|
||||
|
||||
This platform is an alternative to the [`openweathermap`](/components/sensor.openweathermap/) sensor.
|
||||
This platform is an alternative to the [`openweathermap`](/components/openweathermap#sensor) sensor.
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
@ -17,8 +17,8 @@ There are _multiple_ ways of integrating an OpenWRT router for presence detectio
|
||||
* average six-second delay between connecting and being registered as `home`
|
||||
* lots of unnecessary network requests
|
||||
* Examples:
|
||||
* [ubus](/components/device_tracker.ubus/)
|
||||
* [luci](/components/device_tracker.luci/)
|
||||
* [ubus](/components/ubus)
|
||||
* [luci](/components/luci)
|
||||
* __passive/event-based__
|
||||
External services which notify Home Assistant of devices via the [REST API endpoint](https://developers.home-assistant.io/docs/en/external_api_rest.html).
|
||||
* Advantages:
|
||||
|
||||
@ -66,7 +66,7 @@ waypoints:
|
||||
default: true
|
||||
type: boolean
|
||||
waypoint_whitelist:
|
||||
description: "A list of user names (as defined for [Owntracks](/components/device_tracker.owntracks/)) who can export their waypoints from Owntracks to Home Assistant. This would be the `username` portion of the Base Topic Name, (e.g., owntracks/**username**/iPhone)"
|
||||
description: "A list of user names (as defined for [Owntracks](/components/owntracks)) who can export their waypoints from Owntracks to Home Assistant. This would be the `username` portion of the Base Topic Name, (e.g., owntracks/**username**/iPhone)"
|
||||
required: false
|
||||
default: All users who are connected to Home Assistant via Owntracks.
|
||||
type: list
|
||||
|
||||
@ -8,7 +8,7 @@ ha_release: 0.19
|
||||
ha_iot_class: Local Polling
|
||||
---
|
||||
|
||||
The `pioneer` platform allows you to control Pioneer Network Receivers. Please note, however, that the more recent Pioneer models work with [Onkyo](/components/media_player.onkyo/) platform instead.
|
||||
The `pioneer` platform allows you to control Pioneer Network Receivers. Please note, however, that the more recent Pioneer models work with [Onkyo](/components/onkyo) platform instead.
|
||||
|
||||
To add a Pioneer receiver to your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
|
||||
@ -109,13 +109,13 @@ entity_id:
|
||||
## Examples
|
||||
### Using plain MQTT sensor to get the data
|
||||
This is a practical example that uses a multiple of `MQTT sensors` to supply the readings used by the `plant` sensor.
|
||||
Another good source of this data would be the [Mi Flora](/components/sensor.miflora/) component.
|
||||
Another good source of this data would be the [Mi Flora](/components/miflora) component.
|
||||
|
||||
If the sensor data is within the min/max values the status will be `ok`, if not the status will be `problem`. You can use this to trigger a notification, if there is a problem with your plant. Of course you can only monitor attributes of your plant, where the sensor is configured and is providing the data.
|
||||
|
||||
## Data Source
|
||||
|
||||
The main sources of the data will usually be a [MiFlora sensor](/components/sensor.miflora/) or a [MQTT sensor](/components/sensor.mqtt/) receiving the data from a [PlantGateway](https://github.com/ChristianKuehnel/plantgateway).
|
||||
The main sources of the data will usually be a [MiFlora sensor](/components/miflora) or a [MQTT sensor](/components/sensor.mqtt/) receiving the data from a [PlantGateway](https://github.com/ChristianKuehnel/plantgateway).
|
||||
|
||||
If you want to get the date via a PlantGateway, this is a typical configuration for the MQTT sensors:
|
||||
|
||||
|
||||
@ -49,4 +49,4 @@ proxy_params:
|
||||
type: string
|
||||
{% endconfiguration %}
|
||||
|
||||
To get your `chat_id` and `api_key` follow the instructions [here](/components/notify.telegram/).
|
||||
To get your `chat_id` and `api_key` follow the instructions [here](/components/telegram).
|
||||
|
||||
@ -128,7 +128,7 @@ sensor:
|
||||
|
||||
### Single value from a local Glances instance
|
||||
|
||||
The [glances](/components/sensor.glances/) sensor is doing the exact same thing for all exposed values.
|
||||
The [glances](/components/glances) sensor is doing the exact same thing for all exposed values.
|
||||
|
||||
```yaml
|
||||
sensor:
|
||||
@ -240,7 +240,7 @@ sensor:
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
This sample fetches a weather report from [OpenWeatherMap](http://openweathermap.org/), maps the resulting data into attributes of the RESTful sensor and then creates a set of [template](/components/sensor.template/) sensors that monitor the attributes and present the values in a usable form.
|
||||
This sample fetches a weather report from [OpenWeatherMap](http://openweathermap.org/), maps the resulting data into attributes of the RESTful sensor and then creates a set of [template](/components/template) sensors that monitor the attributes and present the values in a usable form.
|
||||
|
||||
{% raw %}
|
||||
```yaml
|
||||
|
||||
@ -142,7 +142,7 @@ sensor:
|
||||
|
||||
### Use an external script
|
||||
|
||||
The example is doing the same as the [aREST sensor](/components/sensor.arest/) but with an external Python script. It should give you an idea about interfacing with devices which are exposing a RESTful API.
|
||||
The example is doing the same as the [aREST sensor](/components/arest#sensor) but with an external Python script. It should give you an idea about interfacing with devices which are exposing a RESTful API.
|
||||
|
||||
The one-line script to retrieve a value is shown below. Of course would it be possible to use this directly in the `configuration.yaml` file but need extra care about the quotation marks.
|
||||
|
||||
|
||||
@ -85,7 +85,7 @@ monitored_conditions:
|
||||
|
||||
<div class='note'>
|
||||
|
||||
This sensor is an alternative to the [`metoffice`](/components/weather.metoffice/) weather platform.
|
||||
This sensor is an alternative to the [`metoffice`](/components/metoffice/) weather platform.
|
||||
The weather platform is easier to configure but less customizable.
|
||||
|
||||
</div>
|
||||
|
||||
@ -175,7 +175,7 @@ The state and the attributes of the sensor by design do not update in a synchron
|
||||
|
||||
### Get battery level
|
||||
|
||||
If you are using the [OwnTracks](/components/device_tracker.owntracks/) and enable the reporting of the battery level then you can use a MQTT sensor to keep track of your battery. A regular MQTT message from OwnTracks looks like this:
|
||||
If you are using the [OwnTracks](/components/owntracks) and enable the reporting of the battery level then you can use a MQTT sensor to keep track of your battery. A regular MQTT message from OwnTracks looks like this:
|
||||
|
||||
```bash
|
||||
owntracks/tablet/tablet {"_type":"location","lon":7.21,"t":"u","batt":92,"tst":144995643,"tid":"ta","acc":27,"lat":46.12}
|
||||
|
||||
@ -131,7 +131,7 @@ image_processing:
|
||||
<img src='{{site_root}}/images/screenshots/ssocr.png' />
|
||||
</p>
|
||||
|
||||
With the help of a [template sensor](/components/sensor.template/), the value can be shown as badge.
|
||||
With the help of a [template sensor](/components/template), the value can be shown as badge.
|
||||
|
||||
{% raw %}
|
||||
|
||||
|
||||
@ -266,7 +266,7 @@ intent_script:
|
||||
|
||||
##### Weather
|
||||
|
||||
So now you can open and close your garage door, let's check the weather. Add the Weather by Snips Skill to your assistant. Create a weather sensor, in this example [Dark Sk](/components/sensor.darksky/) and the `api_key` in the `secrets.yaml` file.
|
||||
So now you can open and close your garage door, let's check the weather. Add the Weather by Snips Skill to your assistant. Create a weather sensor, in this example [Dark Sk](/components/darksky) and the `api_key` in the `secrets.yaml` file.
|
||||
|
||||
```yaml
|
||||
- platform: darksky
|
||||
|
||||
@ -25,7 +25,7 @@ This device tracker needs SNMP to be enabled on the router. It could be that you
|
||||
|
||||
## Presence Detection
|
||||
|
||||
The following OID examples pull the current MAC Address table from a router. This reflects all recent devices seen on the network. However, since devices are not removed until they time out, this is less effective for [device tracker integration page](/components/device_tracker/) than desirable. It is recommended to use [Ping](/components/device_tracker.ping/) or [Nmap](/components/device_tracker.nmap_tracker/) instead.
|
||||
The following OID examples pull the current MAC Address table from a router. This reflects all recent devices seen on the network. However, since devices are not removed until they time out, this is less effective for [device tracker integration page](/components/device_tracker/) than desirable. It is recommended to use [Ping](/components/ping) or [Nmap](/components/nmap_tracker) instead.
|
||||
|
||||
| Brand | Device/Firmware | OID |
|
||||
| --- | --- | --- |
|
||||
|
||||
@ -50,7 +50,7 @@ name:
|
||||
|
||||
## Full configuration example
|
||||
|
||||
In case you would like to convert the values for example to kWh instead of the default Wh, you can use the [template platform](/components/sensor.template/).
|
||||
In case you would like to convert the values for example to kWh instead of the default Wh, you can use the [template platform](/components/template).
|
||||
|
||||
{% raw %}
|
||||
```yaml
|
||||
|
||||
@ -54,7 +54,7 @@ sensor:
|
||||
ip_address: 192.168.1.123
|
||||
```
|
||||
|
||||
In case you would like to convert the values for example to kWh instead of the default Wh, you can use the [template platform](/components/sensor.template/).
|
||||
In case you would like to convert the values for example to kWh instead of the default Wh, you can use the [template platform](/components/template).
|
||||
|
||||
{% raw %}
|
||||
```yaml
|
||||
|
||||
@ -31,7 +31,7 @@ ip_address:
|
||||
|
||||
### Optional template sensor
|
||||
|
||||
If you would like to convert the values from multiple panels or view the total power the house is using, you can use the [template platform](/components/sensor.template/).
|
||||
If you would like to convert the values from multiple panels or view the total power the house is using, you can use the [template platform](/components/template).
|
||||
|
||||
{% raw %}
|
||||
```yaml
|
||||
|
||||
@ -79,7 +79,7 @@ You can also play HTTP (not HTTPS) URLs:
|
||||
|
||||
### Text-to-Speech services
|
||||
|
||||
You can use TTS services like [Google Text-to-Speech](/components/tts.google/) or [Amazon Polly](/components/tts.amazon_polly) only if your Home Assistant is configured in HTTP and not HTTPS (current device limitation, a firmware upgrade is planned).
|
||||
You can use TTS services like [Google Text-to-Speech](/components/google_translate) or [Amazon Polly](/components/amazon_polly) only if your Home Assistant is configured in HTTP and not HTTPS (current device limitation, a firmware upgrade is planned).
|
||||
|
||||
A workaround if you want to publish your Home Assistant installation on Internet in SSL is to configure an HTTPS Web Server as a reverse proxy ([nginx](/docs/ecosystem/nginx/) for example) and let your Home Assistant configuration in HTTP on your local network. The Soundtouch devices will be available to access the TTS files in HTTP in local and your configuration will be in HTTPS on the Internet.
|
||||
|
||||
|
||||
@ -79,7 +79,7 @@ In this section you find some real-life examples of how to use this switch.
|
||||
### aREST device
|
||||
|
||||
The example below is doing the same as the
|
||||
[aREST switch](/components/switch.arest/).
|
||||
[aREST switch](/components/arest#switch).
|
||||
The command line tool [`curl`](http://curl.haxx.se/) is used to toggle a pin
|
||||
which is controllable through REST.
|
||||
|
||||
|
||||
@ -10,9 +10,9 @@ ha_iot_class: Cloud Push
|
||||
|
||||
Use Telegram on your mobile or desktop device to send and receive messages or commands to/from your Home Assistant.
|
||||
|
||||
This integration creates notification services to send, or edit previously sent, messages from a [Telegram Bot account](https://core.telegram.org/bots) configured either with the [polling](/components/telegram_bot.polling/) method or with the [webhooks](/components/telegram_bot.webhooks/) one, and trigger events when receiving messages.
|
||||
This integration creates notification services to send, or edit previously sent, messages from a [Telegram Bot account](https://core.telegram.org/bots) configured either with the [polling](/components/polling) method or with the [webhooks](/components/webhooks) one, and trigger events when receiving messages.
|
||||
|
||||
If you don't need to receive messages, you can use the [broadcast](/components/telegram_bot.broadcast/) platform instead.
|
||||
If you don't need to receive messages, you can use the [broadcast](/components/broadcast) platform instead.
|
||||
|
||||
## Notification services
|
||||
|
||||
@ -166,7 +166,7 @@ Remove the bot from the chat group where it was added.
|
||||
|
||||
## `telegram` notification platform
|
||||
|
||||
The [`telegram` notification platform](/components/notify.telegram/) requires the `telegram_bot` integration to work with, and it's designed to generate a customized shortcut (`notify.USERNAME`) to send notifications (messages, photos, documents and locations) to a particular `chat_id` with the old syntax, allowing backward compatibility.
|
||||
The [`telegram` notification platform](/components/telegram) requires the `telegram_bot` integration to work with, and it's designed to generate a customized shortcut (`notify.USERNAME`) to send notifications (messages, photos, documents and locations) to a particular `chat_id` with the old syntax, allowing backward compatibility.
|
||||
|
||||
The required YAML configuration now reduces to:
|
||||
|
||||
|
||||
@ -289,7 +289,7 @@ sensor:
|
||||
|
||||
The `template` sensors are not limited to use attributes from other entities but can also work with [Home Assistant's template extensions](/docs/configuration/templating/#home-assistant-template-extensions).
|
||||
|
||||
This template contains no entities that will trigger an update, so we add an `entity_id:` line with an entity that will force an update - here we're using a [date sensor](/components/sensor.time_date/) to get a daily update:
|
||||
This template contains no entities that will trigger an update, so we add an `entity_id:` line with an entity that will force an update - here we're using a [date sensor](/components/time_date) to get a daily update:
|
||||
|
||||
{% raw %}
|
||||
```yaml
|
||||
|
||||
@ -13,7 +13,7 @@ value can be obtained by logging in to the Tomato admin interface and search for
|
||||
|
||||
Because of a limitation in Tomato's API, this platform will only track wireless devices.
|
||||
If tracking wired devices like a Philips Hue Hub is necessary,
|
||||
it is possible to use another platform like [Nmap](/components/device_tracker.nmap_tracker/).
|
||||
it is possible to use another platform like [Nmap](/components/nmap_tracker).
|
||||
|
||||
To use this device tracker in your installation,
|
||||
add the following to your `configuration.yaml` file:
|
||||
|
||||
@ -36,7 +36,7 @@ auth_token:
|
||||
|
||||
### Usage
|
||||
|
||||
After configuring the base Twilio component, add and configure either or both of the [twilio SMS](/components/notify.twilio_sms/) and [twilio Phone](/components/notify.twilio_call) integrations to utilize the notification functionality.
|
||||
After configuring the base Twilio component, add and configure either or both of the [twilio SMS](/components/twilio_sms) and [twilio Phone](/components/twilio_call) integrations to utilize the notification functionality.
|
||||
|
||||
To be able to receive events from Twilio, your Home Assistant instance needs to be accessible from the web ([Hass.io instructions](/addons/duckdns/)) and you need to have the `base_url` configured for the HTTP integration ([docs](/components/http/#base_url)).
|
||||
|
||||
|
||||
@ -7,7 +7,7 @@ ha_category:
|
||||
ha_release: 0.7.6
|
||||
---
|
||||
|
||||
_This is one of multiple ways we support OpenWRT. For an overview, see [openwrt](/components/device_tracker.openwrt/)._
|
||||
_This is one of multiple ways we support OpenWRT. For an overview, see [openwrt](/components/openwrt)._
|
||||
|
||||
This is a presence detection scanner for [OpenWRT](https://openwrt.org/) using [ubus](http://wiki.openwrt.org/doc/techref/ubus). It scans for changes in `hostapd.*`, which will detect and report changes in devices connected to the access point on the router.
|
||||
|
||||
|
||||
@ -76,7 +76,7 @@ These attributes are available for each departing train:
|
||||
|
||||
Refer to the [API reference webpage](https://developer.transportapi.com/docs?raml=https://transportapi.com/v3/raml/transportapi.raml##request_uk_train_station_station_code_live_json) for definitions.
|
||||
|
||||
Attributes can be accessed using the [template sensor](/components/sensor.template/) as per this example:
|
||||
Attributes can be accessed using the [template sensor](/components/template) as per this example:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry for a template sensor to access the attributes of the next departing train.
|
||||
|
||||
@ -9,7 +9,7 @@ ha_release: 0.59
|
||||
---
|
||||
|
||||
|
||||
This platform allows you to detect presence by looking at devices connected to a [UniFi AP](https://www.ubnt.com/products/#unifi). This device tracker differs form [Ubiquiti Unifi WAP](/components/device_tracker.unifi/) because it doesn't require the Unifi controller software.
|
||||
This platform allows you to detect presence by looking at devices connected to a [UniFi AP](https://www.ubnt.com/products/#unifi). This device tracker differs form [Ubiquiti Unifi WAP](/components/unifi) because it doesn't require the Unifi controller software.
|
||||
|
||||
To use this device tracker in your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
|
||||
@ -133,7 +133,7 @@ media_player:
|
||||
|
||||
#### Kodi CEC-TV control
|
||||
|
||||
In this example, a [Kodi Media Player](/components/media_player.kodi/) runs in a CEC capable device (OSMC/OpenElec running in a Raspberry Pi 24/7, for example), and, with the JSON-CEC Kodi addon installed, it can turn on and off the attached TV.
|
||||
In this example, a [Kodi Media Player](/components/kodi) runs in a CEC capable device (OSMC/OpenElec running in a Raspberry Pi 24/7, for example), and, with the JSON-CEC Kodi addon installed, it can turn on and off the attached TV.
|
||||
|
||||
We store the state of the attached TV in a hidden [input boolean](/components/input_boolean/), so we can differentiate the TV being on or off, while Kodi is always 'idle', and use the universal media player to render its state with a template. We can hide the Kodi Media Player too, and only show the universal one, which now can differentiate between the 'idle' and the 'off' state (being the second when it is idle and the TV is off).
|
||||
|
||||
|
||||
@ -147,7 +147,7 @@ automation:
|
||||
|
||||
## Advanced Configuration for DSMR users
|
||||
|
||||
When using the [DSMR component](/components/sensor.dsmr/) to get data from the utility meter, each tariff (peak and off-peak) has a separate sensor. Additionally, there is a separate sensor for gas consumption. The meter switches automatically between tariffs, so an automation is not necessary in this case. But, you do have to setup a few more instances of the `utility_meter` component.
|
||||
When using the [DSMR component](/components/dsmr) to get data from the utility meter, each tariff (peak and off-peak) has a separate sensor. Additionally, there is a separate sensor for gas consumption. The meter switches automatically between tariffs, so an automation is not necessary in this case. But, you do have to setup a few more instances of the `utility_meter` component.
|
||||
|
||||
If you want to create a daily and monthly sensor for each tariff, you have to track separate sensors:
|
||||
|
||||
|
||||
@ -85,7 +85,7 @@ vacuum:
|
||||
|
||||
### Control vacuum with Harmony Hub
|
||||
|
||||
This example shows how you can use a Template Vacuum to control an IR vacuum cleaner using the [Harmony Hub Remote component](/components/remote.harmony/).
|
||||
This example shows how you can use a Template Vacuum to control an IR vacuum cleaner using the [Harmony Hub Remote component](/components/harmony).
|
||||
|
||||
```yaml
|
||||
vacuum:
|
||||
|
||||
@ -80,7 +80,7 @@ sensor:
|
||||
command: "cat /home/homeassistant/.homeassistant/.HA_VERSION"
|
||||
```
|
||||
|
||||
You might think that a [`rest` sensor](/components/sensor.rest/) could work,
|
||||
You might think that a [`rest` sensor](/components/rest) could work,
|
||||
too,
|
||||
but it will not as Home Assistant is not ready when the sensor gets initialized.
|
||||
|
||||
|
||||
@ -64,7 +64,7 @@ mode:
|
||||
|
||||
<div class='note'>
|
||||
|
||||
This platform is an alternative to the [`darksky`](/components/sensor.darksky/) sensor.
|
||||
This platform is an alternative to the [`darksky`](/components/darksky) sensor.
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
@ -64,7 +64,7 @@ trusted_networks:
|
||||
default: 149.154.160.0/20, 91.108.4.0/22
|
||||
{% endconfiguration %}
|
||||
|
||||
To get your `chat_id` and `api_key` follow the instructions [here](/components/notify.telegram). As well as authorizing the chat, if you have added your bot to a group you will also need to authorize any user that will be interacting with the webhook. When an unauthorized user tries to interact with the webhook Home Assistant will raise an error ("Incoming message is not allowed"), you can easily obtain the users id by looking in the "from" section of this error message.
|
||||
To get your `chat_id` and `api_key` follow the instructions [here](/components/telegram). As well as authorizing the chat, if you have added your bot to a group you will also need to authorize any user that will be interacting with the webhook. When an unauthorized user tries to interact with the webhook Home Assistant will raise an error ("Incoming message is not allowed"), you can easily obtain the users id by looking in the "from" section of this error message.
|
||||
|
||||
## Full configuration example
|
||||
|
||||
|
||||
@ -433,7 +433,7 @@ The above devices are confirmed to work, but others may work as well.
|
||||
|
||||
Wink Cover garage door functionality varies on the product. Home Assistant can open, close, and view state of GoControl/Linear openers. For Chamberlain MyQ-enabled openers, Home Assistant is limited to show current state (open or closed) only using this Wink cover. This restriction was imposed by Chamberlain for third party control. Wink suggests that MyQ customers should contact Chamberlain directly to inquire about expanding permissions.
|
||||
|
||||
The [MyQ Cover](/components/cover.myq/) does provide full functionality for opening and closing Chamberlain MyQ-enabled garage doors. If installed along with the Wink Component, a duplicate garage door entity may exist. In that case, the semi-functional Wink garage door entity can be hidden via customize.yaml.
|
||||
The [MyQ Cover](/components/myq) does provide full functionality for opening and closing Chamberlain MyQ-enabled garage doors. If installed along with the Wink Component, a duplicate garage door entity may exist. In that case, the semi-functional Wink garage door entity can be hidden via customize.yaml.
|
||||
|
||||
The requirement is that you have setup [Wink](/components/wink/) from above.
|
||||
|
||||
|
||||
@ -11,7 +11,7 @@ ha_iot_class: Cloud Polling
|
||||
|
||||
<div class='note warning'>
|
||||
|
||||
The Yahoo Weather API is being [retired](https://developer.yahoo.com/weather/?guccounter=1). A replacement is the [`darksky` sensor](/components/sensor.darksky/).
|
||||
The Yahoo Weather API is being [retired](https://developer.yahoo.com/weather/?guccounter=1). A replacement is the [`darksky` sensor](/components/darksky).
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
@ -4,7 +4,7 @@ description: "Basic example how to use weather conditions to set states"
|
||||
ha_category: Automation Examples
|
||||
---
|
||||
|
||||
This requires a [Dark Sky](/components/sensor.darksky/) sensor with the condition `precip_intensity` that tells if it's raining or not. You could also experiment with other attributes such as `cloud_cover`.
|
||||
This requires a [Dark Sky](/components/darksky) sensor with the condition `precip_intensity` that tells if it's raining or not. You could also experiment with other attributes such as `cloud_cover`.
|
||||
|
||||
Turn on a light in the living room when it starts raining, someone is home, and it's afternoon or later.
|
||||
|
||||
|
||||
@ -40,7 +40,7 @@ automation:
|
||||
|
||||
#### Send sun rise/sun set notifications
|
||||
|
||||
Send notifications through [PushBullet](/components/notify.pushbullet/) when the sun state is changed.
|
||||
Send notifications through [PushBullet](/components/pushbullet) when the sun state is changed.
|
||||
|
||||
```yaml
|
||||
automation:
|
||||
|
||||
@ -4,9 +4,9 @@ description: "Examples sending notification depending of the presence"
|
||||
ha_category: Automation Examples
|
||||
---
|
||||
|
||||
This will send a message when someone in your known devices list connects to your local network. In other words, when someone arrives home. It will only work if you are using the [Nmap](/components/device_tracker.nmap_tracker/) device tracker or a similar integration.
|
||||
This will send a message when someone in your known devices list connects to your local network. In other words, when someone arrives home. It will only work if you are using the [Nmap](/components/nmap_tracker) device tracker or a similar integration.
|
||||
|
||||
This example uses [Telegram](/components/notify.telegram/) to send the notification.
|
||||
This example uses [Telegram](/components/telegram) to send the notification.
|
||||
|
||||
```yaml
|
||||
notify:
|
||||
|
||||
@ -4,7 +4,7 @@ description: "Example of how to set Foscam to only have Motion Detection Recordi
|
||||
ha_category: Automation Examples
|
||||
---
|
||||
|
||||
This requires a [Foscam IP Camera](/components/camera.foscam/) camera with PTZ (Pan, Tilt, Zoom) and CGI functionality ([Source](http://www.foscam.es/descarga/Foscam-IPCamera-CGI-User-Guide-AllPlatforms-2015.11.06.pdf))
|
||||
This requires a [Foscam IP Camera](/components/foscam) camera with PTZ (Pan, Tilt, Zoom) and CGI functionality ([Source](http://www.foscam.es/descarga/Foscam-IPCamera-CGI-User-Guide-AllPlatforms-2015.11.06.pdf))
|
||||
|
||||
Foscam Cameras can be controlled by Home Assistant through a number of CGI commands.
|
||||
The following outlines examples of the switch, services, and scripts required to move between 2 preset destinations while controlling motion detection, but many other options of movement are provided in the Foscam CGI User Guide linked above.
|
||||
|
||||
@ -24,4 +24,4 @@ camera:
|
||||
<img src='/images/components/camera/generic-google-maps.png' alt='Screenshot showing Google Maps integration in Home Assistant front end.'>
|
||||
</p>
|
||||
|
||||
[generic camera platform]: /components/camera.generic/
|
||||
[generic camera platform]: /components/generic
|
||||
|
||||
@ -27,7 +27,7 @@ automation:
|
||||
message: 'There is a new Home Assistant release available.'
|
||||
```
|
||||
|
||||
You can use [templates](/topics/templating/) to include the release number of Home Assistant if you prefer. The following example sends a notification via [Pushbullet](/components/notify.pushbullet/) with the Home Assistant version in the message.
|
||||
You can use [templates](/topics/templating/) to include the release number of Home Assistant if you prefer. The following example sends a notification via [Pushbullet](/components/pushbullet) with the Home Assistant version in the message.
|
||||
|
||||
```yaml
|
||||
notify:
|
||||
|
||||
@ -6,7 +6,7 @@ ha_category: Automation Examples
|
||||
|
||||
### Restart Home Assistant
|
||||
|
||||
This configuration example is restarting Home Assistant if a [WeMo](/components/switch.wemo/) switch is not detected. An additional MQTT switch is present for stopping Home Assistant and can be triggered by [IFTTT](/components/ifttt/). The running batch script will automatically restart Home Assistant if the process isn't found anymore.
|
||||
This configuration example is restarting Home Assistant if a [WeMo](/components/wemo) switch is not detected. An additional MQTT switch is present for stopping Home Assistant and can be triggered by [IFTTT](/components/ifttt/). The running batch script will automatically restart Home Assistant if the process isn't found anymore.
|
||||
|
||||
```yaml
|
||||
mqtt:
|
||||
|
||||
@ -6,7 +6,7 @@ ha_category: Automation Examples
|
||||
|
||||
### iOS Devices
|
||||
|
||||
If you have a device running iOS (iPhone, iPad, etc), The [iCloud](/components/device_tracker.icloud/) integration is gathering various details about your device including the battery level. To display it in the Frontend use a [template sensor](/components/sensor.template/). You can also use the `battery` [sensor device class](/components/sensor/#device-class) to dynamically change the icon with the battery level.
|
||||
If you have a device running iOS (iPhone, iPad, etc), The [iCloud](/components/icloud) integration is gathering various details about your device including the battery level. To display it in the Frontend use a [template sensor](/components/template). You can also use the `battery` [sensor device class](/components/sensor/#device-class) to dynamically change the icon with the battery level.
|
||||
|
||||
{% raw %}
|
||||
```yaml
|
||||
@ -27,7 +27,7 @@ sensor:
|
||||
{% endraw %}
|
||||
|
||||
### Android and iOS Devices
|
||||
While running the [Owntracks](/components/device_tracker.owntracks/) device tracker you can retrieve the battery level.
|
||||
While running the [Owntracks](/components/owntracks) device tracker you can retrieve the battery level.
|
||||
How you achieve this depends on how you have configured your Owntracks instance.
|
||||
|
||||
#### MQTT
|
||||
|
||||
@ -54,7 +54,7 @@ Home Assistant provides several ways to authenticate. See the [Auth Providers](/
|
||||
|
||||
### Authentication failures from `127.0.0.1`
|
||||
|
||||
If you're seeing authentication failures from `127.0.0.1` and you're using the `nmap` device tracker, you should [exclude the Home Assistant IP](/components/device_tracker.nmap_tracker/#exclude) from being scanned.
|
||||
If you're seeing authentication failures from `127.0.0.1` and you're using the `nmap` device tracker, you should [exclude the Home Assistant IP](/components/nmap_tracker#exclude) from being scanned.
|
||||
|
||||
### Bearer token warnings
|
||||
|
||||
|
||||
@ -38,6 +38,6 @@ entity: weather.dark_sky
|
||||
|
||||
This card works only with platforms that define a `weather` entity.
|
||||
|
||||
E.g., it works with [Dark Sky](/components/weather.darksky/) but not [Dark Sky Sensor](/components/sensor.darksky/)
|
||||
E.g., it works with [Dark Sky](/components/weather.darksky/) but not [Dark Sky Sensor](/components/darksky)
|
||||
|
||||
</div>
|
||||
|
||||
@ -141,7 +141,7 @@ notify:
|
||||
|
||||
|
||||
__Swiss Public transport sensor__
|
||||
The swiss public transport sensor will give you the next two departure times from a given location to another one in Switzerland. See the [component page](/components/sensor.swiss_public_transport/) for more information how to set it up.
|
||||
The swiss public transport sensor will give you the next two departure times from a given location to another one in Switzerland. See the [component page](/components/swiss_public_transport) for more information how to set it up.
|
||||
|
||||
|
||||
__Transmission turtle mode switch__
|
||||
|
||||
@ -33,7 +33,7 @@ Next it was just a matter of integrating everything with Home Assistant. I was
|
||||
Status of the dryer and washer in Home Assistant
|
||||
</p>
|
||||
|
||||
Next I wrote [scripts](/components/script/) that are run whenever the washer or dryer completes a load. This is triggered by the [automation component](/getting-started/automation/). When the laundry is complete I have the lights in the house turn red and [notify me via PushBullet](/components/notify.pushbullet/). Once the laundry is taken care of another script runs that sets the lights back to normal. So far it has been very helpful and very reliable.
|
||||
Next I wrote [scripts](/components/script/) that are run whenever the washer or dryer completes a load. This is triggered by the [automation component](/getting-started/automation/). When the laundry is complete I have the lights in the house turn red and [notify me via PushBullet](/components/pushbullet). Once the laundry is taken care of another script runs that sets the lights back to normal. So far it has been very helpful and very reliable.
|
||||
|
||||
<p class='img'>
|
||||
<a href='/images/blog/2015-08-laundry-automation/moteino-and-sensors.jpg'>
|
||||
|
||||
@ -9,13 +9,13 @@ og_image: /images/supported_brands/glances.png
|
||||
---
|
||||
|
||||
<img src='/images/supported_brands/glances.png' style='border:none; box-shadow: none; float: right;' height='80' />
|
||||
Inspired by a [feature requests](https://github.com/home-assistant/home-assistant/issues/310) I started looking into the available options to do monitoring of remote hosts. The feature request is about displaying system information in a similar way than the [systemmonitor](/components/sensor.systemmonitor/) sensor does it for the local system. After a while I started to think that it would be a nice addition for a small home network where no full-blown system monitoring setup is present.
|
||||
Inspired by a [feature requests](https://github.com/home-assistant/home-assistant/issues/310) I started looking into the available options to do monitoring of remote hosts. The feature request is about displaying system information in a similar way than the [systemmonitor](/components/systemmonitor) sensor does it for the local system. After a while I started to think that it would be a nice addition for a small home network where no full-blown system monitoring setup is present.
|
||||
|
||||
<!--more-->
|
||||
|
||||
The basic problem is to get the data from the remote host. Starting with [psutil](https://pypi.python.org/pypi/psutil) that is used by the systemmonitor sensor, a possible solution is only a click away and named [Glances](https://github.com/nicolargo/glances). Glances has a nice curses-based interface and a [RESTful API](https://github.com/nicolargo/glances/wiki/The-Glances-RESTFULL-JSON-API).
|
||||
|
||||
The [Glances sensor](/components/sensor.glances/) sensor uses that API to get all needed data.
|
||||
The [Glances sensor](/components/glances) sensor uses that API to get all needed data.
|
||||
|
||||
In this post a default Fedora 22 Workstation installation is used on the host that should be monitored. In fact, it doesn't matter if the system is the local one or a remote one as long as Glances is available. With some adjustments it should work on your own systems too. The difference will be the package and the firewall management tools.
|
||||
|
||||
@ -53,7 +53,7 @@ $ curl -X GET http://IP_ADDRESS:61208/api/2/mem/used
|
||||
{"used": 203943936}
|
||||
```
|
||||
|
||||
Add the [glances sensor](/components/sensor.glances/) entry to your `configuration.yaml` file and restart Home Assistant then.
|
||||
Add the [glances sensor](/components/glances) entry to your `configuration.yaml` file and restart Home Assistant then.
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
|
||||
@ -17,7 +17,7 @@ A few weeks have past and it is time again for another release: version 0.7.4. T
|
||||
|
||||
We have added a new [getting started section][start-presence] to get up and running.
|
||||
|
||||
[platform-owntracks]: /components/device_tracker.owntracks/
|
||||
[platform-owntracks]: /components/owntracks
|
||||
[component-zone]: /components/zone/
|
||||
[zone-automation]: /getting-started/automation-trigger/#zone-trigger
|
||||
[start-presence]: /getting-started/presence-detection/
|
||||
@ -29,15 +29,15 @@ Map in Home Assistant showing two people and three zones (home, school, work)
|
||||
|
||||
Ofcourse more things happened in the last three weeks. I'm moving away from my usual long post to a short summary of highlights:
|
||||
|
||||
<a href='/components/media_player.plex/'>
|
||||
<a href='/components/plex#media-player'>
|
||||
<img src='/images/supported_brands/plex.png' style='border:none; box-shadow: none; float: right;' height='50' />
|
||||
</a>
|
||||
|
||||
- Sensor: [rest platform](/components/sensor.rest/) added ([@fabaff](https://github.com/fabaff))
|
||||
- Sensor: [rest platform](/components/rest) added ([@fabaff](https://github.com/fabaff))
|
||||
- Alarm Control Panel: [MQTT platform](/components/alarm_control_panel.mqtt/) added ([@sfam](https://github.com/sfam))
|
||||
- Media Player: [Plex platform](/components/media_player.plex/) added ([@miniconfig](https://github.com/miniconfig, [@adrienbrault](https://github.com/adrienbrault))
|
||||
- Media Player: [Plex platform](/components/plex#media-player) added ([@miniconfig](https://github.com/miniconfig, [@adrienbrault](https://github.com/adrienbrault))
|
||||
- Dev Tools: services can now show description of fields ([@balloob](https://github.com/balloob))
|
||||
- MQTT: Support for certificates and improved error reporting ([@balloob](https://github.com/balloob))
|
||||
- Light: [limitlessled platform](/components/light.limitlessled/) extended with white light support ([@auchter](https://github.com/auchter))
|
||||
- Light: [limitlessled platform](/components/limitlessled) extended with white light support ([@auchter](https://github.com/auchter))
|
||||
- Fuzzy matching for scenes ([@pavoni](https://github.com/pavoni))
|
||||
- Scene support for media player ([@maddox](https://github.com/maddox))
|
||||
|
||||
@ -17,10 +17,10 @@ This release also includes some new platforms (because they keep coming!):
|
||||
|
||||
<img src='/images/supported_brands/blinkstick.png' style='border:none; box-shadow: none; float: right;' height='50' /><img src='/images/supported_brands/rfxtrx.png' style='border:none; box-shadow: none; float: right; clear: right;' height='50' /><img src='/images/supported_brands/telegram.png' style='border:none; box-shadow: none; float: right; clear: right;' height='50' />
|
||||
|
||||
- Light: [blinkstick platform](/components/light.blinksticklight/) added ([@alanbowman](https://github.com/alanbowman))
|
||||
- Device Tracker: [SNMP platform](/components/device_tracker.snmp/) added ([@tomduijf](https://github.com/tomduijf))
|
||||
- Light: [blinkstick platform](/components/blinksticklight) added ([@alanbowman](https://github.com/alanbowman))
|
||||
- Device Tracker: [SNMP platform](/components/snmp) added ([@tomduijf](https://github.com/tomduijf))
|
||||
- Light: [rfxtrx platform](/components/light.rfxtrx/) added ([@badele](https://github.com/badele))
|
||||
- Switch: [rfxtrx platform](/components/switch.rfxtrx/) added ([@badele](https://github.com/badele))
|
||||
- Notify: [telegram platform](/components/notify.telegram/) added ([@fabaff](https://github.com/fabaff))
|
||||
- Notify: [telegram platform](/components/telegram) added ([@fabaff](https://github.com/fabaff))
|
||||
|
||||
Also, the media player was extended by [@maddox](https://github.com/maddox) to support the play media command. This has been implemented for the [iTunes platform](/components/media_player.itunes/).
|
||||
Also, the media player was extended by [@maddox](https://github.com/maddox) to support the play media command. This has been implemented for the [iTunes platform](/components/itunes).
|
||||
|
||||
@ -14,22 +14,22 @@ After two weeks of hard work I'm proud to announce the release of Home Assistant
|
||||
|
||||
<img src='/images/supported_brands/radiotherm.png' style='border:none; box-shadow: none; float: right; margin-bottom: 16px;' height='50' /><img src='/images/supported_brands/firetv.png' style='border:none; box-shadow: none; float: right; margin-bottom: 16px; clear: right;' height='50' /><img src='/images/supported_brands/locative.png' style='border:none; box-shadow: none; float: right; margin-bottom: 16px; clear: right;' height='50' />
|
||||
|
||||
- Device tracker: Newer [TP-Link routers](/components/device_tracker.tplink/) now supported ([@mKeRix](https://github.com/mKeRix))
|
||||
- Alarm Control Panel: [Manual alarm](/components/alarm_control_panel.manual/) added ([@sfam](https://github.com/sfam))
|
||||
- Device tracker: Newer [TP-Link routers](/components/tplink) now supported ([@mKeRix](https://github.com/mKeRix))
|
||||
- Alarm Control Panel: [Manual alarm](/components/manual) added ([@sfam](https://github.com/sfam))
|
||||
- Thermostat: [Radiotherm](/components/radiotherm/) now supported ([@toddeye](https://github.com/toddeye))
|
||||
- Media Player: [Amazon FireTV](/components/media_player.firetv/) now supported ([@happyleavesaoc](https://github.com/happyleavesaoc))
|
||||
- Device Tracker: [Geofancy](/components/device_tracker.locative/) now supported (@wind-rider)
|
||||
- Media Player: [Amazon FireTV](/components/androidtv) now supported ([@happyleavesaoc](https://github.com/happyleavesaoc))
|
||||
- Device Tracker: [Geofancy](/components/locative) now supported (@wind-rider)
|
||||
- New component [Shell Command](/components/shell_command/) can expose shell commands as services ([@balloob](https://github.com/balloob))
|
||||
- [Scripts](/components/script/) can now be customized using `customize` key in `configuration.yaml` ([@balloob](https://github.com/balloob))
|
||||
- Light: [Hyperion](/components/light.hyperion/) now supported (@MakeMeASandwich)
|
||||
- Sensor: [aRest](/components/sensor.arest/) can now also read out pins ([@balloob](https://github.com/balloob))
|
||||
- Sensor: [Forecast.io](/components/sensor.forecast/) now supports specifying units in `configuration.yaml` ([@balloob](https://github.com/balloob))
|
||||
- Light: [Hyperion](/components/hyperion) now supported (@MakeMeASandwich)
|
||||
- Sensor: [aRest](/components/arest#sensor) can now also read out pins ([@balloob](https://github.com/balloob))
|
||||
- Sensor: [Forecast.io](/components/darksky) now supports specifying units in `configuration.yaml` ([@balloob](https://github.com/balloob))
|
||||
- Thermostat: [Heat Control](/components/thermostat.heat_control/) has been completely rewritten ([@balloob](https://github.com/balloob))
|
||||
- Switch: [Rest](/components/switch.rest/) now supported ([@bachp](https://github.com/bachp))
|
||||
- Media Player: [Plex](/components/media_player.plex/) can now be auto discovered and configure itself ([@tomduijf](https://github.com/tomduijf))
|
||||
- Media Player: [Plex](/components/plex#media-player) can now be auto discovered and configure itself ([@tomduijf](https://github.com/tomduijf))
|
||||
- [Downloader](/components/downloader/) will now treat relative paths based on config dir ([@tomduijf](https://github.com/tomduijf))
|
||||
- Line Charts will use interpolation for sensor data and show current and target temperature for thermostats ([@balloob](https://github.com/balloob))
|
||||
- Device Tracker: [OpenWRT via ubus](/components/device_tracker.ubus/) now supported ([@krzynio](https://github.com/krzynio))
|
||||
- Device Tracker: [OpenWRT via ubus](/components/ubus) now supported ([@krzynio](https://github.com/krzynio))
|
||||
|
||||
<!--more-->
|
||||
|
||||
|
||||
@ -27,15 +27,15 @@ homeassistant:
|
||||
<img src='/images/supported_brands/honeywell.png' style='clear: right; border:none; box-shadow: none; float: right; margin-bottom: 16px;' height='50' /><img src='/images/supported_brands/orvibo.png' style='clear: right; border:none; box-shadow: none; float: right; margin-bottom: 16px;' height='50' /><img src='/images/supported_brands/pushetta.png' style='clear: right; border:none; box-shadow: none; float: right; margin-bottom: 16px;' height='50' />
|
||||
|
||||
* Thermostat: [Honeywell](/components/honeywell/) now supported ([@sander76])
|
||||
* Switch: [Orvibo](/components/switch.orvibo/) now supported ([@happyleavesaoc])
|
||||
* Camera: [mjpeg camera's](/components/camera.mjpeg/) now supported ([@ryanturner])
|
||||
* Notify: [Pushetta](/components/notify.pushetta/) now supported ([@fabaff])
|
||||
* Switch: [Orvibo](/components/orvibo) now supported ([@happyleavesaoc])
|
||||
* Camera: [mjpeg camera's](/components/mjpeg) now supported ([@ryanturner])
|
||||
* Notify: [Pushetta](/components/pushetta) now supported ([@fabaff])
|
||||
* Light: [MQTT](/components/light.mqtt/) now supported ([@hexxter])
|
||||
* Light: [Z-Wave](/components/zwave/) now supported ([@leoc])
|
||||
* Switch: [Z-Wave](/components/zwave/) now supported ([@leoc])
|
||||
* New component [logger](/components/logger/) allows filtering logged data ([@badele])
|
||||
* New component [updater](/components/updater/) will notify users if an update for Home Assistant is available ([@rmkraus])
|
||||
* Notify: [PushBullet](/components/notify.pushbullet/) now allows targeting contacts/channels/specific devices ([@tomduijf])
|
||||
* Notify: [PushBullet](/components/pushbullet) now allows targeting contacts/channels/specific devices ([@tomduijf])
|
||||
* Light: Allow controlling color temperature ([@tomduijf])
|
||||
* Frontend: about page added ([@balloob])
|
||||
* Switch RGB as the color unit used in light component ([@balloob])
|
||||
|
||||
@ -19,9 +19,9 @@ Of course most users are running with the [automation](/getting-started/automati
|
||||
|
||||
The [Alarm control panels](/components/alarm_control_panel/) and the [camera component](/components/camera/) are both used by around one third of the participants of the survey. It's safe to say that they cover a niche, but they will gain momentum when people discover how they can build alarm systems with Home Assistant.
|
||||
|
||||
[Philips Hue](/components/light.hue/) is the "winner" in the light category closely followed by [MQTT lights](components/light.mqtt/). [Google Cast](/components/media_player.cast/) and [ Plex](/components/media_player.plex/) are the top media player platforms. [Pushbullet](/components/notify.pushbullet/) is by far the most-used [notification platform](/components/notify/). If you followed the recent efforts to improve this platform it's comprehensible.
|
||||
[Philips Hue](/components/hue) is the "winner" in the light category closely followed by [MQTT lights](components/light.mqtt/). [Google Cast](/components/cast) and [ Plex](/components/plex#media-player) are the top media player platforms. [Pushbullet](/components/pushbullet) is by far the most-used [notification platform](/components/notify/). If you followed the recent efforts to improve this platform it's comprehensible.
|
||||
|
||||
It's interesting to see that most of the sensor, switch, and thermostat platforms are used. A lot of people seem to be interested in the weather data provided by the [Forecast sensor](/components/sensor.forecast/). The MQTT sensors and switches are deployed in almost 50% of all Home Assistant setups.
|
||||
It's interesting to see that most of the sensor, switch, and thermostat platforms are used. A lot of people seem to be interested in the weather data provided by the [Forecast sensor](/components/darksky). The MQTT sensors and switches are deployed in almost 50% of all Home Assistant setups.
|
||||
|
||||
|
||||
<p class='img'>
|
||||
|
||||
@ -25,9 +25,9 @@ It's been a few weeks but we managed to polish a nice new release of Home Assist
|
||||
To update, run `pip3 install --upgrade homeassistant`.
|
||||
|
||||
[lock component]: /components/lock/
|
||||
[lock.wink]: /components/lock.wink/
|
||||
[lock.wink]: /components/wink#lock
|
||||
[binary sensor component]: /components/binary_sensor/
|
||||
[binary_sensor.arest]: /components/binary_sensor.arest/
|
||||
[binary_sensor.arest]: /components/arest#binary-sensor
|
||||
[binary_sensor.mqtt]: /components/binary_sensor.mqtt/
|
||||
[InfluxDB component]: /components/influxdb/
|
||||
[Ecobee]: /components/ecobee/#thermostat
|
||||
|
||||
@ -30,17 +30,17 @@ Alrighty, it's time for Home Assistant 0.10. A lot amazing things have changed a
|
||||
- Binary sensor: [REST] platform added ([@fabaff])
|
||||
- Sensor: [Torque (OBD2)] platform added ([@happyleavesaoc])
|
||||
|
||||
[iCloud]: /components/device_tracker.icloud/
|
||||
[Twitch]: /components/sensor.twitch/
|
||||
[iCloud]: /components/icloud
|
||||
[Twitch]: /components/twitch
|
||||
[Template]: /topics/templating/
|
||||
[Heatmiser]: /components/heatmiser/
|
||||
[Dweet.io]: /components/sensor.dweet/
|
||||
[Dweet.io]: /components/dweet#sensor
|
||||
[Alexa/Amazon echo]: /components/alexa/
|
||||
[FritzBox]: /components/device_tracker.fritz/
|
||||
[Wink]: /components/sensor.wink/
|
||||
[ELIQ Online]: /components/sensor.eliqonline/
|
||||
[FritzBox]: /components/fritz
|
||||
[Wink]: /components/wink#sensor
|
||||
[ELIQ Online]: /components/eliqonline
|
||||
[REST]: /components/binary_sensor.rest/
|
||||
[Torque (OBD2)]: /components/sensor.torque/
|
||||
[Torque (OBD2)]: /components/torque
|
||||
[@andylockran]: https://github.com/andylockran
|
||||
[@balloob]: https://github.com/balloob
|
||||
[@caiuspb]: https://github.com/caiuspb
|
||||
@ -81,9 +81,9 @@ Affected components and platforms:
|
||||
- binary_sensor: [MQTT][binary_sensor.mqtt]
|
||||
- automation: [numeric_state][automation-numeric-state]
|
||||
|
||||
[sensor.arest]: /components/sensor.arest/
|
||||
[sensor.arest]: /components/arest#sensor
|
||||
[sensor.command]: /components/sensor.command_sensor/
|
||||
[sensor.rest]: /components/sensor.rest/
|
||||
[sensor.rest]: /components/rest
|
||||
[sensor.mqtt]: /components/sensor.mqtt/
|
||||
[switch.mqtt]: /components/switch.mqtt/
|
||||
[light.mqtt]: /components/light.mqtt/
|
||||
|
||||
@ -38,25 +38,25 @@ First release of 2016 and we are on 🔥! The [main repository][github-ha] has p
|
||||
- Support calling services via [Amazon Echo] ([@balloob])
|
||||
|
||||
[MySensors]: /components/mysensors/
|
||||
[YR]: /components/sensor.yr/
|
||||
[Locative]: /components/device_tracker.locative/
|
||||
[YR]: /components/yr
|
||||
[Locative]: /components/locative
|
||||
[sun condition]: /getting-started/automation-condition/#sun-condition
|
||||
[command_switch]: /components/switch.command_switch/
|
||||
[wemo]: /components/switch.wemo/
|
||||
[wemo]: /components/wemo
|
||||
[Telldus Live]: /components/tellduslive/
|
||||
[Vera]: /components/vera/
|
||||
[template helper method]: /topics/templating/#home-assistant-template-extensions
|
||||
[OwnTracks]: /components/device_tracker.owntracks/
|
||||
[Philips Hue]: /components/light.hue/
|
||||
[Free Mobile]: /components/notify.free_mobile/
|
||||
[OwnTracks]: /components/owntracks
|
||||
[Philips Hue]: /components/hue
|
||||
[Free Mobile]: /components/free_mobile
|
||||
[MQTT Eventstream]: /components/mqtt_eventstream/
|
||||
[Cast]: /components/media_player.cast/
|
||||
[Universal media player]: /components/media_player.universal/
|
||||
[Netatmo]: /components/sensor.netatmo/
|
||||
[Alarm.com]: /components/alarm_control_panel.alarmdotcom/
|
||||
[Cast]: /components/cast
|
||||
[Universal media player]: /components/universal
|
||||
[Netatmo]: /components/netatmo#sensor
|
||||
[Alarm.com]: /components/alarmdotcom
|
||||
[Proliphix]: /components/proliphix/
|
||||
[rpi-bs]: /components/binary_sensor.rpi_gpio/
|
||||
[rpi-s]: /components/switch.rpi_gpio/
|
||||
[rpi-bs]: /components/rpi_gpio#binary-sensor
|
||||
[rpi-s]: /components/rpi_gpio#switch
|
||||
[input_boolean]: /components/input_boolean/
|
||||
[MySensors sensor platform]: /components/sensor.mysensors/
|
||||
[Amazon Echo]: /components/alexa/
|
||||
|
||||
@ -45,16 +45,16 @@ Example of the new views in the frontend. <a href='/components/group/'>Learn mor
|
||||
[the demo]: /demo/
|
||||
[command sensor]: /components/binary_sensor.command/
|
||||
[Insteon hub]: /components/insteon/
|
||||
[LIFX]: /components/light.lifx/
|
||||
[LIFX]: /components/lifx
|
||||
[Nest]: /components/nest/
|
||||
[onewire]: /components/sensor.onewire/
|
||||
[OwnTracks]: /components/device_tracker.owntracks/
|
||||
[onewire]: /components/onewire
|
||||
[OwnTracks]: /components/owntracks
|
||||
[Rfxtrx]: /components/light.rfxtrx/
|
||||
[Statsd]: /components/statsd/
|
||||
[Template]: /components/sensor.template/
|
||||
[Template]: /components/template
|
||||
[Thermostat]: /components/climate/
|
||||
[time automation]: /getting-started/automation-trigger/#time-trigger
|
||||
[Twitter]: /components/notify.twitter/
|
||||
[Twitter]: /components/twitter
|
||||
[Wink]: /components/wink/
|
||||
[Zigbee]: /components/zigbee/
|
||||
[group]: /components/group/
|
||||
|
||||
@ -93,18 +93,18 @@ Not only did we gain a lot of test coverage, we also attracted a lot of new deve
|
||||
[graphite]: /components/graphite/
|
||||
[SCSGate]: /components/scsgate/
|
||||
[weblink]: /components/weblink/
|
||||
[mfi.switch]: /components/switch.mfi/
|
||||
[mfi.sensor]: /components/sensor.mfi/
|
||||
[nx584]: /components/alarm_control_panel.nx584/
|
||||
[MJPEG]: /components/camera.mjpeg/
|
||||
[unifi]: /components/camera.uvc/
|
||||
[Aruba]: /components/device_tracker.aruba/
|
||||
[mfi.switch]: /components/mfi#switch
|
||||
[mfi.sensor]: /components/mfi#sensor
|
||||
[nx584]: /components/nx584
|
||||
[MJPEG]: /components/mjpeg
|
||||
[unifi]: /components/uvc
|
||||
[Aruba]: /components/aruba
|
||||
[History]: /components/history/
|
||||
[MySensors]: /components/light.mysensors/
|
||||
[Verisure]: /components/lock.verisure/
|
||||
[Speedtest.net]: /components/sensor.speedtest/
|
||||
[Samsung TV]: /components/media_player.samsungtv/
|
||||
[Snapcast]: /components/media_player.snapcast/
|
||||
[Verisure]: /components/verisure
|
||||
[Speedtest.net]: /components/speedtestdotnet
|
||||
[Samsung TV]: /components/samsungtv
|
||||
[Snapcast]: /components/snapcast
|
||||
[mqtt-publish]: /components/mqtt/#publish-service
|
||||
[REST]: /components/notify.rest/
|
||||
[template]: /components/switch.template/
|
||||
|
||||
@ -135,5 +135,5 @@ weblink:
|
||||
```
|
||||
|
||||
[weblink]: /components/weblink/
|
||||
[snapcast]: /components/media_player.snapcast/
|
||||
[mpd]: /components/media_player.mpd/
|
||||
[snapcast]: /components/snapcast
|
||||
[mpd]: /components/mpd
|
||||
|
||||
@ -50,29 +50,29 @@ It's been another two weeks which means it's time for release: 0.14!
|
||||
|
||||
[sensor.rfxtrx]: /components/sensor.rfxtrx/
|
||||
[notify.command_line]: /components/notify.command_line/
|
||||
[Verisure]: /components/sensor.verisure/
|
||||
[binary_sensor.tcp]: /components/binary_sensor.tcp/
|
||||
[sensor.tcp]: /components/sensor.tcp/
|
||||
[Neurio energy sensor]: /components/sensor.neurio_energy/
|
||||
[nx584]: /components/binary_sensor.nx584/
|
||||
[Verisure]: /components/verisure
|
||||
[binary_sensor.tcp]: /components/tcp#binary-sensor
|
||||
[sensor.tcp]: /components/tcp#sensor
|
||||
[Neurio energy sensor]: /components/neurio_energy
|
||||
[nx584]: /components/nx584#binary-sensor
|
||||
[triggers]: /getting-started/automation-trigger/#state-trigger
|
||||
[conditions]: /getting-started/automation-condition/#state-condition
|
||||
[Nest]: /components/sensor.nest/
|
||||
[Ubiquiti Unifi]: /components/device_tracker.unifi/
|
||||
[Nest]: /components/nest#sensor
|
||||
[Ubiquiti Unifi]: /components/unifi
|
||||
[MySensors]: /components/binary_sensor.mysensors/
|
||||
[Bloomsky]: /components/binary_sensor.bloomsky/
|
||||
[Z-Wave]: /components/binary_sensor.zwave/
|
||||
[D-Link smart plugs]: /components/switch.dlink/
|
||||
[Wemo]: /components/light.wemo/
|
||||
[Bloomsky]: /components/bloomsky#binary-sensor
|
||||
[Z-Wave]: /components/zwave
|
||||
[D-Link smart plugs]: /components/dlink
|
||||
[Wemo]: /components/wemo
|
||||
[rollershutter.command_line]: /components/rollershutter.command_line/
|
||||
[Steam]: /components/sensor.steam_online/
|
||||
[Wink]: /components/binary_sensor.wink/
|
||||
[Steam]: /components/steam_online
|
||||
[Wink]: /components/wink#binary-sensor
|
||||
[the cookbook]: /cookbook/python_component_simple_alarm/
|
||||
[script]: /components/script/
|
||||
[Wemo component]: /components/wemo/
|
||||
[switch.cmd]: /components/switch.command_line/
|
||||
[sensor.cmd]: /components/sensor.command_line/
|
||||
[binary_sensor.cmd]: /components/binary_sensor.command_line/
|
||||
[binary_sensor.cmd]: /components/command_line
|
||||
|
||||
[@stefan-jonasson]: https://github.com/stefan-jonasson
|
||||
[@turbokongen]: https://github.com/turbokongen
|
||||
|
||||
@ -50,10 +50,10 @@ automation:
|
||||
player state attributes. This change affects automations, scripts and scenes.
|
||||
|
||||
[services]: /docs/scripts/service-calls/#use-templates-to-decide-which-service-to-call
|
||||
[Hunter Douglas Powerview]: /components/scene.hunterdouglas_powerview/
|
||||
[Hunter Douglas Powerview]: /components/hunterdouglas_powerview
|
||||
[MQTT]: /components/lock.mqtt/
|
||||
[OwnTracks]: /components/device_tracker.owntracks/
|
||||
[Wemo Motion]: /components/binary_sensor.wemo/
|
||||
[OwnTracks]: /components/owntracks
|
||||
[Wemo Motion]: /components/wemo
|
||||
[@fabaff]: https://github.com/fabaff
|
||||
[@partofthething]: https://github.com/partofthething
|
||||
[@persandstrom]: https://github.com/persandstrom
|
||||
|
||||
@ -50,19 +50,19 @@ Rock on.
|
||||
[@srcLurker]: https://github.com/srcLurker
|
||||
[@stefan-jonasson]: https://github.com/stefan-jonasson
|
||||
[embedded server]: /components/mqtt/#use-the-embedded-broker
|
||||
[Arduino]: /components/switch.arduino/
|
||||
[Arduino]: /components/arduino#switch
|
||||
[Discovery]: /components/discovery/
|
||||
[Growl (GNTP)]: /components/notify.gntp/
|
||||
[Hue]: /components/light.hue/
|
||||
[input_slider]: /components/input_slider/
|
||||
[MessageBird]: /components/notify.message_bird/
|
||||
[OwnTracks]: /components/device_tracker.owntracks/
|
||||
[PulseAudio loopback]: /components/switch.pulseaudio_loopback/
|
||||
[Growl (GNTP)]: /components/gntp
|
||||
[Hue]: /components/hue
|
||||
[input_slider]: /components/input_number
|
||||
[MessageBird]: /components/message_bird
|
||||
[OwnTracks]: /components/owntracks
|
||||
[PulseAudio loopback]: /components/pulseaudio_loopback
|
||||
[Tellstick]: /components/tellstick/
|
||||
[Vera]: /components/vera/
|
||||
[Wake on LAN]: /components/switch.wake_on_lan/
|
||||
[Wake on LAN]: /components/wake_on_lan#switch
|
||||
[Z-Wave]: /components/zwave/#services
|
||||
[Yamaha receivers]: /components/media_player.yamaha/
|
||||
[Yamaha receivers]: /components/yamaha
|
||||
|
||||
### Breaking changes
|
||||
- Automation: support for old deprecated config has been removed
|
||||
|
||||
@ -41,12 +41,12 @@ Another big thing is the addition of GTFS support. You probably don't know it, b
|
||||
[@robbiet480]: https://github.com/robbiet480/
|
||||
[@srcLurker]: https://github.com/srcLurker/
|
||||
[@turbokongen]: https://github.com/turbokongen/
|
||||
[GTFS]: /components/sensor.gtfs/
|
||||
[Loop Energy]: /components/sensor.loop_energy/
|
||||
[NZBGet]: /components/sensor.nzbget/
|
||||
[Onkyo receiver]: /components/media_player.onkyo/
|
||||
[Panasonic Viera TV]: /components/media_player.panasonic_viera/
|
||||
[Raspberry PI]: /components/camera.rpi_camera/
|
||||
[GTFS]: /components/gtfs
|
||||
[Loop Energy]: /components/loopenergy
|
||||
[NZBGet]: /components/nzbget
|
||||
[Onkyo receiver]: /components/onkyo
|
||||
[Panasonic Viera TV]: /components/panasonic_viera
|
||||
[Raspberry PI]: /components/rpi_camera
|
||||
[Z-Wave]: /components/zwave/#climate
|
||||
|
||||
### Breaking changes
|
||||
|
||||
@ -57,21 +57,21 @@ Since the last release we have moved all Home Assistant source code etc into its
|
||||
[@TheRealLink]: https://github.com/TheRealLink/
|
||||
[@Turbokongen]: https://github.com/Turbokongen/
|
||||
[@vmulpuru]: https://github.com/vmulpuru/
|
||||
[Bluetooth tracking platform]: /components/device_tracker.bluetooth_tracker/
|
||||
[Bluetooth tracking platform]: /components/bluetooth_tracker
|
||||
[EQ3 Bluetooth Smart Thermostats]: /components/eq3btsmart/
|
||||
[mysensors]: /components/mysensors/
|
||||
[Feedreader]: /components/feedreader/
|
||||
[Homematic platform]: /components/homematic/
|
||||
[media_player.lg]: /components/media_player.webostv/
|
||||
[notify.lg]: /components/notify.webostv/
|
||||
[MPD]: /components/media_player.mpd/
|
||||
[media_player.lg]: /components/webostv#media-player
|
||||
[notify.lg]: /components/webostv
|
||||
[MPD]: /components/mpd
|
||||
[MQTT]: /components/cover.mqtt/
|
||||
[Plex]: /components/media_player.plex/
|
||||
[Sonos]: /components/media_player.sonos/
|
||||
[sensor.Thinkingcleaner]: /components/sensor.thinkingcleaner/
|
||||
[switch.Thinkingcleaner]: /components/switch.thinkingcleaner/
|
||||
[Plex]: /components/plex#media-player
|
||||
[Sonos]: /components/sonos
|
||||
[sensor.Thinkingcleaner]: /components/thinkingcleaner#sensor
|
||||
[switch.Thinkingcleaner]: /components/thinkingcleaner#switch
|
||||
[upnp]: /components/upnp/
|
||||
[Wink]: /components/light.wink/
|
||||
[Wink]: /components/wink#light
|
||||
[Zeroconf]: /components/zeroconf/
|
||||
|
||||
### Breaking changes
|
||||
|
||||
@ -27,7 +27,7 @@ Luckily, OwnTracks supports iBeacons so I could use them to make presence detect
|
||||
To do this you first need to set up [MQTT] and [OwnTracks] in Home Assistant - and make sure that HA can track your phone.
|
||||
|
||||
[MQTT]: /components/mqtt/#picking-a-broker
|
||||
[OwnTracks]: /components/device_tracker.owntracks/
|
||||
[OwnTracks]: /components/owntracks
|
||||
|
||||
You then have to (A) tell Home Assistant where the beacon is located and (B) tell OwnTracks to recognize the beacon.
|
||||
|
||||
@ -118,7 +118,7 @@ Presence tracking sounds easy - and it's an important part of Home Automation. T
|
||||
|
||||
You can find out more about configuring the OwnTracks application and beacons [here](http://owntracks.org/booklet/features/beacons/)
|
||||
|
||||
There is information about configuring Homeassistant to use beacons [here](/components/device_tracker.owntracks/)
|
||||
There is information about configuring Homeassistant to use beacons [here](/components/owntracks)
|
||||
|
||||
#### Connections and disconnecting
|
||||
|
||||
|
||||
@ -82,23 +82,23 @@ light:
|
||||
[con-and]: /getting-started/scripts-conditions/#and-condition
|
||||
[con-or]: /getting-started/scripts-conditions/#or-condition
|
||||
[entity namespace]: /topics/platform_options/#entity-namespace
|
||||
[rpi-rf]: /components/switch.rpi_rf/
|
||||
[Forecast.io]: /components/sensor.forecast/
|
||||
[Snapcast]: /components/media_player.snapcast/
|
||||
[rpi-rf]: /components/rpi_rf
|
||||
[Forecast.io]: /components/darksky
|
||||
[Snapcast]: /components/snapcast
|
||||
[Command line sensor]: /components/sensor.command_line/
|
||||
[allow client key authentication]: /components/mqtt/
|
||||
[Pioneer AVR]: /components/media_player.pioneer/
|
||||
[Acer Projectors]: /components/switch.acer_projector/
|
||||
[Pioneer AVR]: /components/pioneer
|
||||
[Acer Projectors]: /components/acer_projector
|
||||
[HVAC component]: /components/climate/
|
||||
[OctoPrint]: /components/octoprint/
|
||||
[Z-Wave]: /components/zwave/
|
||||
[lock]: /components/lock/
|
||||
[lock.zwave]: /components/lock.zwave/
|
||||
[lock.zwave]: /components/zwave#lock
|
||||
[Dweet component]: /components/dweet/
|
||||
[`as_timestamp`]: /topics/templating/#home-assistant-template-extensions
|
||||
[Google Maps travel time]: /components/sensor.google_travel_time/
|
||||
[Google Maps travel time]: /components/google_travel_time
|
||||
[CORS headers]: /components/http/
|
||||
[Fitbit]: /components/sensor.fitbit/
|
||||
[Fitbit]: /components/fitbit
|
||||
[@balloob]: https://github.com/balloob/
|
||||
[@milaq]: https://github.com/milaq/
|
||||
[@danieljkemp]: https://github.com/danieljkemp/
|
||||
|
||||
@ -66,17 +66,17 @@ device_tracker:
|
||||
[`!include_dir_merge_list`]: /topics/splitting_configuration/#advanced-usage
|
||||
[`!include_dir_merge_named`]: /topics/splitting_configuration/#advanced-usage
|
||||
[`relative_time`]: /topics/templating/#home-assistant-template-extensions
|
||||
[Asus WRT]: /components/device_tracker.asuswrt/
|
||||
[Ecobee thermostats]: /components/notify.ecobee/
|
||||
[Google Play Music Desktop Player]: /components/media_player.gpmdp/
|
||||
[LG Netcast TVs]: /components/media_player.lg_netcast/
|
||||
[Asus WRT]: /components/asuswrt
|
||||
[Ecobee thermostats]: /components/ecobee
|
||||
[Google Play Music Desktop Player]: /components/gpmdp
|
||||
[LG Netcast TVs]: /components/lg_netcast
|
||||
[Logentries]: /components/logentries/
|
||||
[mold indicator]: /components/mold_indicator/
|
||||
[Nest Protect]: /components/sensor.nest/
|
||||
[Nest Protect]: /components/nest#sensor
|
||||
[purge days option]: /components/recorder/
|
||||
[Roku]: /components/media_player.roku/
|
||||
[Roku]: /components/roku#media-player
|
||||
[SNS]: /components/notify.aws_sns/
|
||||
[SQS]: /components/notify.aws_sqs/
|
||||
[supervisord]: /components/sensor.supervisord/
|
||||
[Twilio SMS]: /components/notify.twilio_sms/
|
||||
[Last.fm]: /components/sensor.lastfm/
|
||||
[supervisord]: /components/supervisord
|
||||
[Twilio SMS]: /components/twilio_sms
|
||||
[Last.fm]: /components/lastfm
|
||||
|
||||
@ -81,16 +81,16 @@ We released two hotfixes to address some issues that couldn't wait till the next
|
||||
[@rubund]: https://github.com/rubund
|
||||
[@shaftoe]: https://github.com/shaftoe
|
||||
[@wkonkel]: https://github.com/wkonkel
|
||||
[DTE Energy Bridge]: /components/sensor.dte_energy_bridge/
|
||||
[en-lights]: /components/light.enocean/
|
||||
[en-sensors]: /components/sensor.enocean/
|
||||
[en-switches]: /components/switch.enocean/
|
||||
[DTE Energy Bridge]: /components/dte_energy_bridge
|
||||
[en-lights]: /components/enocean#light
|
||||
[en-sensors]: /components/enocean#sensor
|
||||
[en-switches]: /components/enocean#switch
|
||||
[Feedreader]: /components/feedreader/
|
||||
[Flux like switch platform]: /components/switch.flux/
|
||||
[Flux like switch platform]: /components/flux
|
||||
[Insteon Hub]: /components/insteon/
|
||||
[Kodi]: /components/media_player.kodi/
|
||||
[Kodi]: /components/kodi
|
||||
[LIRC component]: /components/lirc/
|
||||
[Osram Lightify]: /components/light.osramlightify/
|
||||
[Osram Lightify]: /components/osramlightify
|
||||
[RFXTRX]: /components/rfxtrx/
|
||||
[Template switches]: /components/switch.template/
|
||||
[time condition]: /getting-started/scripts-conditions/#time-condition
|
||||
|
||||
@ -73,20 +73,20 @@ netatmo:
|
||||
[@philk]: https://github.com/philk/
|
||||
[@wind-rider]: https://github.com/wind/
|
||||
[@fabaff]: https://github.com/fabaff/
|
||||
[AsusWRT]: /components/device_tracker.asuswrt/
|
||||
[BT Home Hub 5]: /components/device_tracker.bt_home_hub_5/
|
||||
[Cast]: /components/media_player.cast/
|
||||
[AsusWRT]: /components/asuswrt
|
||||
[BT Home Hub 5]: /components/bt_home_hub_5
|
||||
[Cast]: /components/cast
|
||||
[IR switch device]: /components/mysensors/
|
||||
[local file]: /components/camera.local_file/
|
||||
[local file]: /components/local_file
|
||||
[Netatmo]: /components/netatmo/
|
||||
[Pandora]: /components/media_player.pandora/
|
||||
[Pandora]: /components/pandora
|
||||
[shell command]: /components/shell_command/
|
||||
[Sonos]: /components/media_player.sonos/
|
||||
[Sonos]: /components/sonos
|
||||
[Wink]: /components/wink/#cover
|
||||
[alexa]: /components/alexa/#working-with-scenes
|
||||
[Plex sensor]: /components/sensor.plex/
|
||||
[Plex sensor]: /components/plex#sensor
|
||||
[Swagger.yaml format]: https://github.com/home-assistant/home-assistant/blob/dev/docs/swagger.yaml
|
||||
[All-in-One installer]: /getting-started/installation-raspberry-pi-all-in-one/
|
||||
[standalone Raspberry Pi installation guide]: /getting-started/installation-raspberry-pi/
|
||||
[Voltage sensor]: /components/bloomsky/#sensor
|
||||
[SNMP]: /components/sensor.snmp/
|
||||
[SNMP]: /components/snmp#sensor
|
||||
|
||||
@ -10,7 +10,7 @@ og_image: /images/blog/2016-06-cranberry/social.png
|
||||
---
|
||||
|
||||
<img src='/images/blog/2016-06-cranberry/motion.png' style='clear: right; border:none; box-shadow: none; float: right; margin-bottom: 12px;' width='200' />
|
||||
In the past month I was thinking about ways to integrate USB webcams into Home Assistant again. The main reason was that this would give those devices a second life and enable one to benefit from low-cost video surveillance. There are a couple of options available like [pygame](http://www.pygame.org/hifi.html) or [SimpleCV](http://www.simplecv.org/) but I never finished something. With the [Local File camera platform](/components/camera.local_file/) by [Landrash](https://github.com/Landrash) and [motion](http://lavrsen.dk/foswiki/bin/view/Motion/WebHome) you could integrate a local USB webcam with a few very easy steps.
|
||||
In the past month I was thinking about ways to integrate USB webcams into Home Assistant again. The main reason was that this would give those devices a second life and enable one to benefit from low-cost video surveillance. There are a couple of options available like [pygame](http://www.pygame.org/hifi.html) or [SimpleCV](http://www.simplecv.org/) but I never finished something. With the [Local File camera platform](/components/local_file) by [Landrash](https://github.com/Landrash) and [motion](http://lavrsen.dk/foswiki/bin/view/Motion/WebHome) you could integrate a local USB webcam with a few very easy steps.
|
||||
|
||||
In this blog post I am using a Fedora 24 (will most likely work on other distributions too) installation with Home Assistant 0.22.1 on a Foxconn nT-330i with an old [Logitech QuickCam Orbit AF](http://support.logitech.com/en_us/product/quickcam-sphere-af) and a [Logitech HD Webcam C270](http://support.logitech.com/en_us/product/hd-webcam-c270). As a start only the Quickcam is used. No multi-camera setup for now.
|
||||
|
||||
@ -91,7 +91,7 @@ $ sudo motion
|
||||
[0] [NTC] [ALL] motion_startup: Logging to file (/var/log/motion.log)
|
||||
```
|
||||
|
||||
Your `target_dir` will start filling up with images from your camera. `motion` will create a symlink called `lastsnap.jpg` which always point to the latest snapshot. We will setup the [Local File camera platform](/components/camera.local_file/) to use this file.
|
||||
Your `target_dir` will start filling up with images from your camera. `motion` will create a symlink called `lastsnap.jpg` which always point to the latest snapshot. We will setup the [Local File camera platform](/components/local_file) to use this file.
|
||||
|
||||
```yaml
|
||||
camera:
|
||||
@ -107,7 +107,7 @@ camera:
|
||||
|
||||
The machine with the attached USB camera will become a webcam server as well because `motion`'s built-in HTTP server is enabled by default. This means that you could connect your USB webcams to a different machine in your network, run `motion` there, adjust your firewall rules, and use Home Assistant to display the videos. Just check http://[IP of your webcam host]:8081/ to see the stream. This required more powerful hardware than using snapshots, of course.
|
||||
|
||||
In a scenario like this needs a [Generic MJPEG IP Camera ](/components/camera.mjpeg/) in your `configuration.yaml` file.
|
||||
In a scenario like this needs a [Generic MJPEG IP Camera ](/components/mjpeg) in your `configuration.yaml` file.
|
||||
|
||||
```yaml
|
||||
camera:
|
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Loading…
x
Reference in New Issue
Block a user