Home Assistant - Reload Integrations Automatically

Blueprints Exchange
, , ,
1

:brain: Blueprint: Reload Integrations Automatically

Hi everyone! :wave:

I’d like to share a blueprint that has been a game-changer for keeping Home Assistant integrations stable and responsive—especially those that occasionally get stuck or become unavailable.

:arrows_counterclockwise: What it does

This blueprint automatically reloads selected integrations when they stop responding or become unavailable. It’s ideal for:

  • AEMET weather integration
  • Xiaomi / Roborock devices
  • External APIs
  • Wi-Fi sensors and other flaky entities

No more manual reloads or waiting for sensors to recover—this automation keeps your setup running smoothly.

:package: How to use

You can import the blueprint directly into your Home Assistant instance using the badge or manually via the raw URL.

Open your Home Assistant instance and show the blueprint import dialog with a specific blueprint pre-filled.

English version:
https://raw.githubusercontent.com/danimart1991/home-assistant-blueprints/main/automation/reload-integrations/reload-integrations.en.yaml

:page_with_curl: Documentation and full details

:bulb: Tips

  • Start small: test with one or two entities
  • Adjust timing based on integration stability
  • Monitor logs for successful reloads
  • Customize notifications to fit your setup

:handshake: Contributions welcome!

Feel free to suggest features, report issues, or submit your own versions. The blueprint is open-source and designed to grow with community input.

7 Likes
2

I am having a problem with the template. I am trying to monitor 2 sensors; a camera motion sensor and a UPS supply for HA. When I trigger it, I get the following error: “Error: Template rendered invalid entity IDs:”

These are the sensors I am using (which I selected from the dropdown box):
entity_id:
- sensor.apc_status
- binary_sensor.192_168_50_123_motion_active

I am running:
Home Assistant OS
Core: 2025.11.1
OS: 16.3

3

When you launch the automation manually, the action is tied to the trigger. Since when it is launched manually there is no trigger (at least not an entity), it throws an error because it doesn’t know which integration to try to reload, nor when sending the notification, which integration to indicate that it attempted to reload.

1 Like
4

Ok. That makes sense. Thanks for the reply. And thank you for creating this template.

5

Thanks for this! My Chromecast Audio devices have been flaky ever since Google’s certificate fiasco and I was looking for how to reload the integration whenever one went unavailable. This is exactly what I needed, and better!

1 Like
6

@danimart1991 would it be possible to add a additional condition (optional) please?
Because I use your blueprint for my sma integration, but when the sun goes down the lan connection goes away. So than your blueprint runs when it is not possible to relaod the integration.
Thank you

7

Hi

I added the following to make it possige to add some additional conditions to run it:

additional_conditions:
  name: Additional Conditions (Optional)
  description: A list of extra conditions that must be true for either action
    to run
  selector:
    condition: {}
  default: []
1 Like
8

Automations created using a Blueprint could be modified by the user including new funcionality :slight_smile:

1 Like