Homeassistant.reload_config_entry doesn’t work anymore

Configuration
1

homeassistant.reload_config_entry doesn’t work anymore.
It gives the error no target set even if the target is the same. It has stopped working since 2026.4.1

Even if you click on the integration to reload. It was ok since a few versions ago.

errore reload
errore reload1920×1080 147 KB

2

Please don’t post pictures of yaml code - paste the yaml code directly.

I had to zoom all the way in to spot your issue. homeassistant.reload_config_entry requires an entry_id, but you’re using an entity_id in your automation.

The below is from my own (working) automation to reload the Bring integration.

  - action: homeassistant.reload_config_entry
    data:
      entry_id: 3080e6df9e7ec8a9bdc9dfc966158e03

I’m not sure why you’re saying your automation was ok since a few versions ago. I’m still on 2026.2 and can guarantee that your automation never validated correctly if you were using entity_id instead of entry_id:

image
image1059×854 40.4 KB

3

I’m Sorry

This Is the yaml code

action: homeassistant.reload_config_entry
metadata: {}
data:
entry_id: 01KF6A6YRPDWAR6WGH6W2HMN07

Also with entry id it is not working. As well in Yaml as in visual editor. Even if you click on the good entry since a couple of versions it gives back an error.

4

Indeed this service is no longer working, trying to reload the Unifi integration since HA always is up before that, but not working

image
image1544×491 23.2 KB

5

Same here. Even if I check the box for config_id and add the correct integration I need to add a target, but the target list only shows entities, not the integration.
Similar in YAML mode:

action: homeassistant.reload_config_entry
data:
  entry_id: 0a86a19aa272caea034c628bb77b03a2

Error: This action requires a target, please define a target 'entity_id', 'device_id', or 'area_id' under 'target:' or 'data:'

Neither 'entity_id' nor 'device_id' is allowed in as the data.

6

Yep, you're right. Since my last post, I updated to 2026.4 and can confirm this issue.

However, there are workarounds for this in both the Automations & the Actions tab in Dev tools:

For Automations, simply ignore the Frontend warning saying "No Target Set". The Action will still work without a target. Just tested the below multiple times & it let me run the actions with no errors:

data:
  entry_id: 3080e6df9e7ec8a9bdc9dfc966158e03
action: homeassistant.reload_config_entry

For the Actions tab in Dev Tools, the call will fail if you don't define a target & an entity ID, however it is possible to switch to yaml mode & replace the entity with an empty array or null. Both the below options are valid & tested as working:

action: homeassistant.reload_config_entry
data:
  entry_id: 3080e6df9e7ec8a9bdc9dfc966158e03
target:
  entity_id: null

OR

action: homeassistant.reload_config_entry
data:
  entry_id: 3080e6df9e7ec8a9bdc9dfc966158e03
target:
  entity_id: []

I suggest someone raises a bug for this on Issues · home-assistant/core · GitHub

EDIT: Possibly related to this change, though that was done 8 months ago & came out with the 2025.11 release

7

Raised the Github issue myself. If anyone's interested, it's here.