WTH is there no "reload integration" service?

[Ghafla]

This is a very well hidden feature. The website just gives a veneer of documentation.

How do I reload the nextcloud integration? It takes longer to start than even HA so after a complete server restart it’s lagging behind and HA complains about being unable to reach it.

Found this thread and was temporarily happy.
Using

service: homeassistant.reload_config_entry
data:
  entry_id: nextcloud

of course produces an error - I don’t know the integration’s ID (and obviously it’s not the configuration.yaml name).

.
So I read the above mockumentation

Service data attribute	Description
entity_id	List of entity ids used to reference a config entry.

and came to the conclusion to just enter ANY of the integration’s entity_ids to get it done.
But… nada.

WTH?!?

[jazzyisj (Jason)]

You can get the entry_id in the core.config.entities file located in the .storage folder. There may be a easier way, but you can definitely get it there.

[Ghafla]

Thank you for your hint.
I already looked there; .storage/core.config_entries contains just the integrations managed through the UI; nextcloud is YAML.
Found nothing in .storage/core.device_registry, nothing in .storage/core.entity_registry.

Very well hidden @frenck.

[Ih8rain2 (Ed)]

I followed the link which @Frenck added here in the post and it works as a charm. Just follow the link. I made a automation and a script with it and it perfectly works !

[Ghafla]

You made an automation reloading a YAML-only integration with the link Frenck provided?
Would you mind sharing it here?

[Ih8rain2 (Ed)]

I will share my script to reload. As said earlier I followed the link of Frenck. Selected the device (you can find the device name in your Devices. I made a automation for reload on time and a script which I use for a button card. Here is the script.yaml:

alias: Reload Huawei B535-232
sequence:
  - service: homeassistant.reload_config_entry
    target:
      device_id: 5d8254e71f159783b8c2b56990e037f7
    data: {}
mode: single
icon: mdi:autorenew

[Ghafla]

Hmm, you’re reloading a UI-configured device-bound integration.
My need is the reload of a YAML-configured device-less integration without a device_id (from .storage)…

[Ih8rain2 (Ed)]

Well you beat me here

[m00str]

Have you gotten anywhere with this issue? I need to reload the “Onkyo” Integration, which is also a YAML-configured integration. Calling

service: homeassistant.reload_config_entry
target: {}
data: 
  entity_id: media_player.receiver

returns a “unknown error”, perhaps either because this doesn’t work for YAML-integrations or because the Onkyo integration does not create unique IDs for the media_player entities and has no option to do so.

And yeah, there is already a open github issue for the Onkyo integration because it requires the Onkyo receiver to be powered and connected while Home Assistant reboots, if its not, entities for Zone2 and Zone3 are getting deleted. This is rather frustrating and there seems to be no solution.

[JAudi23]

Any suggestions on how to automate this to occur for a specific device/config entry after a restart of Home Assistant?
I have an automation to restart the HA host weekly and have an integration that tends to need a reload to properly display the data in my dashboard.
I’d like to reload that integration after the restart, and once everything is up and running again.

[jazzyisj (Jason)]

@frenck

Please note: It is not normal to have to reload an integration. Those should be considered regular bugs.

That being said…

automation:
  - id: hass_reload_device_integration
    trigger:
      - platform: homeassistant
        id: startup
        event: start
    action:
      - service: homeassistant.reload_config_entry
        target:
          entity_id: cover.garage_door 

Obviously use an entity id from the integration you want to reload.

[m00str]

This doesn’t work for the Onkyo integration. Calling

service: homeassistant.reload_config_entry
target: 
  entity_id: media_player.receiver
data: {}

Creates following log entry:

Logger: homeassistant.helpers.script.websocket_api_script
Source: components/homeassistant/__init__.py:268
First occurred: 12. März 2023, 16:44:19 (8 occurrences)
Last logged: 17:46:19

websocket_api script: Error executing script. Unexpected error for call_service at pos 1: There were no matching config entries to reload
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 451, in _async_step
    await getattr(self, handler)()
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 684, in _async_call_service_step
    await service_task
  File "/usr/src/homeassistant/homeassistant/core.py", line 1808, in async_call
    task.result()
  File "/usr/src/homeassistant/homeassistant/core.py", line 1845, in _execute_service
    await cast(Callable[[ServiceCall], Awaitable[None]], handler.job.target)(
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 762, in admin_handler
    await result
  File "/usr/src/homeassistant/homeassistant/components/homeassistant/__init__.py", line 268, in async_handle_reload_config_entry
    raise ValueError("There were no matching config entries to reload")
ValueError: There were no matching config entries to reload

This solution neither works for integrations that create no entities, nor for integrations that create no unique IDs (I guess).

[somerandoname]

The “entry_id” is in the diagnostics file of the integration page.

[hitnrun30]

What does this mean? I have no idea to get that information from the Integrations page.

[flowby]

My usecase is that of an Axis IP camera which I only turn on when alarm is enabled. I ended up doing a script that powers the camera on using a smart socket, waits 40s and then calls the reload_config_entry service.

While using the reload_config_entry works (on the device entity), the notification warning in the UI does not go away (I wish it did, because if the service does exactly the same as clicking the reload button then it should probably disappear). Is that expected ?

[swamplynx]

Did anyone ever figure out how to reload a yaml integration???

[quizzical]

Also hoping someone finally figured out how to reload a yaml integration

[taw123 (BikeDude)]

@m00str One man’s pain may be another’s pleasure or at least in my case, my GOAL.

I’d LOVE to be rid of the 2 EXTRA and bogus Zones the Onkyo integration generated!

Btw if you haven’t looked yet you might want to consider moving to the HACS version of the Onkyo integration. He added async support that and HOPEFULLY will eventually generate unique IDs.

—T

[tclemos]

here is what worked for me:

Go to:

• Settings:
  

• Devices & Services
  

• Click on the integration you want to restart, in my case it was Tuya
  

• Click on the right top 3 dots and then Download diagnostics
  

• This will download a JSON file and the file name contains the entry_id.
  In this example, it is dabdb61cd4818b4fcdf5aab4066f51e5
  

• another way to get his entry_id is by clicking on the devices or entities link in the integration screen:
  

• this will lead you to the devices page with a URL containing the config_entry parameter, like this:
  

• then you can do a call like this:

service: homeassistant.reload_config_entry
data:
  entry_id: dabdb61cd4818b4fcdf5aab4066f51e5

• In my case, I have set an automation using Node-Red this way:
  
  

I hope it helps!

[m00str]

Sorry for the late answer, but i tried out two different HACS integrations.
This One seems to be just a revamp of the old configuration.yaml based integration but with the new async backend but
This one additionally has the config flow added, which means you can now set it up through the UI, it generates unique IDs so you can just deactivate the entities of zone2 and zone3. This HACS integration is probably the best for you, since you dont want those additional zones.
The second one has a few quirks regarding zone2 / zone3 but if you dont use those, it shouldnt bother you!