Cannot remove theme from HACS (that HA tells me I should remove)

Back story - the HDD in my HA server failed. After replacing and restoring from backup (a few days later), HA notified me I had to remove a theme repository from HACS as it was not there anymore.

Naturally it was the main theme for my dashboard! I downloaded another theme and replaced it in the dashboard and then tried to remove the repository from HACS.

The removal did not work.

  • I have downloaded and removed other themes without issue.
  • I have double checked there are no remaining references to reeder theme in any lovelace config.
  • I have restarted HA (several times)
  • I have manually removed the theme folder from HA, and it persists in HACS gui.

The repository in question for theme Reeder_dark does not exist anymore (gives 404 error in Github).

I am guessing HACS might need something there to complete the removal?

Now I am playing Yossarian between ‘remove the repository’ and ‘cannot remove the repository’.

Cannot find any other reference in forums.
This situation does not really fit a bug report as per the template for HACS, hence asking here. I cannot request removal of the repository because it has already gone.

Is anyone else experiencing this or maybe has seen it before somewhere?

Other parts of HACS are working fine.

(incidental - restoring the backup worked a dream - no significant integration issues)
Maybe I have missed something (apologies if so) -
Thx in advance

PS in case it helps:

I have the same issue and cannot remove it. I deleted the files separately but that did not help the log error.

I have requested removal of the repository but the report was closed because it does not exist (or has already been removed)

Guessing the HACS devs are suggesting maybe this is a HA core issue in reporting the error, and HA is suggesting it is HACS … (as this forum post was moved to 3rd party topic heading) …

Maybe a core update might fix it - but unlike occasional front end updates, that is relatively non trivial - and I need to wait for v12.3 to minimise v12 issues