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

Files

Carlo Costanzo ae2850fe54 Enhance Home Assistant YAML Dry Verifier and related automations

- Added a mandatory resolution policy to the YAML verifier documentation, emphasizing the need for immediate resolution of findings.
- Introduced a new `CENTRAL_SCRIPT` finding type to identify scripts defined in `config/packages` but called from multiple YAML files.
- Updated the verifier script to collect and report on central script usage, including recommendations for moving definitions to appropriate locations.
- Refactored various automations to utilize the new `script.joanna_dispatch` for improved context handling and remediation requests.
- Enhanced existing automations with additional conditions and variables for better control and monitoring of actions.
- Updated README files to reflect new features and improvements across packages.

2026-03-04 17:15:42 -05:00

5.2 KiB

Executable File

Raw Blame History

Bear Stone Smart Home Documentation

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

Reusable scripts that other automations call for notifications, lighting, and safety responses. Pass variables in; let the script do the heavy lifting.

You are here: config/script/ (scripts library)
Repo overview | Config index | Automations | Scenes | Blog: Speech engine video

Featured files to browse

File	Why it matters
notify_engine.yaml	Single entrypoint for rich push notifications.
send_to_logbook.yaml	Generic `logbook.log` helper for Activity feed entries (Issue #1550).
joanna_dispatch.yaml	Shared BearClaw/Joanna dispatch schema for automation remediation requests.
speech_engine.yaml	TTS/announcement orchestration with templated speech.
monthly_color_scene.yaml	Seasonal lighting scenes used across automations.
interior_off.yaml	One-call <20>all interior lights off<66> helper.

Joanna + BearClaw automated resolution flow

script.joanna_dispatch is the shared handoff contract from Home Assistant automations to BearClaw/Joanna.

Why we use it:

Keeps one message schema for remediation context (trigger_context, source, summary, entity_ids, diagnostics, request).
Avoids repeating direct rest_command.bearclaw_command payload formatting in multiple packages.
Makes resolution-trigger automations easier to review, update, and audit.

Current automations that kick off automated resolutions (via script.joanna_dispatch):

Automation ID	Alias	File
`mqtt_open_repair_on_failure`	MQTT - Open Repair On Failure	../packages/mqtt_status.yaml
`onenote_indexer_daily_delete_maintenance`	OneNote Indexer - Daily Delete Maintenance Request	../packages/onenote_indexer.yaml
`onenote_indexer_failure_open_repair`	OneNote Indexer - Open Repair On Failure	../packages/onenote_indexer.yaml
`unifi_ap_no_clients_repair_combined`	Unifi AP Create Repair Issue after 5m of 0 Clients	../packages/wireless.yaml

Tips

Keep scripts generic<69>route data via data:/variables: and reuse everywhere.
If you copy a script, rename any alias and id fields to avoid duplicates.

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

5.2 KiB Executable File Raw Blame History Unescape Escape