As a Network Engineer managing devices discovered via PRTG auto-discovery,
I want auto-discovery (including the default templates Generic Device (Ping Only) and Generic Device (SNMP Enabled)) to create ping sensors whose sensor type label matches their actual channel structure, settings, and documented functionality — i.e., a sensor labeled Ping v2 behaves as documented for Ping v2, or a sensor with Ping v1 behavior is labeled Ping v1,
so that I can trust that sensors were created correctly, reliably filter and manage sensors by type, and avoid wasting time investigating "broken" sensors that are actually just mislabeled.

Background:
In PRTG 26.3.122.1665, when Auto-Discovery is performed using PRTG's default device templates (for example, Auto-Discovery without specifying a template, Generic Device (Ping Only), or Generic Device (SNMP Enabled)), a sensor is created whose sensor type is Ping v2.
However, this sensor has the same channel structure and settings as the old Ping v1 sensor and only provides Ping v1 functionality.
This can lead users to believe that the sensor was not created correctly or is broken because its sensor type is Ping v2, but it does not have the functionality or settings described for Ping v2 in the documentation.
It also causes inconvenience when filtering sensors by sensor type, because these sensors are identified as Ping v2 even though they only have Ping v1 functionality.

We request that the sensor type and its actual functionality be made consistent.
Ideally:
If Auto-Discovery creates a sensor with the Ping v2 sensor type, it should provide the actual Ping v2 functionality.
If Auto-Discovery is intended to create a sensor with Ping v1 functionality, it should create the sensor with the Ping v1 sensor type.