Merge branch 'current' into next
This commit is contained in:
Paulus Schoutsen
commit
636e5c12f2
116 changed files with 335 additions and 2935 deletions
|
|
@ -163,7 +163,7 @@ alexa:
|
|||
|
||||
### {% linkable_title Working With Scenes %}
|
||||
|
||||
One of the more useful applications of Alexa integrations is to call scenes directly. This is easily achieved with some simple setup on the Home Assistant side and by letting Alexa know which scenes you want to run.
|
||||
One of the most useful applications of Alexa integrations is to call scenes directly. This is easily achieved with some simple setup on the Home Assistant side and by letting Alexa know which scenes you want to run.
|
||||
|
||||
First we will configure Alexa. In the Amazon Interaction module add this to the intent schema:
|
||||
|
||||
|
|
|
|||
|
|
@ -19,4 +19,13 @@ Starting with 0.28 your automation rules can be controlled with the frontend.
|
|||
<img src='{{site_root}}/images/screenshots/automation-switches.png' />
|
||||
</p>
|
||||
|
||||
This allows one to reload the automation without restarting Home Assistant itself.
|
||||
This allows one to reload the automation without restarting Home Assistant itself. If you don't want to see the automation rule in your frontend use `hide_entity: True` to hide it.
|
||||
|
||||
```yaml
|
||||
automation:
|
||||
- alias: Door alarm
|
||||
hide_entity: True
|
||||
trigger:
|
||||
- platform: state
|
||||
...
|
||||
```
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
layout: page
|
||||
title: "FFmpeg Binary Sensor"
|
||||
description: "Instructions how to integrate a varius ffmpeg based binary sensor"
|
||||
description: "Instructions on how to integrate an FFmpeg-based binary sensor"
|
||||
date: 2016-08-25 08:00
|
||||
sidebar: true
|
||||
comments: false
|
||||
|
|
@ -14,11 +14,15 @@ ha_iot_class: "Local Polling"
|
|||
---
|
||||
|
||||
|
||||
The `ffmpeg` platform allows you to use every video or audio feed with [FFmpeg](http://www.ffmpeg.org/) for various sensors in Home Assistant. Available are: **noise**, **motion**. If the `ffmpeg` process is broken, the sensor will be unavailable. To restart the instance, use the service *binary_sensor.ffmpeg_restart*.
|
||||
The `ffmpeg` platform allows you to use any video or audio feed with [FFmpeg](http://www.ffmpeg.org/) for various sensors in Home Assistant. Available are: **noise**, **motion**.
|
||||
|
||||
<p class='note'>
|
||||
If the `ffmpeg` process is broken, the sensor will be unavailable. To restart it, use the service *binary_sensor.ffmpeg_restart*.
|
||||
</p>
|
||||
|
||||
### {% linkable_title Noise %}
|
||||
|
||||
To enable your FFmpeg with noise detection in your installation, add the following to your `configuration.yaml` file:
|
||||
To add FFmpeg with noise detection to your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
|
|
@ -29,16 +33,16 @@ binary_sensor:
|
|||
|
||||
Configuration variables:
|
||||
|
||||
- **input** (*Required*): A ffmpeg compatible input file, stream or feed.
|
||||
- **tool** (*Required*): Is fix set to `noise`.
|
||||
- **name** (*Optional*): This parameter allows you to override the name of your camera.
|
||||
- **peak** (*Optional*): Default -30. A peak of dB to detect it as noise. 0 is very loud and -100 is low.
|
||||
- **duration** (*Optional*): Default 1 seconds. How long need the noise over the peak to trigger the state.
|
||||
- **reset** (*Optional*): Defaults to 20 seconds. The time to reset the state after none new noise is over the peak.
|
||||
- **extra_arguments** (*Optional*): Extra option they will pass to `ffmpeg`, like audio frequence filtering.
|
||||
- **output** (*Optional*): Allow you to send the audio output of this sensor to an icecast server or other ffmpeg supported output, eg. to stream with sonos after state is triggered.
|
||||
- **input** (*Required*): An FFmpeg-compatible input file, stream, or feed.
|
||||
- **tool** (*Required*): `noise`.
|
||||
- **name** (*Optional*): Override the name of your camera.
|
||||
- **peak** (*Optional*): Default -30. The threshold of detecting noise, in dB. 0 is very loud and -100 is low.
|
||||
- **duration** (*Optional*): Default 1 second. How long the noise needs to be over the peak to trigger the state.
|
||||
- **reset** (*Optional*): Default 20 seconds. The time to reset the state after no new noise is over the peak.
|
||||
- **extra_arguments** (*Optional*): Extra options to pass to `ffmpeg`, like audio frequency filtering.
|
||||
- **output** (*Optional*): Allows you to send the audio output of this sensor to an Icecast server or other FFmpeg-supported output, e.g. to stream with Sonos after a state is triggered.
|
||||
|
||||
For playing with values:
|
||||
To experiment with values:
|
||||
|
||||
```bash
|
||||
$ ffmpeg -i YOUR_INPUT -vn -filter:a silencedetect=n=-30dB:d=1 -f null -
|
||||
|
|
@ -46,9 +50,9 @@ $ ffmpeg -i YOUR_INPUT -vn -filter:a silencedetect=n=-30dB:d=1 -f null -
|
|||
|
||||
### {% linkable_title Motion %}
|
||||
|
||||
FFmpeg doesn't have a motion detection filter, so it uses a scene filter to detect a new scene/motion. In fact, you can set how big of an object or the size of an image that needs to change in order to detect motion. The option 'changes' is the percent value of change between frames. You can add a denoise filter to the video if you want a really small value for 'changes'.
|
||||
FFmpeg doesn't have a motion detection filter, but can use a scene filter to detect a new scene/motion. You can set how much needs to change in order to detect motion with the option 'changes', the percent value of change between frames. If you want a really small value for 'changes', you can also add a denoise filter.
|
||||
|
||||
To enable your FFmpeg with motion detection in your installation, add the following to your `configuration.yaml` file:
|
||||
To add FFmpeg with motion detection to your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
|
|
@ -60,19 +64,19 @@ binary_sensor:
|
|||
|
||||
Configuration variables:
|
||||
|
||||
- **input** (*Required*): A ffmpeg compatible input file, stream, or feed.
|
||||
- **tool** (*Required*): Is fix set to `motion`.
|
||||
- **name** (*Optional*): This parameter allows you to override the name of your camera.
|
||||
- **changes** (*Optional*): Default 10 percent. A lower value is more sensitive. I use 4 / 3.5 on my cameras. It describes how much needs to change between two frames to detect it as motion. See on descripton.
|
||||
- **input** (*Required*): An FFmpeg-compatible input file, stream, or feed.
|
||||
- **tool** (*Required*): `motion`.
|
||||
- **name** (*Optional*): Override the name of your camera.
|
||||
- **changes** (*Optional*): Default 10%. How much needs to change between two frames to detect it as motion (a lower value is more sensitive).
|
||||
- **reset** (*Optional*): Default 20 seconds. The time to reset the state after no new motion is detected.
|
||||
- **repeat** (*Optional*): Default 0 repeats (deactivate). How many events need to be detected in *repeat_time* in order to trigger a motion.
|
||||
- **repeat_time** (*Optional*): Default 0 seconds (deactivate). The span of time *repeat* events need to occur in before triggering a motion.
|
||||
- **extra_arguments** (*Optional*): Extra option they will pass to ffmpeg. i.e. video denoise filtering.
|
||||
- **extra_arguments** (*Optional*): Extra options to pass to FFmpeg, e.g. video denoise filtering.
|
||||
|
||||
For playing with values (changes/100 is the scene value on ffmpeg):
|
||||
To experiment with values (changes/100 is the scene value in FFmpeg):
|
||||
|
||||
```bash
|
||||
$ ffmpeg -i YOUR_INPUT -an -filter:v select=gt(scene\,0.1) -f framemd5 -
|
||||
```
|
||||
|
||||
If you are running into trouble with this sensor, please refer to this [Troubleshooting section](/components/ffmpeg/#troubleshooting).
|
||||
If you are running into trouble with this sensor, please refer to the [troubleshooting section](/components/ffmpeg/#troubleshooting).
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@
|
|||
layout: page
|
||||
title: "MQTT Cover"
|
||||
description: "Instructions how to integrate MQTT covers into Home Assistant."
|
||||
date: 2016-06-28 17:30
|
||||
date: 2016-09-28 17:30
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
|
|
@ -27,23 +27,24 @@ To use your MQTT cover in your installation, add the following to your `configur
|
|||
# Example configuration.yml entry
|
||||
cover:
|
||||
- platform: mqtt
|
||||
name: "MQTT Cover"
|
||||
state_topic: "home-assistant/cover"
|
||||
command_topic: "home-assistant/cover/set"
|
||||
```
|
||||
|
||||
Configuration variables:
|
||||
|
||||
- **state_topic** (*Required*): The MQTT topic subscribed to receive sensor values.
|
||||
- **name** (*Optional*): The name of the sensor. Default is `MQTT Cover`.
|
||||
- **state_topic** (*Optional*): The MQTT topic subscribed to receive sensor values.
|
||||
- **command_topic** (*Required*): The MQTT topic to publish commands to control the rollershutter.
|
||||
- **name** (*Optional*): The name of the sensor. Default is "MQTT Sensor".
|
||||
- **qos** (*Optional*): The maximum QoS level of the state topic. Default is 0 and will also be used to publishing messages.
|
||||
- **retain** (*Optional*): If the published message should have the retain flag on or not.
|
||||
- **payload_open** (*Optional*): The payload that opens the cover. Default is "UP"
|
||||
- **payload_close** (*Optional*): The payload that closes the cover. Default is "DOWN"
|
||||
- **payload_stop** (*Optional*): The payload that stops the rollershutter. default is "STOP"
|
||||
- **state_open** (*Optional*): The payload that represents open state. Default is "STATE_OPEN"
|
||||
- **state_closed** (*Optional*): The payload that represents closed state. Default is "STATE_CLOSED"
|
||||
- **payload_open** (*Optional*): The payload that opens the cover. Default is `OPEN`.
|
||||
- **payload_close** (*Optional*): The payload that closes the cover. Default is `CLOSE`.
|
||||
- **payload_stop** (*Optional*): The payload that stops the rollershutter. default is `STOP`.
|
||||
- **state_open** (*Optional*): The payload that represents open state. Default is `open`.
|
||||
- **state_closed** (*Optional*): The payload that represents closed state. Default is `closed`.
|
||||
- **optimistic** (*Optional*): Flag that defines if switch works in optimistic mode. Default is `true` if no state topic defined, else `false`.
|
||||
- **qos** (*Optional*): The maximum QoS level of the state topic. Default is `0`. Will also be used when publishing messages.
|
||||
- **retain** (*Optional*): If the published message should have the retain flag on or not. Default is `false`.
|
||||
- **value_template** (*Optional*): Defines a [template](/topics/templating/) to extract a value from the payload.
|
||||
|
||||
## {% linkable_title Examples %}
|
||||
|
|
@ -78,4 +79,3 @@ For a check you can use the command line tools `mosquitto_pub` shipped with `mos
|
|||
```bash
|
||||
$ mosquitto_pub -h 127.0.0.1 -t home-assistant/cover/set -m "CLOSE"
|
||||
```
|
||||
|
||||
|
|
|
|||
|
|
@ -27,6 +27,7 @@ OID examples:
|
|||
- BiPAC 7800DXL: `1.3.6.1.2.1.17.7.1.2.2.1.1` (confirmed on firmware 2.32e)
|
||||
- OpenWrt: `1.3.6.1.2.1.4.22.1.2` (tested on Chaos Calmer 15.05 firmware, need to install snmpd package)
|
||||
- pfSense: `1.3.6.1.2.1.4.22.1.2` (tested on 2.2.4-RELEASE, need to enable SNMP service)
|
||||
- TPLink: `1.3.6.1.2.1.3.1.1.2.19.1` (Archer VR2600v, need to enable SNMP service)
|
||||
|
||||
To use the SNMP platform in your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@
|
|||
layout: page
|
||||
title: "Envisalink Alarm Control Panel"
|
||||
description: "Instructions on how to integrate a DSC/Honeywell alarm panel with Home Assistant using an envisalink evl3/evl4 board."
|
||||
date: 2016-06-19 22:10
|
||||
date: 2016-09-30 22:45
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
|
|
@ -25,6 +25,8 @@ There is currently support for the following device types within Home Assistant:
|
|||
|
||||
This is a fully event-based component. Any event sent by the Envisalink device will be immediately reflected within Home Assistant.
|
||||
|
||||
As of 0.29, the alarm_trigger service is supported. It is possible to fire off an envisalink-based alarm directly from Home Assistant. For example, a newer zwave/zigbee sensor can now be integrated into a legacy alarm system using a Home Assistant automation.
|
||||
|
||||
An `envisalink` section must be present in the `configuration.yaml` file and contain the following options as required:
|
||||
|
||||
```yaml
|
||||
|
|
@ -39,6 +41,7 @@ envisalink:
|
|||
evl_version: 3
|
||||
keepalive_interval: 60
|
||||
zonedump_interval: 30
|
||||
panic_type: Police
|
||||
zones:
|
||||
11:
|
||||
name: 'Back Door'
|
||||
|
|
@ -62,6 +65,7 @@ Configuration variables:
|
|||
- **evl_version** (*Optional*): 3 for evl3, or 4 for evl4. Default: `3`
|
||||
- **keepalive_interval** (*Optional*): This is a periodic heartbeat signal (measured in seconds) sent to your Envisalink board to keep it from restarting. This is required for DSC and Honeywell systems. Defaults to `60` seconds.
|
||||
- **zonedump_interval** (*Optional*): This is an interval (measured in seconds) where the evl will dump out all zone statuses. This is required for Honeywell systems, which do not properly send zone closure events. DSC boards do not technically need this. Default: `30`
|
||||
- **panic_type** (*Optional*): Both DSC and Honeywell boards support a "panic" alarm. This is used when the alarm_trigger service is called in home assistant. This determines which type of panic alarm to raise. Default = Police. Valid values are: Police, Fire, Ambulance
|
||||
- **zones** (*Optional*): 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. *Note: if no zones are specified, Home Assistant will not load any binary_sensor components.*
|
||||
- **partitions** (*Optional*): Again, Envisalink boards do not tell us what is in use and what is not, so each partition must be configured with a partition name. If no partition parameter is specified, then no alarm_panel or sensor components are loaded.
|
||||
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@
|
|||
layout: page
|
||||
title: "Music Player Daemon (MPD)"
|
||||
description: "Instructions how to integrate Music Player Daemon into Home Assistant."
|
||||
date: 2015-06-02 08:00
|
||||
date: 2016-09-30 23:06
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
|
|
@ -16,6 +16,8 @@ ha_iot_class: "Local Polling"
|
|||
|
||||
The `mpd` platform allows you to control a [Music Player Daemon](http://www.musicpd.org/) from Home Assistant. Unfortunatly you will not be able to manipulate the playlist (add or delete songs) or add transitions between the songs.
|
||||
|
||||
Even though no playlist manipulation is possible, it is possible to use the play_media service to load an existing saved playlist as part of an automation or scene.
|
||||
|
||||
To add MPD to your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
|
|
@ -32,5 +34,22 @@ Configuration variables:
|
|||
- **location** (*Optional*): Location of your Music Player Daemon. Defaults to "MPD".
|
||||
- **password** (*Optional*): Password for your Music Player Daemon.
|
||||
|
||||
Example script to load a saved playlist called "DeckMusic" and set the volume:
|
||||
|
||||
```yaml
|
||||
relaxdeck:
|
||||
sequence:
|
||||
- service: media_player.play_media
|
||||
data:
|
||||
entity_id: media_player.main
|
||||
media_content_type: playlist
|
||||
media_content_id: DeckMusic
|
||||
|
||||
- service: media_player.volume_set
|
||||
data:
|
||||
entity_id: media_player.main
|
||||
volume_level: 0.60
|
||||
```
|
||||
|
||||
This platform works with [Music Player Daemon](http://www.musicpd.org/) and [mopidy](https://www.mopidy.com/) with [Mopidy-MPD](https://docs.mopidy.com/en/latest/ext/mpd/) as used by [Pi MusicBox](http://www.pimusicbox.com/).
|
||||
|
||||
|
|
|
|||
|
|
@ -26,9 +26,14 @@ If you want process all data local you need the command line tool `alpr` in vers
|
|||
|
||||
If you don't found binarys for you distribution you can compile from source. A documention how to build a openalpr is found [here](https://github.com/openalpr/openalpr/wiki).
|
||||
|
||||
On a debian system you can use this cmake command to build only the command line tool:
|
||||
On a debian system you can use this cmake command to build only the command line tool (which second part on linux build instruction - ubuntu 14.04+):
|
||||
```bash
|
||||
cmake -DWITH_TEST=FALSE -DWITH_BINDING_JAVA=FALSE --DWITH_BINDING_PYTHON=FALSE --DWITH_BINDING_GO=FALSE -DWITH_DAEMON=FALSE -DCMAKE_INSTALL_PREFIX:PATH=/usr
|
||||
cmake -DWITH_TEST=FALSE -DWITH_BINDING_JAVA=FALSE --DWITH_BINDING_PYTHON=FALSE --DWITH_BINDING_GO=FALSE -DWITH_DAEMON=FALSE -DCMAKE_INSTALL_PREFIX:PATH=/usr ..
|
||||
```
|
||||
|
||||
Verify your alpr installation with:
|
||||
```
|
||||
wget -O- -q http://plates.openalpr.com/h786poj.jpg | alpr -
|
||||
```
|
||||
|
||||
### {% linkable_title Configuration Home Assistant %}
|
||||
|
|
|
|||
|
|
@ -15,11 +15,23 @@ ha_release: 0.29
|
|||
The `bom` platform allows you to get the current weather conditions from the [Bureau of Meteorology (BOM)](http://www.bom.gov.au/) Australia.
|
||||
|
||||
- Each sensor will be given the `device_id` of "bom [optionalname] friendlyname units"
|
||||
- Get the station ID for your local BOM station from the BOM website: State -> Observations -> Latest Observations -> Choose the station
|
||||
- The URL will look like http://www.bom.gov.au/products/IDS60801/IDS60801.94675.shtml. This is for Adelaide. The URL is read as: http://www.bom.gov.au/products/[zone_id]/[zone_id].[wmo_id].shtml
|
||||
- A name is optional but if multiple BOM weather stations are used a name will be required.
|
||||
- The sensor will update every minute 35 minutes after last data timestamp. This allows for the 30 minute observation cycle and the approximate 5 minute update delay in publishing the data.
|
||||
|
||||
To get the station ID `[zone_id]` and `[wmo_id]` for your local BOM station:
|
||||
- Find your station on these maps:
|
||||
- NSW: http://www.bom.gov.au/nsw/observations/map.shtml
|
||||
- QLD: http://www.bom.gov.au/qld/observations/map.shtml
|
||||
- VIC: http://www.bom.gov.au/vic/observations/map.shtml
|
||||
- WA: http://www.bom.gov.au/wa/observations/map.shtml
|
||||
- SA: http://www.bom.gov.au/sa/observations/map.shtml
|
||||
- TAS: http://www.bom.gov.au/tas/observations/map.shtml
|
||||
- ACT: http://www.bom.gov.au/act/observations/canberramap.shtml
|
||||
- NT: http://www.bom.gov.au/nt/observations/map.shtml
|
||||
- alternatively, from the [BOM website](http://www.bom.gov.au/), navigate to State -> Observations -> Latest Observations -> Choose the station.
|
||||
- The URL will look like: http://www.bom.gov.au/products/[zone_id]/[zone_id].[wmo_id].shtml
|
||||
- For Adelaide, the URL will look like http://www.bom.gov.au/products/IDS60801/IDS60801.94675.shtml.
|
||||
|
||||
To add the BOM weather observation to your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
|
|
|
|||
|
|
@ -14,7 +14,7 @@ ha_iot_class: "Cloud Polling"
|
|||
---
|
||||
|
||||
|
||||
Integrate your [ELIQ Online](http://eliq.se) smart meter information into Home Assistant. To get an [acess token](https://my.eliq.se/user/settings/api) and the [Channel ID](https://my.eliq.se/user/settings/data), log in to your account.
|
||||
Integrate your [ELIQ Online](http://eliq.se) smart meter information into Home Assistant. To get an [access token](https://my.eliq.se/user/settings/api) and the [Channel ID](https://my.eliq.se/user/settings/data), log in to your account.
|
||||
|
||||
To enable this sensor in your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
|
|
|
|||
|
|
@ -18,10 +18,11 @@ The Fitbit sensor allows you to expose data from [Fitbit](http://fitbit.com) to
|
|||
Enable the sensor by adding the following to your configuration:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
sensor:
|
||||
platform: fitbit
|
||||
monitored_resources:
|
||||
- "body/weight"
|
||||
- platform: fitbit
|
||||
monitored_resources:
|
||||
- "body/weight"
|
||||
```
|
||||
|
||||
Restart Home Assistant once this is complete. Go to the frontend. You will see a new entry for configuring Fitbit. Follow the instructions there to complete the setup process.
|
||||
|
|
@ -30,6 +31,10 @@ Please be aware that Fitbit has very low rate limits, 150 per user per hour. The
|
|||
|
||||
The unit system that the sensor will use is based on the country you set in your Fitbit profile.
|
||||
|
||||
Configuration variables:
|
||||
|
||||
- **monitored_resources** (*Required*): Resource to monitor.
|
||||
|
||||
Below is the list of resources that you can add to `monitored_resources`. One sensor is exposed for every resource.
|
||||
|
||||
```text
|
||||
|
|
|
|||
|
|
@ -30,7 +30,9 @@ $ curl -X GET http://IP_ADDRESS:61208/api/2/mem/free
|
|||
{"free": 203943936}
|
||||
```
|
||||
|
||||
To enable the glances sensor, add the following lines to your `configuration.yaml`:
|
||||
For details about auto-starting `glances`, please refer to [Start Glances through Systemd](https://github.com/nicolargo/glances/wiki/Start-Glances-through-Systemd).
|
||||
|
||||
To enable the Glances sensor, add the following lines to your `configuration.yaml`:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
|
|
|
|||
|
|
@ -29,18 +29,10 @@ sensor:
|
|||
- 'temperature'
|
||||
- 'target'
|
||||
- 'humidity'
|
||||
- 'mode'
|
||||
- 'last_ip'
|
||||
- 'local_ip'
|
||||
- 'operation_mode'
|
||||
- 'last_connection'
|
||||
- 'battery_level'
|
||||
- 'weather_condition'
|
||||
- 'weather_temperature'
|
||||
- 'weather_humidity'
|
||||
- 'wind_speed'
|
||||
- 'wind_direction'
|
||||
- 'co_status'
|
||||
- 'smoke_status'
|
||||
- 'co_status' # Nest Protect only
|
||||
- 'smoke_status' # Nest Protect only
|
||||
```
|
||||
|
||||
Configuration variables:
|
||||
|
|
@ -49,7 +41,7 @@ Configuration variables:
|
|||
- 'temperature'
|
||||
- 'target'
|
||||
- 'humidity'
|
||||
- 'mode'
|
||||
- 'operation_mode'
|
||||
- 'last_ip'
|
||||
- 'local_ip'
|
||||
- 'last_connection'
|
||||
|
|
|
|||
|
|
@ -28,5 +28,5 @@ Configuration variables:
|
|||
|
||||
- **host** (*Optional*): The IP address of the Pi-Hole system. Defaults to `localhost`.
|
||||
- **ssl** (*Optional*): If `true`, use SSL/TLS to connect to the Pi-Hole system. Defaults to `False`.
|
||||
- **verify_ssl** (*Optional*): Verify the certification of the system. Default to True.
|
||||
- **verify_ssl** (*Optional*): Verify the certification of the system. Default to `True`.
|
||||
|
||||
|
|
|
|||
|
|
@ -49,5 +49,5 @@ Configuration variables:
|
|||
- **sunset_colortemp** (*Optional*): The sun set color temperature. Defaults to `3000`.
|
||||
- **stop_colortemp** (*Optional*): The color temperature at the end. Defaults to `1900`.
|
||||
- **brightness** (*Optional*): The brightness of the lights. Calculated with `RGB_to_xy` by default.
|
||||
- **mode** (*Optional*): Select how color temperature is passed to lights. Valid values are 'xy', 'mired' and 'kelvin'. Defaults to 'xy'.
|
||||
- **mode** (*Optional*): Select how color temperature is passed to lights. Valid values are `xy` and `mired`. Defaults to `xy`.
|
||||
|
||||
|
|
|
|||
|
|
@ -9,6 +9,7 @@
|
|||
<ul>
|
||||
<li>{% active_link /getting-started/installation-raspberry-pi/ Raspberry Pi %}</li>
|
||||
<li>{% active_link /getting-started/installation-raspberry-pi-all-in-one/ Raspberry Pi All-In-One Installer %}</li>
|
||||
<li>{% active_link /getting-started/installation-raspberry-pi-image/ Raspberry Pi Image %}</li>
|
||||
<li>{% active_link /getting-started/installation-docker/ Docker %}</li>
|
||||
<li>{% active_link /getting-started/installation-vagrant/ Vagrant %}</li>
|
||||
<li>{% active_link /getting-started/installation-synology/ Synology NAS %}</li>
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ layout: post
|
|||
title: "0.29: 🎈 Async, SleepIQ, OpenALPR, EmonCMS, stocks, and plants"
|
||||
description: "Move to asynchronous, Support for SleepIQ, OpenALPR, and EmonCMS, and other goodies."
|
||||
date: 2016-09-29 03:04:05 +0000
|
||||
date_formatted: "September 24, 2016"
|
||||
date_formatted: "September 29, 2016"
|
||||
author: Paulus Schoutsen & Fabian Affolter
|
||||
author_twitter: balloob
|
||||
comments: true
|
||||
|
|
@ -28,6 +28,10 @@ On the voluptuous front we have also made great progress. We were able to fully
|
|||
|
||||
As you might have noticed, this release has been delayed by 5 days. This was due to a rare, difficult to reproduce problem with the Python interpreter. A huuuuge thanks to all the people that have helped countless hours in researching, debugging and fixing this issue: [@bbangert], [@turbokongen], [@lwis], [@kellerza], [@technicalpickles], [@pvizeli], [@persandstrom] and [@joyrider3774]. I am grateful to have all of you as part of the Home Assistant community.
|
||||
|
||||
### {% linkable_title Hide automation rules %}
|
||||
|
||||
Since 0.28 [automation rules](/blog/2016/09/10/notify-group-reload-api-pihole/#reload-automation-rules) can be reloaded directly from the frontend. By default all automation rules are shown. If you want to [hide an automation rule](/getting-started/automation-create-first/), use `hide_entity: True`.
|
||||
|
||||
### {% linkable_title All changes %}
|
||||
|
||||
<img src='/images/supported_brands/emoncms.png' style='clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='100' /><img src='/images/supported_brands/sleepiq.png' style='clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='100' /><img src='/images/supported_brands/openalpr.png' style='clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='100' />
|
||||
|
|
@ -64,15 +68,48 @@ As you might have noticed, this release has been delayed by 5 days. This was due
|
|||
- [OpenALPR] support ([@pvizeli])
|
||||
- Minor features and bug fixes by [@fabaff], [@w1ll1am23], [@turbokongen], [@clach04], [@mKeRix], [@pvizeli], [@DavidLP], [@nvella], [@Teagan42], [@ericwclymer], [@wokar], [@kellerza], [@nkgilley], [@jawilson], [@Danielhiversen], [@ej81], [@danieljkemp], [@balloob], [@philhawthorne], [@LinuxChristian], [@milas], [@simonszu], [@Cinntax], [@irvingwa], [@sytone], [@kk7ds], [@robbiet480].
|
||||
|
||||
### {% linkable_title Hotfix 0.29.1 - September 29 %}
|
||||
|
||||
- Fix typo in Nest climate platform. [We are still experiencing issues with Nest.][nest-issues] ([@tchellomello])
|
||||
|
||||
### {% linkable_title Hotfix 0.29.2 - September 29 %}
|
||||
|
||||
- InfluxDB config fix ([@fabaff], reported by [@lwis])
|
||||
- Netatmo config fix ([@jabesq])
|
||||
|
||||
### {% linkable_title Hotfix 0.29.3 - September 29 %}
|
||||
|
||||
- Hue config fix ([@pvizeli])
|
||||
|
||||
### {% linkable_title Hotfix 0.29.4 - September 30 %}
|
||||
|
||||
- Alexa config fix ([@baloob], reported by [@lwis])
|
||||
- Envisalink discovery fix ([@cinntax])
|
||||
- Acer Projector config fix ([@pvizeli])
|
||||
|
||||
### {% linkable_title Hotfix 0.29.5 - September 30 %}
|
||||
|
||||
- Fix Climate Nest platform (@tchellomello, @jawilson)
|
||||
|
||||
### {% linkable_title Hotfix 0.29.5 - October 1 %}
|
||||
|
||||
- Fix segmentation fault ([@bbangert], fixes #3453) 🎉
|
||||
- Fix nested templates in `data_template` would incorrectly get cached ([@balloob])
|
||||
|
||||
### {% linkable_title Breaking changes %}
|
||||
|
||||
- The template methods `now` and `utcnow` have been changed from variables to methods. To get the current time replace `now` with `now()`.
|
||||
- `yahooweather` default name is now `yweather`. Also min and max temperature are now correctly called `Temperature Min` and `Temperature Max`.
|
||||
- `ffmpeg` is now a component for manage some things central. All `ffmpeg_bin` options have moved to this compoment from platforms.
|
||||
- Config has changed for [X10] lights.
|
||||
- For Wink, make sure your config only contains the access token as in the [docs][Wink].
|
||||
- Nest sensor 'mode' has been renamed to 'operation_mode'
|
||||
|
||||
### {% linkable_title If you need help... %}
|
||||
...don't hesitate to use our [Forum](https://community.home-assistant.io/) or join us for a little [chat](https://gitter.im/home-assistant/home-assistant). The release notes have comments enabled but it's preferred if you the former communication channels. Thanks.
|
||||
|
||||
[nest-issues]: https://github.com/home-assistant/home-assistant/issues/3574
|
||||
[@jabesq]: https://github.com/jabesq
|
||||
[@joyrider3774]: https://github.com/joyrider3774
|
||||
[@balloob]: https://github.com/balloob
|
||||
[@bbangert]: https://github.com/bbangert
|
||||
|
|
|
|||
|
|
@ -0,0 +1,34 @@
|
|||
---
|
||||
layout: post
|
||||
title: "We have a Raspberry Pi image now"
|
||||
description: "Release of the Rapsberry Pi Image for Home Assistant"
|
||||
date: 2016-10-01 01:00:00 -0400
|
||||
date_formatted: "October 1, 2016"
|
||||
author: Fredrik Lindqvist
|
||||
comments: true
|
||||
categories: Technology
|
||||
og_image: /images/blog/2016-10-hassbian/social.png
|
||||
---
|
||||
|
||||
Today we're happy to announce our brand new Raspberry Pi image! It is based on Raspbian Lite combined with HASS so we decided to call it Hassbian.
|
||||
|
||||
This image comes pre-installed with everything you need to get started with Home Assistant right away.
|
||||
|
||||
To get started, check out the installation instructions in [the getting started section][gs-image] or watch the latest video by [BRUHAutomation]:
|
||||
|
||||
<div class='videoWrapper'>
|
||||
<iframe width="560" height="315" src="https://www.youtube.com/embed/iIz6XqDwHEk" frameborder="0" allowfullscreen></iframe>
|
||||
</div>
|
||||
|
||||
### {% linkable_title Under the hood %}
|
||||
|
||||
It's based on Raspbian Lite and generated with a fork of the same [script](https://github.com/home-assistant/pi-gen) that builds the [official Raspbian images](https://raspberrypi.org/downloads/raspbian/). For installation of HASS it follows the same install instructions as the [Manual installation](/getting-started/installation-raspberry-pi/). Please note that this project has no association with the Raspberry Pi foundation or their projects.
|
||||
|
||||
On first boot the latest release of Home Assistant will be installed and can be reached after 3~5 minutes. Pre-installed on this image is the MQTT broker [Mosquitto](https://mosquitto.org/), Bluetooth support and settings for the `homeassistant` account to use the GPIO pins of the Raspberry Pi. Mosquitto is not activated by default.
|
||||
|
||||
As it is today there is no pre-compiled Z-Wave support but it can be installed by following the [Getting started instructions for Z-Wave](/getting-started/z-wave/).
|
||||
|
||||
Happy Automating!
|
||||
|
||||
[gs-image]: /getting-started/installation-raspberry-pi-image/
|
||||
[BRUHAutomation]: https://www.youtube.com/channel/UCLecVrux63S6aYiErxdiy4w
|
||||
42
source/_posts/2016-10-02-hacktoberfest.markdown
Normal file
42
source/_posts/2016-10-02-hacktoberfest.markdown
Normal file
|
|
@ -0,0 +1,42 @@
|
|||
---
|
||||
layout: post
|
||||
title: "Participating in Hacktoberfest"
|
||||
description: "Home Assistant will be participating in Hacktoberfest to help people to get started with open-source."
|
||||
date: 2016-10-02 00:04:05 +0000
|
||||
date_formatted: "October 2, 2016"
|
||||
author: Paulus Schoutsen
|
||||
author_twitter: balloob
|
||||
comments: true
|
||||
categories: Community
|
||||
og_image: /images/blog/2016-10-hacktoberfest/social.png
|
||||
---
|
||||
|
||||
Home Assistant will join this year for [Hacktoberfest], an event organised by DigitalOcean and GitHub to support and celebrate open source. The idea is that open source projects like Home Assistant will gather a bunch of entry-level bugs, features and documentation enhancements and that you, a current or future contributor, will fix them. If you submit four pull-requests during the month of October you will have earned yourself a limited edition Hacktoberfest T-shirt!
|
||||
|
||||
Why contribute to Home Assistant:
|
||||
|
||||
- Written in Python3 with 94% test coverage
|
||||
- Active and helpful community
|
||||
- Friendly to new contributors
|
||||
|
||||
Resources to get started:
|
||||
|
||||
- [Sign up for Hacktoberfest][Hacktoberfest-reg]
|
||||
- [List of entry-level issues for Home Assistant][issues]
|
||||
- [Instructions to setup your development environment][dev-env]
|
||||
- [Home Assistant Development Chat][dev-chat]
|
||||
- [Home Assistant Development Forums][dev-forum]
|
||||
- [Hacktoberfest website][Hacktoberfest]
|
||||
|
||||
Are you not a programmer but still want to contribute to Home Assistant? Check out our [list of entry-level issues for the Home Assistant website][issues-doc].
|
||||
|
||||
[![Hacktober fest logo][logo]][Hacktoberfest]
|
||||
|
||||
[logo]: /images/blog/2016-10-hacktoberfest/hacktoberfest.png
|
||||
[Hacktoberfest]: https://hacktoberfest.digitalocean.com/
|
||||
[Hacktoberfest-reg]: https://hacktoberfest.digitalocean.com/sign_up/register
|
||||
[issues]: https://github.com/home-assistant/home-assistant/labels/Hacktoberfest
|
||||
[issues-doc]: https://github.com/home-assistant/home-assistant.github.io/labels/Hacktoberfest
|
||||
[dev-env]: /developers/development_environment/
|
||||
[dev-chat]: https://gitter.im/home-assistant/home-assistant/devs
|
||||
[dev-forum]: https://community.home-assistant.io/c/development
|
||||
|
|
@ -24,7 +24,7 @@ On Windows you can use `python setup.py develop` instead of the setup script.
|
|||
|
||||
After following these steps, running `hass` will invoke your local installation.
|
||||
|
||||
###Developing on Windows
|
||||
### Developing on Windows
|
||||
If you are using Windows as a development platform ensure you have the correct Microsoft Visual C++ build tools installed. Please check [the Windows Compilers](https://wiki.python.org/moin/WindowsCompilers) section on the [Python website](https://www.python.org/) for details. Validation using `tox` will fail if this is not done correctly.
|
||||
|
||||
Ensure you install or upgrade the Setuptools Python package. It contains compatibility improvements and adds automatic use of compilers:
|
||||
|
|
|
|||
|
|
@ -13,7 +13,7 @@ Home Assistant enforces strict [PEP8 style](https://www.python.org/dev/peps/pep-
|
|||
|
||||
### {% linkable_title Local testing %}
|
||||
|
||||
It's highly recommanded to run `tox` before you create your Pull Request to avoid annoying fixes. Local testing requires `tox` to be installed.
|
||||
It's highly recommended to run `tox` before you create your Pull Request to avoid annoying fixes. Local testing requires `tox` to be installed.
|
||||
|
||||
```bash
|
||||
$ pip3 install tox
|
||||
|
|
|
|||
|
|
@ -80,7 +80,7 @@ When you're writing code that is to be executed on the terminal, prefix it with
|
|||
|
||||
### {% linkable_title HTML %}
|
||||
|
||||
The direct usage of HTML is supported but not recommanded. The note boxes are an exception.
|
||||
The direct usage of HTML is supported but not recommended. The note boxes are an exception.
|
||||
|
||||
```html
|
||||
<p class='note warning'>
|
||||
|
|
|
|||
|
|
@ -17,6 +17,7 @@ In this example, we are defining a trigger to track the sunset and tell it to fi
|
|||
# Example configuration.yaml entry
|
||||
automation:
|
||||
alias: Turn on light when sun sets
|
||||
hide_entity: False
|
||||
trigger:
|
||||
platform: sun
|
||||
event: sunset
|
||||
|
|
@ -24,6 +25,8 @@ automation:
|
|||
service: light.turn_on
|
||||
```
|
||||
|
||||
Starting with 0.28 automation rules can be reloaded from the [frontend](/components/automation/) and are shown by default. With [`hide_entity:`](/components/automation/) you can control this behaviour. It's is very handy if you are working on your rules but when a rule is finished and you don't want to see that rule in your frontend, you can set `hide_entity:` to `True`.
|
||||
|
||||
After a few days of running this automation rule you come to realize that this automation rule is not good enough. It was already dark when the lights went on and the one day you weren't home, the lights turned on anyway. Time for some tweaking. Let's add an offset to the sunset trigger and a condition to only turn on the lights if anyone is home.
|
||||
|
||||
```yaml
|
||||
|
|
@ -86,6 +89,7 @@ group:
|
|||
|
||||
automation:
|
||||
alias: Turn on light when sun sets
|
||||
hide_entity: True
|
||||
trigger:
|
||||
platform: sun
|
||||
event: sunset
|
||||
|
|
|
|||
|
|
@ -49,19 +49,20 @@ homeassistant:
|
|||
| sensor_class | Description |
|
||||
| ------------ | ----------- |
|
||||
| cold | On means cold (or too cold) |
|
||||
| connectivity | On meanse connection present, Off means no connection
|
||||
| connectivity | On means connection present, Off means no connection
|
||||
| gas | CO, CO2, etc. |
|
||||
| heat | On means hot (or too hot) |
|
||||
| light | Lightness threshold |
|
||||
| moisture | Specifically a wetness sensor |
|
||||
| motion | Motion sensor |
|
||||
| moving | On means moving, Off means stopped |
|
||||
| occupancy | On means occupied, Off means not occupied |
|
||||
| opening | Door, window, etc. |
|
||||
| power | Power, over-current, etc. |
|
||||
| safety | On meanse unsafe, Off means safe |
|
||||
| safety | On means unsafe, Off means safe |
|
||||
| smoke | Smoke detector |
|
||||
| sound | On means sound detected, Off meanse no sound |
|
||||
| vibration | On means vibration detected, Off meanse no vibration |
|
||||
| sound | On means sound detected, Off means no sound |
|
||||
| vibration | On means vibration detected, Off means no vibration |
|
||||
|
||||
### {% linkable_title Reloading customize %}
|
||||
|
||||
|
|
|
|||
|
|
@ -37,7 +37,7 @@ To update Home Assistant to the latest release check the [Updating section](/get
|
|||
|
||||
### {% linkable_title Troubleshooting %}
|
||||
|
||||
If you run into any issues, please see [the troubleshooting page](/getting-started/troubleshooting/). It contains solutions to many of the common encountered issues.
|
||||
If you run into any issues, please see [the troubleshooting page](/getting-started/troubleshooting/). It contains solutions to many commonly encountered issues.
|
||||
|
||||
In addition to this site, check out these sources for additional help:
|
||||
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@
|
|||
layout: page
|
||||
title: "Raspberry Pi All-In-One Installer"
|
||||
date: 2016-05-12 01:39
|
||||
comments: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
---
|
||||
|
|
|
|||
|
|
@ -0,0 +1,71 @@
|
|||
---
|
||||
layout: page
|
||||
title: "Hassbian image for Raspberry Pi"
|
||||
description: "Instructions to flash the Home Assistant Hassbian image on a Raspberry Pi."
|
||||
date: 2016-09-26 21:00
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
---
|
||||
|
||||
The easiest way to install Home Assistant on your Raspberry Pi is by using Hassbian: a Raspberry Pi image with Home Assistant built-in. The image will install the latest version of Home Assistant on initial boot (~5 minutes).
|
||||
|
||||
1. [Download the latest image][image-download]
|
||||
2. Flash the image to an SD card:
|
||||
- [Windows][flash-windows]
|
||||
- [Linux][flash-linux]
|
||||
- [Mac][flash-macos]
|
||||
3. Ensure your Raspberry Pi has access to the internet.
|
||||
4. Insert SD card to Raspberry Pi and turn it on. Initial installation of Home Assistant will take 5 minutes.
|
||||
|
||||
These instructions are also available as a [video](https://www.youtube.com/watch?v=iIz6XqDwHEk).
|
||||
|
||||
Home Assistant will now be available by navigating with a browser to `http://ip-address-of-pi:8123`. The default username is `pi` and password is `raspberry` (please change this by running `passwd`)
|
||||
|
||||
The following extras are included on the image:
|
||||
|
||||
- GPIO pins are ready to use.
|
||||
- Mosquitto MQTT broker is installed (not activated by default).
|
||||
- Bluetooth is ready to use (supported models only, no Bluetooth LE).
|
||||
|
||||
Some extra tips:
|
||||
|
||||
- Check out the list of [Raspberry Pi hardware specific components][pi-components].
|
||||
- Z-Wave support can be installed by following the [Getting started instructions for Z-Wave](/getting-started/z-wave/).
|
||||
|
||||
### {% linkable_title Technical Details %}
|
||||
|
||||
- Home Assistant is installed in a virtual Python environment at `src/homeassistant`
|
||||
- Home Assistant will be started as a service run by the user `homeassistant`
|
||||
|
||||
{% comment %}
|
||||
|
||||
TODO:
|
||||
|
||||
Add instructions:
|
||||
|
||||
- How to login via shell (?) or at least mention how to work with a Pi
|
||||
- How to restart HASS
|
||||
- How to see the logs for config validation
|
||||
- How to update the config
|
||||
|
||||
{% endcomment %}
|
||||
|
||||
### {% linkable_title Troubleshooting %}
|
||||
|
||||
If you run into any issues, please see [the troubleshooting page](/getting-started/troubleshooting/). It contains solutions to many of the more commonly encountered issues.
|
||||
|
||||
In addition to this site, check out these sources for additional help:
|
||||
|
||||
- [Forum](https://community.home-assistant.io) for Home Assistant discussions and questions.
|
||||
- [Gitter Chat Room](https://gitter.im/home-assistant/home-assistant) for real-time chat about Home Assistant.
|
||||
- [GitHub Page](https://github.com/home-assistant/home-assistant/issues) for issue reporting.
|
||||
|
||||
### [Next step: Configuring Home Assistant »](/getting-started/configuration/)
|
||||
|
||||
[image-download]: https://github.com/home-assistant/pi-gen/releases
|
||||
[flash-linux]: https://www.raspberrypi.org/documentation/installation/installing-images/linux.md
|
||||
[flash-macos]: https://www.raspberrypi.org/documentation/installation/installing-images/mac.md
|
||||
[flash-windows]: https://www.raspberrypi.org/documentation/installation/installing-images/windows.md
|
||||
[pi-components]: /getting-started/installation-raspberry-pi/#raspberry-pi-hardware-specific-components
|
||||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
layout: page
|
||||
title: "Raspbian Lite on a Raspberry Pi"
|
||||
title: "Manual installation on a Raspberry Pi"
|
||||
description: "Instructions to install Home Assistant on a Raspberry Pi runnning Raspbian Lite."
|
||||
date: 2016-09-05 16:00
|
||||
sidebar: true
|
||||
|
|
@ -11,6 +11,14 @@ footer: true
|
|||
|
||||
### {% linkable_title Installation %}
|
||||
|
||||
There's currently three documented ways to install Home Assistant on a Raspberry Pi.
|
||||
- [Manual installation](/getting-started/installation-raspberry-pi/#Manual-Installation). Following this guide doing each step manually. This is highly recommended as a first installation since you get a good overview of the installation.
|
||||
- [Hassbian image](/getting-started/installation-raspberry-pi-image). Basic installation with the same settings as following the manual installation guide. Some additional software is preinstalled to make installation quicker and easier.
|
||||
- [All-in-One Installer](/getting-started/installation-raspberry-pi-all-in-one/). Fabric based installation script that installs and compiles many of the things an advanced Home Assistant install is likely to need.
|
||||
|
||||
|
||||
### {% linkable_title Manual Installation %}
|
||||
|
||||
This installation of Home Assistant requires the Raspberry Pi to run [Raspbian Lite](https://www.raspberrypi.org/downloads/raspbian/).
|
||||
The installation will be installed in a [Virtual Environment](/getting-started/installation-virtualenv) with minimal overhead. Instructions assume this is a new installation of Raspbian Lite.
|
||||
|
||||
|
|
|
|||
|
|
@ -29,7 +29,7 @@ One of the most common problems with Home Assistant is an invalid `configuration
|
|||
- You can verify your configuration's yaml structure using [this online YAML parser](http://yaml-online-parser.appspot.com/) or [YAML Lint](http://www.yamllint.com/).
|
||||
- To learn more about the quirks of YAML, read [YAML IDIOSYNCRASIES](https://docs.saltstack.com/en/latest/topics/troubleshooting/yaml_idiosyncrasies.html) by SaltStack (the examples there are specific to SaltStack, but do explain YAML issues well).
|
||||
|
||||
`configuration.yaml` does not allow multiple sections to have the same name. If you want to load multiplte platforms for one component, you can append a [number or string](/getting-started/devices/#style-2-list-each-device-separately) to the name or nest them using [this style](/getting-started/devices/#style-1-collect-every-entity-under-the-parent):
|
||||
`configuration.yaml` does not allow multiple sections to have the same name. If you want to load multiple platforms for one component, you can append a [number or string](/getting-started/devices/#style-2-list-each-device-separately) to the name or nest them using [this style](/getting-started/devices/#style-1-collect-every-entity-under-the-parent):
|
||||
|
||||
```yaml
|
||||
sensor:
|
||||
|
|
|
|||
|
|
@ -27,7 +27,16 @@ After updating, restart Home Assistant for the changes to take effect. This mean
|
|||
|
||||
[BRUH automation](http://www.bruhautomation.com) has created [a tutorial video](https://www.youtube.com/watch?v=tuG2rs1Cl2Y) explaining how to upgrade Home Assistant.
|
||||
|
||||
#### {% linkable_title Run a specific version %}
|
||||
|
||||
It can happen that a version doesn't play well with your hardware setup. If that's the case you can downgrade to a previous release.
|
||||
|
||||
```bash
|
||||
$ pip3 install homeassistant==0.XX.X
|
||||
```
|
||||
|
||||
#### {% linkable_title Run the development version %}
|
||||
|
||||
If you want to stay on top of the development of Home Assistant then you can upgrade to the `dev` branch.
|
||||
|
||||
<p class='note warning'>
|
||||
|
|
|
|||
|
|
@ -12,7 +12,7 @@ footer: true
|
|||
Z-Wave is a popular home automation protocol that is not always straightforward to setup. This page will try to help you make sense of it all.
|
||||
|
||||
<p class='note'>
|
||||
Upon first run, the `zwave` component will take time to initialize entities and entities may appear with incomplete names. Running a network heal may expidite this proccess.
|
||||
Upon first run, the `zwave` component will take time to initialize entities and entities may appear with incomplete names. Running a network heal may expedite this process.
|
||||
</p>
|
||||
|
||||
## {% linkable_title Supported Z-Wave USB Sticks & Hardware Modules %}
|
||||
|
|
|
|||
BIN
source/images/blog/2016-10-hacktoberfest/hacktoberfest.png
Normal file
BIN
source/images/blog/2016-10-hacktoberfest/hacktoberfest.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 73 KiB |
BIN
source/images/blog/2016-10-hacktoberfest/social.png
Normal file
BIN
source/images/blog/2016-10-hacktoberfest/social.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 558 KiB |
BIN
source/images/blog/2016-10-hassbian/social.png
Normal file
BIN
source/images/blog/2016-10-hassbian/social.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 141 KiB |
|
|
@ -15,11 +15,11 @@ hide_github_edit: true
|
|||
<div class="grid">
|
||||
<div class="grid__item one-third lap-one-third palm-one-whole">
|
||||
<div class='current-version material-card text'>
|
||||
<h1>Current Version: 0.29</h1>
|
||||
Released: <span class='release-date'>September 29, 2016</span>
|
||||
<h1>Current Version: 0.29.6</h1>
|
||||
Released: <span class='release-date'>October 1, 2016</span>
|
||||
|
||||
<div class='links'>
|
||||
<a href='/blog/2016/09/28/async-sleepiq-emoncms-stocks'>Release notes</a>
|
||||
<a href='/blog/2016/09/29/async-sleepiq-emoncms-stocks'>Release notes</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class='join-community material-card text'>
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue