Cannot add a new helper in UI sometimes - seeing a loading indicator about frontend HOT 15 CLOSED

There was an issue, but that was related to the schedule helper not being able to load. That was fixed.

Whenever you have this, check the javascript console for errors. If there are no errors in the javascript console, it must be the loading explained below that fails.

At the point the loading indicator is shown (and never goes away), it needs to do the following:

• Load the possible helpers from the backend (there will be a network request to /api/config/config_entries/flow_handlers?type=helper that should present you the different helpers
• Load the backend translations for the different integrations on the websocket

from frontend.

check the javascript console for errors. If there are no errors in the javascript console, it must be the loading explained below that fails.

Took a minute from this:

to this:

Can you suggest me what shall I do next?

from frontend.

Could you try safe mode first to see if that brings better times?

from frontend.

In safe mode the window is displayed immediately.
Does this mean that some custom integration prevents to show the window fast?

from frontend.

It loads the integration titles for all integrations (helpers, core integrations, custom integrations) at that point. I'm not sure if the amount of custom integrations make it slower or if there would be a specific custom integration that takes a while.

from frontend.

1. I believed that "Add a helper" window allows to create a helper for STOCK integrations, not custom ones. Checked a content of this window- yes, only stock integrations. Then what is a reason of loading titles for ALL integrations then?

2. On the run right after that test "safe mode" run - the window is shown immediately. How can a "safe mode" run fix (may be for a while) this problem?

from frontend.

1. It's not really know what the helpers are when the integration title translations are fetched.
2. Once the integrations title translations are fetched, they are kept in memory until you refresh the whole application.

from frontend.

Noticed that after HA reboot it again needs ~1 minute to show a window.

from frontend.

If you're able to find out if the slowdown comes from the amount of custom integrations you have and not from a single particular one, I'll be able to change it, so it loads only the integration title translations from the helpers.

from frontend.

I am thinking about finding a culprit.
I have some custom integrations - some are defined in yaml, some in UI.
Shall I check for both types?

from frontend.

I think you should check the custom integrations that define a config flow (others said, are configurable from the UI)
I should mention that it would be good to find the culprit as that would help towards the general performance of your home assistant as well.

from frontend.

custom integrations that define a config flow (others said, are configurable from the UI)

Not too many of them:
fontawesome
gismeteo
iPhone device tracker
places
ha-composite-tracker

Shall I disable them one by one - or delete?

from frontend.

Setup a logger in your configuration yaml:

logger:
  default: info
  logs:
    homeassistant.config_entries: debug # add this

Then load the add helper and check for any late "Loaded <integration_name> from <integration_path>"

from frontend.

Added these lines for logger, rebooted - and see no freezes for "add a helper".
Will keep observing within these days.

Thanks for a feedback!

from frontend.

Still do not observe freezes "add a helper".
Closing this issue.
Will reopen if needed.
Thanks again for support!

from frontend.