Minimalistic Templates can't be loaded despite correct configuration

[schaert]

I have tried for hours to make the templates work and I'm starting to doubt my abilities to follow instructions...

frontend: themes: !include_dir_merge_named themes

The indentation is correct (two spaces before themes) and my folder "themes" does exist and contains the two folder with the desktop and mobile themes respectively. The folder is in the same directory as the configuration.yaml. The desktop theme starts as follows:

---
minimalist-desktop:
  #Journal
  state-icon-color: "rgb(var(--color-theme))"
  border-radius: "20px"

etc.

What's weird is that before I installed those two themes I had installed an iOS Dark Theme through HACS and it worked without adding the inclusion on top of this post.

I'm getting the following error when checking my config:

Invalid config for [frontend]: value should be a string for dictionary value @ data['frontend']['themes']['minimalist-desktop']['modes']. Got OrderedDict([('light', OrderedDict([('primary-text-color', '#212121'), ('primary-color', '#434343'), ('google-red', '#F54436'), ('google-green', '#01C852'), ('google-yellow', '#FF9101'), ('google-blue', '#3D5AFE'), ('google-violet', '#661FFF'), ('google-grey', '#BBBBBB'), ('color-red', '245, 68, 54'), ('color-green', '1, 200, 82'), ('color-yellow', '255, 145, 1'), ('color-blue', '61, 90, 254'), ('color-purple', '102, 31, 255'), ('color-grey', '187, 187, 187'), ('color-pink', '233, 30, 99'), (.... (See /config/configuration.yaml, line 5).

Line 5 refers to the include statement posted on top.

The template list is shown in settings, and they can be selected but won't be applied upon selection. Please not that I deleted all other templates to avoid any side effects caused by those.

I have no idea how to proceed after I've found quite a few similar problems on Google which always stated that people are including themes the wrong way but I can't figure out what's supposed to be wrong here.

Any help would be appreciated! Thanks!

[CM000n]

The themes entry belongs under the frontend entry. 😝

So instead of this...
frontend: themes: !include_dir_merge_named themes

...it belongs like this

frontend:
  themes: !include_dir_merge_named themes

[schaert]

You're right - apologies. That and the missing dashes where little changes I made just to check if this changes anything. The dashes for example are something I hadn't seen anywhere else before so I started to apply some trial and error procedure.

I now copied everything again through the samba add-on; I'm connecting directly to the folder on my Raspberry Pi using SMB in my Mac's finder. So basically all the original files from the downloaded ZIP file are now on my config folder unchanged. If you want, I can upload them to the rep as well if it makes sense.

Oh and of course the error is still there :-/

[CM000n]

Even if I don't think it's because of that, where do you load the lovelace resources necessary for the theme? I could not find anything in your config.

This may also help to get a better feeling for what is happening: https://www.home-assistant.io/docs/configuration/splitting_configuration/#debugging-configuration-files

[schaert]

Not sure if I understood your question correctly but the test dashboard I created based on the example can be found in lovelace-minimalist.yaml.

I will take another look at the documentation as well, thanks for the pointer.

[CM000n]

You have not uploaded your lovelace-minimalist.yaml 😉

I mean the Lovelace resources.
The resources (HACS custom cards) currently required for the minimalist UI are also described in our documentation here under point 5. https://ui-lovelace-minimalist.netlify.app/installation/yaml-mode
In my configuration, for example, it looks like this:

# https://www.home-assistant.io/integrations/frontend/
frontend:
  extra_module_url:
    - /hacsfiles/lovelace-card-mod/card-mod.js
  themes: !include_dir_merge_named themes

# https://www.home-assistant.io/lovelace/
lovelace:
  mode: yaml
  resources:
    [ { url: /hacsfiles/bar-card/bar-card.js,                                        type: module },
      { url: /hacsfiles/button-card/button-card.js,                                  type: module },
      { url: /hacsfiles/kiosk-mode/kiosk-mode.js,                                    type: module },
      { url: /hacsfiles/light-entity-card/light-entity-card.js,                      type: module },
      { url: /hacsfiles/light-popup-card/light-popup-card.js,                        type: module },
      { url: /hacsfiles/lovelace-hui-element/hui-element.js,                         type: module },
      { url: /hacsfiles/lovelace-layout-card/layout-card.js,                         type: module },
      { url: /hacsfiles/lovelace-slider-entity-row/slider-entity-row.js,             type: module },
      { url: /hacsfiles/mini-graph-card/mini-graph-card-bundle.js,                   type: module },
      { url: /hacsfiles/swipe-card/swipe-card.js,                                    type: module },
      { url: /hacsfiles/lovelace-xiaomi-vacuum-map-card/xiaomi-vacuum-map-card.js,   type: module },
      { url: /hacsfiles/thermostat-popup-card/thermostat-popup-card.js,              type: module },
      { url: /hacsfiles/my-cards/my-cards.js,                                        type: module }, ]
  dashboards:
    lovelace-minimalist:
      mode: yaml
      title: Minimalist
      icon: mdi:floor-plan
      show_in_sidebar: true
      filename: lovelace-minimalist.yaml

But really mysterious. Your Home Assistant seems to be doing some wild things with your config. 😋

[schaert]

Really weird stuff. Anyway thanks for looking into this. I will probably set up my whole Hass installation from scratch as it's not that complex!