rokka
(Andre)
January 10, 2024, 7:36am
1
Hi,
I am using different thermostats (some from Homematic IP some from SONOFF).
For HomematicIP I can create one Tile Card which displays differnt stats like “current action”, “current temp” and so on.
See upper part of the image
For the SONOFF thermostats this doesn´t seem to be possible.
See lower part of the image
For each entity on the stat content “state” and “last changed” are exposed.
Is there a way to achive the some result like with Homematic IP?
Thanks a lot
Andre
tom_l
January 10, 2024, 8:02am
2
It depends on what the thermostat integration exposes.
rokka
(Andre)
January 10, 2024, 8:51am
3
How can i find out what it exposes?
tom_l
January 10, 2024, 9:08am
4
You already know.
Nothing.
That’s why there are no features for it.
1 Like
rokka
(Andre)
January 10, 2024, 6:06pm
5
Humidity and temperature are different entities.
I am looking for a way to display them in one Tile Card?
Is this possible?
MISEV
(Niels)
January 12, 2024, 6:33pm
8
Add an template helper with those entities and use that
rokka
(Andre)
January 16, 2024, 6:46am
9
Hi @MISEV , could you please provide a minimalistic sample for combining multiple entities in one entity with multiple states or attributes?
That would be great
MISEV
(Niels)
January 16, 2024, 7:54am
10
Hi @rokka sure, you can do something like this. Also look add the templating docs for more options Templating - Home Assistant
{{ states('weather.knmi_home') }} - {{ state_attr('weather.knmi_home', 'temperature') }} °C
jcisio
April 11, 2025, 3:27pm
11
I have different devices (Wi-Fi and Zigbee plugs, and even the Zigbee plugs are from different manufacturer) and they don’t expose the same thing. I haven’t tried templating, but I guess it’s less convenient and not upgradable (when HA changes their UI for example). Is there a way to expose an entity as an attribute of another entity so that it will work “out of the box”?
jcisio
April 12, 2025, 5:26am
12
Oh and I’ve just checked the template integration. It supports some basic entities like sensor or switch, but not more complex entities
Please provide an example of what this means. Templating is VERY capable of handling complex issues.