Thanks for replying…I had skin zen in my url which would not let it run…
Hi,
first of all, thanks for the great work. I already love the new dashboard!!
But I found a minor issue: when I restart Home Assistant, while HADashboard is running (in a docker container) it is not able to reconnect after the Home Assistant instance is running again. It just shows this error:
2017-04-21 22:24:31.154923 WARNING Disconnected from Home Assistant, retrying in 5 seconds
2017-04-21 22:24:36.160690 WARNING Disconnected from Home Assistant, retrying in 5 seconds
2017-04-21 22:24:41.167347 WARNING Disconnected from Home Assistant, retrying in 5 seconds
2017-04-21 22:24:46.169234 WARNING Disconnected from Home Assistant, retrying in 5 seconds
2017-04-21 22:24:51.173692 WARNING Disconnected from Home Assistant, retrying in 5 seconds
Any idea how I can debug this further?
I dont know if its helpful to say, but I use Docker for all of it, and appdaemon and dashboard throw errors like that understandably while HASS resets, but Ive never had them NOT reconnect successfully. I dont know why it would work, and then not, in that situation.
hm ok … first I thought it is related to my nginx configuration, but even if I select the HA ip it does not restart.
ha_url = http://192.168.178.25:8123
Are you using docker-compose?
I do but not in any fancy way
Is Appdaemon going through nginx to get to HASS? Mine is straight up direct.
This is my second install of Hadashboard, but this time on a relative new installation with hassbian.
I have everything installed and I can run it, but can’t connect on port 5050.
The install tutorial say I should se something like this:
2017-02-20 08:07:34.985296 INFO AppDaemon Version 2.0.0beta starting
2017-02-20 08:07:34.985685 INFO Apps are disabled
2017-02-20 08:07:40.141165 INFO Got initial state
2017-02-20 08:07:40.141522 INFO Starting dashboard
2017-02-20 08:07:40.156139 INFO Listening on ('192.168.1.20', 5050)
2017-02-20 08:07:40.158829 INFO Connected to Home Assistant 0.38.3
but I’m only getting these lines, nothing about starting dashboard or listening to port 5050:
2017-04-21 23:01:48.004796 INFO AppDaemon Version 2.0.0beta3.5 starting
2017-04-21 23:01:53.256375 INFO Got initial state
2017-04-21 23:01:53.257311 INFO App initialization complete
2017-04-21 23:01:53.267398 INFO Connected to Home Assistant 0.42.4
What can I be missing?
both configurations run in this problem
This seems like there is no dashboard configuration. Do you have something like this in appdaemon.cfg:
# [dashboard]
dash_url = http://10.0.1.9:5050
dash_dir = /conf/dashboards
disable_apps = 1
dash_force_compile = 0
dash_compile_on_start = 1
Hm, no. Didn’t see that part in the example. Can i just copy that and put my own hass ip of course?
dash_url stands for the dashboard IP so the appdaemon.cfg should look like this:
[AppDaemon]
ha_url = http://<HOMEASSISTANT_IP>:8123
ha_key = <HOMEASSISTANT_API_KEY>
logfile = /conf/dashboard.log
errorfile = STDERR
threads = 10
# [dashboard]
dash_url = http://<DASHBOARD_IP>:5050
dash_dir = /conf/dashboards
disable_apps = 1
dash_force_compile = 0
dash_compile_on_start = 1
Edit: Figured it out. Was not running on sudo, that fixed it. 
Okey, so now I’m getting this instead 
2017-04-21 23:31:21.843392 INFO AppDaemon Version 2.0.0beta3.5 starting
2017-04-21 23:31:21.843923 INFO Apps are disabled
2017-04-21 23:31:27.036193 INFO Got initial state
2017-04-21 23:31:27.036692 INFO Starting dashboard
2017-04-21 23:31:27.037230 WARNING ------------------------------------------------------------
2017-04-21 23:31:27.037545 WARNING Unexpected error in dashboard thread
2017-04-21 23:31:27.037810 WARNING ------------------------------------------------------------
2017-04-21 23:31:27.040258 WARNING Traceback (most recent call last):
File "/appdaemon_dashboard/appdaemon/appdaemon/appdash.py", line 249, in run_dash
set_paths()
File "/appdaemon_dashboard/appdaemon/appdaemon/appdash.py", line 22, in set_paths
os.makedirs(conf.compile_dir)
File "/usr/lib/python3.4/os.py", line 237, in makedirs
mkdir(name, mode)
PermissionError: [Errno 13] Permission denied: '/appdaemon_dashboard/appdaemon/conf/compiled'
2017-04-21 23:31:27.040732 WARNING ------------------------------------------------------------
2017-04-21 23:31:27.050074 INFO Connected to Home Assistant 0.42.4
my homeassistant ip and dashboard ip is the same I presume, since they are on the same rpi.
Check your permissions on this directory. Should be 755 and owner should be the same user you are logging into the pi as. If you login as ‘pi’ than the owner should be ‘pi’.
dash_url: is important and should be the same IP address as the one you are running the Dashboards on, followed by your choice of ports. Remember, only http: is supported at this time.
dash_dir: is not important as long as you are not changing the location from the default. Mine has been commented out since I started testing the first beta.
2 Likes
My radar image doesnt refresh unless i nav from one dashboard “nav” then back to home…any ideas?
How can I fix this? CSS alignment doesn’t seem to work.
what is your dash looking like @Nutti85?
it seems like you have made your font a lot bigger.
@Vasiley i think that is a cashing problem. it could help to put in a second url and let it change automaticly.
Yeah, it’s at 550%.
temp_inne:
widget_type: sensor
title: Temperatur
title2: Inne
title_style: "font-size: 250%;"
title2_style: "font-size: 250%;"
value_style: "font-size:550%;
unit_style: "font-size: 250%;"
units: "C"
entity: sensor.netatmo_stue_temperatureat this moment you cant realign the titles and values.
rather then using such a big fontsize you could zoom the dashboard in on the device where you want to look at it.
1 Like
Hey fellas has been a long time no new release has been released . Is there something in the pipeline ? And which nice new features will wait for us?
Peace out!
hi thunder,
Andrew is away from home at the moment and cant develop anything at the moment.
but I am sure that as soon as he is back he will be all over it again. 
1 Like
I don’t have my list but there will be a bunch of small improvements, some bug fixes and a couple of new widgets on the next couple of weeks
2 Likes