mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-07-14 12:56:54 +00:00
Merge remote-tracking branch 'origin/current' into next
This commit is contained in:
Paulus Schoutsen
commit
ed3de4b595
@ -77,6 +77,8 @@ collections:
|
||||
output: true
|
||||
addons:
|
||||
output: true
|
||||
faq:
|
||||
output: true
|
||||
|
||||
# ----------------------- #
|
||||
# 3rd Party Settings #
|
||||
@ -141,12 +143,12 @@ social:
|
||||
# Home Assistant release details
|
||||
current_major_version: 0
|
||||
current_minor_version: 47
|
||||
current_patch_version: 0
|
||||
date_released: 2017-06-17
|
||||
current_patch_version: 1
|
||||
date_released: 2017-06-21
|
||||
|
||||
# Either # or the anchor link to latest release notes in the blog post.
|
||||
# Must be prefixed with a # and have double quotes around it.
|
||||
# Major release:
|
||||
patch_version_notes: "#"
|
||||
patch_version_notes: "#release-0471---june-21"
|
||||
# Minor release (Example #release-0431---april-25):
|
||||
|
||||
|
||||
@ -11,10 +11,6 @@ footer: true
|
||||
|
||||
Setup and manage a [Dnsmasq](http://thekelleys.org.uk/dnsmasq/doc.html) dns server. This allow your to manipulate some dns requests. I.e. that inside your network, your homeassistant domain will resolve with a internal address.
|
||||
|
||||
<p class='note warning'>
|
||||
At the moment, it will not work with resinos!
|
||||
</p>
|
||||
|
||||
```json
|
||||
{
|
||||
"defaults": ["8.8.8.8", "8.8.4.4"],
|
||||
@ -24,6 +20,7 @@ At the moment, it will not work with resinos!
|
||||
"hosts": [
|
||||
{"host": "home.mydomain.io", "ip": "192.168.1.10"}
|
||||
],
|
||||
"interface": "eth1"
|
||||
}
|
||||
```
|
||||
|
||||
@ -32,3 +29,4 @@ Configuration variables:
|
||||
- **defaults** (*Required*): A list of dns server to forward default requests.
|
||||
- **forwards** (*Optional*): A list of domains that will forward to a specific server.
|
||||
- **hosts** (*Optional*): A list of hosts to resolve it static.
|
||||
- **interface** (*Optional*): If a interface is set, it listen only on this interface. Need to set for resinos.
|
||||
|
||||
@ -13,7 +13,7 @@ featured: false
|
||||
ha_release: 0.44
|
||||
---
|
||||
|
||||
The `dlib_face_identify` image processing platform allows you to use the [Dlib](http://www.dlib.net/) through Home Assistant. This platform allow you do identify persons on camera and fire a event with identify persons.
|
||||
The `dlib_face_identify` image processing platform allows you to use the [Dlib](http://www.dlib.net/) through Home Assistant. This platform allow you to identify persons on camera and fire a event with identify persons.
|
||||
|
||||
For using the result inside an automation rule, take a look at the [component](/components/image_processing/) page.
|
||||
|
||||
|
||||
@ -43,3 +43,5 @@ hass.bus.fire(name, { "wow": "from a Python script!" })
|
||||
"name": "you"
|
||||
}
|
||||
```
|
||||
|
||||
For [`python_script:` examples](/components/python_script/) visit the [Scripts section](https://community.home-assistant.io/c/projects/scripts) in our forum.
|
||||
|
||||
@ -10,11 +10,11 @@ footer: true
|
||||
logo: buienradar.png
|
||||
ha_category: Weather
|
||||
ha_release: 0.47
|
||||
ha_iot_class: "Cloud Polling"
|
||||
---
|
||||
|
||||
|
||||
The `buienradar` platform uses [buienradar.nl](http://buienradar.nl/) as an source for current meteorological data for your location. The
|
||||
weather forecast is delivered by Buienradar, who provides a webservice that provides detailed weather information for users in The Netherlands.
|
||||
The `buienradar` platform uses [buienradar.nl](http://buienradar.nl/) as an source for current meteorological data for your location. The weather forecast is delivered by Buienradar, who provides a webservice that provides detailed weather information for users in The Netherlands.
|
||||
The relevant weatherstation used will be automatically selected based on the location specified in the Home Assistant configuration (or in the buienradar weather/sensor component).
|
||||
|
||||
To integrate `buienradar` with Home Assistant, add the following section to your `configuration.yaml` file:
|
||||
@ -33,11 +33,10 @@ sensor:
|
||||
|
||||
Configuration variables:
|
||||
|
||||
- **platform** (*Required*): buienradar.
|
||||
- **latitude** (*Optional*): latitude to use for selection of data source location. Longitude & latitude will be taken from Home Assistant configuration, but can be overridden/changed in this component to select a different location for buienradar.
|
||||
- **longitude** (*Optional*): longitude to use for selection of data source location. Longitude & latitude will be taken from Home Assistant configuration, but can be overridden/changed in this component to select a different location for buienradar.
|
||||
- **monitored_conditions** array (*Required*): one or more conditions to display in the frontend.
|
||||
- **stationname**: the name of the selected meteo-station.
|
||||
- **latitude** (*Optional*): Latitude to use for selection of data source location. Longitude and latitude will be taken from Home Assistant configuration, but can be overridden/changed in this component to select a different location for buienradar.
|
||||
- **longitude** (*Optional*): Longitude to use for selection of data source location. Longitude & latitude will be taken from Home Assistant configuration, but can be overridden/changed in this component to select a different location for buienradar.
|
||||
- **monitored_conditions** array (*Required*): One or more conditions to display in the frontend.
|
||||
- **stationname**: The name of the selected meteo-station.
|
||||
- **symbol**: A symbol for the current weather.
|
||||
- **humidity**: The relative humidity (%).
|
||||
- **temperature**: The current temperature (in C).
|
||||
@ -45,11 +44,11 @@ Configuration variables:
|
||||
- **windspeed**: The wind speed in m/s.
|
||||
- **windforce**: The wind speed/force in Bft.
|
||||
- **winddirection**: Where the wind is coming from in degrees, with true north at 0° and progressing clockwise.
|
||||
- **windazimuth**: Where the wind is coming from: N (North),Z (south), NO (Noth-East), etc..
|
||||
- **windazimuth**: Where the wind is coming from: N (North),Z (south), NO (Noth-East), etc.
|
||||
- **pressure**: The sea-level air pressure in hPa.
|
||||
- **visibility**: Visibility in meters (m).
|
||||
- **windgust**: The windspeed of wind gusts (m/s).
|
||||
- **precipitation**: the amount of precipitation/rain in mm/h.
|
||||
- **precipitation**: The amount of precipitation/rain in mm/h.
|
||||
- **irradiance**: Sun intensity in Watt per square meter (W/m2).
|
||||
|
||||
Full configuration example where location is manually specified:
|
||||
|
||||
@ -15,7 +15,7 @@ ha_release: 0.47
|
||||
|
||||
This `radarr` sensor platform pulls data from a given Radarr instance.
|
||||
|
||||
To use your [Radarr](https://radarr.tv/) sensor in your installation, add the following to your `configuration.yaml` file:
|
||||
To use your [Radarr](https://radarr.video/) sensor in your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yml entry
|
||||
|
||||
@ -10,10 +10,10 @@ footer: true
|
||||
logo: buienradar.png
|
||||
ha_category: Weather
|
||||
ha_release: 0.47
|
||||
ha_iot_class: "Cloud Polling"
|
||||
---
|
||||
|
||||
The `buienradar` platform uses [buienradar.nl](http://buienradar.nl/) as an source for current meteorological data for your location. The
|
||||
weather forecast is delivered by Buienradar, who provides a webservice that provides detailed weather information for users in The Netherlands.
|
||||
The `buienradar` platform uses [buienradar.nl](http://buienradar.nl/) as an source for current meteorological data for your location. The weather forecast is delivered by Buienradar, who provides a webservice that provides detailed weather information for users in The Netherlands.
|
||||
The relevant weatherstation used will be automatically selected based on the location specified in the Home Assistant configuration (or in the buienradar weather/sensor component).
|
||||
|
||||
To add the buienradar weather to your installation, add the following to your `configuration.yaml` file:
|
||||
@ -25,15 +25,16 @@ weather:
|
||||
```
|
||||
|
||||
Configuration variables:
|
||||
- **platform** (*Required*): buienradar
|
||||
- **latitude** (*Optional*): latitude to use for selection of data source location. Longitude & latitude will be taken from Home Assistant configuration, but can be overridden/changed in this component to select a different location for buienradar.
|
||||
- **longitude** (*Optional*): longitude to use for selection of data source location. Longitude & latitude will be taken from Home Assistant configuration, but can be overridden/changed in this component to select a different location for buienradar.
|
||||
- **forecast** (*Optional*): 'True' to add a temperature forecast, 'False' to suppress it
|
||||
|
||||
- **latitude** (*Optional*): Latitude to use for selection of data source location. Longitude & latitude will be taken from Home Assistant configuration, but can be overridden/changed in this component to select a different location for buienradar.
|
||||
- **longitude**(*Optional*): Longitude to use for selection of data source location. Longitude & latitude will be taken from Home Assistant configuration, but can be overridden/changed in this component to select a different location for buienradar.
|
||||
- **forecast** (*Optional*): 'True' to add a temperature forecast, 'False' to suppress it.
|
||||
|
||||
|
||||
A full configuration example:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
weather:
|
||||
- platform: buienradar
|
||||
name: buienradar
|
||||
|
||||
@ -17,7 +17,6 @@ Home Assistant contains a few built-in events that are used to coordinate betwee
|
||||
### {% linkable_title Event `homeassistant_start` %}
|
||||
Event `homeassistant_start` is fired when all components from the configuration have been intitialized. This is the event that will start the timer firing off `time_changed` events.
|
||||
|
||||
|
||||
### {% linkable_title Event `homeassistant_stop` %}
|
||||
Event `homeassistant_stop` is fired when Home Assistant is shutting down. It should be used to close any open connection or release any resources.
|
||||
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
layout: page
|
||||
title: "Installation on FreeNAS 9.10"
|
||||
description: "Installation of Home Assistant on your FreeNAS."
|
||||
date: 2017-04-06 17:00
|
||||
date: 2017-06-20 11:00
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
@ -29,10 +29,20 @@ Install Home Assistant itself.
|
||||
# pip3 install homeassistant
|
||||
```
|
||||
|
||||
Finally start Home Assistant.
|
||||
Create an `/etc/rc.local` file to enable Home Assistant to start when the jail starts. The command in `/etc/rc.local` can also be run in a terminal session but Home Assistant will exit when that session is closed.
|
||||
|
||||
```bash
|
||||
# hass --open-ui
|
||||
# /usr/local/bin/hass --open-ui --config /home/.homeassistant/ &
|
||||
```
|
||||
|
||||
Some suggestions on using a tmux to keep it running can be found in the FreeNAS forums [HERE](https://forums.freenas.org/index.php?threads/how-to-home-assistant-in-a-jail-tested-on-9-10.50371/)
|
||||
Make `/etc/rc.local` executable so it runs on startup
|
||||
|
||||
```bash
|
||||
# chmod 755 /etc/rc.local
|
||||
```
|
||||
|
||||
Finally restart the jail from the Freenas GUI.
|
||||
|
||||
<p class='note'>
|
||||
USB Z-wave sticks may give `dmesg` warnings similar to "data interface 1, has no CM over data, has no break". This doesn't impact the function of the Z-wave stick in Hass. Just make sure the proper `/dev/cu*` is used in the Home Assistant `configuration.yaml` file.
|
||||
</p>
|
||||
|
||||
@ -31,9 +31,13 @@ Home Assistant contains an embedded MQTT broker. If no broker configuration is g
|
||||
mqtt:
|
||||
```
|
||||
|
||||
<p class='note'>
|
||||
This broker does not currently work with OwnTracks because of a protocol version issue.
|
||||
</p>
|
||||
### {% linkable_title Owntracks%}
|
||||
|
||||
To use Owntracks with the internal broker a small configuration change must be made in order for the app to use MQTT protocol 3.1.1 (Protocol Level 4).
|
||||
|
||||
In the Owntracks preferences (Android: v1.2.3+, iOS: v9.5.1+) open **Configuration Management**; Find the value named `mqttProtocolLevel` and set the value to `4`. The application will now use MQTT 3.1.1 to connect, which is compatible with the embedded broker.
|
||||
|
||||
### {% linkable_title Settings %}
|
||||
|
||||
If you want to customize the settings of the embedded broker, use `embedded:` and the values shown in the [HBMQTT Broker configuration](http://hbmqtt.readthedocs.org/en/latest/references/broker.html#broker-configuration). This will replace the default configuration.
|
||||
|
||||
|
||||
@ -37,7 +37,7 @@ $ hass --script keyring
|
||||
|
||||
### {% linkable_title Benchmark %}
|
||||
|
||||
For testing the performance of Home Assistant the Benchmark scipt runs until you exit using Control+C.
|
||||
For testing the performance of Home Assistant the Benchmark script runs until you exit using Control+C.
|
||||
|
||||
Firing and handling of a million events.
|
||||
|
||||
|
||||
@ -154,7 +154,7 @@ Example:
|
||||
platform: event
|
||||
event_type: zwave.node_event
|
||||
event_data:
|
||||
object_id: aeon_labs_minimote_1
|
||||
entity_id: zwave.aeon_labs_minimote_1
|
||||
basic_level: 255
|
||||
```
|
||||
|
||||
@ -172,7 +172,7 @@ automation:
|
||||
platform: event
|
||||
event_type: zwave.scene_activated
|
||||
event_data:
|
||||
object_id: zwaveme_zme_wallcs_secure_wall_controller_8
|
||||
entity_id: zwave.zwaveme_zme_wallcs_secure_wall_controller_8
|
||||
scene_id: 11
|
||||
```
|
||||
|
||||
|
||||
16
source/_faq/after-upgrading.markdown
Normal file
16
source/_faq/after-upgrading.markdown
Normal file
@ -0,0 +1,16 @@
|
||||
---
|
||||
layout: page
|
||||
title: "After upgrading, your browser login gets stuck"
|
||||
description: "After upgrading, your browser login gets stuck"
|
||||
date: 2017-06-18 09:00
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
ha_category: Usage
|
||||
---
|
||||
|
||||
|
||||
After upgrading to a new version, you may notice your browser gets stuck at the "loading data" login screen. Close the window/tab and go into your browser settings and delete all the cookies for your URL. You can then log back in and it should work.
|
||||
|
||||
Android Chrome
|
||||
chrome -> settings -> site settings -> storage -> search for your URL for home assistant-> "clear & reset"
|
||||
15
source/_faq/component.markdown
Normal file
15
source/_faq/component.markdown
Normal file
@ -0,0 +1,15 @@
|
||||
---
|
||||
layout: page
|
||||
title: "My component does not show up"
|
||||
description: "My component does not show up"
|
||||
date: 2017-06-18 09:00
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
ha_category: Configuration
|
||||
---
|
||||
|
||||
|
||||
When a component does not show up, many different things can be the case. Before you try any of these steps, make sure to look at the `home-assistant.log` file and see if there are any errors related to your component you are trying to set up.
|
||||
|
||||
If you have incorrect entries in your configuration files you can use the `check_config` script to assist in identifying them: `hass --script check_config`.
|
||||
19
source/_faq/connection-error.markdown
Normal file
19
source/_faq/connection-error.markdown
Normal file
@ -0,0 +1,19 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Connection error"
|
||||
description: "Connection error"
|
||||
date: 2017-06-18 09:00
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
ha_category: Usage
|
||||
---
|
||||
|
||||
|
||||
It can happen that you get a traceback that notify you about connection issues while running Home Assistant. Eg.
|
||||
|
||||
```bash
|
||||
ConnectionRefusedError: [Errno 111] Connection refused
|
||||
```
|
||||
|
||||
The chance is very high that this is not a bug but an issue with the service/daemon itself. Check your network (DNS, DHCP, uplink, etc.) first and make sure that Home Assistant and the service are poperly configured. Keep in mind that webservices can be down.
|
||||
13
source/_faq/dependencies.markdown
Normal file
13
source/_faq/dependencies.markdown
Normal file
@ -0,0 +1,13 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Dependencies"
|
||||
description: "Dependencies"
|
||||
date: 2017-06-18 09:00
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
ha_category: Usage
|
||||
---
|
||||
|
||||
The dependencies which are used by Home Assistant are stored in the folder `deps` of the [configuration folder](/docs/configuration/) directory. After an [upgrade](/docs/installation/updating/) the dependences will be upgraded as well.
|
||||
|
||||
12
source/_faq/distutils.markdown
Normal file
12
source/_faq/distutils.markdown
Normal file
@ -0,0 +1,12 @@
|
||||
---
|
||||
layout: page
|
||||
title: "distutils.errors.DistutilsOptionError"
|
||||
description: "distutils.errors.DistutilsOptionError: must supply either home or prefix/exec-prefix -- not both"
|
||||
date: 2017-06-18 09:00
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
ha_category: Installation
|
||||
---
|
||||
|
||||
The problem which leads to `distutils.errors.DistutilsOptionError: must supply either home or prefix/exec-prefix -- not both` is a known issue if you're on a Mac using Homebrew to install Python. Please follow [these instructions](https://github.com/Homebrew/brew/blob/master/docs/Homebrew-and-Python.md#note-on-pip-install---user) to resolve it.
|
||||
13
source/_faq/libyaml.markdown
Normal file
13
source/_faq/libyaml.markdown
Normal file
@ -0,0 +1,13 @@
|
||||
---
|
||||
layout: page
|
||||
title: "libyaml is not found or a compiler error"
|
||||
description: "libyaml is not found or a compiler error"
|
||||
date: 2017-06-18 09:00
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
ha_category: Installation
|
||||
---
|
||||
|
||||
|
||||
On a Debian system, install the Python 3 YAML library by `sudo apt-get install python3-yaml`.
|
||||
16
source/_faq/missing-documentation.markdown
Normal file
16
source/_faq/missing-documentation.markdown
Normal file
@ -0,0 +1,16 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Missing Documentation"
|
||||
description: "The docs are missing or outdated"
|
||||
date: 2017-06-18 09:00
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
ha_category: Documentation
|
||||
---
|
||||
|
||||
|
||||
Home Assistant is a FAST moving open source project. This means occasionally the official documentation will not be 100% current or complete. Since this is an open source volunteer project, we would encourage anyone who finds gaps in the documentation to click the `edit this page on Github` link in the top right and submit any corrections/enhancements they may find useful.
|
||||
|
||||
In the absence of information, many users find it beneficial to look at other people's configurations to find examples of what they want to accomplish in thier own configurations. The easiest way to find these configurations is through this [Github search](https://github.com/search?q=topic%3Ahome-assistant-config&type=Repositories).
|
||||
17
source/_faq/pip.markdown
Normal file
17
source/_faq/pip.markdown
Normal file
@ -0,0 +1,17 @@
|
||||
---
|
||||
layout: page
|
||||
title: "No module named pip"
|
||||
description: "No module named pip"
|
||||
date: 2017-06-18 09:00
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
ha_category: Installation
|
||||
---
|
||||
|
||||
|
||||
[Pip](https://pip.pypa.io/en/stable/) should come bundled with the latest Python 3 but is omitted by some distributions. If you are unable to run `python3 -m pip --version` you can install `pip` by [downloading the installer](https://bootstrap.pypa.io/get-pip.py) and running it with Python 3:
|
||||
|
||||
```bash
|
||||
$ python3 get-pip.py
|
||||
```
|
||||
21
source/_faq/pip3.markdown
Normal file
21
source/_faq/pip3.markdown
Normal file
@ -0,0 +1,21 @@
|
||||
---
|
||||
layout: page
|
||||
title: "pip3: command not found"
|
||||
description: "pip3: command not found"
|
||||
date: 2017-06-18 09:00
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
ha_category: Installation
|
||||
---
|
||||
|
||||
|
||||
This utility should have been installed as part of the Python 3.4 installation. Check if Python 3.4 is installed by running `python3 --version`. If it is not installed, [download it here](https://www.python.org/getit/).
|
||||
|
||||
If you are able to successfully run `python3 --version` but not `pip3`, install Home Assistant by running the following command instead:
|
||||
|
||||
```bash
|
||||
$ python3 -m pip install homeassistant
|
||||
```
|
||||
|
||||
On a Debian system, you can also install python3 by `sudo apt-get install python3`d and pip3 by `sudo apt-get install python3-pip`.
|
||||
14
source/_faq/problems-with-dependencies.markdown
Normal file
14
source/_faq/problems-with-dependencies.markdown
Normal file
@ -0,0 +1,14 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Problems with dependencies"
|
||||
description: "Problems with dependencies"
|
||||
date: 2017-06-18 09:00
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
ha_category: Usage
|
||||
---
|
||||
|
||||
Almost all components have external dependencies to communicate with your devices and services. Sometimes Home Assistant is unable to install the necessary dependencies. If this is the case, it should show up in `home-assistant.log`.
|
||||
|
||||
The first step is trying to restart Home Assistant and see if the problem persists. If it does, look at the log to see what the error is. If you can't figure it out, please [report it](https://github.com/home-assistant/home-assistant/issues) so we can investigate what is going on.
|
||||
@ -3,7 +3,10 @@
|
||||
<h1 class="title delta">Topics</h1>
|
||||
<ul class='divided sidebar-menu'>
|
||||
<li>
|
||||
{% active_link /docs/installation/ Installation %}
|
||||
<b>{% active_link /faq/ FAQ %}</b>
|
||||
</li>
|
||||
<li>
|
||||
<b>{% active_link /docs/installation/ Installation %}</b>
|
||||
<ul>
|
||||
<li>{% active_link /docs/installation/virtualenv/ Python Virtual Env %}</li>
|
||||
<li>{% active_link /docs/installation/raspberry-pi-all-in-one/ Raspberry Pi All-in-One %}</li>
|
||||
@ -12,7 +15,7 @@
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
{% active_link /docs/hassbian/ Hassbian %}
|
||||
<b>{% active_link /docs/hassbian/ Hassbian %}</b>
|
||||
<ul>
|
||||
<li>{% active_link /docs/hassbian/installation/ Installation %}</li>
|
||||
<li>{% active_link /docs/hassbian/customization/ Customization %}</li>
|
||||
@ -22,7 +25,7 @@
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
{% active_link /docs/configuration/ Configuration %}
|
||||
<b>{% active_link /docs/configuration/ Configuration %}</b>
|
||||
<ul>
|
||||
<li>{% active_link /docs/configuration/yaml/ YAML %}</li>
|
||||
<li>{% active_link /docs/configuration/basic/ Basic information %}</li>
|
||||
@ -33,7 +36,7 @@
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
Advanced Configuration
|
||||
<b>Advanced Configuration</b>
|
||||
<ul>
|
||||
<li>{% active_link /docs/configuration/remote/ Remote access %}</li>
|
||||
<li>{% active_link /docs/configuration/packages/ Packages %}</li>
|
||||
@ -45,14 +48,14 @@
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
Core objects
|
||||
<b>Core objects</b>
|
||||
<ul>
|
||||
<li>{% active_link /docs/configuration/events/ Events %}</li>
|
||||
<li>{% active_link /docs/configuration/state_object/ State Objects %}</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
{% active_link /docs/automation/ Automation %}
|
||||
<b>{% active_link /docs/automation/ Automation %}</b>
|
||||
<ul>
|
||||
<li>{% active_link /docs/automation/examples/ Examples %}</li>
|
||||
<li>{% active_link /docs/automation/editor/ Editor %}</li>
|
||||
@ -63,7 +66,7 @@
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
{% active_link /docs/frontend/ Frontend %}
|
||||
<b>{% active_link /docs/frontend/ Frontend %}</b>
|
||||
<ul>
|
||||
<li>{% active_link /docs/frontend/mobile/ Android/iOS Homescreen %}</li>
|
||||
<li>{% active_link /docs/frontend/webserver/ Web server fingerprint %}</li>
|
||||
@ -71,7 +74,7 @@
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
{% active_link /docs/backend/ Backend %}
|
||||
<b>{% active_link /docs/backend/ Backend %}</b>
|
||||
<ul>
|
||||
<li>{% active_link /docs/backend/database/ Database %}</li>
|
||||
<li>{% active_link /docs/backend/updater/ Updater %}</li>
|
||||
@ -79,14 +82,14 @@
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
{% active_link /docs/scripts/ Scripts %}
|
||||
<b>{% active_link /docs/scripts/ Scripts %}</b>
|
||||
<ul>
|
||||
<li>{% active_link /docs/scripts/service-calls/ Service Calls %}</li>
|
||||
<li>{% active_link /docs/scripts/conditions/ Conditions %}</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
{% active_link /docs/tools/ Tools and Helpers %}
|
||||
<b>{% active_link /docs/tools/ Tools and Helpers %}</b>
|
||||
<ul>
|
||||
<li>{% active_link /docs/tools/dev-tools/ Developer Tools %}</li>
|
||||
<li>{% active_link /docs/tools/hass/ hass %}</li>
|
||||
@ -94,7 +97,7 @@
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
{% active_link /docs/z-wave/ Z-Wave %}
|
||||
<b>{% active_link /docs/z-wave/ Z-Wave %}</b>
|
||||
<ul>
|
||||
<li>{% active_link /docs/z-wave/controllers/ Controllers %}</li>
|
||||
<li>{% active_link /docs/z-wave/settings/ Modifying Settings %}</li>
|
||||
@ -102,7 +105,7 @@
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
{% active_link /docs/mqtt/ MQTT %}
|
||||
<b>{% active_link /docs/mqtt/ MQTT %}</b>
|
||||
<ul>
|
||||
<li>{% active_link /docs/mqtt/broker/ Broker %}</li>
|
||||
<li>{% active_link /docs/mqtt/certificate/ Certificate %}</li>
|
||||
@ -115,7 +118,7 @@
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
{% active_link /docs/ecosystem/ios/ iOS %}
|
||||
<b>{% active_link /docs/ecosystem/ios/ iOS %}</b>
|
||||
<ul>
|
||||
<li>{% active_link /docs/ecosystem/ios/notifications/basic/ Basic notifications %}</li>
|
||||
<ul>
|
||||
|
||||
22
source/_includes/asides/faq_navigation.html
Normal file
22
source/_includes/asides/faq_navigation.html
Normal file
@ -0,0 +1,22 @@
|
||||
<section class="aside-module grid__item one-whole lap-one-half">
|
||||
<div class='section'>
|
||||
<h1 class="title delta">Entries</h1>
|
||||
<ul class='divided sidebar-menu'>
|
||||
{% assign faq = site.faq | sort: 'title' %}
|
||||
{% assign categories = faq | map: 'ha_category' | uniq | sort %}
|
||||
|
||||
{% for category in categories %}
|
||||
<li>
|
||||
<b>{{ category }}</b>
|
||||
<ul>
|
||||
{% for entry in faq %}
|
||||
{% if entry.ha_category == category %}
|
||||
<li><a href='/faq#{{ entry.title | slugify }}'>{{ entry.title}}</a></li>
|
||||
{% endif %}
|
||||
{% endfor %}
|
||||
</ul>
|
||||
</li>
|
||||
{% endfor %}
|
||||
</ul>
|
||||
</div>
|
||||
</section>
|
||||
@ -10,6 +10,8 @@
|
||||
{% include asides/getting_started_navigation.html | compact_newlines %}
|
||||
{% elsif url_parts[1] == 'docs' %}
|
||||
{% include asides/docs_navigation.html | compact_newlines %}
|
||||
{% elsif url_parts[1] == 'faq' %}
|
||||
{% include asides/faq_navigation.html | compact_newlines %}
|
||||
{% elsif url_parts[1] == 'hassio' or url_parts[1] == 'addons' %}
|
||||
{% include asides/hassio_navigation.html | compact_newlines %}
|
||||
{% else %}
|
||||
|
||||
@ -42,6 +42,30 @@ Z-Wave is also getting a big update in this release. The confusing entity_ids wi
|
||||
6. Restart Home Assistant to run with new IDs.
|
||||
7. The old entity IDs will be available in the more info dialog to trace down any remaining errors.
|
||||
|
||||
## {% linkable_title Monkey Patching Python 3.6 %}
|
||||
|
||||
Some people have noticed that running Home Assistant under Python 3.6 can lead to segfaults. It seems to be related to the [earlier segfault issues][old-bug] that we experienced when we released the asyncio-based core. We thought that those issues would have been fixed when [Python bug 26617] was resolved. Although we see less reports compared to the old bug, there are still users [experiencing them][new-bug] ([gdb stacktrace points at `PyObject_GC_Del()`][gdb]).
|
||||
|
||||
Since Python 3.6, the Task and Future classes have been moved to C. This gives a nice speed boost but also prevents us from monkey patching the Task class to avoid the segfault. [Ben Bangert] managed to brew up another monkey patch to stop Python 3.6 from using the C classes, falling back to the Python versions instead. This allows us to apply the original monkey patch again.
|
||||
|
||||
Both monkey patches are now active by default starting version 0.47 to avoid our users experiencing segfaults. This comes at a cost of not being able to benefit from all optimizations that were introduced in Python 3.6.
|
||||
|
||||
To run without the monkey patch, start Home Assistant with `HASS_NO_MONKEY=1 hass`. We will further investigate this issue and try to fix it in a future version of Python.
|
||||
|
||||
[old-bug]: https://github.com/home-assistant/home-assistant/issues/3453
|
||||
[Python bug 26617]: https://bugs.python.org/issue26617
|
||||
[new-bug]: https://github.com/home-assistant/home-assistant/issues/7752
|
||||
[gdb]: https://github.com/home-assistant/home-assistant/issues/7752#issuecomment-305100009
|
||||
[Ben Bangert]: https://github.com/bbangert
|
||||
|
||||
## {% linkable_title Release 0.47.1 - June 21 %}
|
||||
|
||||
- Fix Vera lights issue #8098 ([@tsvi] - [#8101]) ([light.vera docs])
|
||||
- Fix Dyson async_add_job ([@CharlesBlonde] - [#8113]) ([fan.dyson docs]) ([sensor.dyson docs])
|
||||
- Update InfluxDB to handle datetime objects and multiple decimal points ([@philhawthorne] - [#8080]) ([influxdb docs])
|
||||
- Fixed iTach command parsing with empty data ([@alanfischer] - [#8104]) ([remote.itach docs])
|
||||
- Allow iteration in python_script ([@balloob] - [#8134]) ([python_script docs])
|
||||
|
||||
## {% linkable_title New platforms %}
|
||||
|
||||
- Added a Taps Aff binary sensor ([@bazwilliams] - [#7880]) ([binary_sensor.tapsaff docs]) (new-platform)
|
||||
@ -109,6 +133,28 @@ notify:
|
||||
recipient: !secret mailgun_recipient
|
||||
```
|
||||
|
||||
- Z-Wave node and scene activated trigger events now use the full entity ID ([@armills] - [#7786]) ([zwave docs]) (breaking change)
|
||||
```yaml
|
||||
automation:
|
||||
- alias: Button 1
|
||||
trigger:
|
||||
platform: event
|
||||
event_type: zwave.scene_activated
|
||||
event_data:
|
||||
entity_id: living_room_remote_13
|
||||
scene_id: 1
|
||||
```
|
||||
```yaml
|
||||
automation:
|
||||
- alias: Event 1
|
||||
trigger:
|
||||
platform: event
|
||||
event_type: zwave.node_event
|
||||
event_data:
|
||||
entity_id: zwave.living_room_remote_13
|
||||
basic_level: 1
|
||||
```
|
||||
|
||||
- LIFX: add multiple modes to pulse effect. The `lifx_effect_breathe` call has been deprecated. Use `lifx_effect_pulse` with the new `mode: breathe` attribute instead. ([@amelchio] - [#8016]) ([light.lifx docs]) (breaking change)
|
||||
- Use standard entity_ids for zwave entities. This also introduces a small API breakage, where `EVENT_SCENE_ACTIVATED` and `EVENT_NODE_EVENT` will no longer supply an `object_id`. They will now be tied to the node entity_id. ([@armills] - [#7786]) ([zwave docs]) ([light.zwave docs]) (breaking change)
|
||||
- Fix attribute entities. Home Assistant will no longer filter out entities that are 'falsey'. So you might see more entity attributes show up. ([@pvizeli] - [#8066]) (breaking change)
|
||||
@ -520,3 +566,12 @@ notify:
|
||||
[gitter]: https://gitter.im/home-assistant/home-assistant
|
||||
[issue]: https://github.com/home-assistant/home-assistant/issues
|
||||
[first-commit]: https://home-assistant.io/help/trivia/#first-commit
|
||||
[#8080]: https://github.com/home-assistant/home-assistant/pull/8080
|
||||
[#8101]: https://github.com/home-assistant/home-assistant/pull/8101
|
||||
[#8104]: https://github.com/home-assistant/home-assistant/pull/8104
|
||||
[#8113]: https://github.com/home-assistant/home-assistant/pull/8113
|
||||
[#8134]: https://github.com/home-assistant/home-assistant/pull/8134
|
||||
[@tsvi]: https://github.com/tsvi
|
||||
[fan.dyson docs]: https://home-assistant.io/components/fan.dyson/
|
||||
[remote.itach docs]: https://home-assistant.io/components/remote.itach/
|
||||
[sensor.dyson docs]: https://home-assistant.io/components/sensor.dyson/
|
||||
|
||||
@ -0,0 +1,63 @@
|
||||
---
|
||||
layout: post
|
||||
title: "[Update: fixed] A frank and serious warning about Senic COVI"
|
||||
description: "The picture painted by Senic COVI is not as great as it seems."
|
||||
date: 2017-06-20 01:04:05 +0000
|
||||
date_formatted: "June 20, 2017"
|
||||
author: Paulus Schoutsen & Robbie Trencheny
|
||||
author_twitter: balloob
|
||||
comments: true
|
||||
categories: Public-Service-Announcement
|
||||
---
|
||||
|
||||
**Update June 21:** Senic has removed our name from their materials and have [issued an apology][apology]. We wish them best of luck with the launch of COVI.
|
||||
|
||||
*Original post:*
|
||||
|
||||
<!--more-->
|
||||
<p class='note'>
|
||||
TL;DR: We are not affiliated with Senic or their COVI product. We will not support their users and you will get a subpar Home Assistant experience by using their product. **Furthermore, we cannot guarantee stability or security if you use Senic products.**
|
||||
</p>
|
||||
|
||||
Recently Home Assistant has been made aware of a product by [Senic] that will be launching later today on [Kickstarter][kickstarter] ([screenshot][ks-backup]). Senic is not new in the IoT business, we have had support for their first product ([Nuimo]) since last September. Their new product, COVI, uses Home Assistant as its core home automation codebase. This is great, that is what open source is all about. However, they also use our name and logo in their Kickstarter, with the press and in their [developer documentation] ([screenshot][docs-backup]) to give the appearance of being affiliated with Home Assistant, against our wishes. Which is not great, at all.
|
||||
|
||||
Take some of the following quotes from their Kickstarter campaign:
|
||||
|
||||
> COVI is built on an open source platform. The Senic team, along with outside developers, contributes to this platform to create the integrations for COVI.
|
||||
|
||||
> With COVI, we have built upon an open platform called Home Assistant that anyone can contribute to alongside our engineers and the Home Assistant community.
|
||||
|
||||
Although those quotes are technically correct, they are very misleading. The Senic team contributes only to their own platform, they have not contributed to Home Assistant, its integrations or related projects. We did receive [1 contribution][netdisco-contrib] from them for [Netdisco], our network discovery package. It included a memory leak and required us to publish [a hotfix release][hotfix] for the 0.39 series. Their contribution has since been reverted. A third party contributor had contributed support for their Nuimo controller.
|
||||
|
||||
Here is a quote that their CEO Tobias Eichenwald gave [to Forbes]:
|
||||
|
||||
> Unlike many larger companies who build closed automation platforms, COVI is built on an open source platform called Home Assistant that includes 500+ contributors. This allows COVI to be integrated into any ecosystem or platform with an open API.
|
||||
|
||||
They reached out to us on April 7 ([screenshot][email-backup]). We replied on April 11 and told them they should not use our name as we do not want to be affiliated with them because we do not want to support their users. After that one e-mail we had never heard from them again until Forbes accidentally published an article about it before the Kickstarter launched. We did not get any chance to give feedback on their Kickstarter campaign content and they went ahead and used our name and logo without authorization or permission.
|
||||
|
||||
If you want an open source and constantly evolving product, get yourself a $35 Raspberry Pi, install our hub [Hass.io] for free and buy yourself some cheap and reliable [IKEA Trådfri lights][tradfri] to get yourself a basic home automation setup. If you want a $250 talking lamp, go buy the COVI. Just know that we are not affiliated with Senic, we will not support their users and you will get a subpar Home Assistant experience by using their product. **Furthermore, we cannot guarantee stability or security if you use Senic products.**
|
||||
|
||||
Senic, we know that this is probably not what you wanted to wake up to on the first day of your Kickstarter but you left us no choice. Please reach out to us to help make this right. **We will always do everything in our power to protect the best interests of the Home Assistant community, <span style='text-decoration: underline;'>our</span> 500+ contributors and 250,000+ users.** If we don't hear from you by Wednesday, June 21st, we will be forced to consider further actions.
|
||||
|
||||
Sincerely,
|
||||
|
||||
**Paulus Schoutsen**<br>
|
||||
Founder, Home Assistant
|
||||
|
||||
**Robbie Trencheny**<br>
|
||||
Core Developer, Home Assistant
|
||||
|
||||
[Senic]: https://www.senic.com/en/
|
||||
[kickstarter]: https://www.kickstarter.com/projects/802159142/1793705123?token=03dc08b4#
|
||||
[ks-backup]: /images/blog/2017-06-senic-covi/covi-kickstarter-screenshot.png
|
||||
[email-backup]: /images/blog/2017-06-senic-covi/email-senic.png
|
||||
[docs-backup]: /images/blog/2017-06-senic-covi/senic-docs-screenshot.png
|
||||
[Netdisco]: https://github.com/home-assistant/netdisco
|
||||
[netdisco-contrib]: https://github.com/home-assistant/netdisco/pull/94
|
||||
[hotfix]: /blog/2017/02/25/config-panel-and-state-restoration/#release-0392---march-1
|
||||
[Hass.io]: /hassio/
|
||||
[to Forbes]: https://webcache.googleusercontent.com/search?q=cache:https://www.forbes.com/sites/paularmstrongtech/2017/06/19/covi-is-about-to-make-some-general-electric-execs-very-unhappy/
|
||||
[tradfri]: /blog/2017/04/17/ikea-tradfri-internet-of-things-done-right/
|
||||
[Nuimo]: /components/nuimo_controller/
|
||||
[developer documentation]: http://blog.senic.com/posts/the-senic-hub-a-brief-software-overview
|
||||
[apology]: https://medium.com/@senic/an-open-letter-to-home-assistant-5ccb53ccf722
|
||||
@ -13,6 +13,8 @@ hide_github_edit: true
|
||||
|
||||
This is a community curated list of different ways to use Home Assistant. Most of these examples are using the [automation] component and other built-in [automation related][sec-automation] and [organization] components available.
|
||||
|
||||
For [`python_script:` examples](/components/python_script/) visit the [Scripts section](https://community.home-assistant.io/c/projects/scripts) in our forum.
|
||||
|
||||
[automation]: /getting-started/automation/
|
||||
[sec-automation]: /components/#automation
|
||||
[organization]: /components/#organization
|
||||
|
||||
29
source/faq/index.markdown
Normal file
29
source/faq/index.markdown
Normal file
@ -0,0 +1,29 @@
|
||||
---
|
||||
layout: page
|
||||
title: "FAQ"
|
||||
description: "Home Assistant's FAQ"
|
||||
date: 2015-10-08 19:05
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
regenerate: true
|
||||
hide_github_edit: true
|
||||
---
|
||||
|
||||
This is a community curated list of frequently asked questions (FAQ) about the installation, setup, and usage of Home Assistant.
|
||||
|
||||
{% assign faq = site.faq | sort: 'title' %}
|
||||
{% assign categories = faq | map: 'ha_category' | uniq | sort %}
|
||||
|
||||
{% for category in categories %}
|
||||
## {% linkable_title {{ category }} %}
|
||||
|
||||
{% for entry in faq %}
|
||||
{% if entry.ha_category == category %}
|
||||
### {% linkable_title {{ entry.title }} %}
|
||||
{{entry.content}}
|
||||
{% endif %}
|
||||
{% endfor %}
|
||||
{% endfor %}
|
||||
|
||||
@ -33,7 +33,7 @@ echo '{ "target": "beer" }' | jq -r ".target"
|
||||
|
||||
## {% linkable_title Add-on Docker file %}
|
||||
|
||||
All add-ons are based on Alpine Linux 3.5. Hass.io will automatically substitute the right base image based on the machine architecture. Add `tzdata` if you need run in correct timezone.
|
||||
All add-ons are based on Alpine Linux 3.6. Hass.io will automatically substitute the right base image based on the machine architecture. Add `tzdata` if you need run in correct timezone, but that is already add in our base images.
|
||||
|
||||
```
|
||||
FROM %%BASE_IMAGE%%
|
||||
@ -41,7 +41,7 @@ FROM %%BASE_IMAGE%%
|
||||
ENV LANG C.UTF-8
|
||||
|
||||
# Install requirements for add-on
|
||||
RUN apk add --no-cache tzdata jq
|
||||
RUN apk add --no-cache jq
|
||||
|
||||
# Copy data for add-on
|
||||
COPY run.sh /
|
||||
@ -96,7 +96,7 @@ The config for an add-on is stored in `config.json`.
|
||||
| map | no | List of maps for additional hass.io folders. Possible values: `config`, `ssl`, `addons`, `backup`, `share`. Default it map it `ro`, you can change that if you add a ":rw" at the end of name.
|
||||
| environment | no | A dict of environment variable to run add-on.
|
||||
| options | yes | Default options value of the add-on
|
||||
| schema | yes | Schema for options value of the add-on
|
||||
| schema | yes | Schema for options value of the add-on. It can be `False` to disable schema validation and use custom options.
|
||||
| image | no | For use dockerhub.
|
||||
| tmpfs | no | Mount a tmpfs file system in `/tmpfs`. Valide format for this option is : `size=XXXu,uid=N,rw`. Size is mandatory, valid units (`u`) are `k`, `m` and `g` and `XXX` has to be replaced by a number. `uid=N` (with `N` the uid number) and `rw` are optional.
|
||||
|
||||
|
||||
@ -15,6 +15,8 @@ To get started with developing add-ons, we first need access to where Hass.io lo
|
||||
|
||||
For Samba, once you have enabled and started it, your Hass.io instance will show up in your local network tab and share a folder called "addons". This is the folder to store your custom add-ons.
|
||||
|
||||
If you are on macOS and the folder is not showing up automatically, go to Finder and press CMD+K then enter 'smb://hassio.local'
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/hassio/tutorial/samba.png' />
|
||||
With Samba add-on enabled, you can browse to your Hass.io server over the local network. It will contain an addons folder to store your local add-ons.
|
||||
|
||||
@ -17,6 +17,16 @@ Create an `authorized_keys` file in the root of your SD card with your public ke
|
||||
|
||||
Windows instructions how to generate and use private/public keys with Putty are [here][windows-keys]. Instead of the droplet instructions, add the public key as per above instructions.
|
||||
|
||||
Alternative instructions, for Mac, Windows and Linux can be found [here](https://help.github.com/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent/#platform-mac).
|
||||
|
||||
Follow steps 1-4 under 'Generating a new SSH key' (The other sections are not applicable to Hass.io and can be ignored.)
|
||||
|
||||
Step 3 in the link above, shows the path to the private key file `id_rsa` for your chosen operating system. Your public key, `id_rsa.pub`, is saved in the same folder. Next, copy your public key file to the root of your SD card.
|
||||
|
||||
<p class='note'>
|
||||
Make sure when you are copying the public key to the root of the SD card that you rename the file correctly with no `.pub` file extension.
|
||||
</p>
|
||||
|
||||
## {% linkable_title Checking the logs %}
|
||||
|
||||
```bash
|
||||
|
||||
@ -22,7 +22,7 @@ Short story of that caption: We loop in our script to fetch data and push it to
|
||||
Our Dockerfile need to install:
|
||||
|
||||
```
|
||||
RUN apk --no-cache add tzdata jq mosquitto-clients
|
||||
RUN apk --no-cache add jq mosquitto-clients
|
||||
```
|
||||
|
||||
Now we can process it with `run.sh`:
|
||||
@ -61,7 +61,7 @@ Short story of that caption: We wait for incoming data from MQTT broker. We can
|
||||
Our Dockerfile need to install:
|
||||
|
||||
```
|
||||
RUN apk --no-cache add tzdata jq mosquitto-clients
|
||||
RUN apk --no-cache add jq mosquitto-clients
|
||||
```
|
||||
|
||||
Now we can process it with `run.sh`:
|
||||
|
||||
Binary file not shown.
|
After Width: | Height: | Size: 1.7 MiB |
BIN
source/images/blog/2017-06-senic-covi/email-senic.png
Normal file
BIN
source/images/blog/2017-06-senic-covi/email-senic.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 53 KiB |
BIN
source/images/blog/2017-06-senic-covi/senic-docs-screenshot.png
Normal file
BIN
source/images/blog/2017-06-senic-covi/senic-docs-screenshot.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 497 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 3.8 KiB After Width: | Height: | Size: 3.6 KiB |
Loading…
x
Reference in New Issue
Block a user