OK Now I’m really confused… it’s working in edge! And also now in chrome!! It’s just a bastard having to clear out settings all the time… logs me out of a bunch of stuff. Anyway thanks!
Awesome, yeah I feel you, it’s annoying,
I’m not sure why the old code still is cached after updating sometimes. Changing the ?v=… part at the end of the resource url should eliminate loading the previous version from cache but it seems pretty hit or miss.
I still do not understand completely one thing:
in the custom updater now i see there is an update of the mini-media-player-bundle. Is it enough to update this component or i must update also mini-media-player.js from github?
Thanks, I’m not sure what you mean, what type of playlists would that be?
Do you have an example how you handle this now?
The bundle is the only thing you need, if you update the bundle from custom_updater or manually from GitHub doesn’t matter.
The bundle contains the source code for the card as well as some external libraries the card depends on. If you have any other files related to mini media player you can delete them.
Im thinking of changing spotify playlists. A dropdown like the source selection under the player would be awesome. Today i solve this with scripts toggled by buttons under the media player, like this:
I do not understand. if I replace the mini-media-player resource in the lovelace file with the last mini-media-player-bundle, the custom-card will no longer work.
If you are using SONOS then this can be achieved by adding your playlist to SONOS favorites. The SONOS favorites is the Source list in this Mini Media Player