DD - Automatic area-based dashboard for desktop, tablet and mobile - V3.7.0

After updating to the recent version of Home Assistant, I sometimes get the following error:

Custom element doesn't exist: dwains-flexbox-card.
type: 'custom:dwains-flexbox-card'
padding: true
cards:
  - type: 'custom:dwains-flexbox-card'
    item_classes: col-xs-12 col-sm-6 col-md-5 col-lg-4
    cards:
      - type: 'custom:button-card'
        item_classes: col-xs-3 d-block d-sm-none
        template: header_house_information
      - type: 'custom:button-card'
        item_classes: col-xs-6 d-block d-sm-none
        template: header_weather
      - type: horizontal-stack
        item_classes: col-xs-12 d-none d-sm-block
        cards:
          - type: 'custom:button-card'
            template: header_house_information_large
      - type: 'custom:dwains-notification-card'
        item_classes: col-xs-12
        style: |
          ha-card {
            padding: 0px;
          }
          #title {
            color: var(--dwains-theme-header-text);
            font-size: 22px;
            font-weight: bold;
          }                        
        title: |
          [[[
            var today = new Date()
            var curHr = today.getHours()

            if (curHr < 12) {
              return "Guten Morgen";
            } else if (curHr < 18) {
              return "Guten Tag";
            } else {
              return "Guten Abend";
            }
          ]]]
        max_notifications: 2
        navigation_path: more_page_notifications
  - type: 'custom:dwains-weather-card'
    item_classes: d-none d-sm-block col-sm-6 col-md-3 col-lg-3
    entity: weather.home
    tempsensor_entity: sensor.netatmo_home_balkon_temperature
    style: |
      ha-card {
        background: var(--dwains-theme-header-button-background) !important;
      }
      .variations, .variations ha-icon, #main {
        color: var(--dwains-theme-header-button-text) !important;
      }
  - type: 'custom:mod-card'
    item_classes: col-12 col-sm-12 col-md-4 col-lg-5
    style: |
      ha-card {
        margin-top: 5px;
      }
      @media only screen and (min-width: 600px) {
        ha-card {
          margin-top: 15px;
        }
      }
    card:
      type: 'custom:dwains-collapse-card'
      card_width: 62px
      cards:
        - type: 'custom:button-card'
          template: header_states_door
        - type: 'custom:button-card'
          template: header_states_window
        - type: 'custom:button-card'
          template: header_states_lock
        - type: 'custom:button-card'
          template: header_states_light
        - type: 'custom:button-card'
          template: header_states_climate
        - type: 'custom:button-card'
          template: header_states_cover
        - type: 'custom:button-card'
          template: header_states_device
        - type: 'custom:button-card'
          template: header_states_media_player
        - type: 'custom:button-card'
          template: header_states_vacuum
        - type: 'custom:button-card'
          template: header_states_plant

It disappers automaticly after several reloads.

Is there anybody else having this issue?

1 Like

Yes, I get the same.

1 Like

I’m working on this :slight_smile: will be fixed in next release, which will come asap.

6 Likes

Is it possible to set the color/brightness of lights for all lights in one room / in general? Didn’t find a way to do to.

Heyy,

Just got a few Zigbee Smoke sensors and tried to integrate them in your theme.
I tried to use this for the room:

safety: binary_sensor.wohnzimmer_rauch

and in global.yaml the normal String :

safety_ok_strings: [“Ok”, “Idle”, “off”]

Sadly I don’t see anything in the room even if I change the value of the sensor to on, which indicates smoke detected.
Is this still working or am I doing something wrong ?

Safety devices will only work in the upcoming 1.5 version, it won’t work in 1.4.1

Thank you for clarifying :slight_smile:
P.s. You are doing a really good job.
I’m really looking forward to 1.5. I no longer update until 1.5 is out just
to be sure it is working fine until release ^^

Important NEWS

