I have followed the instructions to the “T” but HA comes up with error when I check the configuration:
In my configuration file is this:
#custom_updater:
hacs:
token: !secret my_github_access_token
What could I be missing?
I have followed the instructions to the “T” but HA comes up with error when I check the configuration:
In my configuration file is this:
#custom_updater:
hacs:
token: !secret my_github_access_token
What could I be missing?
Did you put the hacs folder (extracted from the zip file) and it’s contents into your config/custom_components folder?
Just installed HACS and looking forward to giving it a go. I previously user custom_updater
, which I’ve removed, and also manually added cards/components via the RAW config editor. Do I need to remove all resources entries for previous card/components from RAW config editor?
@Dayve67 If you have installation issues, please open an issue @ GitHub.
With that said, that check is not the most reliable, I would just try to restart anyway
Nope, this does not change how Lovelace works, but if you used the /customcards
enpoint with custom_updater
you need to change those, since they will not work anymore.
I haven’t read the thread, but I’m sure the question has and/or will be posted, so…
I am currently in the process of overhauling and refreshing all my plugins. One step in this process is to add them to the hacs default repo. One at a time. Have patience.
love it, thanks for your efforts thus far, works as stated
Just switched over from custom updater last night, this is great. Thank you for your hard work.
To do what?
Never mind, I think I am confusing addons with custom components.
I haven’t read the thread, but I’m sure the question has and/or will be posted, so…
Is there a plan to replace the tracker card with a new card that works with HACS to allow for some of the display functionality? I get that code update functions make more sense in the store however I really enjoyed the concise visual aspect of how the tracker card displayed component code version information in an easily accessible way. That being said, Moving to HACS was relatively effortless. Its a great addition to the Home Assistant community!!
about the tracker card.
Thanks for the share… too bad…
As stated both in the OP here and in the documentation, please use GitHub for issues
love the new hacs.
the https://github.com/iammexx/home-assistant-config/tree/master/ui/darksky
Going to be in the installation of hacs?
Not unless it´s split into a seperate repository.
Too bad.
Thanks; done. Was hoping someone here had seen the same issue…
The documentation site at https://custom-components.github.io/hacs/ have been restructured.
This will (hopefully) be easier to navigate and give more / clearer information both for users and developers.