Post 2026.3 update - Mushroom update card "Picture entity" not displaying

[Revamp]

Hello,

I have updated to HA core 2026.3 all looks reasonable except for the Mushroom Update card.

This is where I can’t get the entity picture to be display even though it has been selected correctly in the card.

I have looked at the new local brands integration documentation (for the entity picture - Icon / Logo) but it doesn’t help with my problem.

I think this could be down to a missing token issue but I’m not sure.

For example, looking at the attributes of the “update.home_assistant_core_update” entity via developer tools / status…

I can see the path for the entity picture which seems correct.

But this is where I can see that there is no token passed at the end of the “picture entity” URL path…

The problem is I don’t know how to address and where fix this, or change the requirements as stated in the link below.

Custom integrations can now ship their own brand images | Home Assistant...

This could be a problem or bug related the Mushroom Update card only as I can choose the entity picture in the native Tile card successfully.

Any guidance or solution how to resolve this would be greatly appreciated ?

[WallyR (Wally)]

I have a post about it too.
The path is in the updat entity, but if you go to the path on the web site, then you get an error 403.
It is not the mushroom cards, but the actually core, supervisor and so on th are missing the icons files.

[Revamp]

Thank you for your feedback…

it’s so difficult to determine where the issue lay, hence the post.

I guess we have to wait for an update…

[Ildar_Gabdullin]

Sorry, perhaps I am missing smth, but see no issues with entity_pictures:

These entities have differently defined urls in “entity_picture” (and thus differently stored images):

[Revamp]

Hi,

Thanks for your time and reply…

Yes I agree as stated lower down in my initial post that I can choose the picture entity for the same entity -

“update.home_assistant_core_update”

in the native “Tile card” successfully however not in the mushroom update card as depicted in my first post.

Hence It may be a Mushroom update card bug issue for that card only…

The picture entity is broken for all of my update entities using the Mushroom update card.

I need to verify this before placing a bug report with the mushroom card as this issue occured instantly post the HA Core 2026.3 update.

I noticed the difference between the two cards in the web inspector is that the Tile card had a token number passed to it at the end of the URL where the mushroom card did not. I believe that this is the API token mechanism required to be able to display the entity picture.

However that is the limit of my findings.

[WallyR (Wally)]

I use the entity_picture attribute in the update entities for my update dashboard and all the other ones work.
It is only the ones for the OHP products that fail and if I try to follow the url manually, then it will fail for those too, where as all the others work.

I am using a template for ALL update entities, so I can not just switch to a picture entity for some of them.

[Revamp]

Hi Wally,

It is strange as the folder and icon / logo’s are locally cached ready to be sourced instead of using the CDN URL…
E.g.
api/brands/integration/homeassistant/icon or logo etc

However the system API is just not redirecting to the targeted locally stored cached images for the mushroom update card, I don’t think there is the necessary “brands” folder in the HACS Mushroom plugin yet.

After looking at the native “Tile” card I have seen just how evolved it has become and can do almost do everything I need, however there are still some limitations.

Yes, like you, I have a dedicated controlled dashboard with several views (4) to help manage all the constant flow of updates from HA’s own, HACS, third party software and firmware and more.
It makes it much more easy to spot / see / recognise / control the constant waterfall of changes for all software.

The entity picture is more defined instead of a flat toned Icon especially for those with bad eyes… Hence the background colours of my dashboard (with graduations which change colour and auto switch change to view upon new update availability) for a more distinct contrast for a quick instant easy read.

Anyway one wonders as I have read that the dev of the Mushroom cards is now in house employed by the HA team and this is a subtle push to move across to the native tile card.

Shame it does not have the badge options yet but maybe this can be done in code.

It makes sense as you don’t want to maintain a forked route of your own product if this is indeed the case.

In any case, thanks for your steers, as always they are much appreciated…

Here is an example with token…

<state-badge class="has-no-radius" style="background-image: url(&quot;http://arnac25:8123/api/brands/integration/homeassistant/icon.png?placeholder=no&amp;token=13c431c150cbfdb666e9cccb47e0f158a25c73ab35e685cd6705371200d1ec90&quot;);">

