update: hass documentation (#1171)

This commit is contained in:
ᗪєνιη ᗷυнʟ 2021-09-09 14:05:29 -04:00 committed by GitHub
parent 302bdd1b95
commit f57549eeab
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 40 additions and 2 deletions

View File

@ -2,7 +2,7 @@ apiVersion: v2
appVersion: 2021.6.3 appVersion: 2021.6.3
description: Home Assistant description: Home Assistant
name: home-assistant name: home-assistant
version: 10.1.0 version: 10.1.1
kubeVersion: ">=1.16.0-0" kubeVersion: ">=1.16.0-0"
keywords: keywords:
- home-assistant - home-assistant

View File

@ -1,6 +1,6 @@
# home-assistant # home-assistant
![Version: 10.1.0](https://img.shields.io/badge/Version-10.1.0-informational?style=flat-square) ![AppVersion: 2021.6.3](https://img.shields.io/badge/AppVersion-2021.6.3-informational?style=flat-square) ![Version: 10.1.1](https://img.shields.io/badge/Version-10.1.1-informational?style=flat-square) ![AppVersion: 2021.6.3](https://img.shields.io/badge/AppVersion-2021.6.3-informational?style=flat-square)
Home Assistant Home Assistant
@ -72,6 +72,25 @@ helm install home-assistant k8s-at-home/home-assistant -f values.yaml
## Custom configuration ## Custom configuration
### HTTP 400 bad request while accessing from your browser
When configuring Home Assistant behind a reverse proxy make sure you configure the [http](https://www.home-assistant.io/integrations/http) component and set `trusted_proxies` correctly and `use_x_forwarded_for` to `true`.
For example:
```yaml
http:
server_host: 0.0.0.0
ip_ban_enabled: true
login_attempts_threshold: 5
use_x_forwarded_for: true
trusted_proxies:
# Pod CIDR
- 10.69.0.0/16
# Node CIDR
- 192.168.42.0/24
```
### Z-Wave / Zigbee ### Z-Wave / Zigbee
A Z-Wave and/or Zigbee controller device could be used with Home Assistant if passed through from the host to the pod. Skip this section if you are using zwave2mqtt and/or zigbee2mqtt or plan to. A Z-Wave and/or Zigbee controller device could be used with Home Assistant if passed through from the host to the pod. Skip this section if you are using zwave2mqtt and/or zigbee2mqtt or plan to.

View File

@ -5,6 +5,25 @@
{{- define "custom.custom.configuration" -}} {{- define "custom.custom.configuration" -}}
{{ template "custom.custom.configuration.header" . }} {{ template "custom.custom.configuration.header" . }}
### HTTP 400 bad request while accessing from your browser
When configuring Home Assistant behind a reverse proxy make sure you configure the [http](https://www.home-assistant.io/integrations/http) component and set `trusted_proxies` correctly and `use_x_forwarded_for` to `true`.
For example:
```yaml
http:
server_host: 0.0.0.0
ip_ban_enabled: true
login_attempts_threshold: 5
use_x_forwarded_for: true
trusted_proxies:
# Pod CIDR
- 10.69.0.0/16
# Node CIDR
- 192.168.42.0/24
```
### Z-Wave / Zigbee ### Z-Wave / Zigbee
A Z-Wave and/or Zigbee controller device could be used with Home Assistant if passed through from the host to the pod. Skip this section if you are using zwave2mqtt and/or zigbee2mqtt or plan to. A Z-Wave and/or Zigbee controller device could be used with Home Assistant if passed through from the host to the pod. Skip this section if you are using zwave2mqtt and/or zigbee2mqtt or plan to.