yehor/ha-client-website
Archived
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update docs.md

Browse Source
This commit is contained in:
Yegor Vialov
2019-02-08 16:18:13 +02:00
committed by GitHub
parent cd7782b93e
commit f9eb09dc28
1 changed files with 14 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
docs.md
View File

@@ -1,6 +1,6 @@
# Table of content # Table of content
- [Requirements](#requirements) - [Requirements](#requirements)
- Home Assistant general - [Home Assistant general](#home-assistant-general)
- Port - Port
- HTTP or HTTPS - HTTP or HTTPS
- SSL Certificates - SSL Certificates
@@ -13,3 +13,16 @@
# Requirements # Requirements
## Home Assistant general ## Home Assistant general
To check if you are using right configuration for app, try to access your Home Assistant web interface with the same protocol (http:// or https://), the same domain or IP and port. If it is not loading – the app will not work as well. To check if you are using right configuration for app, try to access your Home Assistant web interface with the same protocol (http:// or https://), the same domain or IP and port. If it is not loading – the app will not work as well.
To connect to your Home Assistant instance with HA Client you need `http` and `websocket_api` components to be enabled as well as [remote access](https://www.home-assistant.io/docs/configuration/remote/) configured. If you are using `frontend` component (Home Assistant web interface actually) `websocket_api` is enabled by default and `http` component is already configured on your server, but still you need to double check.
In other cases changes should be made to you `configuration.yaml`:
```yaml
http:
api_password: #some password here
base_url: #your domain for Home Assistant instance
ssl_certificate: /ssl/fullchain.pem #ssl configuration to access your HA by https
ssl_key: /ssl/privkey.pem
websocket_api:
```