Anashost/MY-HA-DASH layout acts weird!

Configuration Frontend
1

Good day everyone,

I’ve waited quite a while before bringing my issue to you. My apologies in advance if I’ve posted this in the wrong category, let me know if it belongs elsewhere.

Now to the issue:

For about two years, I’ve been happily using the My-HA-DASH Dashboard created by Anahost.

First of all, a big compliment to Anahost for this great work! Of course, I’ve made some tweaks here and there to match the dashboard to my own preferences, and everything worked perfectly, until about two months ago.

After a major Home Assistant update (please don’t ask me which one exactly), the layout of the dashboard started acting up. The strange part is, it doesn’t always happen, but it does happen often. When I open HA, I suddenly see large empty spaces between cards, and some buttons behave weirdly. If I restart HA a few times, things usually go back to normal. But the next time I open it, the issue returns.

image
image867×928 56.3 KB

On the left you’ll see the correct version of the dashboard, and on the right the “broken” one.

When I press the “lamp” icon on the broken dashboard, I would normally be redirected to the lights card. That no longer works in this situation!
Instead, what happens now is that the remaining icons turn grey, as if I’m toggling them on and off. Very strange behavior!

It’s really starting to get annoying. I had hoped one of the newer updates would fix it, but unfortunately… we’re a few updates down the road and the issue persists.

I’m hoping someone in this community might be able to help. Maybe it’s something small, who knows?

If you need more info, just let me know!

Kind regards,
Herman F.

2

Tried to search by “anashost” word, found a little info in community.
Perhaps you should create an issue in this plugin’s repo? Or ask this person himself, he has an account here.

3

Thank you for your response. It hadn’t occurred to me that @Anashost might have an account here as well. I’ll try to tag him in the hope that he notices my post. I genuinely love his work!

1 Like
4

Hey Herman F
I just got notified about your issue. I’m still using the dashboard I built in the repo and haven’t run into any problems, so my best guess is that one of these integrations (or both) might be causing it.

  • card-mod
  • button-card

Both recently had major updates, and I haven’t updated or tested them yet. I’d recommend temporarily rolling them back to these versions:

  • card-mod: 3.4.5
  • button-card: 6.0.0 or 7.0.0

After that, clear your cache and check whether the problem goes away.

Also, make sure that the view is still using the old Masonry Layout, since the dashboard was originally built with that layout in mind.

Let me know how it goes!

5

If you use 2025.11 - may be better to try 3.4.6 since it has fixes for Entities card due to changes in 2025.11.
If you use an earlier HA version - keep using card-mod 3.4.5.
Using card-mod v4 will require from you to add alterations in your code, so first try to localize the issue.

1 Like
6

Wait, I just remembered something I did a while ago after a Mushroom card update. There was something that needed changes on the cards that cause problems.
Replace:
custom:mushroom-template-card
with
custom:mushroom-legacy-template-card

Let me know which one resolves the issue so I can update the repo accordingly.

7

Hello everyone,

@Anashost,how great to receive a response from you! Once again, my sincere compliments on the dashboard you’ve created. I really hope you’ll continue developing it further, because this layout is totally my style. Thanks!

I tried using the custom:mushroom-legacy-template-card, but unfortunately, it doesn’t solve the issue. In fact, it disrupts the dashboard even more.

Rolling back the version of the two cards you mentioned does seem to work for now.

What should be the next step?

Kind regards,

Herman

8

Thanks for your kind words. I would suggest sending me the yaml of one of your problematic cards to test it on my system. That would give me a better idea.

there’s something you can test FIRST that might help.

  • clear browser/ HA app cach

  • try adding this to your configurations.yaml

# Load frontend modules
frontend:
  extra_module_url:
    - /hacsfiles/lovelace-card-mod/card-mod.js

then restart home assistant.

Let me know how it goes.

9

Hello,

I tried to implement the code in the configuration.yaml file. Unfortunately, it keeps indicating that something is wrong with the code. A red exclamation mark appears, which means there is a syntax error.

Do you have any idea what might be wrong?

10

Could be a duplicate. You should already have frontend entery in your file, so just add this under it, then restart.

  extra_module_url:
    - /hacsfiles/lovelace-card-mod/card-mod.js

spacing matter here, otherwise you will get syntax error.

11

You’re absolutely right. I had created a duplicate reference, should’ve checked that more carefully! Thanks for the reminder.

I’ve added the code and updated the cards to the latest version again.

Unfortunately, I still have to report that the issue is still there.

Regards,
Herman

12

mmm. then this would be the next step:

I would suggest sending me the yaml of one of your problematic cards to test it on my system. That would give me a better idea.

13

For card_mod, if you are using HACS, check out latest recommendations on using extra_module_url. if you mix up URLs, card_mod can be running twice. v4 has code to stop duplicate patching when all cached referenced card_mod.js are v4. However you have no guarantee what version might be running if you have mixed URLs.

14

If a user has ONE version physically stored on their PC, and a browser cache is cleared, whether you have an url with a long “12345678” tag or not - it will never load different versions. It may be (since you said you are sure) two different modules of same version.

15

That is correct while nothing has changed, and browser cache has been cleared. Once the stored file changes, say due to upgrade via HACS or manually, different versions will then be running until browser cached cleared again.

16

This is correct. That is why a usual rule should be “always purge a browser cache after installing ANY update”.
Take a HA frontend - same.

17

This will not be required if following the recommendations of using the HACS url or adding manual cache busting search string if installing manually. Also on devices the Home Assistant Frontend cache needs to be cleared which, without any custom javascript solution, or using browser_mod.refresh if available, means using the debug option in the Companion App.

18

Easier to remember a simple rule which I mentioned than remember exceptions like “card/mod v4 does not need clearing a cache” since this rule is common both for custom frontend plugins and frontend itself.

19

Hi @Anashost ,

Where would you prefer to receive the code? I’m asking because I need to anonymize it before sharing it publicly. Can I send it to you directly?

Looking forward to your reply.

Cheers Herman