Releases: custom-components/custom_updater
4.1.0
Changes
- 5ed06c5 sort imports
- 854c99a Update templates
- 4616f77 Fixes typo
- 315ac57 Async, pyupdate major update, a lot more debug logs
This release was created with reporeleaser 🎉
4.0.5
4.0.4
4.0.3
4.0.2
4.0.1
4.0.0
This component has been disabled from updating itself for a while due to this change, I will add this back at a later time
A good amount of changes for handling of custom cards.
The logic behind how this handle versions for installed cards have changed, by doing that it opened up some possibilities, instead of reading line for line in ui-lovelace.yaml it now uses a new jsonfile .storage/custom_updater.cards.
First a couple of good things
Storage mode for lovelace is now supported.
To enable this download this version then add mode: storage to your configuration.
example
custom_updater:
mode: storage
track:
- components
- cardsIf you use YAML mode with lovelace !include are now supported.
So over to the boring (still important stuff)
- The first time you use this version it will not know the local version of your cards, click the
UPDATE ALLbutton to correct this.
Resource url
?v=xxx tags in resource url is no longer need, this version of custom_updater will add another endpoint to your HA instance /customcards/, the goal of this is to not use /local/ which is designed for static files.
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.
old example:
resources:
- url: /local/tracker-card.js?v=0.3.0
type: jsnew example:
resources:
- url: /customcards/tracker-card.js
type: jsNote that both the start of the url, and the tag at the end has changed.
Final words
If you use this component to upgrade custom cards, this has a lot of changes, if you only use it for component and/or python_scripts this will not change anything.
If you encounter issues, or have questions about this component please open a issue here and not in the support channels (discord/forum) for Home Assistant.