If you installed a card through HACS and it doesn’t appear, or your dashboard shows “Custom element doesn’t exist”, the card’s file usually isn’t loaded. Downloading a card in HACS does not put it on a dashboard. You still add the card, and the dashboard has to load the card’s file.
Start with a hard refresh
Most of the time, a cached frontend is the cause. Hard-refresh the browser:
- Windows or Linux: Ctrl+F5 or Ctrl+Shift+R
- Mac: Cmd+Shift+R
In the Home Assistant Companion app, go to Settings > Companion App > Debugging, select Reset frontend cache, then restart the app.
A Home Assistant restart usually doesn’t fix a cached frontend, so clear the browser cache first.
Check the dashboard resource
Each card needs a dashboard resource entry that points to its file.
- Storage-mode dashboards (the ones you edit in the UI): HACS adds the resource for you.
- YAML-mode dashboards: you add the resource yourself, as described below.
To view the resources:
- Turn on Advanced Mode in your user profile.
- Go to Settings > Dashboards, open the three-dot menu, and select Resources.
Each entry should use the URL /hacsfiles/<repo-name>/<file>.js and the type JavaScript module. HACS stores the files in /config/www/community/<repo-name>/, and /hacsfiles/ maps to that folder. Note that /local/ and /hacsfiles/ are not interchangeable for HACS-managed files.
Fix the resource type
The type must be JavaScript module. Older entries registered as plain JavaScript can fail with newer cards. If the type is wrong, edit the entry, change it to the module type, and save.
YAML-mode dashboards
If your dashboard is in YAML mode, add the resource to configuration.yaml under lovelace:, with type: module:
lovelace:
resources:
- url: /hacsfiles/my-card/my-card.js
type: module
Use the file name that HACS installed for your card, then restart Home Assistant. Card resources in YAML mode don’t reload until you restart.
Remove duplicate or stale resources
Old ?hacstag= entries, or manual copies of a card in /local/, can conflict with the HACS version. Keep one resource entry per card, and delete the rest.
Read the browser console
Press F12 to open the browser’s developer tools, then look at the Console and Network tabs. A 404 error for the resource means the file path is wrong. A JavaScript error usually points to the card’s own code.
“Custom element doesn’t exist: X” means one of two things. Either the resource isn’t loaded, or the card type name is misspelled. In YAML, card types need the custom: prefix, such as type: custom:mushroom-entity-card.
Card missing from the picker
Some cards don’t appear in the card picker. You can still add them by choosing the Manual card, which takes YAML. Use the card’s documented type name.
When it still fails
If the card still doesn’t load:
- Uninstall the card in HACS.
- Remove its resource entry from the dashboard’s resources.
- Restart Home Assistant.
- Reinstall the card in HACS, then add the resource back once.
- Clear the browser cache and refresh the dashboard.
Frontend updates can also break older cards. Check the card’s issue tracker and update the card in HACS.
Common misconceptions
- “Downloading a card puts it on my dashboard.” It doesn’t. You still add the card to a dashboard.
- “A restart will fix a cached frontend.” Usually it won’t. Clear the browser cache.
- “Integrations from HACS are cards.” They are not. Integrations appear under Settings > Devices & services after a restart.
For the HACS install steps, see our HACS guide. For card picks, see popular HACS repositories.