jeena/home-assistant.github.io
1
0
Fork 0
Code Issues Pull requests Projects Packages Wiki Activity Actions

Merge remote-tracking branch 'origin/current' into next

Browse source
This commit is contained in:
Paulus Schoutsen 2018-02-25 16:49:29 -08:00
commit d282343710
51 changed files with 378 additions and 171 deletions
Download patch file Download diff file Expand all files Collapse all files

16
source/_docs/ecosystem/certificates/lets_encrypt.markdown
View file

@ -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.

2
source/_docs/ecosystem/certificates/tls_self_signed_certificate.markdown
View file

@ -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.