as I use Yaml mode, the min/max sensor is configured like:
- platform: min_max
name: Mean indoor temp
type: mean
entity_ids: &temp_sensors
- sensor.temperatuur_living
- sensor.dining_table_sensor_temperature
- sensor.auditorium_sensor_temperature
- sensor.frontdoor_sensor_temperature
- sensor.library_sensor_temperature
- sensor.dorm_sensor_temperature
- sensor.corridor_sensor_temperature
as you can see, the list of entity_id’s is ready to be copied and pasted to be used in other logic, eg automations and groups. The anchors illustrates that nicely.
With 2022.4 we can now configure more and more via the UI, especially the helpers section, like this min/max sensor.
That’s very nice, because that way we can be 100% of the correct configuration. And very simple. point and click.
However, configuration via the UI doenst really ‘help’ if you want to return to that helper section to easily check the entity_id’s of the sensor, (we are presented with Names, not entity_id’s) .
added to that, we can not copy them in 1 single selection for use elsewhere in your config. This would not be a big issue, if it weren’t for the fact the entity_ids of the min/max sensors aren’t listed in the attributes at all:
hence this FR:
Please consider adding the list of comprising entity_id’s to the sensor, and to be in line with eg the platform: group entities, do that in an attribute ‘entity_id’:
binary_sensor:
switch:
ofc there are many other examples in the current HA setup that use this method of showing the contained entity_id’s.
this would allow us to check the dev tools State and quickly copy the entity_id’s,
or a bit more sophisticated, but still very default technique, use template :
{{state_attr('sensor.mean_indoor_temp','entity_id')}} to get to the entity_id’s:
This would be a great way to connect the ease and simplicity of the UI config with the more advanced needs of the Yaml config.
thanks for considering
