Just a thought, but it would be nice to add sensor as x, similar to the new switch as x integration.
Though I would recommend an optional text box to allow for putting in a small conversion.
ex, My meter readings come in as sensor.id_of_meter and they tend to be 100 ft³ per int, so I need to divide by 100 to get the proper reading for the energy dashboard.
I know about template sensors, I use template sensors, That’s not the point.
There are template switches, Yet for ease of usability reasons we now have switch as x.
My request is that we do the same for sensors as it will make things a lot more assessable to those who don’t want, need, or have the time to mess around with yaml files.
I would suggest instead of phrasing it as adding Sensor as X you phrase it as a request that there is an option to add a value template / lambda filter from the frontend to modify a sensor value:
Filter: {{ value / 100 }}
This could create a template sensor in the background, but be done from the front end.
It would be to see all entities available to convert to X in the UI ideally, at least with a default config…
For example I have a template fan that converts a light dimmer switch i’m using to variably control my fan which just changes the brightness val, I’ve seen others use that so seems like a common use case.
Things like @cpyarger is doing to convert values using template sensors seem like common use cases that could be done in the UI. “Sensor as X” makes sense to me too given what currently exists