Removed ping entities from configuration.yaml, but they still exist. Why?

Configuration
1

I have not yet installed 2023.12, still on 2023.11. But in preparing for the ping change I removed my pings from configuration.yaml and restarted Home Assistant.

binary_sensor:
  - platform: ping
    host: marvin
    name: "Broker Ping"
    count: 1
    scan_interval: 5

However, even after a restart of Home Assistant the binary sensor still exists:

broker ping
broker ping965×351 29.3 KB

Why?

2

Wasn’t there a recent change to the ping integration that brought them into the UI? When they do that they usually import configuration.yaml entities and leave the yaml ones orphaned for you to delete.

You may need to go to the integrations page and delete them there.

3

He hasn’t upgraded yet so that wouldn’t have happened.

4

As Steve’s avatar would say: Doh!

1 Like
5

I get a warning that Ping has been removed from configuration.yaml, or soon will be.

Configuring Ping using YAML is being removed.

Your existing YAML configuration has been imported into the UI automatically.

Remove the ping configuration from your configuration.yaml file and restart Home Assistant to fix this issue.

Well I use a few binary sensors with Ping to see if security cams are not offline, so I get a warning whenever one goes down. How do I get this information after Ping has been removed?

That it is placed in the ui automatically does not tell me a thing, what does it mean, what will it do, how to put that info in a new binary sensor again, I have no clue of what it means been placed in the UI.

So please how to go about it now?

1 Like
6

Yea it confused me at first too. I had quite a few binary sensors with ping, all set up in my configuration.yaml file.

Ping is now part of Home Assistant, see Ping (ICMP), so anything using the old method of using a binary sensor in the configuration.yaml file needs to be removed.

For me, after trying to update Ping (ICMP) had automatically been added and all the old ping binary sensors imported, so I just had to remove them from the configuration.yaml file. I didnt have to make any changes to my automations etc either, so all good.

7

Settings, Integrations, Ping (ICMP).
Configure and add from there.

8

Thank you found them, the only thing what remains is… do I need an automation to alter the ping interval from standard 30 sec to another time interval?

9

I had the same problem … then I discovered that I had a couple of ping references in my device_tracker.yaml file. Removing these did the trick.

10

Yes. Just add this automation, but change seconds: and entity_id:
entity_id: is the sensor entity created by the ping integration.

# In 2023.12.1 the polling frequency default is 30 seconds.
# You can change this in an automation:

alias: Ping-TenSeconds
description: Ping entities every ten seconds
trigger:
  - platform: time_pattern
    seconds: /10
condition: []
action:
  - service: homeassistant.update_entity
    target:
      entity_id: binary_sensor.zeus_ping
      entity_id: binary_sensor.apollo_ping
    data: {}
mode: single