Help Please: Custom Element Doesn't Exist - Firemote, Universal Remote Card, etc

Hi All,

I am new to Home Assitant and am trying to us eit as a universal remote control. I have been using the web and ChatGPT to try and get thigns setup.

My idea was to have a homepage with buttons like Watch Apple TV, Watch Firestick, Watch Zidoo UHD8000, Etc.

The home page works, including turning on all the needed sources and setting them on the right inputs. Where things all far apart is it does not go to next remote page and the remote is not visible. Instead of the remote being visibile it says, “Custom Element Doesn’t Exist: Universal Remote Card”. This is the same for Firemote, Universal Remote Card and many other HACS downloads.

I have spent hours and hours using chat GPT and searching online.

I have cleared the cash and restarted HA many times and I even did a full reformat and reinstall… same issue.

Please help.

Thank you

I can confirm the resource i listed as:
/local/community/android-tv-card/universal-remote-card.min.js

File path for yaml file:
/homeassistant/www/community/android-tv-card/universal-remote-card.min.js

This is the my configuration yaml:
lovelace:
mode: yaml
resources:
- url: /local/community/HA-Firemote/HA-Firemote.js
type: module
- url: /local/community/android-tv-card/universal-remote-card.min.js
type: module
- url: /local/community/button-card/button-card.js
type: module
- url: /local/community/mini-media-player/mini-media-player-bundle.js
type: module

dashboards:
master-bedroom-controls:
title: “Master Bedroom Controls”
mode: yaml
filename: lovelace_dashboards/master_bedroom_controls_dashboard.yaml

wake_on_lan:

script: !include scripts.yaml
automation: !include automations.yaml

Thank you

try changing all of the resources to this:

lovelace:
mode: yaml
resources:
  - url: /hacsfiles/HA-Firemote/HA-Firemote.js
    type: module
  - url: /hacsfiles/android-tv-card/universal-remote-card.min.js
    type: module
  - url: /hacsfiles/button-card/button-card.js
    type: module
  - url: /hacsfiles/mini-media-player/mini-media-player-bundle.js
    type: module
1 Like

Thank you, but sadly this did not fix it.

Have you tried clearing the browser cache since that change?

Yes, still no joy sadly