mirror of https://github.com/CCOSTAN/Home-AssistantConfig.git synced 2026-04-24 00:57:48 +00:00

Files

Carlo Costanzo 4457dc0bcd Refactor automation configurations and enhance documentation

- Updated guest_mode.yaml to clarify guest mode announcements and added a related issue reference.
- Enhanced night_watchdog.yaml with additional conditions for vacation mode and house sitter presence.
- Improved sunset_turn_on.yaml by refining action sequences and adding vacation presence logic.
- Expanded admin_sections.yaml to include new tiles for front door package detection and related inputs.
- Removed obsolete media player from media_players.yaml and updated switches.yaml to reflect new outdoor seasonal switch IDs.
- Enhanced home_modes.yaml and README.md to clarify home mode toggles and their usage.
- Updated docker_infrastructure.yaml to improve container outage notifications and streamline maintenance checks.
- Enhanced LLM Vision package to include front door package detection and related automation triggers.
closed https://github.com/CCOSTAN/Home-AssistantConfig/issues/793

2026-03-23 10:13:50 -04:00

infrastructure

Enhance Home Assistant configuration and dashboards

2026-03-12 18:13:49 -04:00

kiosk

Add YAML dashboards and enable Lovelace YAML mode

2026-02-09 13:45:43 -05:00

overview

Refactor automation configurations and enhance documentation

2026-03-23 10:13:50 -04:00

shared

Add YAML dashboards and enable Lovelace YAML mode

2026-02-09 13:45:43 -05:00

README.md

Dashboards: HA 2026.8 Lovelace wiring + validation

2026-02-09 13:45:46 -05:00

resources.yaml

Update Home Assistant version to 2026.3.2 and add new automation exclusion

2026-03-16 11:56:36 -04:00

SCRATCHPAD.md

Dashboards: HA 2026.8 Lovelace wiring + validation

2026-02-09 13:45:46 -05:00

README.md

Bear Stone Smart Home Documentation

Be sure to ⭐ my configuration repo so you can keep up to date on any daily progress!

Dashboards (Lovelace YAML)

This folder holds YAML-managed Home Assistant Lovelace dashboards and UI resources.

Why this exists

Home Assistant stores dashboards and resources in config/.storage/ by default (runtime state).
YAML dashboards make the UI version-controllable and editable by automation tools (including Codex).

What is in here

resources.yaml
- Lovelace JS resources used by custom cards (HACS and local resources).
- This is used when lovelace.resource_mode: yaml is enabled.
SCRATCHPAD.md
- Parking lot for multi-step dashboard work and patterns.
<dashboard>/
- One folder per dashboard (example: overview/, infrastructure/, kiosk/).
- dashboard.yaml is the dashboard entrypoint.
- views/ contains one YAML file per view.
- partials/ is reusable card lists included into views.
- popups/ is reusable popup stacks (typically bubble-card) included into views.
- card_mod/ is CSS overrides (use only when card-native options are insufficient).
shared/
- Cross-dashboard reuse only. If something is only used by one dashboard, keep it in that dashboard folder.

How it is wired into Home Assistant

This folder is referenced from config/configuration.yaml via:

lovelace.resource_mode: yaml
lovelace.resources: !include dashboards/resources.yaml
lovelace.dashboards: ...
- Default Overview YAML dashboard: lovelace.dashboards.lovelace.filename: ui-lovelace.yaml
- Additional YAML dashboards: filename: dashboards/<dashboard>/dashboard.yaml

Note:

Do not use legacy lovelace.mode: yaml (removed in Home Assistant 2026.8).

Lovelace resources are loaded from:

config/dashboards/resources.yaml (referenced by lovelace.resources)

Migration / Cutover Notes

During migration you may have both storage dashboards (from the UI) and YAML dashboards (from this folder) at the same time.
Do not try to create YAML dashboards with the same dashboard ID/key as an existing storage dashboard; remove/disable the storage version first in the UI.
Once you confirm the YAML dashboards render correctly:
- Hide or delete the old storage dashboards in Settings -> Dashboards.
- Keep strategies/dynamic dashboards in storage (Map, Areas, etc.) unless you intentionally export them.

Conventions

Include paths in Lovelace YAML should use absolute container paths starting with /config/.
- Example: !include /config/dashboards/overview/partials/some_cards.yaml
Views are loaded using !include_dir_list and ordered by filename (prefix with 01_, 02_, etc.).
Prefer card-native styling; treat card_mod as a last resort.
Prefer CSS variables (var(--*)) over hardcoded hex colors.
When using the Stitch MCP for inspiration, generation may exceed the tool timeout; wait and then fetch results via stitch/list_screens and stitch/get_screen.

Notes

Do not edit config/.storage by hand. Export once, then maintain the YAML files here.
It is safe to restart Home Assistant after dashboard changes as long as a configuration check passes first.

All of my configuration files are tested against the most stable version of home-assistant.

Still have questions on my Config?
Message me on X :

You can buy me a coffee

Affiliate Disclosure