[home-assistant] Homeassistant fails to start with AppDaemon enabled about charts HOT 7 CLOSED

@xeor now you can set any envs you need (at least, for appdaemon)

from charts.

Hi @rwlove, I didn't add this feature but believe that there are a couple of possible problems:

1. It looks like the DASH_URL environment variable (required by appDaemon?) isn't being set unless ingress is enabled.
2. Similarly, the TOKEN environment variable is not set due to the haToken value not being set with the helm chart configuration and thus the appDaemon doesn't have a token to reference at runtime.

Can you try enabling appDaemon ingress and/or setting a token value in the helm configuration to see if this helps?

from charts.

The below changes to my values.yaml seems to allow it to work.

@@ -278,7 +281,7 @@
     # nodePort: 30000
 
 appdaemon:
-  enabled: false
+  enabled: true
 
   ## code-server container image
   ##
@@ -288,7 +291,7 @@
     pullPolicy: IfNotPresent
 
   ## Home Assistant API token
-  # haToken:
+  haToken: <MY_TOKEN_FROM_WEBUI>
 
   ## Additional hass-vscode container environment variable
   ## For instance to add a http_proxy
@@ -296,7 +299,7 @@
   extraEnv: {}
 
   ingress:
-    enabled: false
+    enabled: true
     annotations: {}
       # kubernetes.io/ingress.class: nginx
       # kubernetes.io/tls-acme: "true"

It generates the following appdaemon.yaml file:

log:
  logfile: STDOUT
  errorfile: STDERR
appdaemon:
  threads: 10
  plugins:
    HASS:
      type: hass
      ha_url: http://localhost:8123
      token: <MY_TOKEN_FROM_WEBUI>
hadashboard:
  dash_url: http://0.0.0.0:5050

Can you help me understand how the appdaemon.yaml file gets generated? For example when I grep for “errorfile” which is in the resultant appdaemon.yaml, I don’t get any hits in your repository.

I’d love to upgrade this chart to make use of appdaemon 4.0.3 (currently using 3.0.5). I got it to work by manually updating the appdaemon.yaml file on my persistent storage and rebooting, but if I understood how the appdaemon.yaml file is being generated I could probably provide a patch to update the appdaemon version. Here’s an example of how the resultant appdaemon.yaml file should look when using 4.0.3.

appdaemon:
  threads: 10
  latitude: 15
  longitude: 31
  elevation: 45
  time_zone: 'America/Los_Angeles'
  plugins:
    HASS:
      type: hass
      ha_url: http://localhost:8123
      token: <MY_TOKEN_FROM_WEBUI>
hadashboard:
http:
  url: http://0.0.0.0:5050
admin:
api:

Do you know where the user is supposed to provide the appdaemon.cfg file?

Lastly, I’m a bit confused about where to get the token from. I did this last weekend, but I believe I started Home Assistant once, went to the webui, generated the token, added that token to the helm chart values.yaml and restarted Home Assistant. Do you know if this is the right procedure?

from charts.

@rwlove the appdaemon.yaml file is generated by the appdeamon image (specifically from this script https://github.com/AppDaemon/appdaemon/blob/dev/dockerStart.sh , which is the first script that is executed once the appdeamon pod starts )

I've already opened a pull request AppDaemon/appdaemon#1002 to allow these options to be configured via env variables

from charts.

I don't use ingress, and is hitting this same problem. However, it looks like https://github.com/k8s-at-home/charts/blob/master/charts/home-assistant/values.yaml#L300 the appdaemon.extraEnv is never used..? Is it being used somewhere else? It is missing from https://github.com/k8s-at-home/charts/blob/master/charts/home-assistant/templates/deployment.yaml

from charts.

Welp, here is a typo

I'm working on PR with a fix for this issue and some other improvements.

from charts.

Looks like this issue can be closed because the environment variables should be working for appdaemon :D

Thanks @lexfrei

from charts.