Yes.
As I expected, the kodi component seem to expose “media_season” and “media_episode” even if it’s a movie playing and they shouldn’t (in my opinion) be there, it does even seem to expose “media_album_name” and “media_series_title”, although those are empty.
I guess I’ll have to add additional logic that checks media type and hide irrelevant attributes.
Please open an issue regarding this on GitHub, thanks.
What are those icon color changes you mention, and where are they coming from?
The icons color is based on the theme variable --paper-item-icon-color.
Sure, it does have the correct media content type exposed, but unlike other components I’m familiar with it also seem to expose “media_season” and “media_episode” even though it’s a movie playing, which in my opinion is wrong and is why you see “S-1 - E-1” it in the media information right now.
As mentioned above I might have to add additional logic to filter irrelevant attributes based on content type.
From what I’ve seen, people have used your Button-card to replicate what they previously had in custom-ui due to custom-ui not being compatible with Lovelace
Custom ui worked perfectly with lovelace (for me at least, changing badge colors, icon colors in all the cards I have) until hass 0.85. It still works for entity cards in hass 0.87. But not in mini media player.
So if not with custom ui, would it be possible to change the icon color depending on state, just like power_state?
@NicoS Are you still using this addon?
If you (or anyone else) are in fact still using it.
How do you send tts messages through it? Utilizing the notify service?
I would like to add tts support for it.
Yes, I’m using the Notify service. However I’m looking for other options atm as Google changed the broadcast to always add “Broadcast from xxxx” before every broadcast. This was not the case before.
notify:
- name: Google Assistant
platform: rest
resource: http://[xxx.x.x.xxx]:5000/broadcast_message
Thanks for the info,
Yes, that’s unfortunate.
I think I’ll add support for this anyway, however targeting a specific entity or specifying language won’t be compatible with it.
I am trying to setup mini media player on hassbian. This is my first custom component and I have created a www folder in my configuration folder in /home/homeassistant/.homeassistant. I have placed the resource line in my ui-lovelace.yaml file (url: /home/homeassistant/.homeassistant/www/mini-media-player-bundle.js?v=1.0.1) but home assistant is still saying custom component does not exist. I am not sure what I am doing wrong.
Yes I did. I am unable to access homeassistant on the web browser using .local and have to use the ip address of the pi. Does this affect the resource line that I need to place in the ui-lovelace.yaml file?
In the shortcut item objects the ID of a source must be the same as in /states ? Or what?
EDIT: I have also problems about artwork for echo devices… no artwork showed.
Here it is an extract of my config:
Again, check dev-state and make sure the data has been updated, sometimes it can take a while and some components are in my experience slower than others. The card just compute and render the entity attributes/state data so if this data isn’t “up to date” there’s nothing I can do.