The Problem
My Home Assistant connects to my EV charging station via WiFi. But the connection drops occasionally. Sometimes, HA fully loses connection to the charging station and requires a re-authentication to control it again.
Normally, I’d have to find this disconnection by luck in the HA “Settings” or “Repairs” section. This leads to delays and wrong automations.
The Solution
Home Assistant has a built-in event type for these situations: repairs_issue_registry_updated.
When a device needs a config repair (like a missing password), this event fires. I can use it to trigger notifications immediately via my existing Telegram bot setup.
Why This Matters
- Proactive Maintenance: You won’t know a device is disconnected until you realize things are going wrong.
- Better Automation: You get notified the moment a repair action is required.
The Automation
This is the minimal automation configuration to send a Telegram notification. Replace notify.telegram_bot_xxxxx with your actual notification entity.
alias: Notify Repair Issue Alert
description: ""
triggers:
- event_type: repairs_issue_registry_updated
trigger: event
actions:
- target:
entity_id: notify.telegram_bot_xxxxx
data:
message: |
Action: {{ trigger.event.data.action }}
Domain: {{ trigger.event.data.domain }}
Issue ID: {{ trigger.event.data.issue_id }}
Origin: {{ trigger.event.data.origin }}
title: Repair action occured in HomeAssistant
action: notify.send_message
Event Payload Example
Here is how the event payload looks when I repaired my PEBLAR connectivity. So far I haven’t had it “fail” again, but I assume the action would be different.
event_type: repairs_issue_registry_updated
data:
action: remove
domain: homeassistant
issue_id: config_entry_reauth_peblar_xxx
origin: LOCAL
time_fired: "2026-05-06T07:43:44.373319+00:00"
context:
id: xxxx
parent_id: null
user_id: null
Next Steps
You might want to add more filtering in the if statement logic to handle different types of repairs, or format the message to be more concise depending on your setup.