Lovelace: Mini Media Player

Ok, I think I know what the issue is now.
Your TVs component is most likely sending the input icons as artwork, the card then detects that the media has artwork available and replaces the icon with the artwork provided by the TV component.

That’s also why the “Icon from the TV source” is displayed so big when the artwork option is set to cover.

is there an “artwork: nothanks” option?

Not right now but I should really implement an artwork: none option.
After some more thoughts I’m going to implement this in next version, hopefully tomorrow or monday.

1 Like

Just updated to v0.8.6
Setting artwork: none should now make the card never display artwork.

@kalkih I was trying to put your player in an entity-filter card to only show when playing/paused/on, but haven’t been able to figure it out. Is it do-able as things stand now?

After the last update there is an error.

my files:

  • url: /local/mini-media-player/mini-media-player.js?v=0.8.6
    type: module

      - type: entities
        title: TV 
        entities:
        - entity: media_player.living_room_tv
          type: "custom:mini-media-player"
          artwork_border: true
          power_color: true
          show_source: true
    

super nice card! and loads of options - thank you for your hard work. Just 1 issue since the latest update 0.8.6:

http://<IP>/local/lovelace/mini-media-player.js?v=0.8.6:110:43 Uncaught SyntaxError: Missing } in template expression

same for me, all my mini-media-player are having that error. I have them grouped

  - type: entities 
    title: Speaker piano primo 
    entities: 
    - entity: media_player.portable_speaker 
      type: "custom:mini-media-player" 
      artwork: cover
      show_source: true
      more_info: false
      hide_power: false
      show_progress: true
    #  group: true
    - entity: media_player.dining_room_speaker
      type: "custom:mini-media-player" 
      artwork: cover
      show_source: true
      more_info: false
      hide_power: false
      show_progress: true

Getting same error after update.

I’m really sorry guys, I messed up there, this should be resolved with v0.8.7

2 Likes

No worries. You’re investing so much of your own time for us, we’re not going to complain now are we? :slight_smile:

2 Likes

That should be possible to achieve, I just tried with the following yaml and it seems to work fine:

- type: entity-filter
  entities:
    - entity: media_player.spotify
      type: "custom:mini-media-player"
      group: true
    - entity: media_player.google_home
      type: "custom:mini-media-player"
      group: true
    - entity: media_player.avr_tv
      type: "custom:mini-media-player"
      group: true
  state_filter:
    - "playing"
    - "paused"
    - "on"
1 Like

After upgrading to 0.8.7 i get this in my lovelace:

55

And more after calling the custom_updater i have still the 0.8.6 while i checked and the .js is 0.8.7

09

Also if i do a check nothing change…

My config about it says:

  - url: /local/mini-media-player.js?ver=0.8.6
    type: module

Works wonderfully :muscle:

1 Like

Possible that something went wrong while updating. the config seems fine, although I wouldn’t recommend setting show_progress: null.

You could try restarting HA and then try to update from the custom updater card again.
If that doesn’t solve your issue, I would recommend completely removing the card and the reference and setting it up from the beginning again.

Ok solved, it was a cache problem…
But custom_updater still shows the previous release.

Great!
You could change your ui-lovelace.yaml reference manually this time, and hopefully it should work as expected next update.

- url: /local/mini-media-player.js?ver=0.8.6
  type: module

to:

- url: /local/mini-media-player.js?v=0.8.7
  type: module

Yes, i already changed it, but the same happened also with the previous versions… maybe a custom-updater issue?

Alright, try using ?v=0.8.7 instead of ?ver=0,8.7.
It could also be a file permission issue, if custom_updater doesn’t have permission to write to the file (ui-lovelace.yaml).

Yes, it worked…

1 Like