Add overflow: hidden to the list of styles.
2 Likes
Great gonna test this when I get back, if it works you are the man 
(you already are, but even more then). Thanks
1 Like
Could I ask you share the code for this (combining miniplayer with popup)?
Any ideas about this?
Could you give me a link to the card?
This is the card I’m having issues with. It’s only happening with this one.
I also had the same error, just under darksaky. Here is my code.
local/custom_ui/card-modder.js:44:23 Uncaught TypeError: this.card.style.setProperty is not a function
Has nothing to do with the mini-media-player, but rather the entity being used by the mini-media-player
card:
entity: media_player.office_roku
type: 'custom:roku-card'
volume_up:
service: switch.turn_on
service_data:
entity_id: switch.office_volume_up
volume_down:
service: switch.turn_on
service_data:
entity_id: switch.office_volume_down
volume_mute:
service: switch.turn_on
service_data:
entity_id: switch.office_volume_mute
power:
service: switch.turn_on
service_data:
entity_id: switch.office_power
entity:
- media_player.office_roku
title: Office Remote
type: 'custom:popup-card'
2 Likes
Thanks. I understand how popup card works now. I got it to work with the Roku card. Great usage of those two cards.
1 Like
That’s because I used a lot of custom cards and paulus didn’t want to confuse new to HA users. I am doing up a more “new user” friendly version of lovelace for demo page should be updated over the weekend. That is why you are seeing gaps in the demo page.
Worked like a charm, thanks a lot!
I’ve updated card-modder to work around the odd behavior of the darksky-weather-card thing…
Latest version is 70344a.
HI Jim ,
Would you care to show the conic you made for those buttons (they are buttons are they?) Lights, Devices, Climate, Scenes etc etc? You talk about Picture elements, but as this https://www.home-assistant.io/lovelace/picture-elements/ shows a completely different approach, Ive never even looked at that… Your screens make me rethink, and Id really like to get to know how you did that.
thanks!
They are probably just picture cards with tap_action set to navigate.
Back in the days that was the only way to do it…
1 Like
ofcourse, you can check my github page for my entire lovelace code but trust me, I am not a programmer or anything. I just stumbled upon Home Assistant and so I thought lets try if I can do this. I have no knowledge of how good, nice or clean code should look like and I’m pretty sure it can all be done much simpler. But this is what I came up with which works perfect for me.
edit: I mentioned the picture-elements card because I had trouble making a rounded corner on those. The other ones are indeed just picture cards with a navigation path. But thanks to @thomasloven I know how to make rounded corners on those too.
auto-entities
Sometimes you may wish to add a lot of entities to a card, or perhaps just some, but which ones may change.
Like say you want to list all lights that are turned on, or all sensors whose battery is about to run out.
My first contact with custom lovelace cards was the monster-card by ciotlosm, which does exactly this. It does have some shortcomings, though, and that’s why I made a reimplementation of it which I chose to call
auto-entities
Differences from monster-card includes:
- support for actual regular expressions
- support for custom cards (it can be used to populate a fold-entity-row, for example)
- support for fetching entities from a group
- ability to parse advanced attribute specifications
6 Likes
Awesome!!!
Now there’s the need for a:
- type: custom:thomasloven_magic_monster_update_and_whatever_comes_next_card
1 Like
I’m going to give this a crack to see if I can use it to fix this problem:
