- title: System info
#system info om alt på hass.io
cards:
- type: custom:tracker-card
title:
trackers:
- sensor.custom_card_tracker
- sensor.custom_component_tracker
Anyone see anything I do wrong? I can see sensor.custom_card_tracker, sensor…custom_component_tracker and sensor.custom_python_script_tracker in dev states.
Hello,
My sensor.custom_component_tracker and sensor.custom_python_script_tracker doesn’t work
The sensor.custom_card_tracker works fine and show all my cards.
How can I see my components and phyton scripts ?
Thanks !
Bart
I have a partial working tracker card and are puzzled.
Few facts:
I have tracker_card and custom_updater component installed. Running last version (4) of custom_updater
My configuration.yaml looks as below
Running lovelace in storage all custom cards work fine
Issue:
For some reason the tracker/custom_updater does not see that I have custom cards installed (however does see this for customer components). I’m out of ideas…
well that’s not too easy…
I did, and it made my setup behave rather unexpectedly slow, so loaded the previous version again…
I am a bit puzzled how to define the custom cards. Using Yaml mode with includes, I point my Lovelace setup in ui-lovelace.yaml via resources: !include /config/lovelace/resources/resources.yaml to my resources, which looks like this:
the new setup of the custom_updater says to change the path to the resources, but I cant understand how I need to change my ui-lovelace configuration for the card to work… It should simply follow my configuration shouldn’t it?
this is the bit I don’t get:
old example:
resources:
url: /local/tracker-card.js?v=0.3.0
type: js
new example:
resources:
url: /customcards/tracker-card.js
type: js
If I misunderstand the rather minimal setup instructions, please let me know how, and what I need to do to make it work again? thanks.
yes, I Understand so far… And did change it. But how will the ui-lovelace.yaml find the resources, when the path has changed to an non-existant one…? changing it to /customcards/ will make the config error out won’t it? Or is this in another file, and not the resource path in the ui-lovelace.yaml?
I will, but also want to understand…
If I change the path from /local/ to /customcards/ without having a folder /customcards in my configuration, how can this ever lead to a valid configuration. Unless the new card creates a copy somehow and redirects ui-lovelace? Must be missing some basic information here, but Ive really looked
for example, my current path is
/local/lovelace/resources/card-tools.js?v=6ce5d0
would this become
/customcards/lovelace/resources/card-tools.js or
/customcards/card-tools.js
The first one… you just replace the /local/ with /customcards/ I assume it creates some kind of symlink to the /www folder… Remember it’s called /www/ NOT /local/ as well yet that works perfectly well. Same deal imo.
hmm, gave it another try, and indeed it found the cards and after yet again 560+ seconds my Lovelace interface started to build. But, many issues.
This new card, in my settings (Yaml mode, !includes and resources includes ) doesnt work as it should, taking an enormous toll on the system. causing spontaneous reboot and never getting initialized completely.
returned to the older card once more, et voila, restart in relative quick 2 minutes or so, all cards recognized, and no response lag at all.
Ill back out on this one for now, and will wat to see if it gets better.
OK, I’ve updated to the newer 4.0.1 and seems to work…it updated
all the cards from “na” to their latest versions
The only issue/question is for the components,
it use to show this custom_updater itself as a component to track…but I don’t see it show up in the list anymore. Is it suppose to?