Add Template Sensors to Device page

[andyblac (Andy Blackburn)]

been using for a while with no real issues, if you merge or move entities from one to another, those entities from the orginal device will be move to the other device and thus the original device can be empty ( imo this is expected behaviour), If you remove the device from the merge or remove the entities from the new devcie they do move back to original device with no problem.

in this example ii have merged a Zigbee wall socket and a Shelly PM mini so I get a switch and power readings in the one device.

the Shelly device now has no entities, but it is still required as it has the visit link to open the Shelly webpage, granted it would be nice for ALL info for all device to show in the Main new device, but this is not an issue really.

[siwilson (Simon Wilson)]

I was hopeful this would solve my objective of grouping multiple REST entities under a single device. Sadly it does not seem to support REST sensors.

[andyblac (Andy Blackburn)]

if your taking about the above integration, make sure your sensors have a unique_id.

[siwilson (Simon Wilson)]

Thanks. That did the trick!

[Samedarkclouds]

You sold me. I will give it a try. Thanks for taking the time. I Appreciate it.

[merquel]

If I have a template binary sensor set up via YAML, I can’t add it to a device because YAML doesn’t support that.

But if I set it up via the UI I can’t use the delay_off configuration variable because the UI doesn’t support that.

This whole YAML vs UI thing is starting to get ridiculous now.

[jackson.moormeier (JKM)]

Yea, it’s really frustrating to not see feature parity between the two. Particularly because it creates confusion about the standard and best-practice approach…

[petro]

it’s not possible to add feature parity between the two, we tried at first and it didn’t work quite right. So it’s been limited to UI only.

[drowning-goby]

I can (probably) see why it’s not possible to have device assignment in YAML. But why can’t we have all options in the UI. I’m particularly interested in precision of generic thermostat.

[Jon_White]

I must have missed the release announcement when this was implemented! but as of Feb 2025 this feature is available. In the Template you can select a device to link it to. Then in the device info it appears.

[petro]

Yes, the feature is available, but not available for yaml template entities. Which is why this remains open. This feature was added sometime in the past year.

[andras-tim (András Tim)]

Dear @petro,

I’m glad that when I add a template sensor via the UI, it allows me to attach it to a device.

As far as I see, this uses Home Assistant’s internal device_id‑based matching mechanism, which seems too fragile to expose in YAML, and since the id and friendly_name still are not siplit on the UI, I’m afraid this feature will not be available for YAML any time soon.

Do you see any chance this could be supported?

My Usecase

I have been managing my entire HA configuration with Ansible (for 9 years), so I have many automatically generated configuration parts, e.g. my APC battery pack’s output power calculation and its energy sensor.

[petro]

It won’t be added anytime soon. At a bare minimum, development can’t start until after legacy templates are fully deprecated and removed from the system.