Skip to content

Home Assistant

home-assistant logo

Version: 0.17.0 Type: application AppVersion: latest

Open source home automation that puts local control and privacy first.

This chart is not maintained by the upstream project and any issues with the chart should be raised here

Source Code


Kubernetes: >=1.22.0-0


Repository Name Version common 1.5.1 postgresql 14.0.5

Installing the Chart

To install the chart with the release name home-assistant

helm install home-assistant oci://


helm repo add gabe565
helm repo update
helm install home-assistant gabe565/home-assistant

Uninstalling the Chart

To uninstall the home-assistant deployment

helm uninstall home-assistant

The command removes all the Kubernetes components associated with the chart including persistent volumes and deletes the release.


Read through the values.yaml file. It has several commented out suggested values. Other values may be used from the values.yaml from the bjw-s common library.

Specify each parameter using the --set key=value[,key=value] argument to helm install.

helm install home-assistant \
  --set env.TZ="America/New York" \

Alternatively, a YAML file that specifies the values for the above parameters can be provided while installing the chart.

helm install home-assistant gabe565/home-assistant -f values.yaml

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 component and set trusted_proxies correctly and use_x_forwarded_for to true.

For example (edit the configuration.yaml in your pod):

  ip_ban_enabled: true
  login_attempts_threshold: 5
  use_x_forwarded_for: true
    # Pod CIDR
    # Node CIDR

USB Devices

A USB devices can be used with Home Assistant if passed through from the host to the pod.

The USB device could be volume bound directly into the Pod (documented in the deprecated k8s-at-home/home-assistant chart, but this requires granting privileged access to the Home Assistant pod.

Instead, it is recommended to use Generic Device Plugin or Smarter Device Manager to manage USB devices for you.

For example, if your Z-Wave device is at /dev/ttyACM0, you could deploy Smarter Device Manager with the following configuration:

config: |
  - devicematch: ^ttyACM[0-9]*$
    nummaxdevices: 1

Then, add the following resources to your Home Assistant values.yaml:

    smarter-devices/ttyACM0: 1
    smarter-devices/ttyACM0: 1

Your Home Assistant Pod would automatically be deployed to the correct server, with the USB device available at /dev/ttyACM0. No extra privileges required!


Important: When deploying an application Helm chart you can add more values from the bjw-s common library chart here

Key Type Default Description
addons.codeserver.enabled bool false Enable VS Code server addon. This allows for easy access to configuration.yaml
addons.codeserver.ingress object See values.yaml Enable and configure ingress settings for the VS Code server under this key.
dnsPolicy string "ClusterFirst" When hostNetwork is true set dnsPolicy to ClusterFirstWithHostNet
env object See values.yaml environment variables.
env.TZ string "UTC" Set the container timezone
hostNetwork bool false Enable devices to be discoverable
image.pullPolicy string "IfNotPresent" image pull policy
image.repository string "" image repository
image.tag string "latest" image tag
ingress.main object See values.yaml Enable and configure ingress settings for the chart under this key.
persistence.config object See values.yaml Configure persistence settings for the chart under this key.
postgresql object See values.yaml Enable and configure postgresql database subchart under this key. For more options see postgresql chart documentation
service object See values.yaml Configures service settings for the chart.

Autogenerated from chart metadata using helm-docs