Downloading v3.0.0-beta.1 from HACS installs v2.4.0 instead - other betas work correctly

[owldown]

I've removed the older version of Bubble Card via HACS, verified that the /homeassistant/www/community doesn't contain a directory for Bubble-Card, then restarted Home Assistant, and then re-installed Bubble Card via HACS, choosing the v3.0.0-beta.1 version.

When I edit an existing Bubble Card, or attempt to add a new one, it appears that what is currently installed in version 2.4.0 - that's what the badge at the bottom says, and there are none of the features I'd expect from a newer version, like Modules.

If I instead attempt to install version v.2.5.0-beta.9, everything works as expected, leading me to suspect that there is an issue with the 3.0.0-beta.1 version.

Expected behavior
I expected to be able to use the newest beta version and see those features.

Screenshots
If applicable, add screenshots to help explain your problem.

YAML
If applicable, add any relevant YAML code.

Your code here

Informations (please complete the following information):

• OS: HAOS
• Browser/App: Safari
• Bubble Card version: (this is the core of the issue)
• Home Assistant version: 2025.4.3

Additional context
Add any other context about the problem here.

Thank you! 🍻

[TheSunsGh0st]

Having this exact same issue

[pgale]

I used to see this before I had refreshed the browser cache (it wasn't loading the newer version) - have you done that?

EDIT: saying that, when I download beta 1, bubble card does not work at all. HA can't find the element.

[Clooos]

This is a common issue after some HACS updates.

Check this to fix it:
#1243 (comment)

[pgale]

This is a common issue after some HACS updates.

Check this to fix it: #1243 (comment)

Thanks - that fixed the issue for me :)

Oh, and I meant to say @Clooos - thanks again for all your tireless work and another bumper release! Busy testing it out now.

[TheSunsGh0st]

Downloading beta 2 fixed this issue for me.

[owldown]

Incrementing the HACS tag number didn't work for me, and that linked issue doesn't seem to match my experience. Downloading beta 1 DOES result in a working configuration, which isn't the issue that is referenced there. For me, the Bubble Cards do work after installing that beta, but the version that HACS downloads and installs is 2.4.

Following the instructions for manually downloading the js files does work, but it would be really cool to be able to iterate through the betas with the HACS installation/update process.

I'm totally guessing, but this really seems like a bug somewhere in the way that Bubble and HACS work together, since it doesn't affect any of the many other things that I'm using through HACS, and a manual download works perfectly.

[Clooos]

Yeah, I'm aware of that. I already tried to fix this, and even had a quick chat with the HACS dev here, but I still haven’t found the cause. I can’t reproduce it on my side, which doesn’t help 😅

[owldown]

Just to add more data - I removed the manually installed beta 1 from the resources (which made the Bubble cards not work, as expected), deleted the bubble-card.js from /root/config/www/ and attempted to install the beta 2 today, and got the same result: 2.4.0 was installed.
The hacstag generated from the HACS installation was 6801129193002, and incrementing this value by one had no effect, so the linked solutions also do not work for me.

Just to be more thorough, when I install beta 2 from HACS, the md5sum of the bubble-card.js matches the md5 sum of the file downloaded from GitHub as the 2.4.0 release, which seems to really strongly suggest that HACS is indeed downloading the 2.4.0 files despite my selecting the beta 2 version.

Downloading the beta 2 version from GitHub and running md5sum gives a different result than the 2.4.0 version, as expected.

[Clooos]

Thank you for these detailed informations!

Can I ask you to post your results on this HACS issue I opened? You can link this issue as well, I'm really clueless.

hacs/integration#4501

[MikeDeltaHH]

Just for information - same problem here with v3.0.0-beta.3.

[Clooos]

Like I explained above, this is a common issue after some HACS updates.

Check this to fix it:
#1243 (comment)

[MikeDeltaHH]

Like I explained above, this is a common issue after some HACS updates.

Check this to fix it: #1243 (comment)

Hi!
I have tested both with beta 3, but it doesn't work for me. However, beta 1+2 can be downloaded and are displayed correctly, so I'm sticking with beta 2 for now. Thank you for your fantastic bubble card, I have almost completely rebuilt my two dashboards with it and they look much better than before.

[Clooos]

Have you tried to change the hacstag? This method is working most of the time, just change it by changing the last number + 1.

[MikeDeltaHH]

Have you tried to change the hacstag? This method is working most of the time, just change it by changing the last number + 1.

I may have misunderstood something here - the hacstag is when I download the beta 3 in Dashboard - Resources the 6801129193003 - nevertheless the bubble cards themselves show me the 2.4 - do I have to adjust the version somewhere else?

[Clooos]

If you have downloaded the v3.0.0-beta in HACS, but v2.4 is shown in the editor, this fix can solve that as well.

Go in edit mode, then go to "Manage resources".

Then clic on the line with bubble-card.js, then if the hacstag is like that: hacstag=394082552765 change the last number + 1, so hacstag=394082552766. The new hacstag just needs to be different to the previous one.

[MikeDeltaHH]

If you have downloaded the v3.0.0-beta in HACS, but v2.4 is shown in the editor, this fix can solve that as well.

Go in edit mode, then go to "Manage resources".

Then clic on the line with bubble-card.js, then if the hacstag is like that: hacstag=394082552765 change the last number + 1, so hacstag=394082552766. The new hacstag just needs to be different to the previous one.

Ok, thanks - that's it - I thought that 6801129193003 fits for beta 3 because beta 2 had the hacstag 6801129193002 - but that was probably the mistake!

[Clooos]

Hi everyone! Ludeeus, the HACS dev, was finally able to reproduce this issue, and it will be fixed in the next HACS release! 🥳

This only happens with beta versions (any version that isn’t marked as “latest”). And after three months of beta testing, you can’t imagine how many times this issue has been reported, here, on the HA forum, on Reddit...

So I'm really relieved it's finally identified and being fixed. Huge thanks to everyone who helped report it and stayed patient along the way!

hacs/integration#4603