Announcement: HADashboard v2 Beta!

Third party integrations HADashboard
141

Man, I keep waiting to see a 39.x success story but I haven’t seen any!

142

OK, let us know how it goes.

143

I read through that a couple of times but for some reason I can’t understand it. I think maybe I need to see an example in the docs. I’m sure it’s simple but for some reason I have trouble figuring it out.

144

Remote access issue.

I can get to the pages ok. But it’s like the icons don’t completely load, see below.

I can click on things but nothing happens.

Nothing in the logs, nothing in stdout

145

Expanding on my phone-written reply from last night, I have it this way for 2 reasons:

  1. Sometimes my device trackers mess up and I want an easy way to fix it
  2. It is very useful for testing.

I will add an option to allow you to enable/disable this behavior in the next beta.

146

It did come in handy during skin testing.

147

And another longer explanation :slight_smile:

I do plan to support this, but for this and a number of other widget extensions I am planning, I need a new design pattern - I need to be able to pop up an overlay dialog on the dash. I will use this for a bunch of things - errors, persistent messages, dimmers and color pickers, and perhaps autopopping up camera images when movement is detected, and I also plan to support messages directly from AppDaemon.

I haven’t done the work to figure out the best way of popping up the dialog yet, so those changes will need to wait until I have that done.

148

I was thinking about this myself (I use Chip’s Weather Alert persistents for HA) and was wondering if HTML5 notifications would work here.

149

OK, so you are accessing this remotely over the Internet? I hope you are using an SSL proxy :wink:

I’m not immediately sure what the issue would be here, is this a laptop browser perhaps? If so, can you see what errors there are on the JavaScript console?

150

I’ll certainly look into it :slight_smile:

151

Here is my header

(venv) pi@haweb:~/appdaemon_dashboard/appdaemon/conf/dashboards$ cat header.yaml 
clock:
    widget_type: clock
Chip:
    device: turboc1208_cc1208
    widget_type: device_tracker
    title: Chip  
Susan:
    device: scox1209_scox1209
    widget_type: device_tracker
    title: Susan
Charlie:
    device: ccox0605_ccox0605
    widget_type: device_tracker
    title: Charlie
Sam:
    device: scox0129_sc0129
    widget_type: device_tracker
    title: sam
layout:
    - label(2x2),Chip(1x1), Susan(1x1), Charlie(1x1), Sam(1x1),clock(2x2)
(venv) pi@haweb:~/appdaemon_dashboard/appdaemon/conf/dashboards$

Notice that in my layout there is a widget called label, but it’s not defined in the widgets above.

(venv) pi@haweb:~/appdaemon_dashboard/appdaemon/conf/dashboards$ cat Den.dash 
#
# Main arguments, all optional
#
title: Den Panel
widget_dimensions: [120, 120]
widget_margins: [5, 5]
columns: 8

label:
    widget_type: label
    text: Welcome to the Den

But it is defined in my Den.dash file and in my Master.dash file. In the Den it says “Welcome to the Den” in Master.dash it says “Welcome to the Master Bedroom”. It’s a way to effectively pass a dashboard based variable to the header or footer.

1 Like
152

OK for this one I just need you to do the following:

  1. Make sure you are capturing HA’s logs, including the detailed state information
  2. Turn your media player on then off with the HA client
  3. Raise and lower the volume from HA a few times

That should give me enough info in the HA logs to understand what is going on.

153

Mind if I grab that example as well for the docs?

1 Like
154

That’s fine, I was just working on migrating things to the dashboard and I ran into thinking about my weatherAlert app that uses persistent notifications to pop up messages for the HA UI.

1 Like
155

Thank you! I knew if I saw it, I would understand it better - I guess I am a visual thinker in a lot of respects.

This now makes perfect sense to me! Maybe a similar example can be shown in the docs to helps others with the same type of thinking?

Thanks again.

156

LOL, just got done saying the same thing. I love that app!

157

It’s not going to be hard to do, I just need the time to work on the dialog thing which I currently have slated for right after the beta finishes.

158

I don’t know how easy it is; I had a devil of a time setting them up for HA as did a lot of others.

Robbie ended up helping me on Gitter to get it to work. Although it may be easier from AD.

159

Cheers for all for this!

I’ve just done my first quick cut & paste from my old dashboard - and it went a treat.

first-new-dash.png1089×510 54.1 KB

I’ll get into sprucing it all up now :slight_smile:

One silly thing which stumped me for longer than I’m prepared to admit, config file ordering.

My dashboard wasn’t showing up and there was no listening message because my config file section looked like this:

# Apps
[hello_world]
module = hello
class = HelloWorld

dash_dir = /home/ ... /appdaemon/conf/dashboards

dash_url = http://192.168.178.40:5050

Now it works properly with this:

dash_dir = /home/ ... /appdaemon/conf/dashboards

dash_url = http://192.168.178.40:5050

# Apps
[hello_world]
module = hello
class = HelloWorld

And I’m running on: ubuntu 16.04, x86 64, and not in a virtual env.

2 Likes
160

Yes, you need the dashboard stuff in the AppDaemon section - I’ll clarify that in the docs, thanks!

That’s a mighty fine looking dashboard you have there sir!

1 Like