Add Template Sensors to Device page

Feature Requests
41

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.

Screenshot 2024-10-03 at 13.27.00
Screenshot 2024-10-03 at 13.27.002008×2126 256 KB

Screenshot 2024-10-03 at 13.27.29
Screenshot 2024-10-03 at 13.27.292082×2104 470 KB

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.

Screenshot 2024-10-03 at 13.29.44
Screenshot 2024-10-03 at 13.29.442102×1514 213 KB

1 Like
42

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.

43

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

1 Like
44

Thanks. That did the trick!

45

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

46

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.

3 Likes
47

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…

48

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.

49

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.

1 Like
50

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.

image
image1146×1462 71.9 KB

51

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.

3 Likes