I have an Orvibo socket that I have successfully integrated into HA via yaml config (as it is not supported via the UI). This ordinarily works well.
However the device (or rather entity) is only added if the socket is available on HA restart. If it’s not, then it will not be added when made available, and can’t be added without a restart of HA. I suspect the integration reasonably only tries to add devices during start up. I have a ping sensor for the socket, so know when it is available - all I need to to then is to restart the Orvibo integration.
There is a service that allows the restarting of integrations, but this takes an id that is not available (presumably as it is configured via YAML).
Is there a way to restart the Orvibo integration by the integration name? Or failing that are there any workarounds to force an id or even area on an entity that isn’t loaded?
(raised an issue here: Orvibo devices undetected unless available on HA start · Issue #124572 · home-assistant/core · GitHub)