I had a discussion about the name “Dwains Theme” on my themes Discord server. Home Assistant uses the name theme for some files you can make for customizing the colors of HA itself. As this project is a fully working interface. I was thinking about renaming it to Dwains Interface or Dwains Dashboard. It also confuses people, because they think Dwains Theme is just a file with some colors and not a fully worked-out working interface.

I did a small poll and the outcome was simple. We are going to rename Dwains Theme to Dwains Dashboard.

So in the upcoming next release I will change the name from Dwains Theme to Dwains Dashboard everywhere. I’ve already changed the Github repo name. The problem is that some files still link to the docs on https://dwainscheeren.github.io/lovelace-dwains-theme/ but that URL doesn’t work anymore! The new URL is: https://dwainscheeren.github.io/dwains-lovelace-dashboard

Want to discuss too and know the latest inside news about Dwains Dashboard? Join my Discord server: https://discord.gg/cfWdNqD

5 Likes

Hey,

Just a little question as for now my nuki lock gets unlocked and locked very well.
For 1.5 I would wish to open the door fully not just lock and unlock :slight_smile: (lock.open service)
If it doesn’t make too much work ^^
(I mean I can change it by my own :slight_smile: But natively supported feels better ^^)

Edit:
As for now I changed the hold_action to call lock.open ^^ (the popups currently not working that well so no disadvantages)

Why not using dwainboard for the new name ? I love it :heart:

2 Likes

You can call it Dwainboard my friend :smiley:

1 Like

danke :slight_smile: I will chose maybe a better name :blush:

Good morning!

I’ve got a question which may or may not be possible, but curious if anyone knows none the less. I have updated my smart bulb line up to consist solely of Inovelli LZW42’s. These are great bulbs, with a minor annoyance that they ramp up/down very slowly by default (could take up to around 5 seconds to ramp down from max brightness for example).

There are a few methods that can be used to address this; I could go into the bulb itself and set the transition time directly within the bulb config options. This would resolve all issues, at the cost of me being unable to use a unique transition time within future automation’s… Unfortunately I rely on manually defined transition times in a couple of my automation’s, so I cannot do this.

Option two is, as previously mentioned, define transition time manually in automations. This is the method I’ve used until now and it works well, but there’s no place I can see to do this within Dwains theme. So while it works perfectly (and looks the best out of every theme I’ve tried using in the past), if I use it to turn my bulbs on, they turn on/off very slowly.

Does anywhere know where I could set a defined transition time for this theme, if anywhere? It’s really not the end of the world if it takes a little longer than I’d like to turn bulb on/off, this just became more of a curiosity thing for me at this point. :slight_smile:

Thanks in advance!

To be honest. I don’t know. I only have Philips Hue bulbs (they are the best on the market) and some ESPHome controlled lights.

1 Like

Are you using the normal Philips Hue Bridge?
I’m using deConz and I don’t like Philips Hue as they do not provide firmware updates
for non Hue Bridge Users.

I do yes, I have Hue bridge with all lights + motion sensors. This way my house lights always work 100% uptime. I also have used zigbee2mqtt, cc2351 with ZHA, and conbee stick with ZHA and with Deconz for all my other sensors in the house.

Does anyone use the camera tab?
I have a few camera’s setup but the website crashes if I’m on the tab viewing cameras for more than 30 seconds.

configuration.yaml

    name: Living Room Camera
    username: root
    password: xxxxxx
    authentication: basic
    still_image_url: https://192.168.xx.xx/cgi-bin/currentpic.cgi
    verify_ssl: false
    scan_interval: 5
  - platform: generic

cameras.yaml

cameras:
  - entity:  camera.front_door

Yes I do, and it works fine with my camera connected vis my synology, except I mostly have to reload the page to get the camera picture to show.

The camera tab works fine for me. No crashing and no refreshes required.

What was the solution for the mistake you had?

while parsing a flow mapping in “/config/dwains-theme/addons/rooms/office/sonos/button.yaml”, line 6, column 10 expected ‘,’ or ‘}’, but got ‘[’ in “/config/dwains-theme/addons/rooms/office/sonos/button.yaml”, line 6, column 29