Ok, I did not check the difference but manually updating the card fixed.
Unfortunately before that I reed this:
and updated my resources to the new style. To be sure I have the newest version I copied the custom update file from git to my custom components folder again.
I also added
From this version you NEED to change your resource url’s from /local/ to /customcards/ for all cards that you update with this component.
On your filesystem you will still place the cards under /www/ , this change is only for under resources in your lovelace config.
Have you hit “update all” since then? It suggests that you have to do it once after the update
Is your lovelace config stored using storage (edit via the configure ui option available in the top right corner of Home Assistant, or yaml (“lovelace: mode: yaml” (with appropriate indents and returns) in your config, and edit in ui-lovelace.yaml)? I suspect the storage mode option makes it look at the storage mode config, so if you aren’t using that, it won’t see the list of things to check.
I think you don’t want mode: storage for custom updater UNLESS you are using mode: storage (or unconfigured) for lovelace. Lovelace using storage mode stores in a different location than yaml mode, so I assume that config is telling custom-updater to look at the storage mode config for what it needs to keep and eye on, rather than the default yaml mode ui-lovelace.yaml.
I’d guess you just need to remove the mode: storage from custom updater and it’ll work
Storage mode is the alternative to yaml that is slightly less “just edit the files” than yaml mode (I assume as part of trying to make Home Assistant a little less indepth to manage for newer users). It was added a couple of updates ago.
No idea what ?track=true does, if anything, for the tracker card.
Lots of the lovelace plugins seem to be switching to using module rather than js for their type, haven’t actually looked indepth at what the differences are, but from our point of view as users it doesn’t make any difference. Still put them in www as before.
I believe lovelace actually has three modes, auto-generated, storage, and yaml.
Auto-generated builds something similar to the old, pre-lovelace, ui, and automatically adds things to it. Not actually looked at it since they added it.
Storage is edited through the webpage, the gif on the tracker-card github you linked shows adding the tracker card in it.
Yaml is what we originally had with lovelace when it first launched, edited through the config file, and what many of us are used to.
HA developers so fast, it’s hard to follow everything.
About the tracker_card question. The only file I need is the tracker_card.js file right. There was also a custom_updater file in the dowloaded folder from gut that confused me.
I also like editing my config in a yaml file the most.
Also I don’t care about if it is a module or js, but the thing I’m wondering about is custom updater in that regard.
I update my cards with custom_updater. The component showed me that everything was up to date.
However, it did not change the type of the tracker card from js to module.
So if it updates and is a module now, there is still the line in the yaml file that says js.
I have to say that I missed the new style (Auto update) for the resources (for version 4.0.0 of custom updater).
Maybe that is the reason why my auto-entities did not update right?
I’m also wondering why it still worked, when I had the wrong layout (local instead of custom_components).
The ?track=true does not do anything for existing cards (that you allready have installed)
But it’s a part of a concept I’m calling “super_custom_cards” (my imagination department are lacking) that can help with the installation of new cards https://github.com/custom-components/custom_updater/wiki/super_custom-cards
You need custom_updater component for the backend, and you can use tracker-card to display it in lovelace.
That was bad and I should never had done it, and even then it did not update the type.
Local still works* the issue with using that is that it will cache the cards, something /customcards/ do not do.
There are so may things posted to this forum I will not see them all, if you have any issues/questions about this component that you want me to look into please open an issue here https://github.com/custom-components/custom_updater
What is it for? Should this go to the same folder?
Should we keep the ending ?track=true ?
What do you by should have never done it? Autoupdate?
So am I fine with keeping the new style without local?
The advantage is that we don’t need the ending ?=vXXX right?
