System: Home Assistant OS on a Beelink Mini-PC (no VM, no Proxmox, no Docker), Core 2026.9.1
Symptom
The script component has stopped loading any entities from scripts.yaml — neither pre-existing scripts nor newly created ones, whether defined via YAML or created through the UI. The scripts overview (/config/script/dashboard) always shows “Create your first script”, even though scripts.yaml provably contains correct, valid content. Creating a script through the UI fails with a “Script setup timed out” error.
Notably: no error or warning whatsoever appears in the logs — not even with debug logging enabled for homeassistant.components.script. hass.config.components confirms the component itself is loaded (generic services like script.reload work), but the entities from scripts.yaml are simply never created. script.reload always reports “success”, with no visible effect.
What I’ve already checked / ruled out
- Verified
scripts.yamlcontent directly via a Samba share: syntactically valid, correctly structured homeassistant.check_configconsistently reports “valid”- No explicit
script:key inconfiguration.yaml(0 matches),default_config:is present - Multiple HA Core restarts — no effect
- Full host reboot (the mini-PC) — no effect
- Individually disabled and tested suspect integrations:
open_epaper_link,bambu_lab,awtrix— no effect in any case - Entity registry cleanup: removed all orphaned old script registry entries and restarted HA — the script domain remained completely empty afterward (not even fresh default entries were created)
- Other domains (e.g.
input_boolean,input_button, automations) work perfectly fine — the issue is specific toscript, not a general system or recorder problem - Attempted a Core downgrade to 2026.7.3 (via
update.install, with an automatic backup): Core crashed immediately on startup, and Supervisor auto-rolled back to 2026.9.1 within seconds. Likely cause: the database/registry had already been written in the newer format and was incompatible with the older Core version, so a clean test on an older version wasn’t possible
Similar / known cases
- Discussion #2407 — nearly identical symptom on Core 2026.1.0 (January 2026): timeout dialog on save, empty script list. Also unresolved, was only answered with “wrong channel for support”
- home-assistant/core#94449 — exact same symptom, opened in 2023, closed as “not planned”, never root-caused
- Also related (not linked here to stay under the forum’s link limit for new users): GitHub core issue #134967 (“New automation or script has saved, but waiting for it to setup has timed out”)
- Possibly relevant timing: Home Assistant reworked the internal script/condition API in May 2026 (developer blog post “Changes to the condition and script APIs”, 2026-05-13). I can’t confirm whether this is related, but the timeframe overlaps
Current workaround
Since I don’t have a test environment and a fresh install is planned soon, I’m working around the issue for now: instead of scripts, I use input_button helpers paired with automations (state trigger on the button → desired action). Automations are unaffected by the bug. This works fine for one-off actions, but it’s not a real substitute for reusable, parameterized scripts.
Question for the community
Has anyone found a root cause or fix for this? And: has anyone found that a fresh HA install (e.g. as part of migrating to a new host) actually resolves this, or does the bug survive a fresh install once an existing backup is restored?