and an example without the token…

<img class="picture" src="http://arnac25:8123/api/brands/integration/homeassistant/icon.png?placeholder=no">

[Opontios (Agisilaos Ignatiadis)]

It has affected not only Mushroom cards. The below is a custom button card.

[WallyR (Wally)]

I use markdown cards.

It is not the cards, but HA core, which either have the wrong path to the icon file, is missing the icon file or have some permission issue that prevent access to the icon file on the web service.

[Revamp]

Ahh Yes… Auth… Auth Token.

Keeping in mind that flat icons and the old CDN URL still work, and fetches the image if used.

Fingers crossed… ![] Wally / Opontios that its just an Auth Token issue as you have pointed out that there are going to be more non functioning broken links out there.

I have issued a bug report on GITHub for the developer of the Mushroom implementation and the dev has responded and escalated it to HA, with request to apply the necessary and same token authentication as the “Tile card”.

Just to keep the language straight…

Implementation = Native HA implementation
Plugin = HACS implementation

It might just be that all Implementations / Plugins just needs an empty brands folder to invoke the Auth Token mech but that’s not conclusive as Frenck’s document shows everything in the CC folder rather than the WWW folder and this may be where they need to reside to work… I hope not…

I’m not sure as it might just be an illustrative example placed in the CC folder and not the WWW folder for document purposes only.

As an example if you look at the HACS “Simple Timer” implementation, you will see this has already been implemented in this plugin. The “brands” folder structure exists to make use of a local offline stale image.

However… Note that it resides in the CC folder and not in the WWW folder, I don’t know if this location required for it to work or if it just does not matter.

Moving forward I think all implementations / plugins that require the use of their own entity picture (offline ) will need a “brands” folder.

The problem lay when you want to make use of other stock available branded entity pictures locally (offline) other than its own might have need of a brands folder within its implementation / plugin with alternate Auth token to access it, I’m not sure so we will have to wait and see what happens… ![]

I believe that is how the Auth token mechanism works as stated below.

Starting with Home Assistant 2026.3, custom integrations can include their own brand images (icons and logos) directly in the integration directory. No more submitting to a separate repository — just drop your images in a brand/ folder and they show up in the UI.

Local brand images for custom integrations

Add a brand/ directory to your custom integration with your icon and logo files:

custom_components/my_integration/├── __init__.py├── manifest.json└── brand/    ├── icon.png    └── logo.png

and

These endpoints require authentication. The brandsUrl() helper handles this automatically by appending an access token. If you construct URLs manually, obtain a token via the brands/access_token WebSocket command and append it as a token query parameter.

[Revamp]

Quick update…

“Grâce” to the Dev who owns the Mushroom implantation, he has created a PR to address this issue as quoted below.

Blockquote… Created a PR in HA frontend directly so cards don’t have to handle token authentication (home-assistant/frontend#30111). I hope it will be part of next Home Assistant patch release.

[Revamp]

@WallyR
@Opontios

FYI…

I can confirm after update to HA core 2026.3.2 that Entity Pictures now display correctly…

[WallyR (Wally)]

I can confirm that they do still not seem to work for the update entities of the HA repositories (HA core, HAOS, Supervisor, SkyConnect, ZBT.2).

[Revamp]

Evening Wally,
I generated a bug report for the “Mushroom update card” only and they all display correctly after the “.cache” folder has been generated. This folder is not always created after a HA restart, I had to boot my box for it to pull down and generate the “.cache” folder and copy in all the main images as shown in file editor in the screen shots below.

I believe you are using a different card (that is template or markdown card right) ?

Do you have or has your “.cache” folder been generated yet ?

The entity picture displays in the mushroom implementation range of cards where applicable, without the required “brands” auth token passed at the end of the picture path. Example below…

[WallyR (Wally)]

I have it generated and I also see the icon files.
The issue is that the update entities does not point to those icon files.
The path is wrong in the update entities.