Failed Ping count reset

[kenai2011]

Checklist

• I checked for similar existing requests (both open and closed) before posting.
• My request is generic, other users may benefit from it too.
• I will participate in further discussion about this feature and can test it (if requested) once it's done.

Proposal

Hi,
I use the integration for a couple of days. But to compare the failed ping between some devices over a given time it would be useful to have an option to reset the ping count via switch or automation.
you already answered: What could be implemented instead is a service that can be called, passing the entity ID of the sensor you want to reset. This would allow you to trigger the reset via an automation or script, without directly modifying the sensor state..
This option would also appropriate, i guess the feature itself would be nice, at least to start analysis with fresh statistics instead of creating always new sensors
Thanks
Kenai2011

[studiobts]

Hi @kenai2011 ,

thank you for your interest. After your clarification in the other discussion, I now better understand your use case. Unfortunately, what you are asking for cannot be implemented at the moment.

This sensor exposes an internal counter that is used to determine whether the device should be considered online or offline. Every time a successful response is received, the counter is automatically reset to zero. For this reason, it cannot be manually reset via a service or automation.

What you actually need is a total failed ping counter, independent from the internal availability logic. This would be a separate sensor designed specifically for statistical and analytical purposes, allowing you to reset it on demand and start measurements with fresh data.

Such a sensor is not currently available, but it is a reasonable idea and could be considered for inclusion in a future version.