I’ve been running HACS for a few months now with no problem. Today I noticed the communinty button on the left hand side is gone. I rebooted HA and it still doesn’t come up. I checked the log and HACS appears to start with no reason. Anyone know what I can do to get back in HACS?
Have you tried to re-install HACS?
Like remove it from configuration.yaml, reboot and then re-add the files and the code in configuration.yaml?
I had held off as I saw it was working in the logs but am about to do the above.
Has this happened to you?
I removed it, re added it all and it is still missing. Bummer
Yeah, it was a couple of versions back that it was missing from the side menu because of a change in the component. A reinstall of the files fixed it.
You might need to file an issue at the HACS github.
@finity - Do you know if this issue is resolved? He claimed that he attempted to do a reinstall is HACS and was still not able to revive it.
I ask because I just noticed HACS disappeared from my sidebar as well. Before I chase this rabbit around, I’d like to know if a fix was ever implemented.
Anyone know? Over 900 people reading this to indicate it’s a widespread problem.
Thanks!
No idea. I haven’t had an issue for a while now myself.
Remove hacs here, then reinstall
Yeah… That wasn’t working… I ended up trying a few other things people suggested like deleting files, folders and what not to get to the place where a reinstall could take place. HA started collapsing like a house of cards. I eventually rolled back to a snapshot from two days earlier where HACS was restored. But after going into HACS, all my components were missing - but they appear to be working in HA.
I have to tell you, as awesome as HA is, it is in serious need of some QC. Too often it goes sideways with little to no way to recover. As others have stated, it’s unacceptable. Spending hours upon hours reading through threads to figure out how to restore, recover, rebuild is not for the faint of heart.
This product is on the verge of prime time, but this gap between the newbie/novice and the developers is like the grand canyon. Only a few can get to the other side by other means. There is no simple and direct route of recovery. Documentation is dated, incomplete and leaves too much to the imagination. HA would do itself wonders to install a better QC community and standardization on communicating to the end users.
This is not a complaint… It’s a gripe and an observation. If the key people behind it could take a step back for a moment, take a deep breath and look at the accomplishment of their work, they would see a sea of people who are rooting for their success. They are incredibly appreciative of the software offered to them. But they are also violently frustrated. Yes, we understand it’s open source and all that… But it’s not to be an excuse for poor communication. Developers should NEVER be the ones writing the documentation. Example: Install the component. Ok, maybe that’s an extreme case… But it’s pretty close to the reality. Another pet peeve is when the item being described is referenced in the definition. That’s circular reasoning and useless to someone trying to gain an understanding. It’s simply poor and should be examined. Someone who knows how to write technical documentation should be the person maintaining the wiki’s and documentation for HA.
After I finished getting HACS up again, it’s back to the project that started this whole issue - the installation of the “Tracker-Card” which is incredibly weak in it’s docs. People who respond with “just follow the directions” are useless. Why respond? Don’t you think that someone already did that? Perhaps you can fill in the gaps and be a little more helpful to those who’ve already spent an entire day trying a millions things?
Ok, I’m done venting…
1 Like
I installed HA some weeks ago and installed HACS immediately, because of my devices’ brands. It worked well until the latest system update (0.116.2), when HACS disappeared for me. I agree with Giuseppe, though I think it goes beyond documentation. HA achieves every day its automation and wide compatibility (a lot of it thru HACS, by the way) goal, but it’s seriously lacking management / supervision to synchronize, plan and properly test updates, features and system wide transitions. The “if it breaks, install it again” approach is counterproductive for developers AND users, and VERY (I really mean VERY) problematic for the crescent non-technical portion of the users.
Another thing: why is HACS even separate from the core structure? The way I see it, it’s the very soul of HA and the main representation of its objectives. Much more than Lovelace, that comes preinstalled. Why must we hack the system to get it anyway? #unhackHACS 
Lovelace is the core frontend how would we interact with it, thats why its preinstalled, HACS is a custom integration for installing custom integrations. I think the reason its not in the core there would be an expectation that anything it installs is supported by HA which custom integrations are not hence the warning in the logs.
HACS and all the integrations/cards it installs are custom integration/cards. The documentation for them is not the responsibility of HA but their respective developers