I’m a little confused with the update to custom_updater and where I should put the .js. files within my file structure.
Currently they are in /local/ with, as I understand it, /local being /home/homeassistant/.homeassistant/www
Do I now need to move the .js. files to /local/customcards = /home/homeassistant/.homeassistant/www/customcards or is the local folder not required now, so .js files go into a /home/homeassistant/.homeassistant/customcards
Or am I totally wrong here!
Sorry for the basic question…
Thats not a basic question, it’s realy confusing!
The new custom_updater creates a new endpoint ‘customcards’ which is the same like ‘local’, but without caching.
I hope i’m right with this @ludeeus ?
Thank God I’m not the only one!
The documentation could be clearer I think!
For us dummies! 
So to clear it up,
I should leave my .js files in /local and change only the resources entry in ui-lovelace.yaml?
With /local being
/home/homeassistant/.homeassistant/www
In hassbian files should go in:
/home/homeassistant/.homeassistant/www
On hassio w/ samba:
/config/www
In ui-lovelace.yaml, the resource section, should be called out as:
/local/somefile.js
EDIT: I’ve always found this as odd too. Not sure why local wasn’t just used. Would remove the confusion maybe?
not according to the docs
I read that as it should be /customcards/somefile.js
My initial question is where exactly in the file structure do I put somefile.js:
stay in their original location at
/home/homeassistant/.homeassistant/www
or move to
/home/homeassistant/.homeassistant/www/customcards
or
/home/homeassistant/.homeassistant/customcards
The location on the file system stays the same, it’s just the reference in the config that changes from /local/ to /customcards/.
https://github.com/custom-components/custom_updater/wiki/How-it-works#the-customcards-endpoint
Like with the
/localendpoint the resources still need to be in thewwwdirectory (folder).
OK, thanks for confirming.
The docs are really quite confusing.
it also doesn’t actually mention how to update custom_updater component, I guess just by downloading the latest file from Github using wget?
The custom_updater should be able to update itself
interesting, how would I enable this / check this?
it should be active by default. just run the service custom_updater.update_all or click “UPDATE ALL” in tracker card if you use that.
Ive run this a few times but the component doesn’t update.
I don’t have components enabled in my config
custom_updater:
track:
- cards
card_urls:
- https://raw.githubusercontent.com/kalkih/mini-media-player/master/tracker.json
- https://raw.githubusercontent.com/kuuji/button-card/master/tracker.json
I guess this is why?
If I understand correct, I can now remove the car urls from the updater config?
You are not tracing components, remove that.
Can be removed, you still need the one for mini-media-player
Sorry, im lost again.?
I can remove the
track:
- cards
so my config should look as follows:
custom_updater:
track:
- cards
- components
card_urls:
- https://raw.githubusercontent.com/kalkih/mini-media-player/master/tracker.json
This will give me tracking for cards and components, right?
It will, but cards and components are default so both will be enabled if you remove the track part
Ah ok, I understand.
I’ve made the changes and the component doesn’t get updated, so I guess i can do it manually?
Scrap all that, custom_updater has updated!
Just made the update to v4.2.13, changed my resources in ui-lovelace.yaml and now my tracker card is empty!?
And I don’t see the components being tracked (custom_updater)
perhaps should add that I am getting an error in my log every time I refresh lovelace:
14:35 ERROR (MainThread) [frontend.js.latest.201902200] http://hassbian.local:8123/lovelace/5:0:0 Uncaught
Please open an issue here https://github.com/custom-components/custom_updater/issues/new?template=issue.md