Allow Refreshing Devices During Deletes or Manually

[jmillnik]

• Add an optional force_refresh parameter to delete_timers and delete_alarms
• Add a refresh_devices service to allow manual refreshes

Both options invoke async_request_refresh on the coordinator and therefore restart the refresh timer to prevent over-requesting devices. They provide a reasonable (and optional) method to immediately update devices when deleted, or to allow users to refresh timers/alarms.

[KapJI]

Add an optional force_refresh parameter to delete_timers and delete_alarms

Do we really need this to be configurable? I'm ok with doing it by default, seems reasonable to me.

[jmillnik]

Add an optional force_refresh parameter to delete_timers and delete_alarms

Do we really need this to be configurable? I'm ok with doing it by default, seems reasonable to me.

I know some people have issues with timeouts when they get too many queries. Deleting multiple alarms in succession with automations would be likely to cause noise. Perhaps default to true but leave it there to allow the option to set it to false?

[KapJI]

Yeah, makes sense. Let's default to refresh and name it skip_refresh then. Also it will be great if you can add translations to other languages using some online service.

[jmillnik]

Yeah, makes sense. Let's default to true and name it skip_refresh then. Also it will be great if you can add translations to other languages using some online service.

Makes sense will knock this out after work and get it all cleaned up. Just fixed my pre-commit to fix the linting. Running on a windows laptop atm :(

[KapJI]

Thanks!