Future request: Add possibility to reload config entry

[strutings]

Since the gardena api is quite unstable it would have been great to reload the integration in HA. I have tried doing this several ways with rest command and with the integrated function in HA with no luck.

Reloading give this error: Error executing script. Error for call_service at pos 1: The config entry (gardena_smart_system) with entry_id dd9545e5cab2a75b3c9e1e29f8c46c80 cannot be unloaded because it is not in a recoverable state (ConfigEntryState.FAILED_UNLOAD)

[Paul-Vdp]

+1

[GLehnhoff]

+1

[martinw72]

+1

[moloroplayer]

Based on the instability of the connection and the regular failures of the integration where all entities become unavailable, this would be an important function to automatically restart the integration, so I sincerely ask you to consider the request as a workaround for the connectivity problem.

[eikowagenknecht]

As a workaround, choosing "disable" and then "enable" works just as well, at least in the case that the integration didn't load on startup:

[moloroplayer]

As a workaround, choosing "disable" and then "enable" works just as well, at least in the case that the integration didn't load on startup:

shure but this can't be done automaticaly

[freddeh]

+1

[0la1]

+1

[strutings]

As a workaround, it is possible to use the spook integration to de- and reactivate the Gardena integration.

[freddeh]

As a workaround, it is possible to use the spook integration to de- and reactivate the Gardena integration.

Do you have a reliable trigger for an automation figured out already? From what I have seen so far the states of the entities remain ‘known’ when the connection is lost, maybe one of the attributes can be used? I will try to use Irrigation Unlimited Sync Error for now, although that is already too late then to do something about it.

edit: ok, does not work for me at all since I always get an error that integration failed to unload properly…