Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Custom element doesn't exist: mini-media-player. #437

Closed
AntoxaSa opened this issue Nov 14, 2020 · 13 comments
Closed

Custom element doesn't exist: mini-media-player. #437

AntoxaSa opened this issue Nov 14, 2020 · 13 comments

Comments

@AntoxaSa
Copy link

Custom element doesn't exist: mini-media-player.
entity: media_player.yandex_station_ff98f029b3bab4f30a965b06
shortcuts:
attribute: sound_mode
buttons:
- icon: 'mdi:voice'
id: Произнеси текст
type: sound_mode
- icon: 'mdi:google-assistant'
id: Выполни команду
type: sound_mode
- icon: 'mdi:playlist-star'
id: включи мою любимую музыку вперемешку
type: command
- icon: 'mdi:playlist-music'
id: включи плейлист дня
type: command
- icon: 'mdi:heart'
id: лайк
type: command
- icon: 'mdi:heart-off'
id: снять лайк
type: command
columns: 6
tts:
platform: yandex_station
type: 'custom:mini-media-player'
I installed a mini player via hacks.
The interface is set to manual control, I write it in configuration.yaml
resources:
url: /hacsfiles/mini-media-player/mini-media-player-bundle.js
type: module
I get the error:
Component error: resources - Integration 'resources' not found.
What am I doing wrong? what is the problem?

@wisdomdevil
Copy link

@AntoxaSa Hi man, i have same issue in manual mode. A resolution is put you directory path :

url: /hacsfiles/mini-media-player/mini-media-player-bundle.js
type: module

in lovelace-ui.yaml , but you dont need to write "resource:" befor it, just url and type on top of the in lovelace-ui.yaml

@loic-moriame
Copy link

Since Home Assistant 0.117, you need to add manually ressources for Lovelace Dashboards (dashboard made from the admin panel, not in yaml files)

Go to Configuration > Lovelace Dashboards
config general

Then add a new ressource for mini-player:
config lovelace dashboard

@mgaeremynck
Copy link

Hallo,

Same issue here. Installed the card through HACS but no luck. Always 'Custom element doesn't exist: mini-media-player'. All other custom cards seem to work.

I verified the Lovelace Dashboards and the entry is present and I have restarted multiple times.

Any tips?

@mimokini
Copy link

mimokini commented Dec 3, 2020

Maybe the JS file is wrong

@esolutions4ev1
Copy link

This worked for me. If this is a solution to the issue then possibly an update to the documentation is necessary when in YAML mode.

After a new install of HACS and install of 'mini-media-player' through the UI the player did not work when in 'YAML' mode. I received the same error "Custom element doesn't exist: mini-media-player". I manually added 'resources' but using the URL of "/local/community/mini-media-player/mini-media-player-bundle.js" as that is where HACS places it. Restart HA and everything works.

@boulder240
Copy link

esolutions4ev1 is what worked for me as well.

@horriblenoises
Copy link

Leaving my solution here as google took me to this page.

Manual installed via wget. Added url to lovelace resources ui.
Listing url with version argument causes "element doesn't exist" error. Removing version info, resolves issue.

/local/mini-media-player-bundle.js ?v=1.12.1

@avviano
Copy link

avviano commented Jul 2, 2021

I followed esolutions4ev1 procedure and it worked for me.

@popy2k14
Copy link

This worked for me. If this is a solution to the issue then possibly an update to the documentation is necessary when in YAML mode.

After a new install of HACS and install of 'mini-media-player' through the UI the player did not work when in 'YAML' mode. I received the same error "Custom element doesn't exist: mini-media-player". I manually added 'resources' but using the URL of "/local/community/mini-media-player/mini-media-player-bundle.js" as that is where HACS places it. Restart HA and everything works.

thx, that also worked for me.
Also saw that the path was wrong but i dont worried about this.
But heck, yes, that was the issue.

thx a lot

@NightMean
Copy link

This worked for me. If this is a solution to the issue then possibly an update to the documentation is necessary when in YAML mode.

After a new install of HACS and install of 'mini-media-player' through the UI the player did not work when in 'YAML' mode. I received the same error "Custom element doesn't exist: mini-media-player". I manually added 'resources' but using the URL of "/local/community/mini-media-player/mini-media-player-bundle.js" as that is where HACS places it. Restart HA and everything works.

Worked for me as well, thanks!
The URL that HACS automatically used for me was:
/hacsfiles/mini-media-player/mini-media-player-bundle.js?hacstag=1485208381165

@Lesani
Copy link

Lesani commented Jan 2, 2023

same issue, same solution, just installed via hacs and had the /hacsfiles/ ressource in my ressource list.

maybe add an info to this to the readme @kalkih ?

@peterlouvel
Copy link

I had the same error after an update to HA.
Ended up fixing it by deleting it from the 'Frontend' in HACS and re-downloading via the Explorer & Download Repositories

@tclemos
Copy link

tclemos commented Dec 23, 2023

This worked for me. If this is a solution to the issue then possibly an update to the documentation is necessary when in YAML mode.

After a new install of HACS and install of 'mini-media-player' through the UI the player did not work when in 'YAML' mode. I received the same error "Custom element doesn't exist: mini-media-player". I manually added 'resources' but using the URL of "/local/community/mini-media-player/mini-media-player-bundle.js" as that is where HACS places it. Restart HA and everything works.

I just reinstalled the mini-media-player via HACS, followed these instructions and it worked.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests