pepe2
(Pepe)
February 25, 2024, 6:34pm
1
Hi, I like to use an entity that I see in the developer tools → state ( see picture with green arrow ) but don’t find with the system->entities.
I’m happy if I can have 1 of the green entities. but I don’t find them.
Can somebody point me in the direction?
WallyR
(Wally)
February 25, 2024, 6:38pm
2
That is not a state, but an attribute.
States is listed in column 2 and attributes in column 3.
You can use state_attr(‘climate.xxxx’,‘attribute_name’) tå extract it in Jinja.
You do not write how you want to use it, so I cant be more specific.
pepe2
(Pepe)
February 25, 2024, 6:46pm
3
Ok, I like to use it in a automation. I have a motion detector in my living room and if my pellet heater is on, then it give false detection. So if the heater is on, then I like to cut the motion detection.
Edwin_D
(Edwin D.)
February 25, 2024, 6:48pm
4
If you add a state condition, after entering the entity, you can select an attribute of that entity to test for.
pepe2
(Pepe)
February 25, 2024, 6:56pm
5
If I enter the “zitplaats pellet thermostaat” then I get :
and I don’t find the attribute I need.
jeffcrum
(Jeff Crum)
February 25, 2024, 7:05pm
6
You are doing a Device Condition. Delete that and use a State Condition.
Then, select your thermostat and see a dropdown for attributes.
Edwin_D
(Edwin D.)
February 25, 2024, 7:13pm
7
Avoid using devices in automations and scripts when you can:
Don’t forget that the first post in a community guide is a wiki - feel free to add to it or correct it.
This guide was written with reference to:
Home Assistant 2023.8.3
Supervisor 2023.08.1
Operating System 10.5
Frontend 20230802.1 - latest
Background
When you start writing automations, a device trigger seems the obvious choice. Everybody knows what a device is and it comes at the top of the UI dropdown list.
[image]
It works… but it is certainly not a “great way to start” because it …
1 Like