I'm running the newest version of HACS This seems like an easy way to keep people from losing functionality. In the future, I wonder if HACS could be updated to move orphaned repos (those that return 404) to the already-existing blacklist. I don’t have the patience to go through and format this markdown to text. (A restart wasn’t necessary for me here).Check to see if “Custom Repositories” is available.Restart HACS and check to see if the “Custom Repositories” option is enabled.rm where is the name of the file from the previous step.A file should be listed with a numeric name.Remove references to the component in the hacs directory.Delete the entry in the json file for the repo (I use dd and keep pressing dd until the section was gone, but there’s probably a vimmier way).Type / and then the name of the repo to find it in the json file.vim hacs.repositories to edit HACS’ list of repos.Remove references to the component in hacs.repositories.If present, delete it with rm -rf wakatime.Remove the custom_component if it exists.Open Terminal (using the Terminal & SSH add-on).Make sure “Terminal & SSH” add-on is enabled (this is the low-key one that doesn’t need to extra permissions).Get the name or part of name of the repo you’re trying to remove (in my case, wakatime).Steps to remove a custom repo from HACS manually This isn’t official at all, use at your own risk, editing files directly isn’t advised, etc. I googled around and found very little info on how to manually remove a repo from HACS, so posting some steps here in case its useful to others. Since this orphaned repo was graying out the “Custom Repos” option (or so i suspected), this ffectively meant that HACS was stuck in time – I was unable to add new repos, cutting me off from a lot of desired functionality in HA. Attempting to remove the Wakatime Repo from HACS had no effect - it was still listed even after choosing the option to remove it, and restarting after attempting to remove it had no effect. I suspected that this was the reason that the “Custom Repositories” option was grayed out. I noticed that one of my custom repos, Wakatime (an addon used to track time spent using code editors) was removed from Github, and the repository is returning a 404 now. There are a couple of issues on Github against the HACS repo that talk about this problem, but they’re all either very old or locked. In HACS, there’s a “Custom Repositories” option which allows you to add repositories from Github and install them automagically. I recently wanted to add a new repo to Home Assistant using HACS (specifically, ha-sun2, so I could take a stab at automating my roller shades to open without blinding me in the morning while I’m still in bed).
0 kommentar(er)
