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.
anything changing with the way the .dash files are setup in beta2??
Not at all, I think it is working pretty well, do you disagree???
No I was just wondering if I needed to change my app that builds dash files based off of the HA groups.
Nope, nothing changed, and your app is still cool 
You know what’s really weird…I was having the same problem as you, and I went into my /etc/hosts file and also found an entry for my host’s local network name with 127.0.1.1.
I didn’t put it there.
I’m thinking there must be a bug with some RPi setup or network package we both have used.
Are you thinking the JS should always be recompiled and force or recompile should then only act on the CSS? Just wondering about those not doing any dev and just running the skins, they are most likely not using the recompile and hence wouldn’t get the JS reloads. Like what I was seeing with the background on simplyred not working.