HACS should use the Brands Proxy API for installed custom integrations on Home Assistant 2026.3+

[itsh-neumeier]

Checklist

• I am running Home Assistant 2026.3 or newer
• The custom integration provides local brand assets in custom_components/<domain>/brand/
• The icon is shown correctly in Home Assistant itself
• HACS still shows the placeholder icon

Problem

Starting with Home Assistant 2026.3, custom integrations can provide their own brand assets locally via the Brands Proxy API.

In my setup, the integration icon is loaded correctly by Home Assistant, but HACS still shows the placeholder icon in the repository list. This suggests HACS is still relying on the CDN fallback URL:

https://brands.home-assistant.io/_/<domain>/icon.png

instead of the local HA Brands Proxy endpoint:

/api/brands/integration/<domain>/icon.png

Expected behavior

For installed custom integrations on Home Assistant 2026.3+, HACS should prefer the local Brands Proxy API endpoint and only fall back to the CDN/placeholder if needed.

Example

Domain:
froeling_connect_local

Works in Home Assistant:
/api/brands/integration/froeling_connect_local/icon.png

Still shows placeholder in HACS:
https://brands.home-assistant.io/_/froeling_connect_local/icon.png

Why this matters

The home-assistant/brands repository no longer accepts custom integration brand assets for CDN hosting, so HACS needs to consume the local brand source for custom integrations on modern HA versions.

Reference

https://developers.home-assistant.io/blog/2026/02/24/brands-proxy-api

[hacs-bot]

Thank you for opening an issue in the HACS.

Before proceeding, please verify the following:

Select the correct issue template:
HACS provides different templates for different types of bugs. Choosing the right template ensures you're asked the right questions and helps route your bug appropriately.

Complete the ENTIRE issue template:
Make sure you've read the issue guidelines and filled out every single field in the issue template, even if some fields seem unrelated to your specific situation.

Fill out everything, even if it seems unnecessary:
Don't skip fields because they "don't seem relevant" to your bug. The template asks for specific information because:

• Problems often have unexpected causes that surface through "unrelated" details
• What seems unrelated to you might be the key to solving your bug
• Incomplete information requires follow-up questions, delaying resolution
• The template is designed based on years of troubleshooting experience
• Missing information forces those helping to make assumptions, which can lead to wrong solutions

Issues with incomplete templates take significantly longer to resolve or may be closed without resolution.

If you're experiencing a similar bug:
If your bug is identical to an existing one, please:

• Add a 👍 reaction to the original issue description
• Subscribe to notifications on that issue to stay updated
• Do not add comments like "same here", "I have this too", or "+1"

Adding duplicate comments creates noise and makes it harder to track and resolve issues. Reactions help prioritize issues based on how many users are affected.

Getting help:
If you need assistance filling out the template or understanding your issue:

• Issue Guidelines - Detailed instructions for reporting issues
• HACS Discord - Community support and real-time help

What happens next:
Maintainers and community members will review your issue and may:

• Ask for additional information if the template is incomplete
• Provide a solution or workaround
• Label the issue appropriately for tracking
• Link it to related issues or pull requests

[itsh-neumeier]

I traced the repository list icon rendering to hacs/frontend rather than hacs/integration and opened a frontend PR with a local-brands-first fallback approach: hacs/frontend#929