A tip for splitting up your Lovelace config

Configuration
41

whats at line 51, character 11?

1 Like
42

Assuming your basic ui-lovelace.yaml structure is correct - ie. ‘views:’ is at the top level (far left) - it’s probably something in one of the included files.

Can you try moving files out of the directory one at a time, refreshing, and see if a particular one is causing the problem?

43

Typically when that occurs it calls out the position of the include which should be 6 or 7 characters in not 11. Something else is going on in his config.

1 Like
45

create a new topic.

1 Like
46

Hi!

I just splitted my ui-lovelace.yaml and works fine. The only problem is that my VSC show me a problem at ui-lovelace.yaml.
Incorrect type. Expected “array”. Why?

Captura
Captura730×870 40.2 KB

47

I use this code instead:

#
# Views
#
views: !include_dir_merge_list lovelace/
48

Hi,

I have same issue. Did you resolve this Incorrect type. Expected “array” message somehow?

49

Nothin…i changed configuration but the same result… i modified to merge and change ui-lovelace directory to lovelace buy HA do not show screen

50

am I wrong something or is it normal? let me explain, with the separation of lovelace into single files / views also for the simple configuration changes in lovelace I have to restart the assistant, when before it was enough to just update the page. it’s normal?

51

just hit Refresh, it’s in top-right corner when you click on three vertical dots

1 Like
52

thanks very kind

53

I am trying to use some tips from @petro splitting up my ui-lovelace.yaml. I do use anchors in my main ui-lovelace.yaml file, but it seems to be that i cannot use the anchor withing a view which is included. So

I do have

views: 
  - !include lovelace/views/01-home.yaml

Within the include file i cannot call the anchor and getting error ‘found undefined alias’
How do i solve this?

54

You can’t. Either use includes and no anchors. Or use no inlcudes and anchors.

Your other options are to use the decluttering card (as your anchors) with includes. Also, lovelace_gen with includes (No need for anchors).

Currently I use lovelace_gen. It allows you to piece meal your entire config but it’s not easy to set up. And you have to use heavy jinja in order to piece meal everything.

1 Like
55

I am not sure if I did the right thing. I’ve split the ui-lovelace.yaml file.

custom_header:
  compact_mode: true

views:
  - !include /config/lovelace/views/view_floorplan.yaml

And in the folder /lovelace/view/ the file view_floorplan.yaml

views:
  - id: 0
    icon: 'mdi:home'
    name: Floorplan
    panel: true
    path: floorplan
    title: Floorplan
    cards:
      - elements:
          - entity:
#etc

Bu I only get an empty view.

56

you’re already specifying view ui-lovelace.yaml as well as the dash (indicating the view). Therefore you don’t need either inside vew_floorplan.yaml.

id: 0
icon: mdi:home
... etc...
2 Likes