Unable to manually reinstall archived HACS add-on `text-element`

Third party integrations
1

I’ve been using the HACS lovelace addon: https://github.com/custom-cards/text-element ; which I installed via HACS a while back. After I upgraded Home Assistant from an older version, I received a warning that text-element addon had been archived; and, asked me to either ignore or remove addon; even though the addon still worked perfectly.

I stupidly selected remove. Ever since then, I’ve been pulling my hair out trying to manually install this addon with no luck.

My ui-lovelace.yaml file already contained the below lines. I think at one point I had added it there:

resources:
  - url: /hacsfiles/text-element/text-element.js
    type: module

So, I changed it to:

resources:
  - url: /hacsfiles/text-element/text-element.js?v=2
    type: module

I even tried changing it to:

resources:
  - url: /hacsfiles/text-element/text-element.js?v=3
    type: js

I also verified that the respective .js files are still where they were before (untouched/unaltered):

\config\www\community\text-element\text-element.js
\config\www\community\text-element\text-element.js.gz

I deleted my browser’s file/cookie cache and completely restarted Home Assistant multiple times. However, Home Assistant still doesn’t recognize text-element in Lovelace like it used to.

What’s the trick to force Home Assistant to use text-element again? This is the first time I’ve had difficulty manually installing a community add-on.

Thanks so much in advance!

2

I just forked the repo and added my own repo as a custom repository. There’s already several forks so you can just use an existing one if you don’t want to have your own.

3

I forked the 4 repositories below. HACS is able to see them now. However, when I click on download for any one of them, it just has a spinning circle forever. It never downloads. I ended up manually downloading them.

Do you know how I can make the forked repositories below so they are downloadable? Do I need to modify my forked repositories with newer versions? If so, do you mind telling me how I can modify them to have a newer version? I’m not sure what file(s) to modify or how. I’d really appreciate it.

Thank you for your time and help!

1 Like
4

So my workflow was to delete the old downloads via hacs and restart HA. Fork the repository and then add it as a custom repository in hacs.

Then download via hacs and restart if required. I didn’t have any issues like you describe.

5

Thanks. I think I didn’t restart HA after deleting the old hacs downloads. BTW: Do you think there is a chance anyone would continue to maintain these hacs addons? I know there are a lot of people who still use them. It’s a shame, they are the best-looking lovelace components in Home Assistant.