Both sun entities are included in the fold. One is included via the auto-entities and one is just a plain old entity add. I seem to be getting padding on the left for any auto-entities.
I would expect with this example, both suns to be lined up since they are both part of the same fold with the same padding defined. Is this a bug? or operator error?
EDIT: Actually I see WHY. auto-entities is a card, not a row so its in the wrong place.
Thanks but yes I tried that as well. The issue here is I am trying to combine a nested fold and then single entities. In the example the two suns really would be different entities.
This is the structure:
-> Fold 1 (correct padding)
--> Fold 2 (correct padding)
\auto-entities\ (incorrect padding-left since this is a card and not a row)
--> entity1 (correct padding)
--> entity2 (correct padding)
--> entity3 (correct padding)
No matter how i attempt to structure the above, the left padding spacing is off for the Fold 2 since its a card and not a row. The card doesnāt honor the padding:0 and if auto-entities isnāt wrapped within a fold, it isnāt padded naturally.
THis is better picture of what is happening. The motion sensors are indented as if they are under the fold but they are not. The are a seperate set of entities (unfortunately contained in a dynamic card because of auto-entities. The spacing to the left of those motion entities is what should be pushed left to the same level as the ātimersā fold.
Youāre missing the outer fold. If a card (auto-entities here) is contained in the fold itāll push left as you can see in my code. I have it fixed now though with card-mod.
Because the top-level fold-entity-row in your card is containing auto-entities - but you were advised to change it.
Of course, if fold-entity-row contains āentities cardā you will have horizontal paddings, then card-mod is the only way.
Actually, in your position, with so many rows & many folded lists, I would choose a āfold-entity-row contains an auto-entiiesā schema with card-mod (+scrollbars) too.
It is possible, but with a help of vertical stack w/o margins.
Just place auto-generated 2-levels lists in a stack.
Here is an example of a list of groups:
vertical-stack will give the same issue. The vertical stack canāt be placed under the fold-entity-row without something like custom:hui-element (if this is done, you have the same issue). If the vertical stack is placed at the top most level, you still need to nest the fold/auto-entities just the way I have them.
The end result should look like I have it now in the screenshot above. Do you have an example using vertical stack that produces that result?
type: some-stack-card
cards:
- auto-entities inside fold-entity-row (each element may be also auto-entites inside fold-entity-row)
- auto-entities like above
- etc
Not exactly. Each card will be auto-entities - see my example above which does not have horizontal padding.
I already gave you an example. And already explained:
Repeat: there are TWO options:
use Entities card with fold-entity-rows containing auto-entities + card-mod with negative margins;
use stack with fold-entity-rows containing auto-entities + card-mod to remove spaces between stacks (or use ready stack-in-card).
It is up to you which way to choose. Sometimes the 2nd 1st way is better since CURRENTLY there are some problems with styling fold-entity-row inside auto-entities (if needed) if using 1st 2nd way; and these problems may be solved when using 2nd 1st way; this also includes a possibility to add a scrollbar by card-mod.
Update - I meant the FIRST way in the para before
Buddy, As I said, they both have the same issue and both use card-mod to fix them. Marius solved this many posts back. Everything youāve suggested has the same issue and still requires card-mod. Iām only replying at this point so some other person doesnāt come along and try to use vertical-stack to fix this per your recommendation.
Which āsame issueā, buddy? The initial problem was about horizontal padding. The āstack methodā does not have this problem.
OK, itās up to you).
letās call the whole code in that example āmodule Xā; if needed - add static rows (i.e. not folded) inside auto-entities on a required level (either via āentitiesā option or via one more filter);
place as many āmodules Xā as you need in one stack-in-card.
As a result - you have LIST with a same horiz padding: each row is a folded list of auto-entiies, and each element may be either a folded list of auto-entities or some āstatic rowā.
If you need not-folded rows on the 1st level - add them as Entities card (and yes, here card-mod is needed to add/remove top/bottom margin or padding for the card, do not remember exactly).
Actually, using a āstackā concept in UI cay give you a lot of benefits - each card may be presented as a stack (for instance, some card = a few entity rows, some graph, a few entity rows, a logbook , ā¦). This may be achieved by placing each card in a stack.
Exactly. To get to my example, you still need card-mod and stacking doesnāt do anything to fix it. And obviously if I wanted a static list, I wouldnāt be using auto-entities in the first place.