Reload integrations indiviudally

Archive Month of "What the heck?!" (2020)
1

Would be nice to be able to reload/restart individual integrations after having made a change to the configuration, instead if having to reload the entire configuration.

2

Also, if an integration fails, or happens to only do discovery on startup, the ability to re-load or restart integrations would be very helpful.

This could lead to never having to re-start unless there is an upgrade also (perhaps).

3

Yes I agree, if possible, this would be nice, especially when debugging integrations.

Mentioned this here:

1 Like
4

Being worked on as we speak :smile::+1:

6 Likes
5

I’ll also second this. I run zoneminder on the same server as HA, if I need to restart the box, then the zoneminder config doesn’t load until I restart HA.

6

Both are now merged!

1 Like
7

Is the reload also exposed via a service call? (cannot find it)

2 Likes
8

This would really help me out as well.
Either service call or a python script?

9

I don’t believe there’s a service call for that currently. However it is possible via an API call.

If you look at the code for the tests, it’s called via :

client.post(
        f"/api/config/config_entries/entry/{entry.entry_id}/reload"
    )

I’m not sure how you would write code that can interface with the API to make this call, but it seems possible at least.

10

Ok, thanks. Couldn’t wait and looked, and it is reload via an URL like:
POST /api/config/config_entries/entry/691c716d001011eba8bd99c0f2866538/reload HTTP/1.1

Tricky thing is to find the “691c…” id, that seems to be only in the .storage directory. As long I don’t delete the config entry, the id should stay the same :wink:

11

Can you help and show an example.
How exactly You trigger this URL?
Thanks.

12

If you got the URL, you can use CURL to execute it. If you want HA, put the following in your configuration (the api token you need to add to the secret file):

rest_command:
  reload_sms:
    url: http://192.168.1.1:8123/api/config/config_entries/entry/691c716d001011eba8bd99c0f2866538/reload
    method: POST
    headers:
      authorization: !secret ha_api_token
3 Likes
13

Hey,

Is there already a Service to call ?
Like integration.reload or something else ?

14

No … That’s why we need to resort to such REST API call.

2 Likes
15

Is this something that I can use already?
My IKEA integration i have to reload every time. At least once a day if it isn’t more.

1 Like
16

So this is properly annoying me. I can’t see why its not working at all, it appears to be something wrong with authentication, but I can’t see what…

https://10.n.n.n/api/config/config_entries/entry/a43bfad89c4487c518270203fb3b995a/reload

With

authorization xxx (long live access token)

In the header but I just get a 401 or 403 for http & https.

I’m running https on 443 (not 8123) using lets encrypt.

In the HA log I get

Login attempt or request with invalid authentication from 10.n.n.n

I’ve got api: in configuration.yaml

Really stuck now.

17

I got it working. See my post in a different topic with an example:

18
  • Feels like there should be a “reload” menu option that uses this on every integration in the UI
  • A native service call that can be called via automation not a just a REST call.
  • Even better would be for there to be some form of native recovery option you could set for ALL integration to try and restart them at least once automaticly.

I have about 3 external services “Ombi”, “Unifi”, and “Ikea” that seem to break frequently and it is JUST because the service missed one poll or the service was not available on HA reboot.

1 Like