Update connection.md

This commit is contained in:
Yegor Vialov 2020-07-01 15:57:51 +03:00 committed by GitHub
parent 5019c277db
commit ceed84e7d5
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -2,8 +2,6 @@
- [Quick start](#quick-start)
- [Advanced](#advanced)
- [Port](#port)
- [HTTP or HTTPS](#http-or-https)
- [SSL Certificates](#ssl-certificates)
- [Login with long-lived token](#login-with-long-lived-token)
@ -37,24 +35,6 @@ That's it! You are ready to go.
{% include in_post.html %}
## Advanced
### Port
You don't need to worry about port if you are using [Remote UI](https://www.nabucasa.com/config/remote/). Just leave it blank.
By default your Home Assistant is using port number `8123`. But to access your instance from outside of your home network, probably you configured some port forwarding rules on you router. If you forward some other port from outside to `8123` port on Home Assistant IP, you need to use that port instead.
If you are accessing your web interface without port, then you need to try port `80` or `443` in app.
You can also try to leave port number field blank to make HA Client to try to choose port for you. May be it will succeed.
[Back to top](#help-pages---connection)
### HTTP or HTTPS
You don't need to worry about this option if you are using [Remote UI](https://www.nabucasa.com/config/remote/). Just leave it as is.
It is not required to use secure connection. Just remember: if you are accessing your web interface with `http`, you need to switch “Use ssl” off in app settings as well.
But if you are using ssl (accessing web interface with `https://`) your certificate should be valid and **not self-signed**. This is not a restriction of HA Client, but a known issue of Flutter framework.
[Back to top](#help-pages---connection)
### SSL Certificates
The main requirement is that your SSL Certificate should not be self-signed. Most certificates from providers like Lets Encrypt will work. There is [known issue](https://github.com/estevez-dev/ha_client_pub/issues/24) with RapidSSL certificate, but this problem is common not only for HA Client.