The instructions say custom_components you have custom_component
1 Like
Yep, just figured that out and was about to say nevermind haha. Thanks!
Ok so, I’m not sure what happened must of updated or something, but I woke up to find that HACS had somehow reset itself, now the Setup is showing as fresh install. I went ahead with the setup wizard, and nothing appears.
How do I restore the integrations, plugins and settings again?
From a backup of .storage
Hi,
Since a few days ago I’m getting this error in the log file
http://<my ip>:8123/lovelace/default_view:0:0 Uncaught TypeError: Failed to resolve module specifier "card-tools/src/templates.js". Relative references must start with either "/", "./", or "../".
I reinstalled HACS but it did not help
Reinstall card-mod with HACS 0.21.3+ and clear the cache on ALL clients
I’ve have upgraded to ver 16.3 as requested (downloading the code and replacing in the corrected
folder).Now I’m trying to upgrade to latest ver. through the GUI , and I get ‘500 internal server error (
server got itself in trouble)’
HA hasbien ver 0.105.4 runs on RPI3B.
Please your advice.
I suggest you follow that above.
I have been told by many that HACS is not officially supported and maybe causing my issue on upgrading from .104.3 to .105x. Is there anyway to test / verify which HACS have been tested to what version?
Believe me HACS works on 0.105 and does not prevent upgrade.
Maybe I stated the question wrong. Not HACS itself, but many of the custom integrations / plugins.
Well they may do, but you’d need to ask in relation to the component you suspect.
I am getting no errors in either the core or su logs so it is hard to tell what the issue might be.
Yeah, I think you’re confused about what HACS is and what it does.
HACS is just simply a “store-front” to provide an easy and convenient way to allow users to install and update custom components that are made for HA by third parties.
It has nothing to do with the functioning (or not) of the third party components.
If you may be having trouble with a custom component and there are no logs pointing you to the culprit then you might have to try uninstalling all of the custom components (which HACS allows you to easily do as well) and add them back one at a time to see if you can find the one that is causing the issue.
HACS does seem to have issues with downloading the latest versions of some cards. I am in the habit at the moment of checking if a card has changed after I update it - easy cos I use github desktop to backup my configuration and I know immediately if it has changed. I also have used Winmerge to check the card is different.
I think @ludeeus is still trying to nail what is going on here with HACS. In any case I’m on 0.106.0b2 now and HACS works fine…
I think all cases of downloading wrong versions should be fixed, there is no open issues for it.
1 Like
Seems fixed to me. It used to be that some plugins/integrations would not update because the dropdown version list stayed on the current version instead of the latest. The latest version could be selected manually and the update would occur. I haven’t seen this happen for weeks.
I wasn’t confused with what HACS does or doesn’t due. I just stated what shows up in the logs that HACS and the different custom cards are not tested an they may cause issues. I now believe that my configure.yaml file is not an issue as the identical one works in a new sd that is running .105.5. I had the Lovelace UI also working, but it stopped working after a reboot. I now am suspecting one of my custom cards. The two I think it maybe is custom home feed or calendar card. To restate my question. Is there somewhere that can give a user information show on any custom item, what version it has been tested to?
You’re mixing some things here. 
HACS is the tool, to manage and administrate the installation and update for a custom_component. No more, no less.
That being said, HACS doesn’t know, if a developer tested or otherwise tried different versions to install to. That’s why you should always look at the changelogs in the repository of the custom_component. These are totally different things and HACS can’t check (as it is not the purpose of HACS).
The warning (not error) you get in your log, is from HA itself, and you will get it on every custom_component you have installed. No matter how or from where you installed it.
What brings me to the last point: HACS is “only” a tool to do the installation and upgrade work for you, if you have errors or difficulties with on or more custom_components you have to go back and check the component. Check the logger component, it will bring some light into your problems.
1 Like
Reply #1000
I have never been a fan of long threads they do not help anyone, no one will read through the entire thing before posting.
Most earlier posts will fast be outdated.
Now that this thread is closing in on 1000 replies, I believe that this marks a good place to lock this thread.
Still need help?
Here are some options for further actions.
Issues
Since the beginning of this thread, I have been clear that issues should be posted on GitHub, that will continue.
The same goes for feature requests.
Questions
If you have questions about HACS, please join the Discord server.
Other
Feel free to start a new thread for the specific thing you need help with.
Links
6 Likes