Is it possible to add a panel (side tab in HA) to the dashboard?
if you know how to create it, you could make it yourselve.
in the skins variables.yaml you can include anything you like to the body and to the head.
and thank you for making me think about that.
Thanks @rene !
Any chance you could give me a hint to get started or something to google…I have the html code, I am just confused where to put it,and how to access it once I put it somewhere.
# Custom styles instructions
# 1. Create a new directory under css
# 2. copy these files over
# 3. EDIT
# 4. Select the new dir as the "skin" argument of any
# dashboards you want to use it
This particuraly, is thi what I am looking to do?
1 Like
in any skin (so in the directory custom_css, or in 1 of the default skins) you find a variables.yaml
if you open that you find at the top:
# Core styles. Reference these wherever possible rather than making custom
# versions of red, green, etc. This will make it easier to quickly change the
# overall pallette of the dashboard just by overriding these variables.
# This file contains the application "defaults".
# IF YOU WANT TO CUSTOMIZE styleS FOR YOUR OWN INSTANCE, DO NOT EDIT THIS FILE.
# ----------------------------------------------------------------------------
# Custom styles instructions
# 1. Create a new directory under custom_css
# 2. copy these files over
# 3. EDIT
# 4. Select the new dir as the "skin" argument of any
# dashboards you want to use it
# ----------------------------------------------------------------------------
#
# Custom head includes - should be a YAML List, e.g.:
#
#head_includes:
# - some include
# - some other include
#
# Text will be included verbatim in the head section of the doc, use for styles,
# javascript or 3rd party css etc. etc.
#
# It is your responsibility to ensure the HTML is correct
#
head_includes:
- <! head tags go here ->
#
# Custom body includes - should be a YAML List, e.g.:
#
#body_includes:
# - some include
# - some other include
#
# Text will be included verbatim in the body section of the doc, use it for JavaScript
#
# It is your responsibility to ensure the HTML is correct
#
body_includes:
- <! body tags go here ->
so if you want to add some other HTML to the body (a menu) then the dashboard, you put it at body.
some general js scrips can be put in the head.
if you want a table structure with links in the left part i gues you put it in the body.
i dont know where the dashboard will go, but i expect in the end, thats just trying out pasting some simple things in the body part.
1 Like
Thanks, I appreciate you taking the time to explain it. Im going to play with that in a hour or two, Ill let you know if I get it going.
ill love to see what you come up with.
i would like to have 48 hours in a day to explore all the possibilies and ideas that i have in my head 
LOL. yesss! I would love that! HA is addicting lol
AD even more
Man i really wanna learn that. I planned on reading those docs and starting on my flight to the west cost over the holidays. I ended having to work though…so do you use AD for all your automations and entities? Would you even need hA?
I never use HA, i dont even worry about groups, I got 1 giant nasty page lol. I just use it for the dashboards! 
i use AD for all my automations ( i even recreated automations as an app, to do almost anything i need)
my apps.yaml is 1300 lines!
i create some groups and a lot of important sensors from AD.
but all entities are still part of HA.
i see it like this:
HA is the collection of stuff i have.
AD is everything i do with that stuff (including recording sensor states)
i add all my stuff to HA, to work with it with AD.
1 Like
AH ok, that helps. SO HA does the same thing I use it for but you do all the magic AD instead of me doing all my automations and sensors in HA. Im gonna get started on that…I dont have much to do this weekend so hopefully I can get it! Thanks man!
1 Like
just an automation to think about using HA automations:
bedroom motion detector:
if activated between 0:00 and 6:00 and noone in bed, set person 1 in bed, activate some stuff
if activated between 0:00 and 6:00 and 1 person in bed, set everyone to bed, activate some other stuff
if activated between 6:00 and 12:00 and all in bed, activate some stuff
if activated between 6:00 and 12:00 and 1 person in bed, activate some other stuff
if activated and noone home, notify
if activated at all do also other stuff.
just some things i use AD for with only 1 sensor, which would be extremely complicated with HA automations.
Nice. Seems like there’s a lot more you can do with AD looking around the forums
Can you share it?
i could but you wouldnt find anything usefull in it for you.
apps.yaml is connected to specific apps.
without the apps the yaml is useless.
Understand, wish to start using appdaemon by example (starting by using existing code, with automation that I need, and just changing entity_id
most apps that people write are specific for their own wishes.
those apps that are made a little more general and ten the enities are the first thing that are taken out of the code, so using those apps wont teach you anything.
if you want to start learning how to write your own apps, then start from nothing and just do it.
i wrote appdaemon for beginner, just for that.
1 Like