Custom Lovelace UI #2601
Replies: 53 comments 225 replies
-
|
This looks absolutely gorgeous - both functionally and esthetically ! |
Beta Was this translation helpful? Give feedback.
-
|
Add me as well please :) |
Beta Was this translation helpful? Give feedback.
-
|
Wow, that looks really great!! |
Beta Was this translation helpful? Give feedback.
-
|
I would be interested in seeing the YAML. I am specifically looking for a way to integrate the Search function of MA into my Lovelace Dashboard but am having trouble. Looks like you figured it out. |
Beta Was this translation helpful? Give feedback.
-
|
As far as interest goes you have my Bow AND my Sword |
Beta Was this translation helpful? Give feedback.
-
|
Yes Please 🤩 i’d love seing this into the dashboard |
Beta Was this translation helpful? Give feedback.
-
|
I would also love the YAML for this. |
Beta Was this translation helpful? Give feedback.
-
|
Chiming in to add that I'd greatly appreciate the YAML code for this. Awesome work! btw, @rxritalin, the link in your OP points to https://github.com/orgs/music-assistant/discussions/url instead of to https://github.com/orgs/music-assistant/discussions/2586. You should also just be able to tag the discussion directly via #2586 |
Beta Was this translation helpful? Give feedback.
-
|
I would love to see the YAML for this. I'm currently redoing my dashboards using ui-lovelace-minimalist, so now would be a perfect time to integrate a nice dashboard for mass instead of using the sonos card I am using for my kid's rooms. Installed mass yesterday and it finally finished syncing my PLEX server this afternoon (lots of tracks with quite a few more CDs to finish ripping). |
Beta Was this translation helpful? Give feedback.
-
|
@thewolfman56 @Paul-Vdp @wambs @chriss10an Im about 95% done, just have a few layout quirks I need to deal with. |
Beta Was this translation helpful? Give feedback.
-
|
Hey @Austin1 So the answer would be http://my.local.ha.ip:8095 or for my case http://192.168.86.6:8095 I love having this option as it gives a REALLLY easy way to have a jukebox interface for guests at my house. |
Beta Was this translation helpful? Give feedback.
-
|
Is this in some different branch? I am on the latest branch and i dont see the option to Expose Webserver. Also, am very excited to see your yaml for this. Would love an update on that! TIA! |
Beta Was this translation helpful? Give feedback.
-
|
Are using the addon or docker? |
Beta Was this translation helpful? Give feedback.
-
|
docker. That might explain it. |
Beta Was this translation helpful? Give feedback.
-
|
Yes it will already be enabled |
Beta Was this translation helpful? Give feedback.
-
|
I would also love to see the code behind this. Thanks so much for all your efforts! |
Beta Was this translation helpful? Give feedback.
-
|
Gorgeous! |
Beta Was this translation helpful? Give feedback.
-
|
Yup, like everyone else, I want/need this in my house. UI is where everything get a bit down I would say and this bring the professional uix touch. I wouldn't mind seeing the rest of your dashboard :) |
Beta Was this translation helpful? Give feedback.
-
|
@rxritalin any updates? Would love to get this implemented! Great work! |
Beta Was this translation helpful? Give feedback.
-
|
@rxritalin , I would echo the comments here. Gorgeous! I'd also be very interested in the underlying YAML if you would consider sharing. Thank you in advance! |
Beta Was this translation helpful? Give feedback.
-
|
Beautiful work. Would love to see the YAML / Help with the project. |
Beta Was this translation helpful? Give feedback.
-
|
I am going to take a look into the Decluttering Card module over Christmas break. If anyone has any other suggestions, for adding variables please let me know. @OzGav Does the Floorplan card have some of this built in? Having a look over your files, its seems to? |
Beta Was this translation helpful? Give feedback.
-
|
I figured it out. It was a card thing. I chose Panel and pasted the code from picture elements and down, and didn't include the kiosk part of the code. So it wasn't fitting right. Now I changed the card from Panel to horizontal layout card and it is the way it was intended. See before and after attached. Before: After: |
Beta Was this translation helpful? Give feedback.
-
@OzGav Here is an example of what I am talking about. Lets say the code relies on several helpers that need to be created. This would also be useful for repeating bits of code, where you can create a var at the top that equals a line of code like the one you provided me above. Now in each instance where that bit of code needs to be entered all you need to type is the var name instead. For me I am use to the way things work in WYSIWYG widget editors like Zooper and KLWP. Where these types of things are built into the framework of how the apps operate, because your themes are meant to be exported and easily packaged as APKs that can be downloaded from the Playstore by users to instantly apply your theme without any or much work on their behalf. I also worked in IT for a long period of my life, and know that now matter how good the direction you provide are, some one will fail to understand or overlook something. So KISS has always been a moto I live by if I am sharing my work. Which is why I was hesitant to release my UI in its current form. This is why I was stating I plan on looking into the Declutter Card https://github.com/custom-cards/decluttering-card as it seems it has the ability to do this. I was asking if you know of another way, maybe one that's cleaner, or one that does not require the user to install yet another thing from HACS. |
Beta Was this translation helpful? Give feedback.
-
|
Ok understand. Not aware of a solution for this. I guess this is why I used a package file so it could be dropped in without modification (except for the one input_select at the top). The other thing which I need which will be hopefully fixed in the future is identifying the player provider, currently I rely on renaming the entities with a unique suffix. |
Beta Was this translation helpful? Give feedback.
-
@OzGav Sorry this is going to be a long one... MASS in all honesty is still small, and while HA seems to have adopted it as the official HA music extension, I dont believe its fully caught on with all of the community as of yet. But, as it grows having an official, yet separate, repo / knowledge base for designing cards in Lovelace and sharing full layouts seems like it would be smart idea. Gumming up the MASS wiki and repo discussion area with theming discussions again seems like it could be problematic. Also, having a repo meant for UI designers specifically would give MASS a good roadmap for future development with regard to customization in purpose built MASS Lovelace cards, attributes and what data is exposed for scraping from the local MASS server. I was thinking something like having a Github where the main project pages is a list of submitted themes with screen shots and importantly, and outline of best practices for new designers. Having worked directly for companies that utilize community driven designs and code in the past (see Zooper/Themer/KLWP), its a rare bird to come across a one that can do both design and code. This leads to lots of great looking designs, but with wacky or broken code, ridged layouts that do not scale well, and the heavy use of bitmaps that can not be scaled at all. Admittedly my theme is in this state right now. Think about things like your requirement of a specific suffix at the end of the entity id for the correct players to be included. This is a perfect "best practices" example. That way designers don't end up re-inventing the wheel with every theme, which does nothing but confuse end users. Not to mention as more designers user the "best practices", end users can more easily identify specific segments, if the syntax of the code is uniform from design too design. That way when they inevitably tinker with the layout to make it to their liking, its easier to spot repeating patterns. Design tinkering often leads to new designers, at least in my experience. Other things like a list of commonly needed/used HACS would be beneficial. The themes themselves would of course be housed in the submitters own repo, where issues with said theme are managed by them. The main repo would simply link to these designs. So think of the main repo like a community landing page for MASS theme designers. There could of course be a discussion section in the main repo regarding each theme, for community help. As for the wiki, users could submit suggestions and code snippets which would then be analyzed, categorized and added to the wiki. If the design community does grow, the readme.md could be scrapped and added to the Music Assistant web page for better user exposure. Something like this could be linked on that main page. https://home-assistant-cards.bessarabov.com/
|
Beta Was this translation helpful? Give feedback.
-
|
I work on the project in various areas but not as one of the significant contributing devs. The team is small for the project size and user base so we are happy with all contributions. Your idea to have a separate place for HA resources sounds good. So if you would like to run with that we are happy to provide answers to any MA questions you may have. I also help out with ha-floorplan so can answer most questions about that as well. |
Beta Was this translation helpful? Give feedback.
-
|
@rxritalin It just occurred to me, what version of Home Assistant are you using? I'm running 2024.12.3 Core, 2024.11.4 Supervisor, and 13 HAOS. I'm wondering what impact this could be having on us. Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
@XarusLonestar I think exactly the same. Yesterday I was testing and in Hassos the code for kiosk didn't work (and it's the official documentation code!) However, in the same documentation there is a video of a YouTube user and... jackpot! I only had to adapt it a little. I'm sure that slide and hie elements, in HASSOS new updates, must be "declared" in a different way than it was done in the code. Core : 2024.12.3 **Could you do me a favor? Could you test the latest code for the 'simple' card from GitHub to ensure that it works for you (since you've managed to get it working) |
Beta Was this translation helpful? Give feedback.
-
|
@jbega Yeah the player is functional and all. I can quickly copy and paste the code from the repository and do find/replace on the media player and URLs but my issues remain with the input_selectd menu list not going back to CoverArt when input_boolean menu is off. |
Beta Was this translation helpful? Give feedback.
-
|
just want to thank you for this. It was easy for me to setup because i already had all the cards. as for the coverart not re-displaying i just added a new menu option for now. also noted you have CoverArt in the yaml and Coverart in the input_select
|
Beta Was this translation helpful? Give feedback.
-
|
Had a little breakthrough for me in regards to the Cover Art! All I did was simply create an automation to switch the Input_Select to Cover Art when the Menu is set to off. In case there are any future code updates by @rxritalin I think I'll keep the automation separate from the dashboard code but I'm happy to have realized a simple fix! Now onto tweaking the rest! alias: RX Stereo Set Cover Art
updated12-16.mp4 |
Beta Was this translation helpful? Give feedback.
-
EDIT: On second thought, it might be related to this issue as well. Make sure you create a new automation with the code provided and change the device ID to your media_player. https://github.com/orgs/music-assistant/discussions/2601#discussioncomment-11609376 I have this issue as well, if I am not using the Bubble Theme (comes with bubble cards) as the main theme across Home Assistant, and the "Custom Mushroom" theme I provided as the individual theme for media UI's Dashboard View. As I have stated, this was release in a not ready for public consumption manner. IE lots of little bits that work fine with my setup, but maybe not yours. I will be working on the Theme file itself over christmas break to determine all the portions of the Bubble theme that need to be copied over, at which point I will update the the github repo. I will likely change the name of the theme, to something more in line with the project at that point as well. |
Beta Was this translation helpful? Give feedback.
-
@XarusLonestar Yeah this edit makes sense, I built it the way I did to work with that funky screen I have which acts as an interface for an antique stereo console in my livingroom that I resto-modded. That background image determines the size of the entire card, as its the first layer in the layout-card. I also need to get a better grasp on how HLML/CSS pixel formatting work. |
Beta Was this translation helpful? Give feedback.
-
|
Hey @jbega
This makes sense, I needed to do this due to my hardware setup. This UI runs on a little mini PC connected to a touch screen on my stereo console. The PC is connected to a Yamaha Amp in the console through its DAC. The PC is setup as a Squeezebox player through the MASS companion app. There is an odd situation that can happen for this setup, if any of those two devices lose power for a moment. Basically windows will drop the DAC connection and default to another audio output (even if I have all others disabled... fucking windows), this causes the MASS companion app to lose its connection to the audio device it thinks should be there, and its response is the kill the Squeezebox player. This is yet another thing I have to work on, but its outside of the UI's scope obviously.
This is not the case for me. So long as I have something in the queue for the MASS player I am using it will show the album art. If I restart HA or MASS for that matter, then you are correct the art will not show. My plan (not completed yet) is to have another bitmap display if the player has nothing in the queue. Something like a generic image with a music note or something.
I see the problem here. Yet another automation that I forgot to include. I have updated the repo. This is a dirty way to handle this though. The main problem being it completely blocks the ability make this a multi-device card in the future. What I need to do is set the power off button to trigger not just the media_players power state, but also turn off the menu/volume helpers. This would fix the issue with making them vanish. I'll get to this over christmas break, but the automation is there for anyone else right now. |
Beta Was this translation helpful? Give feedback.
-
|
@rxritalin This afternoon I was just finishing up the necessary automations (like the example you mentioned of an empty or full queue list that should display different cards; I've solved this using the 'duration' attribute up to 0) and I also have a Yamaha amplifier that handles all the playback. For now, everything seems to be flowing as it should. |
Beta Was this translation helpful? Give feedback.
-
The issue arises when the input_select.rx_stereo_menu_list is set to "coverart" and there's no information to display (turns on without a playback queue/when playing the playback queue.) This could be resolved with these automations: 1- WakeUpFlow -> https://pastebin.com/ri7eDNNF 2- QuequeFinishFlow -> https://pastebin.com/8B0SnP2j *create options "off" and "home" in input_select.rx_stereo_menu_list WHEN -> entity changes from playing to idle (playback queue ends)
3 - VolumeCollapseFlow -> https://pastebin.com/kZRp5drx
I tweaked it a bit to make things run smoother 4- CollapseMenuFlow -> https://pastebin.com/Nynn6xdY When you turn off the player with the volume/menu open, they remain open and the select menu list stays in its last state. 5- ShutDownFlow -> https://pastebin.com/uC4Vks6z |
Beta Was this translation helpful? Give feedback.
-
|
Any plans for a mobile friendly version? I use custom Sonos card which is nice too
…On Dec 16, 2024, 5:13 PM, at 5:13 PM, rxritalin ***@***.***> wrote:
> yes i was thinking that too, but i still want to have menu on and
coverart. im thinking about using a toggle approach where a subsequent
click on active section will bring up the coverart
The automation is required, but I totally forgot about it. I have
updated my repo.
Since the whole UI is based on the Picture Elements card, everything
acts as a layer. So my plan was to have a small button that would be
visible over the top of the iFrame cards, but only if the menu was
open. This button would show/hide the cover-art with the menu still
open.
Likewise the button would be visible over the cover-art, but only if
the "input_select.rx_stereo_menu" was on.
--
Reply to this email directly or view it on GitHub:
#2601 (reply in thread)
You are receiving this because you commented.
Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
@Vansmak Of this layout, Im not sure? After I overhaul it's layout method to automatically adjust to different horizontal aspect ratio's, I could look at seeing how hard it would be to add a portrait mode. But the most likely case is that it would need a secondary card specific to it. I dont mind working in portrait, thats the design work I use to do in Zooper/Themer/KLWP, but because I know from experience that means a ton of different resolutions, DPI's, and slight changes to aspect ratio's across all the mobile devices available. So to answer your question, yes... maybe, LOL. If it happens it will be a little while. I am kind of using this as a crash course in learning CSS, and figuring out the best way to share complex Lovelace cards with minimal effort from the end user for install. The HA environment is NOT setup for this at present. Once I get my head around all this I want to start building out other cards, some of which are more Portrait layout friendly, as noted here in this post https://github.com/orgs/music-assistant/discussions/2601#discussioncomment-11569269 |
Beta Was this translation helpful? Give feedback.
-
|
No not necessarily same layout just a version. I created my own and I'm happy. As long as I've been creating ha dashboards I can't believe I never that of use mass web server via iframe. Kinda no duh moment for me. |
Beta Was this translation helpful? Give feedback.
-
|
I'm not sure if this would interest anyone here but in case it does, I managed to figure out how to show the last playing song including artwork in the player also. Here's how I got it to work:
Then I created automations to make it all work. Here is the sensors I created in my config file: And here is the yaml for the automations: Then using the sensor data, you would enter that into your media card - which ever one you use. Here's my yaml portions I used for my media card:
|
Beta Was this translation helpful? Give feedback.
-
@ColtonYYZ Nice work man! I was about to reply to @Vansmak with the same thing. I dont think this is currently possible especially with using MASS as the player source. I have suggested a few changes for them including some specific MASS cards for Lovelace and addtional attributes that would come in really handy for designing these layouts. Have a look here and add to the list if you think of anything. I also want to talk with MASS about creating a separate child/daughter repo with its own Wiki, for exactly this kind of thing. Lovelace layouts, Lovelace cards, Lovelace code snippets to accomplish specific tasks, etc. MASS in all honesty is still small, and while HA seems to have adopted it as the official HA music extension, Its not fully caught on yet. |
Beta Was this translation helpful? Give feedback.
-
|
Nice work. Next song would be more useful
…On Dec 20, 2024, 12:46 PM, at 12:46 PM, Colton YYZ ***@***.***> wrote:
I'm not sure if this would interest anyone here but in case it does, I
managed to figure out how to show the last playing song including
artwork in the player also. Here's how I got it to work:
- I created sensors to read the current song, current artist, and
current artwork.
- I then created text input helpers for each of them.
- I then created text input helpers for "previous artitst", "previous
song", and "previous artwork"
- I created text input helpers called "previous artist storage",
"previous song storage" and "previous artwork storage".
Then I created automations to make it all work. Here is the sensors I
created in my config file:
```
- platform: template
sensors:
active_media_player:
value_template: >
{% for entity_id in state_attr('group.all_media_players', 'entity_id')
%}
{% if states(entity_id) == 'playing' %}
{{ entity_id }}
{% endif %}
{% endfor %}
attribute_templates:
media_title: >
{% for entity_id in state_attr('group.all_media_players', 'entity_id')
%}
{% if states(entity_id) == 'playing' %}
{{ state_attr(entity_id, 'media_title') }}
{% endif %}
{% endfor %}
media_artist: >
{% for entity_id in state_attr('group.all_media_players', 'entity_id')
%}
{% if states(entity_id) == 'playing' %}
{{ state_attr(entity_id, 'media_artist') }}
{% endif %}
{% endfor %}
- platform: template
sensors:
current_title_playing:
friendly_name: "Current Song Playing"
value_template: >
{{ state_attr('sensor.active_media_player', 'media_title') }}
- platform: template
sensors:
current_artist_playing:
friendly_name: "Current Artist Playing"
value_template: >
{{ state_attr('sensor.active_media_player', 'media_artist') }}
- platform: template
sensors:
current_artwork_playing:
friendly_name: "Current Artwork Playing"
value_template: >
{{ state_attr('sensor.active_media_player', 'entity_picture') }}
- platform: template
sensors:
previous_artwork_played:
friendly_name: "Previous Artwork Played"
value_template: >
{{ states('input_text.previous_artwork') }}
```
And here is the yaml for the automations:
```
- id: '1734404937564'
alias: Update Previous Song
description: ''
triggers:
- trigger: state
entity_id:
- media_player.colton_s_echo_show
attribute: media_title
actions:
- data:
entity_id: input_text.previous_song
value: '{{ states(''input_text.previous_song_storage'') }}'
action: input_text.set_value
- data:
entity_id: input_text.previous_song_storage
value: '{{ states(''sensor.current_title_playing'') }}'
action: input_text.set_value
- id: '1734418970406'
alias: Update Previous Artist Playing
description: ''
triggers:
- trigger: state
entity_id:
- media_player.colton_s_echo_show
attribute: media_artist
conditions: []
actions:
- data:
entity_id: input_text.previous_artist
value: '{{ states(''input_text.previous_artist_storage'') }}'
action: input_text.set_value
- data:
entity_id: input_text.previous_artist_storage
value: '{{ states(''sensor.current_artist_playing'') }}'
action: input_text.set_value
mode: single
- id: '1734558768034'
alias: Update Previous Artwork Playing
description: ''
triggers:
- entity_id: media_player.colton_s_echo_show
attribute: entity_picture
trigger: state
conditions: []
actions:
- target:
entity_id: input_text.previous_artwork
data:
value: '{{ states(''input_text.previous_artwork_storage'') }}'
action: input_text.set_value
- target:
entity_id: input_text.previous_artwork_storage
data:
value: '{{ state_attr(''media_player.colton_s_echo_show'',
''entity_picture'')
}}'
action: input_text.set_value
mode: single
```
Then using the sensor data, you would enter that into your media card -
which ever one you use.
Here's my yaml portions I used for my media card:
```
- type: custom:config-template-card
entities:
- sensor.previous_artwork_played
card:
type: picture
image: ${states['sensor.previous_artwork_played'].state}
style:
top: 59%
height: 7%
width: 7%
left: 44%
card_mod:
style:
ha-card: |
div.mmp__bg {
border-radius: 24px;
}
########################################################
- type: custom:mushroom-template-card
primary: ""
secondary: >-
Previous Song - {{ states('input_text.previous_song_storage') }} by {{
states('input_text.previous_artist_storage') }}
icon: ""
entity: media_player.colton_s_echo_show
fill_container: true
layout: horizontal
tap_action:
action: none
hold_action:
action: none
double_tap_action:
action: none
card_mod:
style: |
:host {
{% if is_state("input_boolean.rx_stereo_menu", "off") %}
left: 70%;
width: 50%;
{% else %}
left: 65%;
width: 50%;
{% endif %}
}
ha-card {
--card-primary-font-size: 20px;
--card-secondary-font-size: 20px;
--card-primary-line-height: 24px;
--card-secondary-line-height: 24px;
--card-primary-color: #ffffffba;
--card-secondary-color: #ffffffba;
border: none !important;
box-shadow: none;
background: none !important;
font-family: "Arial Black", "Helvetica";
text-shadow:1px 1px 10px #3, 1px 1px 10px #3;
padding: 0px !important;
}
.content {
display: inline-block !important;
background: none !important;
padding: 10px;
}
style:
top: 74%
height: 32px
```
--
Reply to this email directly or view it on GitHub:
#2601 (comment)
You are receiving this because you commented.
Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Hey @Vansmak, I'm looking at your YAML, (thank you btw!) but did I miss a step? I created the sensor. I changed the media player entity in the automation but then when I try to select mass.get_queue, I get the folllowing error: Error in describing action: Cannot read properties of undefined (reading 'get_queue') |
Beta Was this translation helpful? Give feedback.
-
|
not sure, i did make it simpler so the automation runs the get queue action on the mass player, in my case office_3 and then gets the next_item and updates the input_text. i assume you created the input_text.next_track_info helper? This works but for some reason it is erratic, next_item starts reverting back to current item for some reason i do not understand. |
Beta Was this translation helpful? Give feedback.
-
|
Hey @Vansmak, whats ur setup? Sonos/Google/Other and which radio service are you pulling it from? SiriusXM/Spotify/Other? |
Beta Was this translation helpful? Give feedback.
-
|
Sonos and Spotify. For this setup I'm using Mass and my provider is Spotify and player is Sonos, but mass creates it's own player entity |
Beta Was this translation helpful? Give feedback.
-
|
@Vansmak, so I was able to get TONS of entities with Spotifyplus using this in Developer tools, Actions. See below. The queue is shown in the results. But how can I create a sensor extracting the next track? Here's a sample of what is shows in the results which shows track 2 (the next song to be played - track 1 is the current song playing - track 3 is the 2nd song coming up, etc. I listened to them and verified the sequence. The entity "track_number: X" is how you can quickly skip a ton of code and find the next track - X being the track number of course) The entities I would like to create sensors for are: Here's one complete section of code for 1 song (I removed the mile long list of countries to keep this short): |
Beta Was this translation helpful? Give feedback.
-
|
I have to admit this looks pretty dope on my large tv. This thread is hard to follow so I have a mash up of some of the ideas I've seen here. I'd like to credit the op with this background but I cant find the post. |
Beta Was this translation helpful? Give feedback.
-
|
Oh that's mine. I got the artwork on Adobe Stock and did some edits to it to make it fit with a MA dashboard we also did some work on. Glad you like it, I credit the OP of the MA card as he created the awesome menu and concept. I just added in this background. |
Beta Was this translation helpful? Give feedback.
-
|
Original artwork |
Beta Was this translation helpful? Give feedback.
-
|
Yeah they Spotify and Sonos I can do or get just about anything but I'm trying to use mass more. I really like the random 500 playlist because it doesn't use Spotify's bogus algorithm
…On Dec 23, 2024, 4:41 PM, at 4:41 PM, Colton YYZ ***@***.***> wrote:
@Vansmak, so I was able to get TONS of entities with Spotifyplus using
this in Developer tools, Actions. See below.
```
action: spotifyplus.get_player_queue_info
data:
entity_id: media_player.spotifyplus_colton
```
The queue is shown in the results. But **how can I create a sensor
extracting the next track?**
Here's a sample of what is shows in the results which shows track 2
(the next song to be played - track 1 is the current song playing -
track 3 is the 2nd song coming up, etc. I listened to them and verified
the sequence. The entity "track_number: X" is how you can quickly skip
a ton of code and find the next track - X being the track number of
course)
The entities I would like to create sensors for are:
```
image_url: (this is the artwork)
name: (this is song name)
artists:
name: Beyoncé
```
Here's one complete section of code for 1 song (I removed the mile long
list of countries to keep this short):
```
- album:
album_type: album
artists:
- external_urls:
spotify: https://open.spotify.com/artist/6vWDO969PvNqNYHIOW5v0m
href: https://api.spotify.com/v1/artists/6vWDO969PvNqNYHIOW5v0m
id: 6vWDO969PvNqNYHIOW5v0m
name: Beyoncé
type: artist
uri: spotify:artist:6vWDO969PvNqNYHIOW5v0m
available_markets:
copyrights: []
external_ids: {}
external_urls:
spotify: https://open.spotify.com/album/39P7VD7qlg3Z0ltq60eHp7
genres: []
href: https://api.spotify.com/v1/albums/39P7VD7qlg3Z0ltq60eHp7
id: 39P7VD7qlg3Z0ltq60eHp7
image_url:
https://i.scdn.co/image/ab67616d0000b273801c4d205accdba0a468a10b
images:
- url: https://i.scdn.co/image/ab67616d0000b273801c4d205accdba0a468a10b
height: 640
width: 640
- url: https://i.scdn.co/image/ab67616d00001e02801c4d205accdba0a468a10b
height: 300
width: 300
- url: https://i.scdn.co/image/ab67616d00004851801c4d205accdba0a468a10b
height: 64
width: 64
label: null
name: I AM...SASHA FIERCE
popularity: null
release_date: "2008-11-17"
release_date_precision: day
restrictions: {}
total_tracks: 11
type: album
uri: spotify:album:39P7VD7qlg3Z0ltq60eHp7
artists:
- external_urls:
spotify: https://open.spotify.com/artist/6vWDO969PvNqNYHIOW5v0m
href: https://api.spotify.com/v1/artists/6vWDO969PvNqNYHIOW5v0m
id: 6vWDO969PvNqNYHIOW5v0m
name: Beyoncé
type: artist
uri: spotify:artist:6vWDO969PvNqNYHIOW5v0m
available_markets:
disc_number: 1
duration_ms: 261640
explicit: false
external_ids:
ean: null
isrc: USSM10804556
upc: null
external_urls:
spotify: https://open.spotify.com/track/4JehYebiI9JE8sR8MisGVb
href: https://api.spotify.com/v1/tracks/4JehYebiI9JE8sR8MisGVb
id: 4JehYebiI9JE8sR8MisGVb
image_url:
https://i.scdn.co/image/ab67616d0000b273801c4d205accdba0a468a10b
is_local: false
is_playable: null
name: Halo
popularity: 71
preview_url: null
restrictions: {}
track_number: 2
type: track
uri: spotify:track:4JehYebiI9JE8sR8MisGVb
```
--
Reply to this email directly or view it on GitHub:
#2601 (reply in thread)
You are receiving this because you were mentioned.
Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
@Vansmak, As would I because it's only 1 portion of code verses creating code for all the streaming sites. I just don't know how MASS can pull the queue data regardless of the music source. For now though, would you know how to create the 3 sensors for Spotify? I would be grateful if you know how. And maybe someone else better at MASS could advise me how to do it at that level instead of individual provider levels. |
Beta Was this translation helpful? Give feedback.
-
|
I can play with it tomorrow |
Beta Was this translation helpful? Give feedback.
-
|
They are though, because it shows on the queue view within mass player section.
…On Dec 23, 2024, 5:44 PM, at 5:44 PM, Colton YYZ ***@***.***> wrote:
@Vansmak, As would I because it's only 1 portion of code verses
creating code for all the streaming sites. I just don't know how MASS
can pull the queue data regardless of the music source.
For now though, would you know how to create the 3 sensors for Spotify?
I would be grateful if you know how. And maybe someone else better at
MASS could advise me how to do it at that level instead of individual
provider levels.
--
Reply to this email directly or view it on GitHub:
#2601 (reply in thread)
You are receiving this because you were mentioned.
Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
But this is where I am struggling because I can't see them. :( |
Beta Was this translation helpful? Give feedback.
-
|
I'd be happy if I could just link to this view |
Beta Was this translation helpful? Give feedback.
-
|
That looks like those are local files. Or are they from streaming services? I don't see what you see. Plus I'm using a Desktop and you're using your cell so it is going to look different in that regard also. Feel free to message me on Discord if you can still help me. I don't want to spam this discussion. |
Beta Was this translation helpful? Give feedback.
-
|
Check this out hokiebrian/spotify_plus#1 (comment)
…On Dec 23, 2024, 4:41 PM, at 4:41 PM, Colton YYZ ***@***.***> wrote:
@Vansmak, so I was able to get TONS of entities with Spotifyplus using
this in Developer tools, Actions. See below.
```
action: spotifyplus.get_player_queue_info
data:
entity_id: media_player.spotifyplus_colton
```
The queue is shown in the results. But **how can I create a sensor
extracting the next track?**
Here's a sample of what is shows in the results which shows track 2
(the next song to be played - track 1 is the current song playing -
track 3 is the 2nd song coming up, etc. I listened to them and verified
the sequence. The entity "track_number: X" is how you can quickly skip
a ton of code and find the next track - X being the track number of
course)
The entities I would like to create sensors for are:
```
image_url: (this is the artwork)
name: (this is song name)
artists:
name: Beyoncé
```
Here's one complete section of code for 1 song (I removed the mile long
list of countries to keep this short):
```
- album:
album_type: album
artists:
- external_urls:
spotify: https://open.spotify.com/artist/6vWDO969PvNqNYHIOW5v0m
href: https://api.spotify.com/v1/artists/6vWDO969PvNqNYHIOW5v0m
id: 6vWDO969PvNqNYHIOW5v0m
name: Beyoncé
type: artist
uri: spotify:artist:6vWDO969PvNqNYHIOW5v0m
available_markets:
copyrights: []
external_ids: {}
external_urls:
spotify: https://open.spotify.com/album/39P7VD7qlg3Z0ltq60eHp7
genres: []
href: https://api.spotify.com/v1/albums/39P7VD7qlg3Z0ltq60eHp7
id: 39P7VD7qlg3Z0ltq60eHp7
image_url:
https://i.scdn.co/image/ab67616d0000b273801c4d205accdba0a468a10b
images:
- url: https://i.scdn.co/image/ab67616d0000b273801c4d205accdba0a468a10b
height: 640
width: 640
- url: https://i.scdn.co/image/ab67616d00001e02801c4d205accdba0a468a10b
height: 300
width: 300
- url: https://i.scdn.co/image/ab67616d00004851801c4d205accdba0a468a10b
height: 64
width: 64
label: null
name: I AM...SASHA FIERCE
popularity: null
release_date: "2008-11-17"
release_date_precision: day
restrictions: {}
total_tracks: 11
type: album
uri: spotify:album:39P7VD7qlg3Z0ltq60eHp7
artists:
- external_urls:
spotify: https://open.spotify.com/artist/6vWDO969PvNqNYHIOW5v0m
href: https://api.spotify.com/v1/artists/6vWDO969PvNqNYHIOW5v0m
id: 6vWDO969PvNqNYHIOW5v0m
name: Beyoncé
type: artist
uri: spotify:artist:6vWDO969PvNqNYHIOW5v0m
available_markets:
disc_number: 1
duration_ms: 261640
explicit: false
external_ids:
ean: null
isrc: USSM10804556
upc: null
external_urls:
spotify: https://open.spotify.com/track/4JehYebiI9JE8sR8MisGVb
href: https://api.spotify.com/v1/tracks/4JehYebiI9JE8sR8MisGVb
id: 4JehYebiI9JE8sR8MisGVb
image_url:
https://i.scdn.co/image/ab67616d0000b273801c4d205accdba0a468a10b
is_local: false
is_playable: null
name: Halo
popularity: 71
preview_url: null
restrictions: {}
track_number: 2
type: track
uri: spotify:track:4JehYebiI9JE8sR8MisGVb
```
--
Reply to this email directly or view it on GitHub:
#2601 (reply in thread)
You are receiving this because you were mentioned.
Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Thank you!!! I had the wrong spotifyplus installed. I didn't notice there are (2):
The second one is the one that you reference in your link - for others who didn't know this already! :( |
Beta Was this translation helpful? Give feedback.
-
|
Well that was a bust! Looks like Spotify changed access to some of their APIs... |
Beta Was this translation helpful? Give feedback.
-
|
HA 2025 RC release looks promising with this: home-assistant/core#133521 i think this will allow someone to actually make a native card/frontend feature for searching a MASS library. |
Beta Was this translation helpful? Give feedback.
-
|
Like Jake said, I'm just waiting for the core mass to add and fix things. After all this is a discussion about a frontend for mass.
…On Dec 25, 2024, 12:03 AM, at 12:03 AM, Colton YYZ ***@***.***> wrote:
Thank you!!! I had the wrong spotifyplus installed. I didn't notice
there are (2):
- https://github.com/thlucas1/homeassistantcomponent_spotifyplus
- https://github.com/hokiebrian/spotify_plus
The second one is the one that you reference in your link - for others
who didn't know this already! :(
--
Reply to this email directly or view it on GitHub:
#2601 (reply in thread)
You are receiving this because you were mentioned.
Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
grabacion-2025-01-08-182219_1Z2UvBcf.mp4It's just a little multiplayer prototype. |
Beta Was this translation helpful? Give feedback.
-
dddddddddd.mp4I've made further adjustments to trigger the select menu (blue speaker) when powering down a player while another is active. This visual cue helps users switch between active players. I'm also experimenting with highlighting active players in blue, but I haven't finalized the code yet. If no players are active, only the power logo is displayed. Upon activation, the system directly navigates to the selection screen. |
Beta Was this translation helpful? Give feedback.
-
20240709105204.mp4
A custom Lovelace UI I built using the picture-elements card as the base, with a bunch of different cards both built-in and from HACS. This was made for a 13" 1920x720 touch screen I have setup on my main stereo. The UI is obviously based around Volumio's new UI with a few changes to make it more touch friendly on my display and easier to see from a distance.
If there is interest I will share the yaml for it, though there is quite a bit you would need to setup and change in your home-assistant instance.
The part that has been driving me crazy is the iFrame cards used to look at Search, Playlists, Artists, etc. I can get rid of the scrollbars on my side of the iFrame, but since I can't card_mod into an iFrame page, I cant get rid of the scrollbars built into MASS UI. Please please please devs, add some CSS styling for your scroll bars to hide them, you are looking like WinXP over here.
The link below is to a feature request I opened with some ideas on how to create these types of layouts easier, with more customization, and more options.
(https://github.com/orgs/music-assistant/discussions/2586)
Beta Was this translation helpful? Give feedback.
All reactions