HADashboard can't find HA, losing my mind - Solved

Third party integrations HADashboard
1

Hello all,

Running Ubuntu Server 16.04. Running HA in docker container. HA and Docker all up to date, 0.64.1 as of yesterday. No issues in HA.

Trying to install HADashboard in a docker container following the acockburn/appdaemon dockerfile. Tried to load the test, no HA connection. Tried to load production with persistence, no HA connection. Below is the -D DEBUG output from terminal. The only thing I can think is that I need python3.6. Thoughts?

Here is the line I use to try and load the test.

docker run --rm -it -p 5050:5050 -e HA_URL="http://192.168.1.203:8123" -e EXTRA_CMD="-D DEBUG" -e DASH_URL="http://192.168.1.203:5050" acockburn/appdaemon:latest

cp: cannot stat ‘/usr/src/app/conf/apps.yaml.example’: No such file or directory
2018-03-01 23:47:49.452334 INFO AppDaemon Version 3.0.0b3 starting
2018-03-01 23:47:49.452561 INFO Configuration read from: /conf/appdaemon.yaml
2018-03-01 23:47:49.452641 DEBUG AppDaemon Section: None
2018-03-01 23:47:49.452711 DEBUG HADashboard Section: None
2018-03-01 23:47:49.453498 INFO AppDaemon: Starting Apps
2018-03-01 23:47:49.453774 DEBUG AppDaemon: Creating worker threads ...
2018-03-01 23:47:49.459794 DEBUG AppDaemon: Done
2018-03-01 23:47:49.459991 DEBUG AppDaemon: Entering run()
2018-03-01 23:47:49.460143 INFO AppDaemon: Loading Plugin HASS using class HassPlugin from module hassplugin
2018-03-01 23:47:49.549910 INFO AppDaemon: HASS: HASS Plugin Initializing
2018-03-01 23:47:49.550271 INFO AppDaemon: HASS: HASS Plugin initialization complete
2018-03-01 23:47:49.550451 DEBUG AppDaemon: Starting utility loop
2018-03-01 23:47:49.550561 INFO Dashboards are disabled
2018-03-01 23:47:49.550632 INFO API is disabled
2018-03-01 23:47:49.550694 DEBUG Start Loop
2018-03-01 23:47:49.551102 DEBUG AppDaemon: Event type:ha_disconnected:
2018-03-01 23:47:49.551239 DEBUG AppDaemon: {}
2018-03-01 23:47:49.551320 WARNING AppDaemon: HASS: Disconnected from Home Assistant, retrying in 5 seconds
2018-03-01 23:47:49.551395 WARNING AppDaemon: HASS: ------------------------------------------------------------
2018-03-01 23:47:49.551463 WARNING AppDaemon: HASS: Unexpected error:
2018-03-01 23:47:49.551529 WARNING AppDaemon: HASS: ------------------------------------------------------------
2018-03-01 23:47:49.572137 WARNING AppDaemon: HASS: Traceback (most recent call last):
  File "/usr/local/lib/python3.6/site-packages/appdaemon/plugins/hass/hassplugin.py", line 178, in get_updates
    if url.startswith('https://'):
AttributeError: 'NoneType' object has no attribute 'startswith'

2018-03-01 23:47:49.572609 WARNING AppDaemon: HASS: ------------------------------------------------------------
2018-03-01 23:47:54.575654 DEBUG AppDaemon: Event type:ha_disconnected:
2018-03-01 23:47:54.576088 DEBUG AppDaemon: {}
2018-03-01 23:47:54.576390 WARNING AppDaemon: HASS: Disconnected from Home Assistant, retrying in 5 seconds
2018-03-01 23:47:54.576653 WARNING AppDaemon: HASS: ------------------------------------------------------------
2018-03-01 23:47:54.576976 WARNING AppDaemon: HASS: Unexpected error:
2018-03-01 23:47:54.577225 WARNING AppDaemon: HASS: ------------------------------------------------------------
2018-03-01 23:47:54.577819 WARNING AppDaemon: HASS: Traceback (most recent call last):
  File "/usr/local/lib/python3.6/site-packages/appdaemon/plugins/hass/hassplugin.py", line 178, in get_updates
    if url.startswith('https://'):
AttributeError: 'NoneType' object has no attribute 'startswith'
2

what is in your appdaemon.yaml file? There should be a app_dir line in there that points to where your apps.yaml file is stored.

3

@turboc, the docker run command is for a temporary instance of HADashboard to test connectivity and port accessibility. According to the Docker Tutorial it should output in the terminal that it is connected to HA and I should be able to open the browser to port 5050 and get the Welcome screen. I can’t customize any of the data and have it persist but for the test, it isn’t necessary.

The issue is though that I get the exact same errors running the test command versus a production command.

4

Ok, I’m not familiar with Docker. Sorry. That’s just an unusual place for the apps.yaml.example file. Also with it being named example, that’s strange, but if it’s a test the maybe it’s ok.
Sorry

5

This has been solved.

1 Like