I spent a lot of time doing exactly this when I first moved to HACS. I am running over 20+ integrations and plugins, many of which did not natively support HACS at the time. When I lost everything less than 24 hours later, I simply didn’t have the heart to do it all over again. Hence my request.
I honestly don’t want to beat a dead horse. My HACS migration experience didn’t go smoothly and I’m merely sharing my experience with the author with no expectations whatsoever.
I don’t know what went wrong for you and I agree it’s a pain having to get HACS to D/L everything again but I’ve migrated several systems from custom_updater to HACS and it works fine once it’s all setup.
Are you saying that not only did HACS itself get corrupted but that it also removed all of your integration/plugin files that it had downloaded and removed your configuration code from configuration.yaml for all of those things as well?
No. The HACS downloaded files and config.yaml code was still there. But the HACS app was completely reset. So despite the existence of the downloaded files and config.yaml settings, all of my integrations and plugins had to be re-added via the HACS UI if I wanted to continue updating said integrations and plugins going forward.
Getting things back into the HACS system is literally just clicking “install” on the stuff you already had installed. Then at the end restarting HA once.
This sounds like a great way of keeping track, but I am not exactly sure what you do. Could please elaborate a bit? What package are you creating for your CC’s?
Thanks
in my packages directory I create a file called “custom_components_package.yaml”. In that file I have all of the configuration code required for any of the custom components.
a ok, thanks. I’ve organized my complete HA config like that (have the packages per functionality/use and also the CC settings in there)
Thought you might have had a special CC library for the Lovelace resources in HACS.
Yesterday the beta didn’t show up in the menu, even though ‘show beta’ was selected.
Solved it with ‘settings’ -> ‘upgrade all’, beta was installed.
Today 0.14.0b1 shows up, but after upgrade and restart (multiple times) i’m still on 0b0.
Anyone else?
If you are using my Lovelace Home Feed Card, a great way of including details updates from HACS in your feed is to have a config something like this:
type: 'custom:home-feed-card'
title: Home Feed
id_filter: ^home_feed_.*
entities:
- entity: sensor.hacs
icon: 'mdi:update'
multiple_items: true
list_attribute: repositories
content_template: 'Update available for {{display_name}} to {{available version}}'
Note: I’m using the HACS beta, which added display_name as an attribute to the repositories list for sensor.hacs, if you aren’t on the beta simply replace display_name with name