[AlexandrLisitsa]

Why

⚠️ Alert: Grid Voltage Out of Range waited 20 s after grid_condition_safe tripped and only then read the voltage. grid_safe's 300 s delayed_off keeps it unsafe long after a short spike, so the reading was usually back in range. On the night of 1–2 Nov:

Trip (UTC)	What tripped it	Alert said
01:50, 02:14, 03:13, 04:08, 04:13	250.0–253.5 V for a few seconds	"Low 248/247 V" or "High 253 V"
05:33	9-second dropout to 2 V	"Low 226 V"

What changed

• The automation triggers on the trip itself and reads trip_volts first. grid_safe has a 5 s delayed_on, so that reading is the one that was out of range.
• The 20 s hold moves into the actions, then grid_safe must still be unsafe. If grid_down is still on 20 s after the hold, the Grid Outage alert has already fired and the run stops. A shorter dropout pages as Low.
• The title comes from trip_volts: High at 250 V or more, Low at 185 V or less, otherwise Out of Range.
• Message: "Mains went to 252 V, outside 185-250 V (248 V now)."
• ✅ Grid Voltage Normal is unchanged. Its condition still holds because last_triggered is the trip time, which is inside the spell.

Testing

• check_automations.py section 2b covers the trigger, the order of the steps, each title and the message. All checks pass.
• Already deployed to the box: its copy matched master before the copy, ha core check passed, and the reloaded config has the new actions.

🤖 Generated with Claude Code