Hi Kalkih
I was wondering, is there a maximum number of letters for sources in the source picker? Not all my sources are showing after being selected, and I then reload the page. Music is still playing, but the source is empty. I still see them all in the list, when I press the source picker. I have noticed, that the sources with short names are visible even after reloading the page, but longer sources seem to disappear.
Alright, I need a bit more info to try to re-create this.
Roughly, how many characters are the sources that doesnât show?
Which browser are you having this issue in?
I see it both on pc (chrome, edge) and from the Ios app.
I have a source with 10 letters, which is not visible
Hmm, I canât reproduce this issue.
Are you on the latest version v0.8.2?
Does it show up in the regular source select (more info dialog)?
Is it just this particular source that doesnât show up?
Is it still saying âAfslapningâ if you refresh the site?
Yes, I have tried with the newest, same result.
It is only Skala FM and DR P3 that works. The rest results in not being visible, if I refresh the site, eventhough the source is correctly playing. And no, they do not show up in the regular source select either 
Oooh wait! It seems that only the sources connected to a tunein station works. The rest are playlists marked as Sonos Favourites. I think that could be the issue. Just tried adding a new radio station, and that one workes just as the other stations DR P3 and Skala FM.
Ok, itâs possible that this is a bug in the sonos component where the source attribute is not reported to the entities state properly. Thatâs probably also why itâs gone after a refresh since I use the entities source attribute to display the current source.
Added: show_progress option to show a progress bar when media progress information is available
Added: support to display media_series_title, media_season & media_episode information when available #13
I have this in my lovelace:
- title: Media Mini
icon: mdi:boombox
cards:
- type: entities
title: Google Devices
entities:
- entity: media_player.all_speakers
type: "custom:mini-media-player"
group: true
show_tts: google
artwork: cover
power_color: true
scroll_info: true
- entity: media_player.living_areas
type: "custom:mini-media-player"
group: true
show_tts: google
artwork: cover
power_color: true
scroll_info: true
- entity: media_player.bedroom_speaker
type: "custom:mini-media-player"
group: true
show_tts: google
artwork: cover
power_color: true
scroll_info: true
- entity: media_player.office_speaker
type: "custom:mini-media-player"
group: true
show_tts: google
artwork: cover
power_color: true
scroll_info: true
- entity: media_player.lounge_speaker
type: "custom:mini-media-player"
group: true
show_tts: google
artwork: cover
power_color: true
scroll_info: true
- entity: media_player.lounge_room_tv
type: "custom:mini-media-player"
group: true
artwork: cover
power_color: true
- type: entities
title: Other Media Players
entities:
- entity: media_player.roku_5x46aj056306
type: "custom:mini-media-player"
group: true
artwork: cover
power_color: true
scroll_info: true
- entity: media_player.foxtel_7587
type: "custom:mini-media-player"
group: true
artwork: cover
power_color: true
scroll_info: true
- entity: media_player.kodi
type: "custom:mini-media-player"
group: true
artwork: cover
power_color: true
scroll_info: true
- entity: media_player.osmc_vero4
type: "custom:mini-media-player"
group: true
artwork: cover
power_color: true
scroll_info: true
- entity: media_player.txnr1009
type: "custom:mini-media-player"
group: true
artwork: cover
power_color: true
scroll_info: true
show_source: true
- entity: media_player.samsung_tv
type: "custom:mini-media-player"
group: true
artwork: cover
power_color: true
show_source: true
Which seems to work fine. But I am getting this error:
2018-10-02 10:23:57 ERROR (MainThread) [frontend.js.latest.201809270] https://domain.duckdns.org:30443/local/mini-media-player.js?ver=0.8.3:680:22 NotSupportedError: Cannot define multiple custom elements with the same tag name
Maybe itâs the colons in your JS include âmini-media-player.js?0.8.3:680:22â
Replace the colons with something else, dashes maybe?
the colons are not in the JS include. Only in the error.
Yes, you are probably right about that 
I actually saw this error in my log once as well, but it didnât make sense so I ignored it and it has not showed up again.
My first thought was that it were a caching issue, where the old version would still be loaded in parallel with the new one.
The error message indicates that the custom-element tag name mini-media-player (I suppose) is already defined.
The card still works as expected right?
You donât import the mini-media-player twice under resources: in ui-lovelace.yaml?
Would you mind posting everything from your resources: in your ui-lovelace.yaml?
Hi,
i have some problems with the mini-media-player
http://hassio.local:8123/local/mini-media-player.js?v=0.8.3:9:1 Uncaught SyntaxError: Unexpected token <
In my config.yaml it looks like this:
frontend: javascript_version: latest
and my ui-lovelace.yaml:
title: My Awesome Home
# Include external resources
resources:
- url: /local/mini-media-player.js?v=0.8.3
type: module
views:
- title: Home
id: Home
cards:
# The filter card will filter entities for their state
- type: picture-glance
image: /local/schlafzimmer.png
title: Schlafzimmer
entities:
- light.schlafzimmerlampe
- light.bettlampen
- light.schlafband
- sensor.temp_schlafzimmer
- binary_sensor.bewegung_schlafzimmer
- binary_sensor.fenster_schlafzimmer
- sensor.helligkeit_schlafzimmer
- type: vertical-stack
cards:
- type: picture-entity
image: /local/wohnzimmer.png
entity: light.sofa
- type: glance
entities:
- light.sofa
- light.wohnzimmerlampe
- sensor.temp_wohnzimmer
- title: Test
id: Test
cards:
- type: custom:mini-media-player
entity: media_player.wohnzimmer
icon: 'mdi:cast'
artwork_border: true
power_color: true
show_source: true
Iâve searched the hole thread but didnât find any solution. Maybe somebody here, has an idea where my failure is.
thx
Hey!
Error indicates that there is a < (<) token in the mini media-player.js file at row 9.
This seems strange, that shouldnât be there.
I would suggest checking your mini-media-player.js file to make sure everything is fine there, compare it with this.
Found it. Thx 
I have only seen it a few times⊠not all the time and yes the card is working fine. I am only importing it once. Resources:
title: Home
resources:
- url: /local/tracker-card.js?v=0.1.5
type: js
- url: /local/custom-lovelace/upcoming-media-card/upcoming-media-card.js?v=0.1.9
type: js
- url: /local/custom_ui/dark-sky-weather-card.js?v=1
type: js
- url: /local/mini-media-player.js?ver=0.8.3
type: module
- url: /local/column-card.js?ver=7221e1
type: js
views:
Alright, that looks fine. But yeah, might be a caching issue after updates.
Loving this card, however Iâm also getting the âmini-media-playerâ doesnât exist error.
The annoying thing is that it is happening on my FireHD tablet, running fully kiosk browser. The mini media player card works ok in Chrome on Desktop. Iâve set the type: module correctly.
I installed Fully Kiosk on my Google Pixel 2XL just to test and the card works fine.
But I suspect the web engine might be different on your Fire tablet and might not support some ES5/ES6 features that are used in this card.
Make sure you have javascript_version: latest in your configuration.yaml under frontend:.