I don’t think so. The -in the descriptive name translates to _ in the entity_id.
I just created this test automation and set the state to off via Dev Tools and the ping platform changed it back to on within 2 seconds (the car is currently ON in the garage so ping is successful) and this new automation fired:
alias: Clarity Ping
description: ''
trigger:
- platform: state
entity_id: binary_sensor.clarity_wi_fi_ping
to: 'on'
condition: []
action:
- service: notify.windows_11_hass_agent
data:
title: Clarity
message: Ping triggered
mode: single
I think I found it. The Visual editor shows For (optional) for all 3 conditions but when unset, the yaml is blank. In this automation, one of the conditions had a left-over from when I did have a For (optional) setting but changed it to 0:00:00 and the yaml then reflected those new 0:00:00 settings:
for:
hours: 0
minutes: 0
seconds: 0
Once I deleted that block the automation started working.