Hass with AppDaemon - Can't connect to hadashboard - Connection timeout

[nomaam]

I am running hass on a Pi3 and installed appdaemon with pip

I am able to start hass and start appdaemon. I am able to log into the browser connection for hass and all seems well.

I am not able to access my dashboard (hadashboard). I get a connection timeout error.

I am new to this software, so any help you could provide would be much appreciated. Thanks.

appdaemon.yaml

appdaemon:
    disable_apps: 1
    threads: 10
    plugins:
      HASS:
        type: hass
        ha_url: http://192.168.1.142:8123
        token: long-token-key

hadashboard:
  dash_url: http://192.168.1.222:5050
  dash_password: pass

Running AppDaemon:

user@raspberrypi:/home/homeassistant/conf $ sudo appdaemon -c /home/homeassistant/conf
2019-01-13 13:08:09.196505 INFO AppDaemon Version 3.0.2 starting
2019-01-13 13:08:09.197134 INFO Configuration read from: /home/homeassistant/conf/appdaemon.yaml
2019-01-13 13:08:09.201414 INFO AppDaemon: Starting Apps
2019-01-13 13:08:09.209281 INFO AppDaemon: Loading Plugin HASS using class HassPlugin from module hassplugin
2019-01-13 13:08:09.423501 INFO AppDaemon: HASS: HASS Plugin Initializing
2019-01-13 13:08:09.424509 INFO AppDaemon: HASS: HASS Plugin initialization complete
2019-01-13 13:08:09.425380 INFO Starting Dashboards
2019-01-13 13:08:09.441225 INFO API is disabled
2019-01-13 13:08:09.456470 INFO AppDaemon: HASS: Connected to Home Assistant 0.84.6
2019-01-13 13:08:09.494752 INFO AppDaemon: Got initial state from namespace default
2019-01-13 13:08:11.662408 INFO AppDaemon: Adding /home/homeassistant/conf/apps to module import path
2019-01-13 13:08:11.664762 INFO AppDaemon: App initialization complete

Hello.dash

title: Hello_Panel
widget_dimensions: [120, 120]
widget_margins: [5, 5]
columns: 8

label:
widget_type: label
text: Hello World

layout:
- label(2x2)

[nickrout]

Just let me check - HA is running on a different machine to appdaemon? Because your IP addresses are different.

[nomaam]

well then… that fixed it. thank you.

I changed the dash_url to be the same ip as ha_url but different port, and now it works.

For some reason, I thought it wanted its own ip on the network.

A quick followup question: how should I be running ha and appdaemon user wise?

I start home assistant with the following

sudo -u homeassistant -H -s
source /srv/homeassistant/bin/activate
hass

So then I changed the owner and group of all files regarding appdaemon to be homeassistant and then try to run appdaemon as a homeassistant user as well

sudo -u homeassistant -H -s
appdaemon -c /home/homeassistant/conf

Is this the recommended approach?

Thank you.

[nickrout]

Frankly I am not sure on which user should run appdarmon. I use appdaemon in docker.

[robg (Robert Gallesio)]

Appdaemon ownership and permissions

I’m tinkering with appdaemon and like it a lot as I prefer python to yaml. I installed it according to the tutorial with sudo so root owns it and the directories I have created. As a result, I have to use sudo to edit the files and it makes we wonder what the “standard” way of installing is. That is, who should own the files and folders? Should I just make homeassistant the owner since we’re putting the conf directory in homeassistant’s home directory?

As for the IP, if on the same machine use localhost…don’t need to worry about IP changes like your original problem!!
EG:
ha_url: http://localhost:8123
hadashboard:
dash_url: http://localhost:5050

[ReneTode]

thats possible.
allthough i rather prefer to use an ip then something i dont know what it is.
you need to know the ip anyway if you want to browse to the server locally (unless you install a local dns server)

@nomaam indeed you best use 1 user (in this case homeassistant). for sure because you have your AD configuration inside your homeassistant configuration.

it would have been even better if you (besides the HASS venv) also create a seperate venv for appdaemon.
but at least because HASS is in a venv they are not in the same python area.