Lovelace: Mini Media Player

[kalkih (Karl Kihlström)]

@jchasey

There is no tts component setup so not clear on how you would configure access with this player?

It’s not possible with this card. This cards does only support tts through the tts component.
You could however fork the source code and modify a few lines of code in the _handleTts function to make it work for your use case.

[Yoinkz]

WHat’s the difference between the mini-media-player and the one that is in the latest release (bundle)?

Should I change my old config to the new one using the new js file and resource?

[kalkih (Karl Kihlström)]

@Yoinkz

Should I change my old config to the new one using the new js file and resource?

Yes, I recommend you to change over to the bundle version. Here’s a quote from earlier regarding this.

@kalkih

I recommend everyone to go through the install instructions again. You don’t have to, BUT if you don’t, you’ll continue loading the external dependency.

Bundling the dependencies instead of loading them externally will both make the card load faster and available offline.

[Yoinkz]

@kalkih

Yes, I recommend you to change over to the bundle version. Here’s a quote from earlier regarding this.

kalkih:

I recommend everyone to go through the install instructions again. You don’t have to, BUT if you don’t, you’ll continue loading the external dependency.

Bundling the dependencies instead of loading them externally will both make the card load faster and available offline.

Thanks - sorry I didn’t catch that part during the reading

[kalkih (Karl Kihlström)]

@Yoinkz

Thanks - sorry I didn’t catch that part during the reading

No worries, just happy to help!

[RomRider]

Thanks @kalkih! Nice trick, I wouldn’t have thought about this! Will keep that in mind.
I managed to use the universal media player component to do what I want and it’s perfect now!

[Yoinkz]

For some reason when using: show_progress it doesn’t seem to display?
Am I the only one experiencing this?

[kalkih (Karl Kihlström)]

@Yoinkz

For some reason when using: show_progress it doesn’t seem to display?
Am I the only one experiencing this?

It’s not supported by all media players.
The players backend component need to expose the following attributes:

• media_duration
• media_position
• media_position_updated_at

You can check if the media player exposes these attributes in the dev panel while playing something on the media player.

[FrankLeith]

HA is still new to me. But I already love lovelace and Mini Media Player.
Is there a way to make media players always visible. Almost all of them disappear when I turn the device off.

[Yoinkz]

@kalkih

It’s not supported by all media players.
The players backend component need to expose the following attributes:

• media_duration
• media_position
• media_position_updated_at

I’m only using it on the spotify media player, which I thought would work.
I just noticed it on the pictures you had in your examples, so I assumed it work on that

[kalkih (Karl Kihlström)]

@FrankLeith

Is there a way to make media players always visible. Almost all of them disappear when I turn the device off.

Sounds strange, I don’t think it’s an issue related to this card though.
What type of media players are the ones that disappear?

@Yoinkz

I’m only using it on the spotify media player, which I thought would work.
I just noticed it on the pictures you had in your examples, so I assumed it work on that

Yeah, the Spotify component doesn’t report media progress unfortunately.
The example pictures are actually just mock-ups made in Sketch.

[hdaalder (Hermen)]

Hi Guys,

H E L P … getting the same error that a few others reported and I can’t figure out what I am doing wrong

In ui-lovelace.yaml:
resources:
- url: /local/mini-media-player-bundle.js?v=0.9.2
type: module

I have all the files in my config/www folder and also dowloaded the directory from GIThub in this folder

Cleared my cache, rebooted HA and my desktop computer, tried different browsers, operating systems.

Appreciate any help.

Thanks Hermen

[kalkih (Karl Kihlström)]

@hdaalder

Appreciate any help.

Looks like you are missing the mini-media-player-bundle.js file in the www folder.
You can grab it from here.

That’s the only file you need, you can delete all other files related to mini media player.

[hdaalder (Hermen)]

I’m sorry… thought that with ‘bundle’ you meant all the files in the zip-file. Thank you very much… up and running. Awesome development Kalkih!!

[kalkih (Karl Kihlström)]

Awesome, happy to help, thank you!

[kalkih (Karl Kihlström)]

New version v0.9.3

Including full artwork cover, responsive design improvements and new idle view option

Changelog

• Added: artwork: full-cover option to display the full artwork #31

• Added: idle_view option to render an alternate view while player state is idle

• Fixed: issue where power button color would not display correctly in idle view and power_color enabled

• Fixed: responsive design improvements #30

[klogg]

Ignore this (A browser restart seems to have cleared the problem)

[DavidFW1960 (David)]

@kalkih

Changelog

• Added: artwork: full-cover option to display the full artwork #31

full-cover isn’t working and it’s giving me lovelace errors in the log

Log Details (ERROR)
Tue Nov 20 2018 10:15:16 GMT+1100 (Australian Eastern Daylight Time)

https://domain.duckdns.org:xxxxx/lovelace/4:0:0 Uncaught 

Actually the error might be because 2 media players aren’t available but it’s not displaying the full cover whereas the regular card is showing it.

[sfnetwork]

Since the update, I keep getting those

http://192.168.1.9:8123/lovelace/0:0:0 Uncaught

[sparkydave (🇦🇺 Dave)]

yep, same error here whenever a lovelace tab which contains the mini-media-player opens / is refreshed