Closed myztillx closed 5 years ago
Hi,
This is not designed to work this way, it only can track resources you have in the ui-lovelace.yaml
file.
I'll add a FR label to this, but not sure how/if/when I can add that
No problem. Thanks for the update! I can adjust my ui-lovelace.yaml to conform.
I have changed into a related setup using the original resources section of the ui-lovelace.yaml in a dedicated file resources.yaml in /config/lovelace/resources, and reference that in my ui-lovelace.yaml as follows:
title: Main Lovelace
resources: !include /config/lovelace/resources/resources.yaml
views:
- !include /config/lovelace/views/view_Home.yaml
- !include /config/lovelace/views/view_Lights.yaml
etcetc
all my cards are loaded fine and no change there, only the tracker card doesn't see these resources any longer.
Please have the tracker card follow the resources referenced in ui-lovelaced.yaml.
thanks!
Adding another vote for this feature as I have my cards set up in the same way and they don't show up in the tracker/component.
Will come later today
This is now a thing :)
https://github.com/custom-components/custom_updater/releases/tag/4.0.0 Please read the entire release note before upgrading :)
Version of the custom_component 3.1.8
Describe the bug Custom Cards not appearing.
Have the following in configuration.yaml
I do have a less common configuration setup. Where every entry is a separate file.
I do not have my resources directly in my ui-lovelace.yaml, instead I reference them like below: And then the references in the lovelace/resources file reference back to local/lovelace/cards/x. Example below:
log