Every time I make a change in the config, or I load a new HACS extension I need to restart HA. I would love to have a way to reload the configuration without restarting.
When you add a new item from hacs, you aren’t adding new configuration. You’re adding code to HA. HA uses importlib, however I’m not sure that lib would work without a restart in between.
As for changing the config, there’s reload yaml in developer tools / yaml tab.
1 Like
If it would be possible to reload complete integrations after an update / installation via HACS without restarting, that would certainly reduce my restarts by 90%.
2 Likes
Hi Petro, thank you for replying.
About HACS: When I add a new application to my computer I don’t need to restart, I expect a similar experience in Home Assistant with HACS (obviously there’s a technical reason for having to restart, but it’s unclear to me why it’s really needed) .
About config: My experience with the reload is that it works correctly for some changes but not for others, so I always restart.
2 Likes
When you add a new application (Addon) to home assistant, you don’t need to restart. Addons are equivalent to applications in regards to your analogy.
Integrations are built inside HA, it’s not equivalent to adding applications. It would be equivalent to adding things inside applications.
1 Like
I have this bad habit of modifying any YAML or adding integrations, and I will habitually restart. I feel that restarting would be more effective. Perhaps this is an illusion.
1 Like
Ok, then let’s rephrase. “When I add an extension to Chrome, I don’t need to restart my browser (or my computer).”
This WTH is very similar to this one: WTH can't we install/update (custom) integrations without restarting HA?
Yes it was created earlier and has more votes, but misses the discussion part (posts). Maybe it’s possible to merge the topics? I think the votes (the more the better) are as important as the discussion.
I agree, my reference was only added to add cross-visibility to both topics as otherwise, it could mean splitting of votes. Unless otherwise mentioned, I think both should be voted for.
I voted, but perhaps this could also be thought of as “WTH is restarting HA so disruptive?”
If the “various reasons” mentioned in OP can be solved / ameliorated, I would think that a more valuable improvement. After all, there will always be reasons (such as updating) to restart.
Reasons:
- duration of restart
- disruption of current operations (e.g. automations in a delay action, or waiting for a trigger)
- …
Integrations run I the same memory space as HA. You’re asking for the equivalent to Windows Server 2025 hot patch.
(hint: it took Microsoft over 35 years to finally do it…)
You need a COMPLETE rearchitecture of the entire system for it to work differently.
If your integration vendor does it correctly they Can just reload the components from a quick reload in the restart console but no… You won’t get away from at least having to reload.
And maybe it’s time for that re-architecturing, given the issues that come from having these custom components such a significant part of the HA experience.
IMO, there’s no reason for them to be implemented as you describe (other than “that’s how it’s always been”) – they should be able to run like Chrome Extensions (which can be added, removed, updated, or reconfigured without restarting the entire application).
1 Like