HI,
only recently learned we don’t need the /config/ in front of the paths to the views, when using includes in ui-lovelace.yaml.
instead of
- !include /config/lovelace/views/view_Home.yaml
this is fine, since the config is in /config/, no need to point to itself…
- !include lovelace/views/view_Home.yaml
trying to keep things as short as possible, would it be possible to leave the lovelace/views out of the config below, using a base link or something? Or have it point to the main folder structure for views at lovelace/views?
this is what I have now:
views:
- !include lovelace/views/view_Home.yaml
- !include lovelace/views/view_Lights.yaml
- !include lovelace/views/view_Ikea_tradfri.yaml
- !include lovelace/views/view_Philips_hue.yaml
- !include lovelace/views/view_Floorplan.yaml
- !include lovelace/views/view_Settings.yaml
- !include lovelace/views/view_Home_climate.yaml
- !include lovelace/views/view_Home_summary.yaml
- !include lovelace/views/view_Summary_groups.yaml
- !include lovelace/views/view_Home_assistant.yaml
- !include lovelace/views/view_Home_energy.yaml
- !include lovelace/views/view_Home_solar_energy.yaml
- !include lovelace/views/view_Phones_tablets.yaml
- !include lovelace/views/view_Travel.yaml
- !include lovelace/views/view_Weer_klimaat.yaml
- !include lovelace/views/view_Tijd_agenda.yaml
- !include lovelace/views/view_Computer_netwerk.yaml
- !include lovelace/views/view_Audio_video_gaming.yaml
- !include lovelace/views/view_Media_players.yaml
- !include lovelace/views/view_Health.yaml
- !include lovelace/views/view_Home_automation.yaml
- !include lovelace/views/view_Weblinks.yaml
- !include lovelace/views/view_Leftovers.yaml
- !include lovelace/views/view_Developer.yaml
- !include lovelace/views/view_Test.yaml
something like
set path = lovelace/views
- !include view_Home.yaml
- !include view_Lights.yaml
- !include view_Ikea_tradfri.yaml
- !include view_Philips_hue.yaml
- !include view_Floorplan.yaml
- etc