then I am 100% agree! 
Great news!
Iām in for the beta if itās not to late.
Just to expand on Reneās comments - a huge part of why I did this was to provide a basis to move forward. I am building this in as open ended a way as possible, as others who know my work from AppDaemon would agree that I like to do
So when I see something like the dash you just posted, my immediate thought is āyes, I could do that widget this wayā, oh and thatās a cool idea we could build something like that", instead of with the old dash: āwow, Iām glad its still working, but I have no idea to add in something like thatā - if you check my thoughts at the beginning of the thread you will see that this agrees with what I said then.
So while I canāt promise to duplicate OpenHabās interface, nor would I want to, I am very open to cool ideas for new widget types. So far we are covering the basics with 1:1 mappings of device types to widgets, but there is a huge amount of potential for cool compound widgets that show multiple pieces of info and allow interaction, and I will happily accept ideas from any source.
So would this need to run on the same server as where I have AD installed, or can it run on a different server? Can you have two AD instances talking to the same HA instance?
It is integrated with AD, so you would just use the same instance in production.
For the Beta it is perfectly fine to run a second instance for testing purposes if you want to ensure your existing automations arenāt affected. If you do that, it can be on a separate machine yes.
The reason I ask is Iām already getting time skew adjustment warnings in my AD log. So Iām trying to keep a handle on anything I add to that box. I can move the entire AD install to another box away from HA, and that will give me room (cpu/memory) to install this too and not overtax things to much.
OK, makes sense. For what itās worth, although I didnāt intend it to be used this way you can perfectly happily run them separately on separate hosts in production as well. There is code in there to shutdown the pieces you arenāt actually using, e.g. all of the app stuff if just using the dashboard.
one noobish question. Will there be a hoe-to to setup the dashboard as I am not into AD
Yes, the docs are in place. You need to install AppDaemon in the same way, but you donāt need to program any Apps, the Dashboard is configured with YAML files which should be familiar to all.
The Beta notice as well as the docs will contain full instructions.
uuugh I went to AD to get away from YAML. LOL
Donāt worry, it isnāt very complex YAML, it never goes more than one field deep!
As long as I donāt have to learn templates.
i have been running appdaemon on my windows pc a long time after i did put HA on my RPI and that did work fine.
i dont think you have implemented anything now that would give a problem running appdash on a different machine.
1 Like
No templates. Here is a quick idea:
Layout of the dasboard:
layout:
- mode(2x1), label(3x1), side_humidity, andrew_presence, binary_sensor.porch_multisensor_sensor_27_0
- clock.clock(2x1), weather(2x2), scene.office_on, office_off, hall, office_light
- media_player(2x1), rene, input_slider.test, input_boolean.heating, office_light_switch
- summary(2x1), garage
- spacer(8x1)
- include: bottom_panel
and a simple example of an (optional) widget declaration:
side_humidity:
widget_type: sensor
title: Humidity
title2: Sensor
units: "%"
precision: 0
entity: sensor.side_humidity_corrected
OKJā¦ just added APPDAEMON to my hass serverā¦ it is running up. just need to figure out how to start on boot as i am currently using screen
+another 1 for beta, please
1 Like
Bear in mind youāll need a new version for the Dashboard, but the install will be identical.
I need to be into the beta 
Now I have my AD running and with my apps all set up, next thing is test this
1 Like
If you still adding people to beta group I am in too!
Excited
Sure thing - it will be completely open - stay tuned for a Beta announcement thread
3 Likes