Why did they make the change to ping, dropping the interval setting? I looked through the linked pages but didn’t see an obvious explanation. I assume there is a reasonably good reason for it.
The suggestion to remove the recorder days is interesting. I have mine set to just a few days, because the partition the database is on its low on space, and I haven’t gotten around to dealing with it. Storing more in the same space would be good. I didn’t understand how the database would be smaller despite having more info.
Why did they make the change to ping, dropping the interval setting? I looked through the linked pages but didn’t see an obvious explanation. I assume there is a reasonably good reason for it.
The suggestion to remove the recorder days is interesting. I have mine set to just a few days, because the partition the database is on its low on space, and I haven’t gotten around to dealing with it. Storing more in the same space would be good. I didn’t understand how the database would be smaller despite having more info.
I normally shrug off most of the changes, but dropping ping from yaml AND fixing the interval just does my head in.
I’m using HA’s basic, built-in, doesn’t need an integration, standard ping, to monitor my network and inform me if people are home, turned off, etc…
And it was simple to just add more ping sensors in yaml, just copy some similar ones.
Now? Jeez…
And overloading HA via too high a ping rate? That’s a fundamental design issue with HA, not a reason to force a move to an automation…
Oh… and my lights don’t work now… ffs