Agreed. That’s exactly what I was trying to figure out. I’ll probably have to make a script or automation based off of a template that monitors entities that go unavailable for “x” period of time. Then use another template in the action to pull the entities id and run a Home Assistant Core Integration Reload All. Basically running a reload of all yaml configuration without restarting the entire box.
I usually don’t have too much of an issue as I already have a daily simple reboot and weekly database purge and full system restart occur.
The issue is mostly with the Tuya, VeSync, & Overkiz integrations, but sometimes also with Hue.
Every few weeks some device(s) stops following the scheduled automations. More often than not, reloading the integration once resolves this issue.
This is not a reauthentication problem.
I’d rather not restart the whole thing if i can get away with it, but If necessary I could schedule a 3am reboot weekly. (I’ve had problems in the past with scheduling reboots bricking my whole system so im fairly reticent to go that route.)
With so many integrations giving you issues this is more likely a networking issue. I’ve never read of issues with the Hue integration on the forum (even though I don’t use it).
See the following post where I try to come up with a way to do this in lovelace with a card & a script. Integration Reload w/Card & Script - no luck so far. I may have missed it above but the service call with an entity_id does not seem to support templates for the entity_id.
After a power outage, some integrations stop working so this feature will be amazing … as I don’t need to check if they work or not.
Some integrations require a reload from time to time.
This type of comment does not help; worse, it is misleading.
The majority of integrations cannot reload programmatically (using actions that can be used in automation); some examples of integrations that I’m using that don’t have this capability are Broadlink, Ecoflow-cloud, Landroid-cloud, Midea Smart AC, Roborock, Smartthings, Watchman and many more; like 99% of all integrations.
Please do your research before chastising people for “unhelpful” comments.
Even though you listed mostly custom integrations (not made by HA), every single integration you listed can be reloaded with an automation using homeassistant.reload_config_entry action.
No. You just use a single entity from the integration and it will reload the entire thing. If you have multiple integrations of it, then you’d need multiple entities.
this being an entity part of the HomeKit devices. Only that entity was reset, not even all entities part of the same device. All the other devices from the HomeKit devices list have not been reloaded.
To reiterate, even if this will work … this is not a future-proof solution as when this entity is deleted you will need to update the automation.
It depends on the integration, if each device creates a separate instance of the integration, then you’d need to add all the devices. But that doesn’t make any sense because they’d have a different connection and there’d be no reason to reload them all if you’re having issues with 1.
Did you read the link I posted? I don’t think so, you can also use the entry_id. You don’t need to use entity_id, you can use anything target accepts.
I’ve read the documentation, however; you are missing my point or unwilling to understand what I’m saying.
When an issue happens it happens with one or multiple integrations (for example after a power outage). I rarely had issues with only one device.
For the stuff that is working on Home Assistant, please consider adding the ability to reload an integration that is based only on an integration identifier.
I’m not missing the point, you keep moving the bar even though you can do exactly what you’re saying. You can reload integrations, entry_id is akin to integration name.
After a power outage, I have 3 integrations that need to be reloaded because they don’t recover, guess what I use? This service with 3 entry_ids.
Sorry that the current implementation doesn’t meet your standards.
Here’s a script that will reload all config entries associated with an integration.