Ordering of dashboards in YAML mode

Configuration Frontend
1

I use YAML mode for my lovelace configuration. ui-lovelace.yaml contains:

title: Beatrice
views: !include_dir_merge_list ui-lovelace

The ui-lovelace/ folder contains a hierarchy of folders and files which assemble into a working interface. The top level of the hierarchy is:

$ ls -l ui-lovelace/
total 16
drwxr-xr-x    2 root     root          4096 Apr 21 11:00 000-default
drwxr-xr-x    2 root     root          4096 Apr 17 07:24 020-map
drwxr-xr-x    2 root     root          4096 Apr 22 10:51 030-spaces
drwxr-xr-x    3 root     root          4096 Apr 22 10:51 040-services

Each folder contains a dashboard definition which begins in a similar
way. For example, the 000-default folder contains a 000-default.yaml
file which begins:

  - title: Home
    path: default_view
    type: panel
    cards:
      ...
      ...

I expect my menu to be ordered according to the !include alphabetic sort, but in fact my menu bar items are ordered “SPACES SERVICES MAP HOME”

Nothing I do in terms of renaming the included directories or their included yaml files results in a change in the established order, which seems to be stuck. I have checked the order in the .storage direcory’s ui-lovelace file and it is correct (in the sense that the view entries are ordered alphabetically).

So, how do I dictate the order in which dashboards appear in the lovelace menu bar?

PR

2

I would suggest you not to use this method.
Use an explicit list instead:

views:
  - !include .../.../xxx.yaml
  - !include .../.../xxx.yaml
  - !include .../.../xxx.yaml
  - !include .../.../xxx.yaml
  - !include .../.../xxx.yaml

where every view contains (note - no leading “-”)

title: xxx
path: xxx
cards:
  ...

Pros:
– user-defined order
– you may place yaml-files for views in separate subfolders like “car”, “garden” - where each folder has topic-related views.

3

Thank you for the suggestion which solves my problem.

Interestingly, the ui-lovelace file generated in .storage is exactly the same whichever method I use, but only your suggestion of using explicit separate !include statements results in a properly arranged view menu. Bizarre!