How to migrate from group views (best practice)?

Hello,

before version 0.107 my (view) setup looked like this:

I had defined several views in group.yaml like this one:

vwaschmaschine:
    name: Waschmaschine
    view: yes
    icon: mdi:washing-machine
    entities:
        - group.waschmaschine

waschmaschine:
    name: Waschmaschine
    view: no
    entities:
        - waschmaschine.status
        - waschmaschine.start
        - waschmaschine.end
        - waschmaschine.duration
        - sensor.waschmaschine_spannung
        - sensor.waschmaschine_strom
        - sensor.waschmaschine_leistung

No further configuration was needed and the view was added automatically to lovelace.

With version 0.107 group view was removed.

I tried to recreate my (view) setup:

group.waschmaschine seems not to be supported in the view configuration, so I tried adding each entity manually.

I am a bit stuck at the moment. Can someone point me to the right direction, what I should configure, that my views look like before 0.107?

What is the best practice way to migrate from group views? Thank you!

You didn’t have badges before, you had what is now an entities card.

Thanks for the hint. That works.

One further question: Previously with groups, I could use a group as “entitiy card” in the home view and also as a view itself (without further configuration).

On the home view I got a entity card with entitys from group.waschmaschine.
And I got a view Waschmaschine with the same entitys.

Am I right, that I cannot use groups anymore, and therefore have to define the same entity card twice, one for the Home view and one for the dedicated Waschmaschine view?
And If the “group” changes, I have to edit both entity cards (in home & waschmaschine view) in the future?

Or is there a way to reference one to the other, to avoid redundant configuration?

Correct

Only in YAML mode where you can use !include to include files.

1 Like

Thank you!