The app name will show up if there’s no other media information available.
Hello everyone!
I need help:
I put the file in the folder “/config/www”
mini-media-player-bundle.js
no “ui-lovelace.yaml”
the next:
resources:
- url: /local/mini-media-player-bundle.js?v=1.0.2
type: module
I’m using duckdns, I’m in version 0.88.2 of HA HASSIO.
I get the information: "custom element does not exist: mini-media-player."
What am I doing wrong? What is missing ?
I’m sorry, my bad. The card had disappeared from custom updater, and I didn’t realize I didn’t have the latest version… Doh!
1 Like
Hey!
What do you mean by - no “ui-lovelace.yaml”.
If you mean you are using the GUI to edit the UI, check out this post.
Just a heads up, v1.0.0 had quite a few breaking changes, so might have to adjust your card configs 
1 Like
Sorry for the translator
I want to say that I added the entry in the file: ui-lovelace.yaml
Thanks for the quick response!!!
Congrats on the job!
Okay, if you just created the www folder you might need to restart Home Assistant.
If you still have problems, double check that the file is located in the correct folder and check the browser developer log for additional errors.
Thanks!
I noticed! 
I could not visualize error walks in develop. Would I have the way I need to look?
I wanted to use this card a lot … But I do not know where my mistake is …
I do not know what to try anymore … 
I didn’t understand if you managed to open the dev console or just didn’t see any error messages.
To open it In Chrome:
Windows: CTRL-SHIFT-J OR F12
Mac: ⌥-⌘-J
Perhaps, this guide can help you:
1 Like
I opened it. But I do not see how to locate a bug … Open panel I got …
My ui-lovelace.yaml:
title: Minha Casa
# Include external resources
resources:
- url: /local/my-custom-card.js
- url: /local/custom_ui/weather-card.js
type: js
- url: /local/my-webfont.css
type: css
- url: /local/button-card.js
type: module
- url: /local/mini-media-player-bundle.js?v=1.0.2
type: module
my configuration.yaml :
whitelist_external_dirs:
- /tmp
- /config/temp/
- /config/www/Have you managed to get any other custom cards working?
I managed to solve … as I am using the new editing interface I had to put the resources in it … see how it was !!
Sorry for the inconvenience … but the tips for the next ones are …
resources:
- url: /local/mini-media-player-bundle.js?v=1.0.2
type: module
- url: /local/my-custom-card.js
- url: /local/custom_ui/weather-card.js
type: js
- url: /local/my-webfont.css
type: css
- url: /local/button-card.js
type: module
resources: null
- url: /customcards/github/thomasloven/card-tools.js?track=true
type: js
title: Home Assistant
views:
- badges:
- binary_sensor.tv_sala
- binary_sensor.mi_box
- binary_sensor.ki_plus
- device_tracker.renato_iphone
- device_tracker.juliana_iphone
- sensor.temp_message
- sensor.sonoff01_double_hold
- sensor.dark_sky_temperature
- sensor.campainha
- sensor.disk_use_percent_home
- sensor.iphone_de_renato_battery_state
- sensor.iphone_de_renato_battery_level
- sun.sun
cards:
- entities:
1 Like
I had a similar error, the card wouldn’t show till I put the resources line near the very top of the lovelace-ui. Now all good!
I was wrong. It must be the first line in the raw editor. Then it works fine, Thanks to all.
I read that this card is not working good with the latest alexa_media custom component. Is it right? And if yes, how to fix it? I have problems with tts alexa platform as it always doesn’t work telling me it cannot use tts google platform.
Where did you read that?
You would have to specify platform: alexa in order for tts to work with the custom “alexa/echo component”.
- type: custom:mini-media-player
entity: media_player.echo
tts:
platform: alexa
I read it here:
About the platform i have alexa already set for my echo devices, but always get ‘failed a call to media_player/alexa_tts service’ or something similar…
They are using invalid configurations.
Ogh, you said “telling me it cannot use tts google platform.” before, that’s why I thought you had an incorrect card config.
Not sure, doesn’t look like anything has changed from reading the docs.
I don’t see why it wouldn’t work, and I can’t test it since I don’t have any echos.
Ok, so i hope someone else having an echo can test it and help me to solve this issue…
Posted in the custom alexa component thread, and seems like at least this guy/gal got it to work.