HACS still claims component is archived and deleted despite recent release/update #30
Comments
|
Hi, this integration as well as other similar ones used to be on HACS a long time ago. Back then, it was a lot easier to add custom integrations to HACS. I've already added almost all the changes necessary for them to be compliant with the latest HACS requirements. I'm still waiting for the below PR's (Home Assistant Brands repo) to be approved/merged to pass HACS workflow-based validation. After that happens, there is one last step.. to add these integrations's URLs to the official HACS repo for them to be searchable. home-assistant/brands#5180 Hang in there. I will do this as soon as it's possible. |
|
No worries. Thanks and thanks again for all your efforts, it's truly appreciated. I was just trying to understand why it was that even after I MANUALLY added your repo to HACS that it still complained. My understanding is much like repo management in other platforms MANUAL adds would bypass any kind of "official" HACS certification/qualification management hurdles. Perhaps that's NOT how things work in HACS, or something that was lingering from the initial version wasn't deleted when I removed and then later re-added the integration. Regardless thanks having gotten back to me and keeping these integrations alive. |
|
Hi, |
|
Hi @douginoz , I'm also excited about bringing back the original integrations for Upcoming Media Card and also Upcoming Media card itself. They aren't yet available in the current Home Assistant version. If you want to start using them now, you will need access to your Below, is an example of how you would do it. You should backup the existing files before deleting anything; just in case something goes wrong. You can always put the files/folder back exactly how it was and reboot to return it back to how it was. Instructions for the official latest version of
|
|
That's awesome! I guess I was lucky to stumble across that whole system only a couple of days ago. It all seems to work well apart from songs missing new features so it's been a good experience so far. I'll try following your steps to get this integrated. Let me know if there are other similar steps available for the other modules or the main ones (to enable deep links for instance!). Thanks for your ongoing commitment to this project. |
That doesn't appear to work. I think what you meant to say is to copy the subdirectory "sonarr_upcoming_media" that's in the "sensor.sonarr_upcoming_media-master folder into the custom_components folder. That's where the older sonarr_upcoming_media folder was. Otherwise the 'sensor.sonar_upcoming_media' entity is gone. Also, after doing that, my card works correctly: but it's still not clickable. Tried on FF and Chrome. That's probably related to the upcoming-media-card but as far as I can tell I'm running the latest version. I followed the instructions on that readme, including adding the following to I'm not sure that the version info in that string is right. The readme instructions go on to say that: If you're not updating using tracker-card and/or custom-updater be sure that you are adding to a version number at the end of your lovelace resources when you update your cards, But both tracker-card and custom-updater are over 5 years old and no longer in use. So perhaps the readme instructions are out of date and I'm installing things incorrectly. I tried updating the ui-lovelace.yaml to ?v=0.4.4 but it didn't make any difference. |
|
Sorry, my manual installation instructions weren't intended to be followed verbatim. It was just a general guide. I would make sure that your sonarr_upcoming_media integration (or whatever integration you're using) is providing deep_link for example: Yeah the readme instructions are quite old. I need to update it. It's not required to append a version number when manually adding the latest BTW: I just updated Upcoming Media Card with a new tooltip feature today. I also updated the documentation for how to enable tooltips. Dont forget to download Upcoming Media Card again to get this new feature (along with some bugfixes). Just copy the file(s), reboot; then, finally delete your web browser's cache. After doing this, does tooltips work for you? |
|
Home Assistant OS 12.1 Desktop: kubuntu (latest) 6.5.0-21-generic Actions taken:
HACS continues to give me the warning that I'm ignoring: I ignore it to ensure that I don't tell it to delete those files.
Which looks like this: But the cursor doesn't change nor is anything clickable.
Are there additional files I need to install besides the one .js one and to edit the ui-lovelace.yaml file? I'm also trying to move the upcoming-media-card.js somewhere else because the path in your README doesn't seem to exist. It might be correct but as you probably know, when using the Terminal program to access files, they appear to be in a different root location because it's really just a docker shell you're accessing. I noticed that my existing ui-lovelace.yaml has the following. Note the different paths of the 2 entries:
I tracked down the first one - button-card.js - it's located in www/community/button-card, which is also where a bunch of other cards are - vertical-stack-in-card, lovelace-card-mod, mini-media-player etc. So I've now moved upcoming-media-card to that same location and changed ui-lovelace.yaml to be:
I'll update this when I've finished trying that. While doing this, I tried removing everything, rebooting, and re-adding everything, trying to follow the instructions. One of the instructions for adding sensor.sonarr_upcoming_media is: This is confusing me. Am I really supposed to be adding those lines to ui-lovelace.yaml, which currently contains completely different looking values? Is there more than one ui-lovelace.yaml? |
|
I'm starting to think that I need to wait until you update everything including the instructions. I think they're too old to follow and I'm not expert enough to work out what I should really be doing to get this working with the 2024 versions of HA. I'll be more comfortable adding things the supported way via HACS etc rather than this manual way, which introduces so many questions and opportunities to get it wrong. You're likely running HA in a different way (supervised, container, core) and probably on Windows, so your instructions don't work "out of the box" when trying to install on a different version. |
|
Have you checked to see if the rest of the new features I added to Upcoming Media Card work or not? There are 5 more features. If none of them work, that's your problem. It would mean you're using an old version of Upcoming Media Card. If all the new features work, except for deep_links; then, I will try to reproduce it in order provide a fix. Let me know.. |
|
I tried enabling transparency but didn't see any difference at the time. I wasn't sure if that was because my background is black and there's nothing to bleed through, or because it wasn't working. As I wrote previously, I've completely removed the upcoming media card files as well as the sonarr/plex/radarr sensor files and folders, and rebooted. I've now added them back in by doing exactly this:
Then to install the upcoming-media-card I followed the instructions in it's readme here. However, some of the instructions are very old and probably don't work now. But it's all I have so I have no choice but to do what they instruct:
I read this explanation of where this file is located and I think I have the right location; but it appears that this file isn't used much any more because it's all done via the UI. That may be why mine is essentially empty. I don't know where that's supposed to go; my ui-lovelace.yaml file only has the lines in it I pasted above. There's nowhere for these new lines to go. At that point I'm stuck. After rebooting, trying to create the card again results in the error "Custom element doesn't exist: upcoming-media-card". I thought perhaps I should try installing this card via HACS, even though there's no mention in the instructions. I believe I did that last time, but might have screwed it up somehow. This time, I added the repository but using the category 'Lovelace' rather than as an 'Integration'.During installation it said: And now it works! |
Glad you got it working! There is one important bugfix I need to upload in the next day or so; along with providing a respective new version on the official UMC repo. It will be the version that people will use when it's on HACS. Ill let you know once its ready. Sorry for all the hassle. |
|
Thanks again. So as someone who dosen’t actively use to many HACS components… given I was using the OLD components and never removed them will your update when it goes live show us as a potential update (and thus clear the msg about the repo is deleted) allowing me to update via normal approach or will I have to do something else when you slot back into HACS? I know I am a VERY corner case….. 😆 |
|
@taw123 Please don't kill me. I just realized that all this time I forgot to change the version of this integration in the manifest file; which is definitely needed for HACS to detect you have a new version update. I had done this for all the other integrations except for this. I'm not sure how it would affect your case though since its still not available on HACS yet. Anyway, give it a shot. maybe that's what was needed to nudge it into working for you. |
|
Apologies for highjacking the thread, if my issues is not related I will delete and create a new one, I'm struggling with installing this at the minute, I had no issues with the plex upcoming media integration, my issue feels related to this thread, sorry if it isn't. When I follow the instructions and add the yaml to the configurations file and restart I get the following error: I decided to see if installing Sonarr and using sensor.sonarr_upcoming from it would work, but If I add a media card with the following config I get this error. Any ideas? |
Hi @rosarch it doesn't sound like you're doing it right. It's a lot easier for me to just show you below. It only takes a few seconds.
|
|
Thanks @mkanet, I have worked out my issue, it was a clash in the configuration.yaml with the Plex integration. I temporarily removed the plex configuration and it works fine now. I just need to update it to incorporate both of them. |
|
Maybe I'm missing something, but HACS is still complaining that the repo(s) are archived.
|
I can confirm this happens to me too. There is a list of archived repos that HACS keeps track of which unfortunately doesn't change until these repos are officially added to HACS. I am still anxiously waiting for my PRs to be approved by HACS repo moderators. Just to be safe, I think I'll open an issue on the HACS repo to double-check that the above will happen automatically. If there is another quicker way to do it, I'll find out. |
|
I am reopening this issue for others to see. |
The "solution/workaround" for me (and my sanity) with a number of these has been to MANUALLY add the custom Repo(s) to HACS AFTER removing any/ALL installed (forked/offically recognized) versions of these related integrations/lovelace components. If I did NOT remove them it "seemed" like I CONTINUED to get the other- much OLDER, forked versions, of these components. These were/are very old versions that were forked by others during the time that these components were listed as "archived" and others in some cases steeped up to fork/support them. For example.... Take the case of Plex Recently Added:This was forked and "supported" per HACS by NemisisRE. At some point over the years I actually moved over to it as it looked like this was the path to continued updates to the component given the maykar archive announcement. In other cases where there was no one who took over, I just kept the original integration/cards (which actually was the genesis of this original bug/issue) While moving to this new repo resolved the ... "Repo is archived" log msgs, and for a period I think might have actually provided several updates, it is far behind what has been done here at what I consider to be true Head of tree (even if HACS might not). This led to HACS shooting BOTH repos as the "source" with 2 very different code bases. The integration info page HACS brings up for SOME of these components clearly lists BOTH Repos in the header (see below) with not clear indication WHICH one is ACTUALLY installed. You could however look at the info data and date of last update too tell it REALLY was the old version (with last update of last year) 
Now that folks have been kind enough to pick these back up, we have the potential to return to the canonical source repos for these components. But due to the either the craziness of HACS (or MUCH more likely may poor understanding of it's use and internals), combined with the fact that Maykar's PRs haven't yet been accepted leads to a case were his "updates" are not yet seen as upgrades for the forks. Thus the need to "force"(?) to use his Repo is the source for your HACS installation. If not I kept getting the option ONLY to install the OLD version from last year. So I went to and added the listed repo(s) to the HACS custom repos per below:
This then results in several less than ideal outcomes (that I will list) BUT does seem to ensure that you have installed the DESIRED/most current/supported version of the component(s) from the original author. It ALSO SHOULD mean that as they are updated you will get those updates/version control.... VERY IMPORTANT
Hopefully in time all of this will work it's self out as all four of these become the canonical reference in HACS which should potentially solve both the duplicate listings AND the warning about archived components which were caused by the forked components using the same identifiers as the original now UNARCHIVED components. Thanks again to ALL who helped... The original and not active authors, AS WELL AS those who forked and tried to help fill a gap. And as was said above HOPEFULLY this helps someone who actually read all of this. If you are just scanning and jumped to the end (no judgement).
|
|
Thanks @taw123 that's pretty much what I've been doing. I just received confirmation from a HACS moderator that this will clear automatically once these repos are officially added to HACS. hacs/integration#3625 "It will be automatic" |
|
Not sure if I should qualify this as a "bug" but... HomeAssistant today informed me that: Seems YAML config has been deprecated in the move to config flow? So I commented out my the config in my config.yaml, rebooted and proceeded to add through UI as it seems that the EXISTING config wasn't migrated to to the new config_UI. Took me a couple guesses to get it right as of course I/we are ahead of any documentation of the ui (via HACS or the local repo) so I'll offer the follow as a hint for anyone else attempting to use... If you want to keep your existing dashboards and ui configs simple add it back with NO hostname and the entity will again have the name sensor.sonarr_upcoming_media except it will now be "upgraded"/recreated(?) as a full-fledged HA citizen with unique ID. In the case of this sensor, it wasn't critical for ME that data continuity be preserved in logging/recorder, so I didn't fully check to see if the entity ATTRIBUTES remained continuous across the platform/config_UI change but the entity has and that's ok for me. I looks like the other media_card feeding integrations I mentioned above still use the classic platform/config.yaml. Is this also expected to change for your Radarr integration? Looking good! |
|
@mkanet Applogies for the interruption. Does the FULL version release of Radarr_UpcomingMedia mean now that one can remove ALL versions off that integration through HACS (and the corresponding workaround of the custom repo), reboot, then ADD it back again through HACS and not have to deal with the archived message in the logs? It would SEEM to me that since the version NOW exceeds the previous version strings that this should resolve the issue of getting the wrong integration assuming it's now "fully blessed" by HACS (or whatever they call their certification process). I'm posting it here as if this IS correct then I would expect the same process should be followed for those who have posted here when you have an opportunity to update Sonarr_upcoming |
|
Hi @taw123 unfortunately HACS still hasn't officially added these repos yet. Until that happens, you will have to continue using the same method you have been using to install/upgrade. The only reason you even see Radarr Upcoming Media in HACS (with new updates) is because you manually added the respective repo URL to your HACS configuration. You will know when these repos are officially added to HACS when messages like below go away after a future Home Assistant upgrade. At least, that's what the HACS developers suggested. |
|
NP... and thanks for getting back to me. I have set ignored slo fortunately I don't have to deal with them in the main UI, but of course they are still present in the log as I deal with other issues ;) |
|
Yeah, its pretty annoying for me to see that message too. Hopefully, the HACS moderators will get to approving these repos soon. Its already been about a couple of months. |
Hi, Just wanted to chip in to be sure you guy's know this. The problem right now is the radarr et sonarr_upcoming_media repos are still in the "blacklist" as listed here: https://github.com/hacs/default/blob/master/blacklist#L100 It has been done two years ago with this PR for plex, radarr and sonarr: hacs/default@cb2dfeb I wasn't able to understand why plex_upcoming_media was still working while being in the blacklist: https://github.com/hacs/default/blob/master/blacklist#L96 Untill I figured @NemesisRE added his fork in 2022.. hacs/default#1382 So I don't know, maybe it would be simplier to first be removed from the blacklist in another PR and at the very least people adding the repo manually will not face the archived repo error while we wait for HACS to accept your latest PR ? |
|
Guys, Im going to close this issue since there isn't anything that can be done until HACS moderators approve these integrations (and UMC) to be back on HACS again. As stated earlier, these repos will automatically be removed from the "archived repos list" that they maintain: |
Describe the Bug
Looooooong time ago installed and set up Sonarr Upcoming sensor to feed upcoming media card. A while back HACS claimed integration was deleted/archived (std msg). Of course sensor continued to work and I lived with the warning in the UI, while occasionally looking/hoping for an update.
Fast forward to this week when I found while getting ready for 2024.2 that you had updated this... I thought I would finally be rid of the msgs after manually downloading and updating the component.
The Error
Unfortunately HA still complains about the integration being deleted/archived. I tried deleting the integration from my HACS install and then RE-ADDING the repo manually (by url). Same result...
Don't believe the issue is mine though an engineer for many years don't have much of an understanding of HA internals or HACS internals so perhaps there is something more at play here besides what I am hoping is just a matter of getting qualified in the HAC Store?
Though if I DID understand how HACS works that SHOULDN'T be an issue if I MANUALLY added your GitHub repo into HACS, right? Private (non "store" "certified/qualified") repos CAN be added via HACS to HA for version control right? And in that case there shouldn't be any messages deprivation/archive marking (again if my shaky understanding is indeed correct)
Thanks for any insights you might have on this and your plans for your equally useful RADARR sensor (didn't want to your time opening an exact duplicate of this issue on that component as well, since I suspect one answer will cover both)
Version: HA Core 2024.2.0 -- Docker
The text was updated successfully, but these errors were encountered: