I didn’t understand how to chose skins in fact 
You put this at the end of your URL - after the dash name - in your browser:
?skin=skinname
For example: http://192.168.1.181:5050/MainPanel?skin=default
Besides the default skin, there are four skins in the beta, and they are called as follows:
?skin=zen
?skin=obsidian
?skin=simplyred
?skin=glassic
Keep in mind that when you apply a skin, your font sizing may need to be adjusted for certain widgets. It was hard for me to determine a size that would work fro everybody, so some adjustment is expected.
2 Likes
I should put that in the docs 
1 Like
You know, I never noticed that was missing. If you remember when we started, I had just guessed the proper URL to call a skin and gotten lucky. I guess we both forgot after that!
If I reduce size (change ratio) of widget in the dashboard should it automatically shrink icon and all other items inside widget like shown below? Notice that I have reduce the height to 90 from 120. But my dashboard didn’t reduce icon size, how do I specify to reduce it?
title: Kitchen Panel
widget_dimensions: [120, 90]
widget_margins: [5, 5]
columns: 8
The widget dimension is really there to fine tune the aspect ratio so a set of tiles fill the screen off your tablet. Making drastic changes will mess with alignment as you have seen. In future I hope to make the widgets better at handling this, but the only solution I have now would be to ditch the alignment as was the case in the previous dashboard and nothing would line up, and the result would be just as bad
You can make the icons smaller by changing their styles either at the widget level oir in a skin which should help a little.
Try something like this in the widget definition:
icon_active_style: "font-size: 200%"
icon_inactive_style: "font-size: 200%"
And play with the numbers until you get something better. That style will apply to the icons and text. Check the widget desctiptions to see which style options are supported.
Nice, I will play with numbers to best suit my needs. Let’s see how it goes with different tables and phones.
thanks
At the very least it should be possible to center the icons vertically which is 99% of the issue, but I need to add some additional templating and parsing to the widgets to enable that which I am not planning to do just now.
i think they like it so much that they really would like to intergrate the 2.
i can easily see ways to replace the old frontend with dashboard completely.[quote=“scadaguru, post:346, topic:13141”]
but it would be really nice if we could just reuse the icons which are already customized in HA
[/quote]
customized icons are an atribute in HA.
i think that it isnt that difficult to set those icons as default for a widget and then only override if an icon is set in the widget yaml.
am i right @aimc is this an easy option for after beta?
Shouldn’t be hard, I’ll add it to the list. Only issue is that HADashboard supports active an inactive icons, but I can just use the HA icon for noth and you can override if desired in the widget definition.
2 Likes
That would be great if someone like me wants both HA and AdDashboard look and feel same.
Thanks
Can you pass a variable into a scene or into a dashboard through the URL
NOt yet although I am planning some integration between the two - along the lines of letting AppDaemon send state information to the Dashboard.
2 Likes
If you think of it in terms of CSS, the widgets are the box-model. Changing the size only changes the size of the box, not the styles of the content.
I’m having this same exact issue.
ha_admin@habuntu:~/appdaemon_dashboard/appdaemon$ python3 -m appdaemon.appdaemon -c ~/appdaemon_dashboard/appdaemon/conf
Traceback (most recent call last):
File “/usr/lib/python3.5/runpy.py”, line 184, in _run_module_as_main
“main”, mod_spec)
File “/usr/lib/python3.5/runpy.py”, line 85, in _run_code
exec(code, run_globals)
File “/home/ha_admin/appdaemon_dashboard/appdaemon/appdaemon/appdaemon.py”, line 35, in
import appdaemon.appdash as appdash
File “/home/ha_admin/appdaemon_dashboard/appdaemon/appdaemon/appdash.py”, line 13, in
import appdaemon.dashboard as dashboard
File “/home/ha_admin/appdaemon_dashboard/appdaemon/appdaemon/dashboard.py”, line 7, in
from jinja2 import Environment, BaseLoader, FileSystemLoader, select_autoescape
ImportError: cannot import name ‘select_autoescape’
I tell it to install jinja2 2.9.5 and it installs 2-2.8 markup 0.23
ha_admin@habuntu:~/appdaemon_dashboard/appdaemon$ pip3 install Jinja2==2.9.5
Collecting Jinja2==2.9.5
Using cached Jinja2-2.9.5-py2.py3-none-any.whl
Collecting MarkupSafe>=0.23 (from Jinja2==2.9.5)
Installing collected packages: MarkupSafe, Jinja2
Successfully installed Jinja2-2.8 MarkupSafe-0.23
You are using pip version 8.1.1, however version 9.0.1 is available.
You should consider upgrading via the ‘pip install --upgrade pip’ command.
So when’s beta 2 going to be released?
I found the culprit; there apparently was an invalid character in the config. Most probably due to an invalid line end by using the wrong EOL settings in one of my editing programs.
.the docs are very large. So maybe some users here could post their Screenshots and config they did to make it easier for people to start… Like me… 
the easiest way i can think of. (but its my way)
a main.dash like this:
title: Main Panel
widget_dimensions: [120, 120]
widget_margins: [5, 5]
columns: 4
layout:
- input_boolean.huiskamerverwarming, sensor.huiskamer_box_4_1, switch.hboog, switch.epchoek
- input_slider.huiskamerthermostaata, switch.kachel_9_2, switch.hbank, switch.ewandmeubel
- input_slider.huiskamerthermostaatb, switch.kachel_9_3, switch.hrozenhoek, switch.eraamhoek
- input_slider.huiskamerthermostaatc, switch.irverwarming, switch.kachel_9_1, input_boolean.allesuit
- input_slider.huiskamerthermostaatd, switch.relay_template_35_1, input_boolean.swr3, input_slider.radio_volume
- input_slider.huiskamerthermostaate, switch.relay_template_35_2, spacer, spacer
- dashboard.buiten, dashboard.keuken, dashboard.slaapkamer, dashboard.gang
wil result in a dashboard.
from that moment on i start finetuning.
for each entity i create a file with the name entity.yaml like switch.kachel_9_2.yaml
in those files you can finetune all kind of settings like title, icons etc.
widget_type: switch
title: Huiskamer
title2: kachel stand 1
entity: switch.kachel_9_2
icon_on: fa-fire
icon_off: fa-fire
When I get to the end of my list of stuff to do! A lot of the work is under the covers - rewriting widgets, adding error checks etc.
Why, what are you expecting to see in it?