Atticus Maximus

I could not reproduce it in a web browser (Chrome). I could, however, reproduce it with the Android HomeAssitant App, but after I turned on debugging for this component and...

Most probably the fully kiosk browser has a not fully compatible implementation of the onClick event or the addEventListener method. At click - through the added onClick listener - the...

Didn't you click by mistake on the card that disappeared (and reappeared after the due date)? The hide_on_click configuration parameter is true by default since it was added [1] [1]...

The card will reappear after the due day or, if hide_before is used, hide_before days before the upcoming due date.

@Rayeliint this card written some 2 years ago displays information in a table whose layout setting is not really flexible [1]. It would require quite some effort to rewrite it...

You may use custom button-card [1] to build an inline-type button-card. It provides a great flexibility (that's why I'm not creating custom cards for my newer integrations). See an example...

You'll have to consult your configuration to see if your Lovelace runs in yaml or storage mode. The card's description refers to yaml mode. In storage mode you'll have to...

The right format for icon shoud be: `icon: mdi:trash-can` and it should be defined at the sensor definition not the card.

@rbovenkampclearict I'm not familiar with UI mode, but generally speaking you'll have to add this card as a resource in a similar way you're doing for other custom card.

Have you added the card via HACS? Do you see the related directory on file system level under $[HASS_CONF}/www/community?