Features in mushroom ? or Mushroom-features ?

[BBE-FR]

I first wanted to start by a huge thanks to @piitaya for the work done first in Mushroom, and later on on the core frontend.

Thanks to the evolution of the frontend, I try to convert as many mushroom card to Tiles, and I was tempted to change totally from Mushroom to Tiles, but I am lacking the functionalities of the Mushroom template card.

To achieve this, I tried setting the "template" part into the entity with helpers. But it is adding to much complexity to my view. And I prefer to push the template when needed to the display only (I tried both, and the mushroom approach is to my opinion the best one), not even talking about the customisable badge that is a versatile option to add supplemental information.

But if I have well understand, the introduction of Jinja2 template into core card is not planned.
And we will long be missing a template Tile... Thus I might be staying with mushroom template cards for the template capability.

On the other hand, I finally get quite used to the feature of the Tile card. And I thought it could be a nice addition, replacing the need to add specific buttons to many mushroom cards.
#55
#1422
#1286

When features are available in a card, they can be customized with this nice project: https://github.com/Nerwyn/custom-card-features
Again, I am not sure this level of customization will make it to the core. For example the new area card could fit here, but really lacks customisation...

In mushroom world, it could be a nice addition. I was hoping since a long time to have a way to incorporate mushroom tile into the template card, but feature may be a more pragmatic way to introduce control into cards. Maybe easier to maintain on the long term.
This could be a pragmatic way to have an really customisable card with controls like my dream room card: home-assistant/frontend#19930

I know this subject is slightly overlapping the mushroom card, but I wanted to open the discussion...

[piitaya]

FYI, I'm currently working on that 😄

[BBE-FR]

That is a very good news !

I am enthusiast on the way the frontend evolves, but really lacking the capabilities of the mushroom template card.
In the same manner, the refurbishing of the area card is very interresting, but a card with the same look, and customisable in the same manner as the mushroom template card would be a killer !

[BBE-FR]

If you manage to define a way to create buttons or features as simple as it is to define mushroom chips (including conditional chips and template chips) that would be marvelous.

I think that we miss the right complexity level for buttons:

• the area card proposed controls are very simple to setup but no real customisation is possible (limited to toggle covers, light and switches, and you can only choose display it or not, you cannot change or select the targeted entities).
• Tile features are simple to setup, but no deep customization is really possible and moreover they are limited to the entity of the Tile and cannot target other entities.
• custom-card-features are very complete but not intuitive nor straightforward to setup

The chips are to my opinion the perfect amount of customisation, with entity based chips for an easy display setup and template chips for a complete control of the display, while being able to adjust the tap, hold, double tap actions to your exact need (toggle, navigate, launch action, more info...). The function of the conditional chips could be replaced by a visibility panel to be consistent with core frontend evolution.
That would be the exact complexity to customisation ratio that I am searching, to target people (like me) that do not want to go full yaml and offer to beginner a way to customise a little bit more their dashboards.

[piitaya]

Yeah I'm also planning to release some generic features with the template support. Custom card feature is great but too complex sometimes for simple use cases (colored switches and sliders) because you have to deal with CSS.

[BBE-FR]

This is another great news !!

And an occasion to get rid of stack-in-card and card mod...

[BBE-FR]

A first implementation is available in V5.0

😍

With the selection of an Area, it gives a way to select the area feature or the associated entity feature, that is an interresting first step!

It also unlock the capcity to use custom-card-features for a full control of the feature if needed.

But I found cutom-card-features a litle bit too complex and clumsy for a simple need and I prefer the chips philosophy and simplicity...

Thus...

... I would be very interested into a possibility to continue this evolution and have some day in mushroom a way to select easily a row of button with the same level of complexity as the mushroom chips.

This could be done with two levels of possible customization:

- a first level of buttons close to the entity chips, the tile or the heading-card entities:
You could add buttons in the same way you add entities to the heading card. This would add buttons like in the area card, based on the selected entities, with the same level of customisation and same interface as as for a Tile card :

• chosen entity would pilot the default appearance and actions of this button (same look and behavior as the tile card icon/color/tap action)
• customise the content (icon and color, maybe icon could be replaced by a text there if not too complex)
• adjust the visibility (optional, but could allow to create conditional buttons depending on scenarios)
• adjust the action (toggle the selected entity, display the more info of the entity, navigate, launch an action...) (with optional hold and double tap action in yaml as for the Tile card)
  This kind of button row would be consistent with area card and heading card in term of behaviour, interface and look and could solve 90 to 99% of the need for custom cards...

- an advanced level of templatable buttons close to the template chips:
You could add template-button in the same way you add entities to the heading card. This would add buttons like in the area card, based on the selected entities, with the same level of customisation as for the template card :

• chosen entity would serve as a shortcut for templates
• icon, icon color (or text) would be driven by Jinja2 template
• adjust the visibility
• adjust the actions

---

Moreover, I see two way to implement this:

• a simple one that could be to offer the possibility to select this kind of feature in mushroom cards (like in the mushroom template card).
• a more powerful one which could be a custom mushroom-feature with the same kind of behavior than custom-card-feature, where any card supporting feature could select this "mushroom-feature" as described above. This would make the frontier between mushroom and tile even thinner because you could use "mushroom-feature" in a tile if you only want to customise the features.

[piitaya]

I have in plan to provide similar features than custom-card-features but way easier (very similar of what you propose) 🙂

[BBE-FR]

Very great news !

I tried in my proposal to stay close to the mushroom functionality, and even to the core card behavior (Tiles / heading cards) to have the maximum commonality (and possibly maximum re-use of existing code and interfaces).

I am looking forward for these evolution which will probably be the basis of my dashboard and the end of card_mod and stack_in_cards for me !!

Thank you very mush for all your contributions, both in mushroom and in core dashboard. I am really thankfull for your pragmatic approach of this deep level of customisation, while keeping simple UI based ergonomics!

[BBE-FR]

I have in plan to provide similar features than custom-card-features but way easier (very similar of what you propose) 🙂

Did you progress on this promising idea ?