#Ping integration scan_interval removed

1 messages Β· Page 1 of 1 (latest)

tiny mist
#

@warped plinth πŸ‘‹

After migrating the Ping integration to config flow the scan_interval YAML option is dropped and the interval defaults to 5 minutes, which can be a breaking change for some, or at least it broke the things a bit for me πŸ˜‡ IMHO this should be explicitly stated in the release notes and the docs should mention how to use custom interval if needed.

warped plinth
#

Fair point. Thanks for the hint πŸ‘

mossy flare
#

probably like with any integration: deselect auto update, and automate the update process manually with a service/automation

tiny mist
#

In docs there's an include for it:
{% include common-tasks/define_custom_polling.md %}
(credits go to @unborn warren)

warped plinth
#

Oh perfect, will create a PR later

tiny mist
#

I meant for discovering it, but yeah πŸ˜…

mossy flare
#

and what about the consider_home: configuration option?

#

seems we can not set that either?

warped plinth
#

Thanks for spotting, will add this as a optional field to the config flow