Can’t set own ping interval

[danmrossi]

The problem

In 2023.12.0 we have lost the ability to set our own ping intervals which breaks functionality for those of use who utilise Home Assistant for operations other than making a house “smarter”

Please do not read anything I have said prior or after in a negative light as not trying to upset or step on anyone’s toes. Just trying to get my point across.

I am all for change and the move of various bits and bobs out of YAML yet there is a lot of us out there that get peeved when not all of the functionality that we had with YAML doesn’t come across and coders make their own minds up on what functionality either comes across or what settings will be changed then can’t be edited etc etc when their can be hundreds of use cases that one is not aware of.

If we can’t have individual ping intervals per sensor/entity then even a global option that we can set our own value would be a great compromise.

I do really genuinely appreciate everyone’s help to me over the years and appreciate for a lot of people coding on here is more of a love job than a paid job I just hope you read this in a positive light and hope at some point this can be rectified.

What version of Home Assistant Core has the issue?

2023.12.0

What was the last working version of Home Assistant Core?

2023.11.3

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Ping

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[danmrossi]

If I have to roll back to 2023.11.3 that’s fine by me it’s just I only really updated because I wanted the fix in the front end for half created automations that you don’t save that still hang around.

[joostlek]

Look, setting a custom update interval isn't an issue specific for a single integration. To avoid having every integration implement their own way of doing scan interval, we have made something that is way more flexible that will suite probably everyones need. The update_entity service.

This service gives you way more freedom than just an input field when configuring an integration.

1. You can change the update interval whenever you want. If you have an API limit on your solar panels for example, you can now choose to only ping per hour during night and during day you poll more, giving you more data points. Or maybe you don't want the weather to update as much when you're not at home. You do you, make it fit your need.
2. You can apply this to every integration. If every integration would have to implement a configuration to add scan interval, you would not be able to set scan interval in 95% of all integrations at this point.

So to end this topic now. You can still do your use case, except you need to do a bit of effort to make it work. But this solution is the most consistent way over all integrations, giving you more freedom and possibilities than with just an input field.

[home-assistant]

Hey there @jpbede, mind taking a look at this issue as it has been labeled with an integration (ping) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of ping can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign ping Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

ping documentation
ping source
_{^{(message by IssueLinks)}}

[danmrossi]

Yes but the documentation is severely lacking on how anyone can do this

…

Sent from my iPhone On 8 Dec 2023, at 11:02 pm, Joost Lekkerkerker ***@***.***> wrote:  Look, setting a custom update interval isn't an issue specific for a single integration. To avoid having every integration implement their own way of doing scan interval, we have made something that is way more flexible that will suite probably everyones need. The update_entity service. This service gives you way more freedom than just an input field when configuring an integration. 1. You can change the update interval whenever you want. If you have an API limit on your solar panels for example, you can now choose to only ping per hour during night and during day you poll more, giving you more data points. Or maybe you don't want the weather to update as much when you're not at home. You do you, make it fit your need. 2. You can apply this to every integration. If every integration would have to implement a configuration to add scan interval, you would not be able to set scan interval in 95% of all integrations at this point. So to end this topic now. You can still do your use case, except you need to do a bit of effort to make it work. But this solution is the most consistent way over all integrations, giving you more freedom and possibilities than with just an input field. — Reply to this email directly, view it on GitHub<#105304 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AMCDRZOVEHERAJGHPZT32EDYIMTY3AVCNFSM6AAAAABAMW5RIWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNBXGMZTINRRGM>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[joostlek]

But since you have the freedom, there is no default way to do what you want. When you just want to higher or lower the interval, checkout the time interval trigger: