Pre Announcement: HADasboard v2!

There is some basic info in skinning in the docs I am writing, but things will be very subject to change during the beta.

With this many people waiting to test on so many different platforms, it just makes sense to concentrate on bug squashing and function first.

I could even see a separate sub forum for skinning, including questions and sharing of skins. But we need to make sure that everything is in place first and that will take a little time.

Iā€™m thinking positively there arenā€™t going to be any functional bugs. :smile: With that said, when you get to the pretty stuff and you need an idiot to go through it and tell you what he doesnā€™t understand. I volunteer. :slight_smile:

2 Likes

4 Likes

Iā€™m going to start setting up my second instance in preparation for the beta. Iā€™m planning to do the following.

  1. Install AD on a new RPI
  2. Point it at my production HA install without shutting down my production AD install.
  3. Install beta and have fun.

RIght?

Right, except that the Beta is a new version of AppDaemon code so you will need to grab it again if you install anew AppDaemon.

Great,
Any new features in AD???

It runs HADashboard v2.

Thatā€™s new. :wink:

1 Like

Thatā€™s pretty much it - itā€™s a huge amount of code for the dashboard piece but no changes to the App piece.

Just thinkingā€¦ I currently run HAdashboard via Docker. What will the plan be for running v2 with this installation type?

You get to test it for us but it should work :slight_smile:

Hope I will not break my F5 key in order to find the beta link to V2. :slight_smile:

is there an uninstall process for the current hadashboard? (other than rebuild my server I mean)

Thanks! I basically took a hatchet to Polymer and broke things until I got far enough to prove out what it could look like. Itā€™s not something I use in my production version but if I ever get there iā€™ll be sure to share my notes. I canā€™t wait to mess around with HADashboard though, iā€™ll definitely be looking to recreate the same sort of look.

I love your idea of changing the background to correspond to the time of day by the way.

1 Like

Certainly doesnā€™t look like a ā€˜hatchetā€™ to me. Looks polished. Perhaps once the HA devs see the way the skinning is being done in Dash2, similar ideas could be adopted. They are both based on Jinja2 and Gridster, so there is a lot of commonality.

I have no doubt that you will be able to do so and rather quickly. You can probably reuse a lot of the CSS!

Thanks; itā€™s kind of basic right now, but next round I am hoping to do the same with background images instead of just colors, then maybe skinning the Weather Widget so the background corresponds to the conditions.

You donā€™t have to uninstall to run the beta; in fact itā€™s probably better that you donā€™t and run the Dash version with no apps in a separate instance for the beta to keep things clean in testing and looking for bugs.

Iā€™m running your Weather Alert app on my original instance of AD (once again, thanks for that!) and thatā€™s separate from the one that is running my dashboards.

I donā€™t have any dashboards running. The old one didnā€™t give me what I wanted so Iā€™m just on the standard HA UI right now. I was just cleaning partial installs, etc off my other PI where I am going to install this.

I think if you look at the install procedures for HADash v1 and just run it in reverse order doing pip/pip3 uninstalls instead of installs then delete the directories, that should work. But I would get a second opinion from @aimc as he would know better.

In my case, I just disabled the service and deleted the directories. I figure any of the libs he installed donā€™t take up much space and will be used elsewhere anyway.

I just deleted the directories. Iā€™ll see where that gets me and go from there. any issues with putting the new dashboard in a venv?

1 Like

Iā€™m not aware of any; I would assume that if you run AppDaemon in a venv then you could do the same with Dash2.

Iā€™m currently running it in a terminal window in as a python 3 command line for the beta.

Basically, I am doing what @aimc suggested until he tells me otherwise. My feeling is that for this beta to run smoothly, itā€™s best if we all use whatever install method that he suggests. There are a LOT of people who are going to be running this as soon as it is released and for the sake of Andrewā€™s sanity, I am strongly suggesting to folks that they follow the guidelines as he gives them.

I can only provide so much support and much of that is regarding skinning, which isnā€™t the focus of this first beta. Most of the tech support is going to be on how this gets installed or why that config doesnā€™t work on Docker or Ubuntu or what have you, and while I intend to help wherever I can, a lot of the first phase questions are going to be on him. Rene can also provide more expertise than I can, but I donā€™t know if heā€™s going to be back in time for the release.

So if you want more cool stuff like this and even better features, it just makes sense to not make these guys burn out. Iā€™m saying that the smartest and most efficient thing we can do to support him (and Rene, who is on the road at the moment) is for all of us to try to be as standardized as we can in our set ups so that we are playing in a level field. It makes it that much easier to rule out things and get to what the issue is.

Just my personal two cents from experience in FOSS over the decade.