Merge remote-tracking branch 'origin/current' into next
This commit is contained in:
Paulus Schoutsen
commit
d282343710
51 changed files with 378 additions and 171 deletions
|
|
@ -11,6 +11,8 @@ footer: true
|
|||
|
||||
When launched for the first time, Home Assistant will write a default configuration file enabling the web interface and device discovery. It can take up to a minute for your devices to be discovered and appear in the user interface.
|
||||
|
||||
The web interface can be found at `http://ip.ad.dre.ss:8123/` - for example if your Home Assistant system has the IP address `192.168.0.40` then you'll find the web interface as `http://192.168.0.40:8123/`.
|
||||
|
||||
The location of the folder differs between operating systems:
|
||||
|
||||
| OS | Path |
|
||||
|
|
|
|||
54
source/_docs/configuration/entity-registry.markdown
Normal file
54
source/_docs/configuration/entity-registry.markdown
Normal file
|
|
@ -0,0 +1,54 @@
|
|||
---
|
||||
layout: page
|
||||
title: "Entity Registry"
|
||||
description: "The entity registry contains."
|
||||
date: 2016-04-20 06:00
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
---
|
||||
|
||||
<p class='note'>
|
||||
This is a new and experimental feature of Home Assistant.
|
||||
</p>
|
||||
|
||||
Starting with version 0.63, Home Assistant keeps a registry of known entities.
|
||||
The entity registry makes sure that entities get unique identifiers and allow
|
||||
customizing the identifiers and names of these entities.
|
||||
|
||||
As this is still a very new part of Home Assistant, changes will require a
|
||||
restart of Home Assistant to take affect. A config user interface will be added
|
||||
in a future version.
|
||||
|
||||
<p class='note'>
|
||||
An entity needs to have a unique ID to be registered in the entity registry.
|
||||
Not all integrations currently provide a unique id for their entities.
|
||||
</p>
|
||||
|
||||
The entity registry is stored in `<config>/entity_registry.yaml`. As a user,
|
||||
you are unable to add entries, only update them. Here is an example file:
|
||||
|
||||
```
|
||||
climate.downstairs_virtual:
|
||||
platform: nest
|
||||
unique_id: EPoMyWkpNyoYu3pGlmGxabcdefghijkl
|
||||
name: Downstairs thermostat
|
||||
light.study_ceiling:
|
||||
platform: hue
|
||||
unique_id: f0:fe:6b:00:14:00:00:00-00
|
||||
disabled_by: user
|
||||
```
|
||||
|
||||
As a user, you can change the `entity_id` and add the `name` and `disabled_by`
|
||||
value to each entry.
|
||||
|
||||
- The value of `name` will override the name of the entity as given by the
|
||||
integration.
|
||||
|
||||
_Added in Home Assistant 0.64._
|
||||
- The key `disabled_by` can either be `hass` or `user`. This functionality
|
||||
is even more experimental than the whole entity registry itself and might
|
||||
cause integrations to fail and might be removed in the future.
|
||||
|
||||
_Added in Home Assistant 0.64._
|
||||
|
|
@ -43,12 +43,13 @@ script:
|
|||
msg_who_is_home:
|
||||
sequence:
|
||||
- service: notify.notify
|
||||
message: >
|
||||
{% raw %}{% if is_state('device_tracker.paulus', 'home') %}
|
||||
Ha, Paulus is home!
|
||||
{% else %}
|
||||
Paulus is at {{ states('device_tracker.paulus') }}.
|
||||
{% endif %}{% endraw %}
|
||||
data_template:
|
||||
message: >
|
||||
{% raw %}{% if is_state('device_tracker.paulus', 'home') %}
|
||||
Ha, Paulus is home!
|
||||
{% else %}
|
||||
Paulus is at {{ states('device_tracker.paulus') }}.
|
||||
{% endif %}{% endraw %}
|
||||
```
|
||||
|
||||
[Jinja2](http://jinja.pocoo.org/) supports a wide variety of operations:
|
||||
|
|
|
|||
|
|
@ -113,7 +113,7 @@ static routers=192.168.0.1 <---- Your router's IP address
|
|||
static domain_name_servers=192.168.0.1 <---- Your router's IP address
|
||||
```
|
||||
|
||||
It is important to note that the first three bits of your static IP address and your router's IP address should be the same, eg:
|
||||
It is important to note that the first three bytes of your static IP address and your router's IP address should be the same, eg:
|
||||
|
||||
```text
|
||||
Router: 192.168.0.1
|
||||
|
|
@ -538,13 +538,13 @@ In your `configuration.yaml` add the following automation, adding your preferred
|
|||
automation:
|
||||
- alias: 'SSL expiry notification'
|
||||
trigger:
|
||||
platform: numeric_state
|
||||
entity_id: sensor.ssl_cert_expiry
|
||||
below: 21
|
||||
action:
|
||||
service: notify.[your_notification_preference]
|
||||
data:
|
||||
message: 'Warning - SSL certificate expires in 21 days and has not been automatically renewed'
|
||||
platform: numeric_state
|
||||
entity_id: sensor.ssl_cert_expiry
|
||||
below: 21
|
||||
action:
|
||||
service: notify.[your_notification_preference]
|
||||
data:
|
||||
message: 'Warning - SSL certificate expires in 21 days and has not been automatically renewed'
|
||||
```
|
||||
|
||||
If you receive this warning notification, follow the steps for a manual update from step 8. Any error messages received at that point can be googled and resolved. If the manual update goes without a hitch there may be something wrong with your chosen method for automatic updates, and you can start troubleshooting from there.
|
||||
|
|
|
|||
|
|
@ -12,7 +12,7 @@ redirect_from: /cookbook/tls_self_signed_certificate/
|
|||
|
||||
If your Home Assistant instance is only accessible from your local network you can still protect the communication between your browsers and the frontend with SSL/TLS.
|
||||
[Let's encrypt]({{site_root}}/blog/2015/12/13/setup-encryption-using-lets-encrypt/) will only work if you have a DNS entry and remote access is allowed.
|
||||
The solution is to use a self-signed certificate. As you most likely don't have a certification authority (CA) your browser will conplain about the security. If you have a CA then this will not be an issue.
|
||||
The solution is to use a self-signed certificate. As you most likely don't have a certification authority (CA) your browser will complain about the security. If you have a CA then this will not be an issue.
|
||||
|
||||
To create a certificate locally, you need the [OpenSSL](https://www.openssl.org/) command-line tool.
|
||||
|
||||
|
|
|
|||
|
|
@ -14,7 +14,7 @@ redirect_from: /getting-started/updating/
|
|||
The upgrade process differs depending on the installation you have, so please review the documentation that is specific to your install [Hass.io](/hassio/), [HASSbian](/docs/hassbian/common-tasks/#update-home-assistant), [Vagrant](/docs/installation/vagrant/), or [Virtualenv](/docs/installation/virtualenv/#upgrading-home-assistant).
|
||||
</p>
|
||||
|
||||
View what's new in the latest version and potential impacts on your system [here](https://github.com/home-assistant/home-assistant/releases).
|
||||
Check what's new in the latest version and potentially impacts your system in [Home Assistant release notes](https://github.com/home-assistant/home-assistant/releases). It is good practice to review these release notes and pay close attention to the **Breaking Changes** that are listed there. If you haven't done an update for a while, you should also check previous release notes as they can also contain relevant **Breaking Changes**. **Breaking Changes** may require configuration updates for your components. If you missed this and Home Assistant refuses to start, check `<config-dir>/home-assistant.log` for details about broken components.
|
||||
|
||||
The default way to update Home Assistant to the latest release, when available, is:
|
||||
|
||||
|
|
|
|||
|
|
@ -99,14 +99,14 @@ tls_insecure:
|
|||
type: boolean
|
||||
tls_version:
|
||||
required: false
|
||||
description: "TLS/SSL protocol version to use. Available options are: `auto`, `1.0`, `1.1`, `1.2`. Defaults to `auto`."
|
||||
description: "TLS/SSL protocol version to use. Available options are: `'auto'`, `'1.0'`, `'1.1'`, `'1.2'`. Make sure to put quotes around the value. Defaults to `'auto'`."
|
||||
type: string
|
||||
{% endconfiguration %}
|
||||
|
||||
<p class='note warning'>
|
||||
There is an issue with the Mosquitto package included in Ubuntu 14.04 LTS. Specify `protocol: 3.1` in your MQTT configuration to work around this issue.
|
||||
|
||||
If you get this error `AttributeError: module 'ssl' has no attribute 'PROTOCOL_TLS'` then you need to set `tls_version: 1.2`.
|
||||
If you get this error `AttributeError: module 'ssl' has no attribute 'PROTOCOL_TLS'` then you need to set `tls_version: '1.2'`.
|
||||
</p>
|
||||
|
||||
<p class='note'>
|
||||
|
|
|
|||
|
|
@ -43,6 +43,10 @@ Here is where you [include and exclude](/docs/z-wave/adding/) Z-Wave devices fro
|
|||
|
||||
* **Test Node** sends no_op test messages to the node. This could in theory bring back a dead node.
|
||||
|
||||
<p class='note warning'>
|
||||
Since 0.63 and the new experimental [entity registry](https://home-assistant.io/docs/configuration/entity-registry/) **Rename Node** no longer changes the entity id for anything other than the `zwave.` entity for the node (it does change, the default *friendly_name* and *old_entity_id* and *new_entity_id* attributes for all the entities). See [this issue](https://github.com/home-assistant/home-assistant/issues/12430).
|
||||
</p>
|
||||
|
||||
<p class='note'>
|
||||
Battery powered devices need to be awake before you can use the Z-Wave control panel to update their settings. How to wake your device is device specific, and some devices will stay awake for only a couple of seconds. Please refer to the manual of your device for more details.
|
||||
</p>
|
||||
|
|
@ -130,6 +134,20 @@ If your node has user codes, you can set and delete them. The format is raw hex
|
|||
Some non compliant device like tag readers, have implemented to use raw hex code.
|
||||
Please refer to a hex ascii table to set your code. Example: http://www.asciitable.com/
|
||||
|
||||
Here is a small Python program than will take numbers on the command line and print the correct sequence for compliant devices:
|
||||
|
||||
```python
|
||||
#! /usr/bin/python3
|
||||
import sys
|
||||
|
||||
translations = {}
|
||||
|
||||
for x in range(0, 10):
|
||||
translations["%s" % x] = "\\x3%s" % x
|
||||
|
||||
for c in sys.argv[1]:
|
||||
print(translations[c], end='')
|
||||
```
|
||||
|
||||
## {% linkable_title OZW Log %}
|
||||
|
||||
|
|
|
|||
|
|
@ -27,7 +27,7 @@ You need to have a [supported Z-Wave USB stick or module](https://github.com/Ope
|
|||
| ZWave.me UZB1 | ✓ | | |
|
||||
|
||||
<p class='note'>
|
||||
If you're using Hass.io, it's recommended to use a USB stick, not a module. Passing a module through Docker is more complicated than passing a USB stick through.
|
||||
If you're using Hass.io or running HASS in a Docker container, it's recommended to use a USB stick, not a module. Passing a module through Docker is more complicated than passing a USB stick through.
|
||||
</p>
|
||||
|
||||
## {% linkable_title Stick Alternatives %}
|
||||
|
|
|
|||
|
|
@ -53,7 +53,7 @@ usb_path:
|
|||
type: string
|
||||
default: /zwaveusbstick
|
||||
network_key:
|
||||
description: The 16-byte network key in the form `"0x01, 0x02..."` used in order to connect securely to compatible devices.
|
||||
description: The 16-byte network key in the form `"0x01, 0x02..."` used in order to connect securely to compatible devices. It is recommended that a network key is configured as security enabled devices may not function correctly if they are not added securely.
|
||||
required: false
|
||||
type: string
|
||||
default: None
|
||||
|
|
@ -82,7 +82,7 @@ new_entity_ids:
|
|||
required: false
|
||||
type: boolean
|
||||
default: True
|
||||
device_config:
|
||||
device_config / device_config_domain / device_config_glob:
|
||||
description: This attribute contains node-specific override values. (For releases prior to 0.39 this variable is called **customize**) See [Customizing devices and services](/docs/configuration/customizing-devices/) for the format.
|
||||
required: false
|
||||
type: string, list
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue