Marco
Marco
As shown in this post: https://community.home-assistant.io/t/lovelace-flexible-horseshoe-card-donut-graph-flexible-layout-multiple-entities-actions-animations-including-next-gen-experimental-examples/137850/47, template sensors using a value_template don't render.  Sensor is defined as: ```yaml esxi_vm0_datastore1_total_capacity: friendly_name: 'VM0 Used Disk Space - Datastore 1' value_template: "{{...
This issue only implements the background color, NOT the drop shadows on a per element basis. See #5 for the drop shadows. As requested here: https://community.home-assistant.io/t/lovelace-flexible-horseshoe-card-donut-graph-flexible-layout-multiple-entities-actions-animations-including-next-gen-experimental-examples/137850/52 The idea is this:...
Second part of #4 Add per item drop shadows. It should replace and/or complement the CSS filter which is applied to the full SVG. - Texts should be ok -...
## The Problem To Be Solved The user manual currently describes the tools and includes the 12 examples. The tools are described as a kind of reference manual. The 12...
## The Problem To Be Solved All of the current tools support 1 entity: the entity which its state is based upon. Simple and straightforward. No problems. However, in some...
## The Problem To Be Solved Currently, one needs a derived_entity and some javascript to convert the brightness to a 0..100% range. That can be done easier from a user...
## The Problem To Be Solved It would be nice if a state or something like that could be used to toggle different versions of the visualization. Take for instance...
## Bug report notice **Before** you file a bug, make sure that you did not make a configuration mistake. The Swiss Army Knife in its current state does not yet...
## The Problem To Be Solved All the tools that support user interaction respond directly to that user interaction. In most cases that is fine, but in some cases, a...
## The Problem To Be Solved There were two rendering paths for Icons: one for Safari (SVG) and one for Chrome (ForeignObject/SVG). Due to longstanding ForeignObject bugs in Safari, Safari...