using !include in the Lovelace configuration is still a bit if a exploration for me.
I have my main ui-lovelace.yaml point to my view_files.yaml in a dedicated folder /config/lovelace/
works very nicely indeed and makes for a very very clean ui-lovelace.yaml
resources are simply called via their own dedicated path, pointing to a subfolder in the /local/lovelace (www folder) so nothing special.
I had already found out that I can use images in he same way, but only in that www folder (or a subfolder ). Not in the /config/subfolder
Because I wanted to use my tiles files as a kind of cut and paste modules,( in fact like the original Tiles setup in regular Ha calling the group) I tried the with an !include to the same www folder /local/lovelace/tiles/tiles.yaml
doesn’t work at all, the files are not recognized.
I hence tried it in the /config/lovelace/tiles folder, et voila, there they are! My tiles back, and I can call them in all views simply like this:
title: Settings
path: settings
icon: mdi:tune
cards:
- !include /config/lovelace/modules/tiles_mode_selection.yaml
- type: custom:tracker-card
title:
trackers:
- sensor.custom_card_tracker
- sensor.power_wheel_tracker
- sensor.custom_component_tracker
or:
title: Light Panel
path: lights
icon: mdi:light-switch
cards:
- !include /config/lovelace/tiles/tiles_lights_panel.yaml
- !include /config/lovelace/tiles/tiles_lighting_activity.yaml
which is kind of cool.