I’ll see if I can get that into beta 2.
Not sure what I have done wrong. Can anyone help? This is what I get when starting.
2017-03-11 10:22:25.257715 INFO AppDaemon Version 2.0.0beta1 starting
2017-03-11 10:22:30.580364 WARNING ‘elevation’ directive is deprecated, please remove
2017-03-11 10:22:30.581240 WARNING ‘latitude’ directive is deprecated, please remove
2017-03-11 10:22:30.584547 WARNING ‘longitude’ directive is deprecated, please remove
2017-03-11 10:22:30.584941 WARNING ‘time_zone’ directive is deprecated, please remove
/home/debian/appdaemon_dashboard/appdaemon/conf/apps
2017-03-11 10:22:31.006635 INFO Got initial state
2017-03-11 10:22:31.009030 INFO Loading Module: /home/debian/appdaemon_dashboard/appdaemon/conf/apps/hello.py
2017-03-11 10:22:31.012906 INFO Loading Object hello_world using class HelloWorld from module hello
2017-03-11 10:22:31.156960 INFO hello_world: Hello from AppDaemon
2017-03-11 10:22:31.161112 INFO hello_world: You are now ready to run Apps!
2017-03-11 10:22:31.162055 INFO App initialization complete
2017-03-11 10:22:31.288667 INFO Connected to Home Assistant 0.39.3
I’m guessing your appdaemon.cfg file looks a bit like this:
[AppDaemon]
ha_url = http://192.168.1.4:8123
ha_key =
logfile = STDOUT
errorfile = STDERR
threads = 10
latitude = 50.7274
longitude = 6.8762
elevation = 21.82
time_zone = Europe/Dublin
dash_dir = /home/hass/appdaemon_dashboard/appdaemon/conf/dashboards
dash_url = http://192.168.1.40:5050
# Apps
[hello_world]
module = hello
class = HelloWorld
If it does, change it so it looks like this:
#latitude = 50.7274
#longitude = 6.8762
#elevation = 21.82
#time_zone = Europe/Dublin
And make sure your dash_dir, and dash_url lines are before the # Apps section, as in the example above.
That should do it.
1 Like
Thanks. Working great. Now I can have fun. lol
2 Likes
Here’s my latest try at a Portrait mode for the R Pi touchscreen.
The settings that worked for me:
title: R Pi Portrait Panel
widget_dimensions: [118, 118]
widget_margins: [7, 7]
columns: 5
I resized the images I liked to 640 x 1138, and found most of them via https://www.reddit.com/r/Verticalwallpapers/
It’s such a pleasure using this new way of doing things 
I’m starting to feel sorry for the main HA view.
There wouldn’t, by any chance, be a clever person working on how to change the background to a poster of currently playing Kodi file?
3 Likes
Not yet but it’s certainly possible - adding to list 
1 Like
Glad you think so - me too! I just rebuilt a load of my dashboards and it was pretty easy using the new layout vs HADashboard v1.
1 Like
Yes, I removed them already, they will no longer be there in beta 2.
1 Like
This now officially IS in beta2
Wonderful!!! Thanks
@aimc @rpitera in regards to the JS not loading on reload widget or page refresh…I am not losing my mind, I figured it out. Guessing you both have “dash_force_compile = 1” in your .cfg file. I didn’t and that is why things were not working on refresh/reload. With it added all works as expected. I can now put my javascript for dummies book back on the bookshelf 
1 Like
You’re absolutely right. Nice find and I’m glad you got that mystery solved.
Thanks, you and me both! Called my insurance company to check my mental health coverage options… Thanks to both for testing things and letting me know it really was something local to my install/setup.
1 Like
It never even occurred to me, but I think it’s something @aimc will be glad to be aware of. Maybe there could be a flag or switch in the future to force compile only CSS.
At the moment you can force it in the config file, or per dash by adding recompile=1 or just recompile to the URL args. (I don’t remember if that last one was in beta 1 or not). Given that I can’t really figure it out dynamically when skins add new filles via the includes, I think I will strengthen the recommendation (or even add it!) that you use force_compile whenever developing skins.
Thanks for reporting back!
1 Like
I’m still having problems with an input slider not coming over correctly. This particular input slider is created in HA with a default value of 0. It then gets updated from my production copy of AD. But the web install of AD isn’t picking up the value. How does the dashboard get the value from HA? Does it just do a get_state or something else?
Here is the widget from my dashboard file.
dsp1hp_black:
widget_type: input_slider
value_style: "font-size: 100%;"
entity: input_slider.dsp1hp_black
title: dsp1hp black
increment: 1
units: u
Here is how it looks in HA. Notice the value is definitely not 0.
Same thing is happening with a couple of normal input sliders that don’t have anything to do with the production version of AD.
nighttime_hour:
widget_type: input_slider
value_style: “font-size: 150%;”
entity: input_slider.nighttime_hour
title: nighttime hour
increment: 1
units: H
nighttime_minutes:
widget_type: input_slider
value_style: “font-size: 150%;”
entity: input_slider.nighttime_minutes
title: nighttime minutes
increment: 1
units: M
What happens if you don’t specify the increment?
New version of input slider in beta 2 tomorrow.
No difference. I tried refreshing the screen via the browser, reloading the screen and specifying recompile on the url.
Ok, let’s see what happens with beta 2 and we will take it from there.