"hacstag" not always correct? #4501
Comments
|
Make sure you have read the issue guidelines and that you filled out the entire template. If you have an issue identical to this, do not add comments like "same here", "i have this too", instead add a 👍 reaction to the issue description. Thanks! 👍 |
|
maybe adding the .js file to the release assets can solve the problem? |
|
What do you mean by that? The .js file is in the archive, here's my latest release: https://github.com/Clooos/Bubble-Card/releases One more thing, some users also get a previous release when they update, this has been reported yesterday and this is not the first time they report me this. I really suspect an issue with the hacstag number, this could also cause the "downgrade" issue. Also I've seen this issue reported on some other custom cards as well, this was not the case before HACS v2. Edit: This issue is really unusual 😅
|
|
I meant that you could directly upload the module .js file to assets in the corresponding release.
|
|
Yes that's what I thought, but I still don't understand why you think this would help (just curious to know), and I still believe it should works without as it was before, this is definitely a bug to me. I will try for my next release, but please consider taking a look at this, I'm definitely not alone in that boat. |
|
The "hacstag" will not cause "Custom Element doesn't exist", only failure to load the recourse will do that. As for the issues described, it sounds to me that they have the same resource defined several times, and these are fighting. If that is not it, without providing debug logs of the "failed" update, there would be too much guessing for me to even start troubleshooting here. |
|
Thank you so much for your answer @ludeeus. And what about the "downgrade" issue, they see the correct version in HACS, but the previous cached version is loaded, changing the hacstag to an higher one fix the issue in that case. Can this be related to the fact that my releases are named like "Bubble Card v2.5.0-beta.9"? The version of the release is of course just "v2.5.0-beta.9". Or even the structure of my releases? I'm still not sure to understand how this can happen and if something can be changed on my side. I'm sorry for not having provided logs (I asked to my users, without any luck). I will try again to reproduce this myself, then if I can I will provide you the logs. I'm not a backend dev at all, so I can't help much on this even if I would love to. |
This could explain any "downgrade" / "Custom Element doesn't exist" issues. |
|
Thank you again, I will share your answer to see if I can get some feedback about that 🙂 |
|
Just jumping in as a user - I'm experiencing the teh 'Custom Element doesn't exist" error, most definitely haven't defined it in multiple places, have tried clearing cache, using private browsing mode to avoid the cache, am not using cloudflare/proxy other than using nabu, and can see nothing in home-assistant.log mentioning bubblecard. Oddly enough, it's not occurring in the iOS app, but is on numerous cheap tablets, and my main Win11 machine (firefox & chrome). I'd be happy to delve deeper if you can steer me? |
|
For "Custom Element doesn't exist" there would not be anything in the home assistant log, that would be in the browser console. |
|
facepalms of course. I need more coffee today it seems. Even worse, I've just fixed it by following steps another user reported - redownloading (the specific latest version, not latest) via HACS. Hopefully someone else can grab the logs. |
|
Hi Since this (apparently random) issue appears to be happening reliably (every time) for me it appears an opportunity to send you any logs you may require to assist you (and I) of the cause?
|
|
https://hacs.xyz/docs/use/troubleshooting/logs/ would be the logs needed. |
|
Hi, someone sent me his logs, in this case v3.0.0-beta.6 is going to be installed but v2.4.0 is installed instead. And the logs when successful (the user can't install v3.0.0-beta.6 and try to install v3.0.0-beta.4 instead): Thank you so much in advance for taking a look at this 🙂 |
|
How was the install done? |
|
That was not my HACS DEBUG log but I too have been experiencing same issue. I attach another HACS debug log for reference and I added notes at the beginning of the file explaining how I went about installing which may assist HACS DEBUG LOG BubbleCard Beta 3.6 Install home-assistant_hacs_2025-05-13T07-50-41.160Z.log |
|
But how are you "installing" betas? |
|
Sorry thought I was clear in the notes I sent ... I selected HACS, filtered to BubbleCard, selected three vertical dots 'Redownload'. |
|
Thanks! |
|
FYI: The "hacstag" is not incremented by 1, it is a concatenation of the repository ID (680112919) and all the numbers in the version that was used (3006 for v3.0.0-beta.6), which (in this case) becomes 6801129193006. |
|
Thanks for reviewing and explanation of Hacstag - I did not mean to convey I knew how Hacstag number is created - rather to specifically describe the steps I took (as suggested by others). There is a but though.. AFTER I sent you that message I was busy. I can back to HA a short while ago to find that HA was again showing BubbleCard doesn’t exist!!
Edit: for completeness the (working) Dashboard Resource entry for BubbleCard, after the install (as described in the HACS Debug Log I sent earlier is: /hacsfiles/Bubble-Card/bubble-card.js?hacstag=6801129193007 /hacsfiles/Bubble-Card/bubble-card.js?hacstag=6801129193006 FAILS Cheers |
|
I just thought of something. A few months ago, someone opened a PR to include a gzipped version of the project in the Edit: Also, I asked to the user who shared his logs, to answer here to your previous question about how he did the update. |
|
I doubt it, but at this stage it is not clear what it is. |
|
If I have time tomorrow I'll try deleting and reverting back to non-beta version then progressively adding a few of beta versions to see if there is any pattern to this incrementing - would that be useful & let me know if there is anything particular you wish me to check / log. |
|
Good morning. The logs that Clooos shared where from me. I first deleted the resource in the dashboard for bubble (I had been trying to get this installed for a while) Just in case it may be relevant (think it is not, but I was in QA for over a decase), this is an HA Green Hardware. Fully updated. |
|
Just info |
|
I understand, this was part of the a list of things that we were doing trying to force it to install the correct version. Sometimes, if you changed the number at the end of the resource HACS would let you install. I got BC Beta-5 to install once by doing this. Was hit or miss. |
|
It was pretty hidden in this report, but I could reproduce it, it only happens on new installations, not on updates, as I thought by how this was presented. |
|
Thank you so much! I was unable to reproduce this, so I hope someone here can try it. Some instructions for them to know how to test it? |
|
If you need instructions on how to patch a custom integration, please don't try. |
|
I'm indeed not aware of how this works, I'm "just" a frontend dev. Also are you sure this is not happening for users who were on latest first then updated to the beta? Anyway, I truly hope this fix will works, you can't imagine how many new issues I got because of this 😂 Thank you so much again for your work and your time on this! |
|
Going "stable" -> "beta" would probably also trigger the same bug, but I did not specifically test that. Edit: Re-tested that, no it does not apply. |
|
Thank-you I removed Bubble card, installed non- |
Hey, i was facing this exact issue, tried to update from Bubble-Card v2.4.0 to v3.0.0-beta.7 for some fixes and kept getting stuck in caching issues and JS Errors. I tried downgrading / updating / reinstalling and a few fixes from the Issues on the Bubble-Card Repo to no avail before reading this issue. I did not see your Comment in time, so with v.2.4.0 installed, i applied your PR #4603 locally, restarted Home Assistant, updated to v3.0.0-beta.7 and reloaded the Tab. But as i said, before applying your patch nothing else worked, so in my opinion this a valid fix for the issue. |
|
Hi again, someone just shared these logs, is it related to the issue you fixed? I asked him to send the full logs, I'm waiting for his answer. |
|
No, is most likely due to GitHub breaking today https://www.githubstatus.com/incidents/d0nm3xcdc5jw |
|
Oh ok! Thank you for that quick answer 🙂 Also, when can we expect a new HACS update with that fix? |
|
At least not in the next 2 weeks. |
|
So what’s the fix, because I went and got BC Beta 9, and I’m back to 2.4.0. |
|
3.0.0 b7 -> b8 was OK for me, but when I went to b9 it broke. Going back to b7 or b8 from b9 fix this issue instantly. It also happens beta to beta upgrade as well. |
Uh oh!
There was an error while loading. Please reload this page.
System Health details
Not relevant
Checklist
Describe the issue
Hi!
I'm the Bubble Card developer, and since a few releases, I often have users reporting that updating Bubble Card with HACS give them the "Custom Element doesn't exist" error, this was not the case before and I don't think that I've made a change that could break that (but I might be wrong).
It seems that manually editing the hacstag to an higher number is working for some users, but also downgrading then reinstalling the new version (sometime twice?), but not for everyone. This issue is discussed here and here if you're interested on the users feedback.
What I don't understand is that this issue seems to be random, some users don't have it. I tried myself and I haven't had this issue. This issue seems to happen more with my beta releases, but I'm not sure of that.
I also checked if it was a common issue on your GitHub page, but I haven't really found something similar.
Thank you so much in advance for your help and your time! 🙂
Reproduction steps
Debug logs
Diagnostics dump
Not relevant
The text was updated successfully, but these errors were encountered: