This file is about my precentation, the principles I have selected to implement.

YAML-dashboard, Mushroom and Popup's:

I'm combining GUI and YAML-dashboard with include and re-use of cards with push-entitites to card. Also heavily using YAML-node anchors in both solutions and dashboards/card, so some guidance on that is added here:

Quick overview:

• Both GUI and YAML-dashboard
• Advanced YAML-dashboard-guide: Card include
• Advanced YAML-dashboard-guide: "entity inject"
• Mushroom/popup's;Card-in-card, templating
• Themes

---

By using YAML-dashboard it opens up a few more tools one can use:

• easier copy/share with others (because the card-yaml-file is actually automagically uploadable to GitHub)
• Can include one card in several views ( !include-functionality enabled in YAML-dashboards)
• Can use node-anchors easily for reuse of card-mod etc (also applicable for gui-mode??)
• Can re-use same card with mulitiple entities (see description below)

• my basics: Packages
• HA-integration: Lovelace

• Dashboard-folder
• lovelace.yaml
  • adding YAML-config in addition to GUI to my setup

---

• Including dashboard-files see to add cards/viwes wherever you want,, se example in "My implementation"
• No additional functionality required, using standard !include functionality

• YAML-dashboard enabled (see above)

• use "!include" to map/reuse views; mob_dashboard.yaml
• use "!include" to map/reuse cards; home_mob_view.yaml - adding multiple area-cards in one view

---

• Re-use dashboard-files, "entity-inject", see example heater_card.yaml which is used by several room-cards by calling heater_card with different entities

  • Important first -step

  • Lovelace_gen; 'passing arguments to included files' (or "entity-inject" as I call it ;)

    #thanksThomasLoven

• NB;

• my basics: Packages
• HACS; Lovelace_gen , Important first -step - "entity-inject"

• use card-variables like "{{ area_temp }}" to map/reuse files entities 'injected into card' at point of !include; heater_card.yaml

---

Trying to make one card pr "Solution", so there is one tab for status, one for config and one for histori see example on heater_card.yaml

• my basics: Packages
• HACS; Mushroom
• HACS; Browser_mod (v2)
• HACS; stack-in-card
• HACS; tabbed-card

• use "!include" to map/reuse files; mob_dashboard.yaml
• node_anchor to re-use code
• area-cards, one card pr area with colored chips for status of most important stuff. - Then drilldown with popups - status-card pr area, will gather small solutions and preferred status in those (And alert if not OK)
• tabbed card, one card pr "Solution"
• templating, change colours by entity state (see chips in area-cards)
• Popup, on most chips in room-cards,,
• (this requires BrowserMod2,, #thanksThomasLoven)

---

Currently still stuck on the UI-minimalist dark theme,, I've shared it so you can pick elements neeeded to get same view as my dashboard/card I believe it is only line-depth on ha-card that is actually required, but there are also color-definitions that are in use ,,, will need to dig deeper into themes/coulors when finished with actual dashboards ;)