templates-archived

[floral shuttle]

I am still looking how to kill several strings inside various names. |replace('battery','') works ifc, but I alos want to delete battery level, Batterij etc etc

{{i.name|replace('battery','')}}: {{i.perc}}%

[jolly wigeon]

You are right! Fixed and it now seems to be working! Thank you!

[shrewd dust]

Really annoys me that the UI YAML editor won't throw an error if there's an error in your template. Thank goodness I finally thought of the Template developer tool.

[marble jackal]

?

Oh wait, you say YAML editor.. VSCode should be able to render templates in your YAML if you use the HA extension

[shrewd dust]

Oooh, I didn't realize that was an option. I should look at it.

Spent a few days trying to figure out one of my 3 templates wasn't working. Turns out I'd missed a ) which I couldn't easily see because the line was too long. 😂

Template checker immediately pointed it out to me.

[marble jackal]

The HA Extension for VSCode will also check your jinja on such things

[plain magnet]

@vapid olive I converted your message into a file since it's above 15 lines :+1:

[marble jackal]

you can see (unless you are colorblind, but there are probably themes for that) that the opening curly brackets are yellow, but the closing ones are white, this indicates an issue with paranthesis

[shrewd dust]

Yeah in vscode, but I was just editing via UI YAML, which has fewer colors.

[marble jackal]

@vapid olive what do you mean with a 4 way switch?

[shrewd dust]

I'm not sure I can easily use the vscode extension as I'm hosting on a Pi.

[marble jackal]

the problem is most probably in your scripts, which you didn't share

[vapid olive]

@marble jackal I turn it on (turns on things), then i turn it off (only the icon color changes to gray), then I turn it on again (it turns off things) then I turn it off again (only the icon color changes back to gray).

[marble jackal]

that must be in your scripts then

wait

you are turing a script off

that probably doesn't do what you think it does

that turns a script off while it's running it's actions

[vapid olive]

well the script is simple

i'll paste a screenshot of it

well, I can't, don't know why, but here is the yaml version

metadata: {}
data: {}
target:
  entity_id:
    - switch.tv
    - switch.parlantes
    - switch.pieza

[inner mesa]

On purpose, because you were going to post a picture of text 🤷

His point was that script.turn_on causes a script to start running and script.turn_off causes it to stop if it's waiting for something. Yours doesn't wait, so turn_off does nothing at all

Seems like you just always want to run the script...

[vapid olive]

it makes sense, i'll try adjusting that part, maybe just using toggle instead of turning on/off (?)

[inner mesa]

No

Please re-read

Your script already toggles the switches. Just turn the script on whenever you want that to happen

There are very few cases where turning off a script or toggling one makes any sense

This is not one of them

[vapid olive]

not really, i was going to post the GUI version, but yeah

[vapid olive]

I understand, thanks for your help 🙂

[inner mesa]

YAML text is the only way to post in a way to get help here

[mighty ledge]

As script is only on when it has a delay in it. Otherwise it's stateless

so you can't toggle it

well, you can, but it has to have a delay

[mighty ledge]

to clarify robs statements, this channel is for #templates-archived which is code. Other channels like #frontend-archived allow images because it's not code

[vapid olive]

great! now it works as intended, many thanks! ♥️

[acoustic arch]

any way to get 'cloudy' 'sunny' in local language when templating the weather state?

the UI tells me local language. calling the state in a template does not

[haughty breach]

Try {{ state_translated("weather.example") }}
Templating - state_translated

[acoustic arch]

nice! thx

[cosmic hamlet]

How can i check if state_attr('sensor.algemeen','entries')[0]['summary'] exists?

If i read it and it does not exist my markup does not parse

[bronze prawn]

I'm working on some assist custom sentences for weather related stuff. Right now I can do things like 'What will the high temperature be tomorrow' and 'Will it rain today'. Those are easy as I know today is item 0 and tomorrow is item 1 in the forecast entity.

The thing I would like to expand to is saying 'Will it rain Thursday'. Is there any easy way to translate what today is (like Sunday 0, Monday 1, Tuesday 2...) and then use that value to get the correct index? If that makes sense. Target day of week minus today day of week equals index sort of thing.

[marble jackal]

You need to take the current weekday with now().weekday() (Monday = 0)

And then calculate how many days there are between that and the wanted day

[bronze prawn]

Nice one. With a little searching I see Petro posted this clever way to determine what the current day is:
{{ ['Monday','Tuesday','Wednesday','Thursday','Friday','Saturday','Sunday'][now().weekday()] }}

I've modified it to use it this way:

{% set day_to_find = 'Friday' %}
{% set position = days.index(day_to_find) if day_to_find in days else None %}
{{ (position - now().weekday())|abs - 1 }}

I THINK this will give me what I need

[mighty ledge]

if you have the forecast, there's no reason to even know the day

choose the first day with rain. If it's today, say today, else say the name.

if you know the day already via voice, you'd want to reverse the map

if you're asking "is it going ot rain thursday"

[marble jackal]

Yeah, you need to map Thursday to the weekday, but you can already do that in your custom intent

So Thursday will be 3. Then you need to find out how many days that is from now, and take that item out of the forecast

Also note that there are weather integrations that don't include today in the forecast

They do all have the iso format datetime string, so you can also use that

[bronze prawn]

Yeah, that's what I think I'd like to try. I don't know how to do it though.

[mighty ledge]

{% set day = "Thursday" %}
{% set t = today_at() %}
{% set ns = namespace(days=[]) %}
{% for i in range(7) %}
  {% set dt = t + timedelta(days=i) %}
  {% set ns.days = ns.days + [(dt.strftime('%A'), dt.date()|string)] %}
{% endfor %}
{% set days = dict.from_keys(ns.days) %}
{% set forecast = response['weather.home'].forecast | selectattr('datetime', 'contains', days['Thursday']) | first | default({}) %}

[bronze prawn]

Thanks for this. I'll have to digest it. I'm getting a response undefined but it is probably because my forecast entity is different. Tried changing to

{% set forecast = response['sensor.daily_forecast'].forecast| selectattr('datetime', 'contains', days['Thursday']) | first | default({}) %}

But did not work.

[mighty ledge]

well yeah

you have to use a service call to get the forecast with get_forecasts and assign it to response

[bronze prawn]

oh. I see now. I have a sensor that updates rather than on demand. My provider only has daily forecast so I don't see the need to update on demand via service call.

[viscid oyster]

Hello everyone, I have another question/case: I have a sensor (energy_total) that registers the energy in a cumulative way (increasing number) and I need a daily value realtime value. I am sure there must be a million ways to do it, but I think the easiest would be to: 1. Store the value of the sensor at a fixed time every day (sensor_fixed). 2. Create a new sensor with the value of the difference: energy_daily=energy_total-sensor_fixed.

Does that look like a good idea? how can I store the value of the sensor at a predetermined time?

I see that there's an integration called "utility_meter", but I am not sure if that returns a real-time value, or just calculates a value at the end of the day

[viscid oyster]

--> Solved!! the utility_meter does give dynamic results, it was even easier than I expected, I used the utility meter and just created a new sensor with the daily value of the original one, I have already added it to the automations and seems to work correctly.

[mighty ledge]

You're not updating it on demand, the way you get forecasts in HA now is through the get_forecasts service call. It doesn't actually refresh the data, it gets the current cached forecast information.

[bronze prawn]

Thanks for this. Did not know. I am really having a hard time wrapping my head around this change. I guess I should go look at the post and reread it.

[tribal cedar]

Does anyone know of a way with light groups, to check (easily) if any of its children are having any issues/unavailability. I basically have a fairly good dashboard at this point, showing various groups of lights in each room. From time to time some of my lifx light strips within some groups go offline, but the overall group itself doesn't report it (I guess by design) and looks available.

I was wondering, without writing custom logic to check per entity within the group if they are having issues, if there was some feature/attribute on the group entity itself that can highlight eg 1 / 5 strips are unavailable, 4 / 5 are on, etc.

[marble jackal]

{{ expand('light.group') | rejectattr('entity_id', 'has_value') | list | count }}

This will give you a count of group members which are not available

[inner mesa]

really? with entity_id?

[tribal cedar]

Oh wow, thats great, many thanks!

[inner mesa]

{{ state_attr('group.downstairs_lights', 'entity_id')|reject('has_value')|list|count }}

[marble jackal]

Yes, has_value works on entity_id's

[inner mesa]

ok, wouldn't have thought to use it that way

[marble jackal]

I was going to propose that next, with the additional comment it only works if you don't include subgroups as member of the group

[inner mesa]

yeah, makes sense

[bronze prawn]

      {{ sensors|max(attribute="last_changed")|attr('entity_id') if sensors|length >= 1 else 'None'}}

Looking for some advice. This is how I am determining which microphone device is active for devices that use HA to determine if wake word is said. This works great.

I am now trying to incorporate devices that use onboard wake word (ESP32S3 satellites). These use a different type of detect (binary sensor). I am think of adding another group of just those devices and doing something like:

{%- set sensors_onboard_wakeword = expand(['group.assist_onboard_wakeword'])|selectattr('state', 'eq', 'on')|rejectattr('last_changed', 'eq', None)|list -%}```
I would then want to compare the sensors and sensors_onboard_wakeword variables in a similar way to the second line above.  Does that make sense or is there an easier way to get the one entity value returned?

[hallow plover]

Is it possible to extract the data from the weather forecasts? I have an entity called weather.metno (met.no weather data). When I use states to see the state attributes I don't see any numbers from the forecast. But when I add a forecast card it has all kinds of numbers in it.

{{ states.weather.metno }} gives me this, which does not seem helpful.

<template TemplateState(<state weather.metno=partlycloudy; temperature=58, dew_point=46, temperature_unit=°F, humidity=63, cloud_coverage=39.8, pressure=29.87, pressure_unit=inHg, wind_bearing=56.7, wind_speed=6.03, wind_speed_unit=mph, visibility_unit=mi, precipitation_unit=in, attribution=Weather forecast from met.no, delivered by the Norwegian Meteorological Institute., friendly_name=Forecast Wayne Manor, supported_features=3 @ 2024-04-17T17:43:12.651212-05:00>)>

[haughty breach]

https://www.home-assistant.io/integrations/weather/#service-weatherget_forecasts

[hallow plover]

so does that service.get_forecasts bit go in an automation/script?

[haughty breach]

Yes, or in the action block of a trigger-based template sensor (as shown in the Examples)

[bronze prawn]

{{ sensors|max(attribute="last_changed")|attr('entity_id') if sensors|length >= 1 else 'None'}}

{%- set sensors_onboard = expand(['group.assist_voice_mics'])|selectattr('state', 'eq', 'on')|rejectattr('last_changed', 'eq', None)|list  -%}
{{ sensors_onboard|max(attribute="last_changed")|attr('entity_id') if sensors_onboard|length >= 1 else 'None'}}

Still working on this. So I have this returning both but I want to only return one. There SHOULD only be one of these active at a given time. How do I return sensor if it is not set to none or sensors_onboard if it is not set to none? I think I have what I want but I just can't figure out how to return the value

[haughty breach]

{% set ent_list = state_attr('group.assist_mics', 'entity_id') + state_attr('group.assist_voice_mics', 'entity_id') %}
{{ (expand(ent_list | select('is_state', ['on','start'])) | rejectattr('last_changed', 'eq', None) | max(attribute='last_changed'))['entity_id'] | default('None', true)-}}

[modern torrent]

~~Hey, i was using the following template to get the precipitation probability of certain times in a day. Not sure what exactly changed in the updates but for a few days, maybe even a week this does not seem to work anymore:

    (state_attr('weather.openweathermap', 'forecast') | selectattr('datetime',
    'ge', now().replace(hour=11,minute=0).isoformat()) | selectattr('datetime',
    'lt',now().replace(hour=12, minute=0).isoformat())) |
    map(attribute='precipitation_probability') | list | max | round(0)}}```
this just gives the error `UndefinedError: No aggregated item, sequence was empty.` if i go under dev tools and check the template, but if i remove the `| max | round(0)` i get an empty list `[]` Guessing the first error is expected when the list is empty, i just don't get why the list is empty 😄

The weather card for this entity works and also shows all the precipitation_probability correctly for the diffrent times. Anybody able to help me with this? i am not to familiar with the templates and getting the last one to work took me ages~~

actually i just saw the issue with a message above, the forecast attribute is deprecated, well gotta figure out how this weatherget forecasts service works then
Edit: got it working as a template sensor that basically works the same as before but uses the weather.get_forecasts service 👍

[hallow plover]

When creating a template sensor in yaml I can add a delay_on value. Is it possible to do when creating a template entity via the UI?

[marble jackal]

No

[bronze prawn]

Thanks for this. I didn't realize you could have a list like that. This greatly simplifies things as I can mix both mic 'types' in the same group. Woot!

[opal dawn]

Trying to make a template sensor of the deviceclass timestamp.
I've checked it in the template examples part in HA and reports back a time.
But the created sensor in HA displays "unkown" , the logs dont show any errors about it....

this is the sensor:
- name: "Tijd warmte lamp uit" device_class: timestamp state: "{{ strptime(states('input_datetime.uv_lamp_uit'), '%H:%M:%S') - timedelta(hours=2) }}"

input_datetime.uv_lamp_uit has the following predefined state: 08:00:00

[marble jackal]

This is a lot easier:
state: "{{ today_at(states('input_datetime.uv_lamp_uit')) - timedelta(hours=2) }}"

[opal dawn]

That works pretty nice ! It does seem that the time being shown in the sensor is not the same as doing in the template enviroment of HA

Should | as_local be added?

This is shown in in the template example HA
state: "2024-04-18 18:00:00+02:00"
So it seems that i'm missing those +02:00 hours 😄

[opal dawn]

and this is the sensor state: 2024-04-18T16:00:00+00:00

[marble jackal]

It's the same time

One is in UTC, the other is in your local time

But it's exactly the same time

[inner mesa]

It's the way ISOwhatever works 🙂

[north bison]

afternoon guys... am presuming this is simple.. but am relatively new to HA... I have two ESPHome sensors at home... one in the bedroom.. and one in the living room... I have them tracking the RSSI of my Galaxy Watch4... and they are reporting its distance... how would I go about creating a sensor that reads these two values.. and whichever is lowest.. it can set it to that room... I'll them need to display that on my dashboard.. also.. sensor values for the RSSI look like this "-62 dBm" etc... so I have no idea how I would check if one is lower than the other.. can anyone point me at a template and sensor I could adapt for this? and please remember I am kinda new to this automation stuff... thanks in advance..

am presuming I need a template for this... I add those to configuration.yaml, right?

never done a template before.

[hallow plover]

In the met.no forecast results, what is precipitation? Is it the chance of precipitation or the total amount expected?

[inner mesa]

pretty sure it's the amount expected:
precipitation: 0.01

[hallow plover]

{'condition': 'partlycloudy', 'datetime': '2024-04-18T17:00:00+00:00', 'wind_bearing': 330.0, 'temperature': 56, 'templow': 45, 'wind_speed': 16.53, 'precipitation': 0.0, 'humidity': 33}

[cosmic hamlet]

the LLM of My washing maschine sometimes want to post none working twitter links on his mastodon acount. How can i filter out any word containing twitter from a string?

regex_replace('\b\Stwitter\S\b', '')

[opal dawn]

So using this in an automation would trigger it on the right time? Will give it a try thanks !!

[marble jackal]

It's the expected amount of rain, some integrations also provide precipitation_probability

This is everything I see in a daily forecast

    - datetime: "2024-04-19T00:00:00+02:00"
      condition: rainy
      precipitation_probability: 80
      wind_bearing: 308.5
      cloud_coverage: 79
      temperature: 10.7
      apparent_temperature: 8.7
      templow: 5.8
      pressure: 1009
      wind_speed: 30.8
      precipitation: 7.6
      wind_gust_speed: 56.6
      uv_index: 3
      dew_point: 7.9
      humidity: 86

[marble jackal]

Oh wait, you had hourly, I have this there

    - datetime: "2024-04-19T09:00:00+02:00"
      condition: rainy
      wind_bearing: 283
      precipitation_probability: 92
      cloud_coverage: 100
      uv_index: 0.1
      temperature: 9
      apparent_temperature: 5.2
      dew_point: 7.8
      pressure: 1007.1
      wind_speed: 25.9
      precipitation: 0.2
      humidity: 93

[languid sandal]

I have a rgb strip connected through dynalite but it creates the rgb channels different not into one rgb light ? Can Somebody please tell me that how can i use template to convert it into a rgb bulb in homeassistant.

[summer salmon]

is it possible to render a template through the home assistant RESTful API?

[mighty ledge]

what do you mean

[languid sandal]

Please! tell me if this could be done or not ?

[marble jackal]

you can combine the 3 lights in one template light

[languid sandal]

I have tried it but i can't make it as a working rgb bulb. Also new to home assistant so sorry for anything stupid said by me

[summer salmon]

Mainly curious.. if I could do a ha template from a py or if i have to do a template sensor in ha and grab the state from that entity

[mighty ledge]

You want HA to render a template for you? Is that what youre asking?

Like feed a template to an api and it responsds with a result?

[summer salmon]

Yeah? Or is that weird? As i said im just curious.. since I can do it from siri shortcuts

[mighty ledge]

not wierd

https://developers.home-assistant.io/docs/api/rest

there's a websocket api and a rest api. You don't need template sfor the websocket api, but the rest api has the ability to render templates

[mighty ledge]

You have to provide more info, yes it can be done. Without knowing what i nformation you have, we can't help.

[summer salmon]

I was just there, how did I miss it, facepalm.
Thanks

[winter forge]

      "universal" )| select('search',  "chromecast" ) |
      select('is_state', 'playing') | list   | map(attribute='last_changed') | sort(reverse=True) | first | default(now()) }}```

This gives me the timestamp of the last chroemcast that turned to play. How can I see it's entity id, while keeping the sorting?

[mighty ledge]

| sort(attribute='last_changed', reverse=True) | map('entity_id')

[winter forge]

I get TemplateRuntimeError: No filter named 'entity_id'.

[mighty ledge]

map(attribute='entity_id')

[winter forge]

That results in "UndefinedError: 'str object' has no attribute 'last_changed'"

Just {{ integration_entities("universal") | select( search', "universal" )| select('search', "chromecast" ) | select('is_state', 'playing') | list | map(attribute='last_changed') | sort(reverse=True) | first | default(now()) }} works

[mighty ledge]

{{ integration_entities("universal") | select('search', 
      "universal" )| select('search',  "chromecast" ) |
      select('is_state', 'playing') | expand | sort(attribute='last_changed', reverse=True) | map(attribute='entity_id') | first | default(None) }}

[winter forge]

I get null

[mighty ledge]

you're mixing state objects and entity_ids

you can't get an attribute from a non-state object

[winter forge]

so I need to use the throttled state.* ?

[mighty ledge]

no, use what I wrote

[winter forge]

Oh, it gave me null at first

now it works

[languid sandal]

I have a rgb controller which i have added using philips dynalite integration but it adds it in seperate 3 channels of red green and blue, I want to combine them and create it as a rgb bulb. I can also send you the screenshot, if you'd want

[thorny snow]

Hi, can someone tell me how I would find todays highest temperature as a state? I want to send that data point to tts and I haven't been able to find it in states.

[marble jackal]

Temperature of what? Your CPU? Living room thermostat? Body temperature? Weather forecast?

[red moat]

Hi all,
I was trying to finish the work on my garagedoor opener, I started a while ago.
I currently have this template that works:

service: system_log.write
data:
  level: error
  message: >
    {% if python_script_output['authorized'] == True %} "Approved!" {% else %}
    "Denied!" {% endif %}

It writes to the system log when the output of a previous python script was True.
I also have a relay that automatically toggles back to "off" when turned on. But... I have no clue how to integrate this relay into the above template.
I tried to follow this text: https://www.home-assistant.io/integrations/switch.template/
But in confuses the heck out of me. The opening text makes it sound like it's what I need, but in the body it's about reading a sensor?
Anyone who could point me in the right direction?

[tribal cedar]

Is there any documentation describing the order in which HA processes things like the values of custom sensors which use templates.

When referencing certain sensors in the developer tools as well as some custom sensors which also reference such sensors, there seems to be a visible lag between when they update.

I'm not sure for example if an automation triggers because sensor x changes, if that automation references inside some custom sensors y (which uses a template that also references the value of x) am I guaranteed sensor y will have its updated value once referenced in said automation or could it update a second later meaning the automation ends up seeing the old / non updated version.

[plain magnet]

@crude crest I converted your message into a file since it's above 15 lines :+1:

[fossil venture]

No that is not possible. You can see this in the documentation.

[languid sandal]

@mighty ledge Help plz

[remote void]

Hello! I haven error in my logs and I'm having trouble finding out where the error comes from:

Logger: homeassistant.helpers.template
Source: helpers/template.py:771
First occurred: April 18, 2024 at 11:47:09 AM (15 occurrences)
Last logged: 12:00:37 PM

Error parsing value: 'value_json' is undefined (value: , template: {"in_progress": {{ iif(value_json['update']['state'] == 'updating', 'true', 'false') }} })
Error parsing value: 'value_json' is undefined (value: , template: {{ value_json['update']['installed_version'] }})
Error parsing value: 'value_json' is undefined (value: , template: {{ value_json['update']['latest_version'] }})

How would I go to find which template is causing the error? I have no clue where that could be. Obviously there's a double-i in the if ...

[haughty breach]

iif() is a valid function.

[mighty ledge]

search for the template itself. If you can't find it, it's coming from MQTT

[austere lark]

Am I doing something wrong here?

{% set some_list = ["a", "b"] %}

{% macro test(some_list_arg, some_bool) -%}
    {{ some_list_arg | length > 1 and some_bool }}
{%- endmacro %}

{{ test(some_list, true) or test(some_list, false) }} {# Returns True #}
{{ test(some_list, false) or test(some_list, true) }} {# Returns False #}

Do macros use some sort of weird caching? Why would it suddenly return false in the second statement 🤔

Oh I thought it might have had to do with list filtering but that's not even it

{% macro test(some_bool) -%}
   {{ some_bool }}
{%- endmacro %}

{{ test(true) or test(false) }} {# Returns True #}
{{ test(false) or test(true) }} {# Returns False #}

Am I using macros completely wrong here?

https://community.home-assistant.io/t/2023-4-custom-template-macros-and-many-more-new-entity-dialogs/556528/436

Welp

Thanks Petro <3

[stuck grail]

Is there currently an efficient (1-liner) way to generate a list of entity_ids assigned to a floor that have a specific label applied to them?

[weary elk]

Hi everyone, is it possible to have relative_time in right locale ?

[marble jackal]

@weary elk https://github.com/TheFes/relative-time-plus

[marble jackal]

{{ floor_areas('first_floor') | map('area_entities') | sum(start=[]) | select('in', label_entities('some_label')) | list }}

[stuck grail]

@marble jackal Thank you! I has just stumbled across another post you shared which was similar and got it to work. I appreciate the help.

[stuck grail]

I guess I'll take my line of questioning a little further...I'm trying to create a template sensor that triggers whenever one of the entities matching the filter above changes state, but is not 'unknown' or 'unavailable' (which appears to require the use of 'has_value'.

Basically, I'm trying to dynamically trigger a sensor update from entities with a certain label.

Is such a configuration possible? I'm a little confused by how template triggers work (or don't) with more than one entity.

[marble jackal]

So you want to trigger on any state change of such an entity. You can create a template sensor which has the most recent last_changed value of those sensors, and trigger on a state change of that template sensor

[haughty breach]

Template triggers only fire when the value they render goes from false to true. As TheFes commented it is often easier or necessary to use an intermediary sensor so you can access the other trigger types.

[stuck grail]

Unfortunately, creating intermediate sensors is what I'm trying to work around. The goal of triggering based on something tagged with a label is to avoid having to manually creating helpers for those labeled entities.

Perhaps I am better off triggering on State Changed events end evaluating labels from there.

[keen geyser]

It 's possible to define global variable for a card, for example to factorize this code ?
https://pastebin.com/dbskuY9V
For exemple, count the number of light at the beginning of the card, and not 2 times in the card :
{{ label_entities('lumieres') | expand | selectattr('entity_id', 'in', area_entities("[[room]]")) | selectattr ( 'state' , 'eq' , 'on' ) | map(attribute='entity_id') | reject('is_hidden_entity') | list | count }}

[inner mesa]

not in that card

[keen geyser]

and in which one we can do that ?

[remote void]

where would I do that? But that said, i guess it's coming from z2m then ...

[mighty ledge]

you cna't do anything about it if it's coming from z2m

[remote void]

sure, but I also can't tell if it actuall is coming from z2m. I was just checking my logs trying to resolve a bunch of errors it throws.
can you elaborate what you mean with "search for the template itself"? knot in my brain prevents me from making sense of it.

[inner mesa]

You should just make a template sensor for that and then reference it wherever you need it

[keen geyser]

the problem is that it depend of [[room]] variable

[inner mesa]

where does that come from?

[keen geyser]

decluttering card

[inner mesa]

ah, gets even more complicated

you can presumably make a Jinja macro and use that. beyond that, you're already doing a bunch of stuff that I have no experience with

[keen geyser]

i have a generic card for all my rooms, but i hate the fact that i need to compute the same data 2 or 3 times in the card ...

[haughty breach]

Only tested for basic use so far...

{% set ts = now() - timedelta(seconds=1) %}
{% set newest = expand(floor_areas('Your Floor') | map('area_entities') 
| sum(start=[]) | select('in', label_entities('Your Label') | select('has_value') | list ))
| sort(attribute='last_changed', reverse=1) | map(attribute='last_changed') | first | default(ts, 1) %}
{{ newest > ts }}

[winter forge]

I am still rushing with pulling all entities from an area 😦

I tried both:

    | sum(start=[]) | select('match', '^light.') | select('is_state','off') |
    unique | list }}```

```{{  area_id("binary_sensor.group_kitchen_motion_occupancy") |  map('area_entities') | map('area_entities')
    | sum(start=[]) | select('match', '^light.') | select('is_state','off') |
    unique | list }}```

I am not sure why this is not working.  But I am very noob with Jinja2

Derp, I was missing square brackets somehow.

    | sum(start=[]) | select('match', '^light.') | select('is_state','off') |
    unique | list }}``` works

[inner mesa]

"isn't working" isn't enough

[winter forge]

Sorry, it's outputing nothing.

Why do I need to have square brackets around the area_id() ? Knowing how it works would help me memorize it

[inner mesa]

because you're using map()

[winter forge]

And map needs an array?

[inner mesa]

it iterates

[winter forge]

Ah! gotcha

So "test" is bad. but ["test"] and ["test1","test2"] is chill

[inner mesa]

{{ area_id('Kitchen')|area_entities }}

you were iterating over each character in the area_id

[winter forge]

Aaaaah!

Ok thanks. Sorry, I have no formal coding formation. Well, beside a 100hours class during my tech support course

Still learning stuff every day

[stuck grail]

Ooh…interesting. I’ll play with this. Thank you.

[sick ice]

in developer > states, I notice that the state of the entity doesn't match what is shown in the device view.
For example, state of climate.izone_controller_200011148 is fan_only, where on the device page, logbook or climate card, it shows as Fan only

Is this more human friendly name available somehow? I'm using {{states('climate.izone_controller_200011148')}} in a card but would prefer the latter. I'm sure this is described better somewhere I just don't have the right terminology to find it.

[inner mesa]

https://www.home-assistant.io/docs/configuration/templating/#state-translated

[sick ice]

well look at that. Once again, there's a feature for it.

I think that could be applied in A LOT of places throughout my dashboards. yeesh.

[languid sandal]

Anyone any solution for this ?

[mighty ledge]

My man, you have to provide more info. We have no idea what entities you have and what their states are. Secondly, no one is going to write the whole thing for you. Try something , anything, then ask questions when the things you try don’t work.

[languid sandal]

Sorry, The channels which are lights have brightness attribute, also i have tried it by creating the template from chatgpt but it dosen't work properly. Would it help if i send you the screenshots ?

[mighty ledge]

Post what you've tried here, as text. No screenshots.

Make sure you format it properly.

so it reads as code, not text

[languid sandal]

Ok, I'll Paste it

[plain magnet]

@languid sandal I converted your message into a file since it's above 15 lines :+1:

[mighty ledge]

So the brightness of each light is the color rgb value?

where are the rgb values coming from? And how do you adjust the rgb values?

that definitely looks like a Chatgpt thing making up crap, it doesn't appear to actually use anything in yoru system.

[thorny snow]

I'm trying to get a value, 0, that returns from a json as true but I can't tell what I'm missing, any ideas?

message: >- You have an alert: {{ trigger.json.monitor.name }} is down and {{ trigger.json.heartbeat.status }} {% if ('trigger.json.heartbeat.status') == '0' %} really down {% endif %}

trigger.json.heartbeat.status does come back as 0, when I test it with tts, it says '0'.

[buoyant pine]

  message: >-
    You have an alert: {{ trigger.json.monitor.name }} is down and {{ trigger.json.heartbeat.status }} {% if
    trigger.json.heartbeat.status == '0' %} really down {% endif %}
``` but are you sure that `trigger.json.heartbeat.status` is actually returning `'0'` (zero as a string) as opposed to `0`  (zero as a number)?

[thorny snow]

that, I'm not sure. When I looked at the json from the webhook it was 0 in the field and not zero.

This is the json for the heartbeat:

{ "heartbeat": { "monitorID": 38, "status": 0, "time": "2024-04-22 14:43:41.958", "msg": "connect EHOSTUNREACH 192.168.2.240:443", "important": true, "duration": 0, "timezone": "America/New_York", "timezoneOffset": "-04:00", "localDateTime": "2024-04-22 10:43:41" },

the only other thought is that it returns '0,' and not '0' ...?

[buoyant pine]

nah, it's returning 0

[thorny snow]

sigh, right

[buoyant pine]

did you make the tweak that i shared above though?

[thorny snow]

I'll try that now

didn't work, tts said blah is down and 0, but didn't say 'really down'

[mighty ledge]

ya did something wrong still

[thorny snow]

lol, yes, I did

[mighty ledge]

trigger.json.heartbeat.status == 0

[buoyant pine]

oh whoops yeah, that was the implication that i didn't actually state out loud lol

[mighty ledge]

that and he had 'trigger.json.heartbeat.status' in quotes

[thorny snow]

so just remove all the quotes?

[mighty ledge]

just use if trigger.json.heartbeat.status == 0

[buoyant pine]

yeah i took that out of my example though

[mighty ledge]

🤷‍♂️

[thorny snow]

damn it, thanks guys that worked

can I ask why that worked?

[buoyant pine]

'0' and 0 aren't the same thing

same as 'trigger...' and trigger.

[thorny snow]

right, I get theyre' not the same, so what are they?

[buoyant pine]

'0' is a string, 0 is a number. computers interpret those differently

[thorny snow]

thanks!

sigh, I appreciate the help and the teaching

but there are some occasions where a number might be a string, just not here, right?

[buoyant pine]

yeah, if it's in quotes

[thorny snow]

which clearly in the json it wasn't

[buoyant pine]

correct

[thorny snow]

thanks again

[thorny snow]

thanks!

[languid sandal]

As in the code that light.fall_red ,green and blue are the different channels of rgb but are imported as different light by the philips dynalite integration. So, i want to use them and make make a rgb bulb and they only have brightness attribute

[winter forge]

{{ [area_id('binary_sensor.group_office_motion_occupancy')] | map('area_entities') | sum(start=[]) | select('search', 'speakers') | select('is_state','playing') | unique | list }}

How would I go about adding the integration_entities('universal') filter to this template? I want to limit the pulled entities by only checking for devices in that integration

I tried a few permutations with no luck.

Amongs them : {{ [area_id('binary_sensor.group_office_motion_occupancy')] | map('area_entities') | integration_entities('universal') | sum(start=[]) | select('search', 'speakers') | select('is_state','playing') | unique | list }}

[inner mesa]

{{ [area_id('binary_sensor.group_office_motion_occupancy')] | map('area_entities') | select('in', integration_entities('universal'))|sum(start=[]) | select('search', 'speakers') | select('is_state','playing') | unique | list }}

that's a roundabout way to do that, though

[winter forge]

Roundabout? What is that?

[inner mesa]

what is your goal with the first part there?

you're giving it a specific entity, only to get the area from it?

just start with area_entities('whatever')

[winter forge]

I am user trigger.entity_id in lieux of the hard coded binary sensor

[inner mesa]

ok, still

{{ area_id('light.dr_light_group')|area_entities }}

making a list and then using map() are extra, unnecessary steps

[winter forge]

Thanks for the info, i'm very noob with templates

[atomic blade]

Is there a way to work with state durations in templates? Like determining if an entity has been in a given state for a certain duration

Searching the docs isn't hitting any keywords I'd expect

[sacred sparrow]

Sensor is showing 79 but the template is still showing 'Good'. What am I doing wrong here?

        {% if aqi >= 0 <= 50 %}
          Good
        {% elif aqi >= 51 <= 100 %}
          Moderate
        {% elif aqi >= 101 <= 150 %}
          Poor
        {% elif aqi >= 151 <= 200 %}
          Very Poor
        {% elif aqi >= 201 <= 250 %}
          Severe
        {% else %}
          Very Severe
        {% endif %}```

[buoyant pine]

Just do

{% if aqi < 50 %}
  Good
{% elif aqi < 100 %}
  Moderate
...

What you're doing now isn't the proper way to define a range, but you also don't need to be that specific

[sacred sparrow]

ah great! thank you 🙂

[sacred sparrow]

would you know why it wouldn't work for this:
https://pastebin.com/8UMCkixX

[buoyant pine]

What isn't working? You don't have an else which would be an issue if it's 300 or higher

[sacred sparrow]

the colours aren't changing

I can do {% elif states(config.entity) | int <>300 %} for the other fix

[buoyant pine]

Oh you can't use templates there

[sacred sparrow]

It works when it's not in a conditional

[buoyant pine]

Orly

[sacred sparrow]

haha yeah weird!

I did it so the colours are on the main entity and not on the conditional instead and it works now so I'll settle for that

[thin pivot]

sensor.keul_last_update_time shows this: 2024-04-22 21:25:31.474553-06:00
I'm Trying to extract day (and time) from this sensor

   {%- set day = (states.sensor.keul_last_update_time).strftime('%w') %}
          {%- set days = ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday", "Saturday", "Sunday"] %}
          {{- days[ day | int -1 ] }}

I get this Error: 'homeassistant.helpers.template.TemplateState object' has no attribute 'strftime'

It works on another sensor but not this one.

[inner mesa]

You're calling that on a state object

{{ ("2024-04-22 21:25:31.474553-06:00"|as_datetime).strftime("%A") }} -> Monday

[worldly mason]

A simple (ish) question if anyone has any ideas.

I have a switch that I am wanting to put either a PIN or a CONFIRMATION in front of. I have looked at using Alarm Panel (Manual) but before I head down that route, I am wanting to know if there are any other tricks out there that I can use?

[thin pivot]

||{{ ("2024-04-22 21:25:31.474553-06:00"|as_datetime).strftime("%A") }}
Gives Monday as output but this gives a template error

{%- set day = (states.sensor.keul_last_update_time |as_datetime).strftime('%w') %}
          {%- set days = ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday", "Saturday", "Sunday"] %}
          {{- days[ day | int -1 ] }}

[marble jackal]

An entity is in its current state since the last time it changed. So now() - states['your.entity'].last_changed will be the duration it has been in that state

@thin pivot You are using as_datetime on the entire state object

You need to use it on the state

[thin pivot]

I'm just trying to get the day out of that sensor....

So there no way to do this?

[marble jackal]

Sure there is

{%- set day = (states('sensor.keul_last_update_time') |as_datetime).strftime('%A') %}

[thin pivot]

That outputs
Result type: string
This template listens for the following state changed events:
Entity: sensor.keul_last_update_tim

Not the day.

I'll post it on the forums.

[wanton sapphire]

It listens to state changed events of that sensor and it outputs the day. Isn't that what you wanted to acheive?

[thin pivot]

Amazing, someone answered right away . This works
{{ (states('sensor.keul_last_update_time')|as_datetime).strftime('%A') }}

[fickle sand]

That's exactly the same as TheFes posted, but he put it in a variable, so to get the output you had to at:
{{ day }}

For reference see this pinned message #templates-archived message

[thin pivot]

I've now got exactly the text output i was trying to get but I want to add a line feed after the day/time. I tried /n and /r to no avail

{{ (states('sensor.keul_last_update_time')|as_datetime).strftime('%A %I%M%p')}} 
/n {{states('sensor.keul_detailed_description')}}

Is there a trick to escaping chars?

[fickle sand]

Use {{ '\n' }} for a new line

[gentle sundial]

Hi!
I have an attribute ( sensor.mySensor.myAttribute ) which contains an array.
Now I wanna check, if the average is X, Y or Z.
Don't know, where to start.
Any hint ist appreciated!
Thanks - M.

[marble jackal]

{{ state_attr('sensor.your_sensor', 'your_attribute') | average in [x, y, z] }}
Something like that?

[atomic blade]

Thanks, that sounds like it would work well!

[formal ember]

service: light.turn_off
target:
  entity_id: >-
    {{ states.light | map(attribute='entity_id') | reject('eq',
    'light.wled_christmas_tree_master','light.wled_christmas_tree','light.wled_christmas_tree_star')
    | list }}

this template used to turn off all my lights bar my christmas tree when that is being used. it no longer works. has something changed with templating or ha that won't allow this?

error says Failed to call service light.turn_off. Error rendering service target template: TypeError: eq expected 2 arguments, got 4

[fickle sand]

    {{ states.light | map(attribute='entity_id') | reject('in',
    ['light.wled_christmas_tree_master','light.wled_christmas_tree','light.wled_christmas_tree_star'])
    | list }}

eq expects only one item to search for, while in can iterate over a list with multiple items

[formal ember]

ah right

wonder why it used to work and not anymore, thanks @fickle sand !

Failed to call service light.turn_off. Error rendering service target template: TypeError: test_in() takes 2 positional arguments but 4 were given

still getting this unfortunately

actually working now, my bad!

[fickle sand]

Hahah, you also needed to convert the entities into a list

[cosmic hamlet]

{% for calendar, events_list in events.items() %}
  {% set all_events = all_events + events_list %}
{% endfor %}

why gets all_events reset outside the for loop?

[inner mesa]

you need to use a namespace

#templates-archived message

[cosmic hamlet]

O thanks. that notice helped.

can i use dutch words like vandaag(today) and morgen(tomorrow) in time defined functions? voice my voice assistant to show the agenda of today tomorrow?

[narrow surge]

Is it possible to query the state_changed event and get the last_changed time but only if it was triggered by a specific id/parent_id/user_id?

[inner mesa]

yes, you would use a condition based on the context

[narrow surge]

Yep, I'm trying to get rid of a timer which is started based on a specific id/parent_id/user_id. And change it into a condition, so the condition will be true after 1 hour after a specific a specific id/parent_id/user_id changed the entity for the last time.

[cosmic hamlet]

I cant get the namespace to work inside a automation service call. works fine in template

[mighty ledge]

You can't use namespace across multiple templates

[cosmic hamlet]

https://paste.debian.net/1314974/

inside a single service call

would be a shame i can hear my agenda for today in the morning but cant use it with a voice command.

[mighty ledge]

looks fine, so it must be your service call getting the response data

[cosmic hamlet]

metadata: {}
data:
  start_date_time: '{{ now().strftime(''%Y-%m-%d 00:00:00'') }}'
  end_date_time: '{{ now().strftime(''%Y-%m-30 23:59:59'') }}'
target:
  entity_id:
    - calendar.persoonlijk
    - calendar.verjaardagen
    - calendar.feestdagen_in_nederland
response_variable: data```

OH WAIT

thanks

[mighty ledge]

you need to iterate the data dictionary

[cosmic hamlet]

today is no agenda. holy macaroni

[mighty ledge]

no, tha'ts not it

data won't have .events

[cosmic hamlet]

im listening

[mighty ledge]

data['calendar.xyz'].events

you need to iterate the calendars

[cosmic hamlet]

wait...

old code..

im making bad mistakes..

turn of coding mode watching a movie or something..

[mighty ledge]

{% for entity_id, evts in data.items() %}
  {% for event in evts %}
    ...
  {% endfor %}
{% endfor %}

secondly, you don't need namespace

{{ data.values() | list | sum(start=[]) | sort(attribute='start') ....

not sure what you're doing with that match... if you're trying to get for today... then...

[cosmic hamlet]

I thank your helping efford petro. but im toast for today.

will bug you again in some days.

it is home assistant needs to be fun.

[mighty ledge]

well anyways

{{ data.values() | list | sum(start=[]) | sort(attribute='start') | rejectattr('start', '>', (today_at() + timedelta(days=1)).isoformat()) | map(attribute='summary') | join(', ') }}

[primal copper]

trying to do things the "proper" way and use an input_helper for an upcoming datetime -- is there any way to set it to "off" or null? or must it always contain a date?

my use case: I want a helper that shows the next upcoming game on a schedule if it's in the next two weeks -- otherwise, I want it to have no value

[marble jackal]

It always has to have a value, but you can set it to midnight 1st of January 1970 or 31st of December 2999

[primal copper]

okay, figured -- thanks for the confirmation 🙂

[torpid crag]

Hi All, Is there any way to work around this error in a template helper - if so how please? The plex player is currently offline due to the TV being off 🙂
2024-04-24 09:40:16.877 WARNING (MainThread) [homeassistant.helpers.template] Template variable warning: 'homeassistant.util.read_only_dict.ReadOnlyDict object' has no attribute 'media_library_title' when rendering '{% if 'Movie' in states['media_player.plex_plex_for_samsung_tv_2020'].attributes.media_library_title %} true {% else %} false {% endif %}'

[inner mesa]

sure

[torpid crag]

Good point, I should not just ask if there is a way todo it 😄

[inner mesa]

{{ states.media_player.plex_plex_for_samsung_tv_2020.attributes.media_library_title is defined and 'Movie' in state_attr('media_player.plex_plex_for_samsung_tv_2020', 'media_library_title') }}

if you're ever return "true" or "false", you should just return the test itself

[torpid crag]

Thanks! I see - always learning.

[umbral ridge]

anyone have any experience with creating shopping lists with the mealie api? I'm struggling with getting them to sync...using this post for reference
https://community.home-assistant.io/t/mealie-in-ha/603560/27 (ref my.spider.died
Michael post)

[polar venture]

how can I check if a sensor value is unavailable or unknown?

[umbral ridge]

nvm , I just figured out how to do at least a one way sync to HA, now to figure out the other way...

[lucid thicket]

has_value as either a function or a filter. See https://www.home-assistant.io/docs/configuration/templating/#states

[plain magnet]

@sonic pivot I converted your message into a file since it's above 15 lines :+1:

[marble jackal]

@sonic pivot which integration is this, are you sure that field supports templates?
Anyway, your template can be simplified, expand is not required.
And you should not use a hyphen there, use the template directly as input for the field.

entities: >
  {{
        states.light
        | selectattr('state', 'eq', 'on',)
        | rejectattr('entity_id', 'in', area_entities('Master Bedroom'))
        | map(attribute='entity_id')
        | list
  }}

[twin compass]

Anyone can help me debug this?

sensor: - platform: rest resource: "https://graph.facebook.com/v19.0/oauth/access_token?grant_type=fb_exchange_token&client_id=XXX&client_secret=XXX&fb_exchange_token={{ states('sensor.facebook_access_token_rest') }}" name: "Facebook Access Token REST" value_template: "{{ value_json.access_token }}" json_attributes: - access_token scan_interval: 00:01

I keep getting this error when I process it

'dict object' has no attribute 'access_token' when rendering '{{ value_json.access_token }}'

I double checked that the resource is correct when initiating and "access_token" is a response in the GET

is there a way I can see what the return of the call is?

This is an example of the call's response:

{ "access_token": "EAAN2AUUqHjEBO6HhiRGGMdrUh137c3jWlJDO0XDJj905AQCqGCi3Ioe3gp9vVd4KUYDhKEljLildk9GFTRZBc86ZCj78nE2bUg4kzHDZBTUSZAXUSluwf5YxPjxwx0jFtqvxEpGuZCfe94Wpf9jIsKoykS4h8SgdP0Fue2UlZBFoRAJ80towdF7vKQDsPsRtivDBTRjhUK4rQyHg85", "token_type": "bearer", "expires_in": 5169136 }

[mighty ledge]

uh, circular reference

you're creating the entitty that the resource is using

chicken-egg

[inner mesa]

Yeah, the call is probably giving back garbage or an error because the token is old or missing

[mighty ledge]

Yep

[twin compass]

That is on purpose as I am trying to refresh the tokens everytime

I give it the initial value and then i want it to keep refreshing it daily

I actually managed to do it with node-red 🙂

and storing it in a sensor 😄

[mighty ledge]

if you want to do that, then you can do that with

https://graph.facebook.com/v19.0/oauth/access_token?grant_type=fb_exchange_token&client_id=XXX&client_secret=XXX&fb_exchange_token={{ states('sensor.facebook_access_token_rest') if states('sensor.facebook_access_token_rest') | has_value else "other token" }}

[cosmic hamlet]

Fout: Error rendering data template: TypeError: can only concatenate list (not "dict") to list

I'm back feeling better. time to tackle this one

[mighty ledge]

did you use the template exactly? It's a list of events not a dictionary

[cosmic hamlet]

let me look

    {% for entity_id, evts in data.items() %}
  {% for event in evts %}
    {{event}}
  {% endfor %}
{% endfor %}

gives me the events i need to sort. I dont know where the {{data.values() | list enz comes in place

I dont get why my template with namespace is not working in the automation

[mighty ledge]

which service are you using?

list_events or get_events?

[cosmic hamlet]

https://paste.mozilla.org/5qarrXmn#L16

the new one

getevents

[mighty ledge]

your response variable is data

and you aren't using it in any template

nm, I see it

[cosmic hamlet]

it works in the templating.

[mighty ledge]

data.events should not work

because data is going to return a dictionary of entity_id: event list pairs

[cosmic hamlet]

oh. then i have errors. in the template test data. A window where you can past yaml data in the template to use would be a nice feature

[mighty ledge]

ok, i see what's wrong

{{ data.values() | map(attribute='events') | sum(start=[]) | sort(attribute='start') | rejectattr('start', '>', (today_at() + timedelta(days=1)).isoformat()) | map(attribute='summary') | join(', ') }}

[cosmic hamlet]

OKe that gives something.

oke also sorts correctly how do i add the time in HH:mm?

this is the bonus points question

[marble jackal]

If you need both the summary and the start time, you need a namespace and a for loop

[cosmic hamlet]

 {% for events in  data.values() | map(attribute='events') | sum(start=[]) | sort(attribute='start')  %} 
   {{events.summary}}  
   {% if  events.start.split('T')[1]  %} 
   om {{events.start.split('T')[1][:5]}}   
   {% endif %} {
% endfor %}

[mighty ledge]

I'm not sure why you use the goofy spacing, it makes it harder to read and write

[cosmic hamlet]

ha made it googfy

[mighty ledge]

{% set ns = namespace(items=[]) %}
{% for event in data.values() | map(attribute='events') | sum(start=[]) | sort(attribute='start') | rejectattr('start', '>', (today_at() + timedelta(days=1)).isoformat()) %}
  {% set t = event.start | as_datetime | as_local %}
  {% set ns.items = ns.items + [ t.strftime('%H:%M - ') ~ event.summary ] %}
{% endfor %}
{{ ns.items | join(', ') }}

[cosmic hamlet]

regression.

it works for today only I want it also work for tomorrow. and your solution shows the 00:00 time of all day events

[mighty ledge]

you can add those into the loop, just add timedelta(days=2) instead of 1

and you can skip the events if the time == 00:00

[cosmic hamlet]

does days=1 works if all data is of tomorrow?

[mighty ledge]

it's a time delta

it's taking midnight today_at() adding 1 day to it

and it's rejecting all events beyond that time

if you want events for tomorrow and today, just change the 1 to a 2

[cosmic hamlet]

in the end I want a voice command for today tomorrow or a day of the week. So it should ignore it and use all data in the scope of the given data.

    {% set ns = namespace(items=[]) %}
    {% for event in data.values() | map(attribute='events') | sum(start=[]) | sort(attribute='start') %}
    {% set t = event.start | as_datetime | as_local %}
    {% if t.strftime('%H:%M') == '00:00' %}
    {% set ns.items = ns.items + [ event.summary ] %}
    {% else %}
    {% set ns.items = ns.items + [ t.strftime('%H:%M - ') ~ event.summary ] %}
    {% endif %}
    {% endfor %}
    {{ ns.items | join(', ') }}

[cosmic hamlet]

Is there a way i can get the name of a day in dutch with out manual translation?

[mighty ledge]

you can make a list of the days in order starting on monday. Then use thelist[t.weekday()]

[rose sail]

Hello, I'm having some troubles creating a template. I want to display it as door in HomeKit and reading the documentation, I understood that I have to create a cover template and set the device_class as door.
The problem is that I also have to use "set_cover_position" but the device I want to trigger is a lock that only has open/closed states.

I created a template that works but when I trigger it in Apple Home, it does get stuck to "unlocking" state. I would like to change it to closed after some seconds, likes the lock actually does. Any hint?

[cosmic hamlet]

Thanks petro got it worked out.

[bronze prawn]

In an effort to make the installation of my project easier, I'd like to try and create an extension integration at least for use of setting up the custom sensor devices I'm currently using. One big problem with this approach: I don't know much of anything about building these and the docs are really involved.

Does anyone know of an example custom component that illustrates how the sensor configuration can be done without the extra stuff for the control of those devices? I think if I can find just the part I need I can probably modify that enough to accomplish my goal.

[mighty ledge]

what's an 'extension'?

[bronze prawn]

Pardon. Using the wrong term. Meant integration

[mighty ledge]

the development documentation covers creating integraitons

for help, use the #developers or #devs_core-archived channels

https://developers.home-assistant.io/docs/creating_component_index

[sly adder]

I have a webhook trigger which includes some data (let's say an animal). I want to have a dashboard card with the latest animal received through that webhook and another card with all recent animals it sent. What is my best option for that? A text helper?

[mighty ledge]

a template sensor

using a webhook trigger

[sly adder]

Thanks, I'll take a look!

[bronze prawn]

Thanks. I may be ahead of my skill level on this one. I have read through these docs. I find it easier to see examples specific to what I'm trying to accomplish. I'll check in devs. Thanks

[mighty ledge]

Pick an integration in CORE that does something similar to what you're trying to do

[bronze prawn]

    - name: AssistSat_ViewLR
      attributes:
        type: view_audio
        mic_device: "sensor.firehd_7_stt"
        mediaplayer_device: "media_player.tabletfullkiosk"
        display_device: "sensor.tabletfullkiosk_browser_path"
        browser_id: "Tabletfullkiosk"      

I'm really wanting to create something that will allow the user to set these attribute values and have the other attributes (not listed) set up as defaults. This would greatly simplify the need for the users to have to edit YAML. I'm trying to make it easy to add and manage these devices through the UI

I'll take a look at what is provided in core and see if there is something that does similar. Eventually I may try to figure out how to move some of the handling I'm doing from automations to integration but for now the sensor creation via the UI would be ideal for usability.

[sly adder]

My template sensor is not getting recognised as an entity (at least that's what I would expect it to become)...

Am I doing something wrong?

template:
  - trigger:
    - platform: webhook
      webhook_id: id
    sensor:
      - name: "last_animal"
        state: "{{trigger.json.animal}}"

[inner mesa]

Where did you put that?

[sly adder]

In a yaml file in my sensor folder

[mighty ledge]

it goes in configuration

[sly adder]

Oh, why is that

I thought it's a sensor, so it goes with the other sensors

[inner mesa]

You should see the docs 🙂

It's a template

[sly adder]

Yeah a template sensor though

So slightly confusing in a way

but I must have glanced over this in the docs, thanks 🙂

[inner mesa]

It's supported by the template integration

And integrations can create any of the base entity domains. Little by little, HA is moving from domain/platform to integration/domain style

[edgy umbra]

How can i show the day wen the sensor last started? The sensor shows "2024-04-25T05:43:53+00:00" as a state and the template below is working but it just shows the short day and not the short day wen the sensor is last started.

        state: >
          {% set days = ['Ma', 'Di', 'Wo', 'Do', 'Vr', 'Za', 'Zo'] %}
          {{ as_timestamp(states.sensor.inverter_opstarttijd.state) | timestamp_custom(days[now().weekday()] ~  ' %I:%M' + 'u') }}

[mighty ledge]

that shows the short day and the time it started

so what exactly is the problem?

you want a long day?

[edgy umbra]

No i want to show the short day the sensor is actualy started.

So now it just show the day (short) of the week. If the sensor was last started tuesday lets say 8am it show Tue 8am on Wednesday 7am because the sensor is not yet started (changed state...) for that day.

[mighty ledge]

        state: >
          {% set days = ['Ma', 'Di', 'Wo', 'Do', 'Vr', 'Za', 'Zo'] %}
          {% set t = states('sensor.inverter_opstarttijd') | as_datetime | as_local %}
          {{ days[t.weekday()] ~ t.strftime(' %I:%Mu') }}

[edgy umbra]

Thanks allot Petro!

[visual cedar]

I have a binary sensor that was made in config (via HACS) and that doesn't have a unique ID. I'd like it to have one, ideally, so I can assign a label to it in the UI. I've had success adding a "unique_id: <UID>" line for a lock template to the yaml, but when I tried doing that with this binary_sensor template, I got an error that said that unique_id is not an expected variable for binary_sensor (or some similar error message). Is there any way to add a UID for a binary sensor (or some other workaround to add labels to it via the UI)?

[mighty ledge]

You can't add unique_id's to entities

you have to create new entities that point to non-unique_id entities using tepmlate entities

and template binary_sensors support unique_id

[visual cedar]

Thanks for the quick reply! If you have the time and patience, could you explain a little more? I'm having a hard time understanding why I can add a unique_id to this:

`lock:

• platform: template
  unique_id:
  ...but not to this:binary_sensor:
• platform: template
  sensors:
  ...`

[marsh cairn]

You can: https://www.home-assistant.io/integrations/template/#legacy-binary-sensor-configuration-format

binary_sensor:
  - platform: template
    sensors:
      example_binary_sensor:
        unique_id: xxxxxxxxx
        value_template: "{{ now() == now() }}"

[inner mesa]

that's quite the existential template

is now really now?

[marsh cairn]

Colonel Sandurz: Just now.
Dark Helmet: When will then be now?
Colonel Sandurz: Soon.
Dark Helmet: How soon?

[marble jackal]

I guess you need a really fast machine for that to return true

[marsh cairn]

It depends on how now now really is

[inner mesa]

survey says:

that's it. time itself is broken

physics is dead

Einstein warned us about this stuff

[marsh cairn]

It is all relative... until the next release

[marble jackal]

They are rendered after each other, so there are milliseconds microseconds difference

[inner pagoda]

i would bet on less than milliseconds, but the timestamps are quite high resolution.

[marble jackal]

Sorry, I indeed meant microseconds

[visual cedar]

Thank you! I'll try that. I see the difference (even if I don't understand why it's necessary!)

[marsh cairn]

Because you are using the legacy format. And in that a template binary sensor is something completely different than a template lock.

[modern sluice]

Hi, I think I'm in need of a template but if there's a better way to do this without a template, please let me know. I have 3 people in my Home Assistant. When only 1 of them is home (regardless of who it is), I want to trigger an announcement. How can I operationalize the counting of persons who are home and then automate when that number = 1?

[marble jackal]

the state of zone.home will be the number of person entities in that zone

[modern sluice]

well how about that? thanks I found it

[dusk sorrel]

i want to create switch or button with changeable icon. How to solve it? relay_regulator: name: Relay regulator icon: > {% if is_state('input_boolean.relay_regulator', 'on') %} {%mdi:electric-switch-closed %} {% else %} {%mdi:electric-switch %} {% endif %} but not work and i can not show icon.

[marsh cairn]

Show the full code

Also there should not be {% %} around the mdi icons

It is not a statement

[dusk sorrel]

same not work but concept is right?

[marsh cairn]

What?

As I said, show the full code

[mighty ledge]

please read the pins

they cover what the {% %} and {{ }} mean

[dusk sorrel]

in input_boolean.yaml relay_regulator: name: Relay regulator icon: > {% if is_state('input_boolean.relay_regulator', 'on') %} mdi:electric-switch-closed {% else %} mdi:electric-switch {% endif %} That is all code.

[mighty ledge]

you can't make up configurations for integrations

input_boolean does not support icons or templates

[marsh cairn]

I don't think input_booleans support templates for icons

Oh. Too late again

[dusk sorrel]

aanhan!!! How to create switch or button with changeable icon and name?

[marsh cairn]

Create a template switch or template button

[dusk sorrel]

@mighty ledge @marsh cairn Thank you guys.

[atomic blade]

How can I boolean or everything in a list in a filter?

I guess I could just do select('true') and see if the count is > 0. Is there a way to do like a reduce operation though?

[fickle sand]

if true in []

[atomic blade]

Thanks that works

I am kinda curious if you can do some kind of reduction operation though

Or for an or operation id just need to find the first. Anyways, that way is probably the easiest to read

[bronze prawn]

{{ expand('group.assist_satellites') |map(attribute='attributes.display_device')|list }}
this returns:

  "sensor.tabletmaster_browser_path",
  "sensor.thinksmart_lr_browser_path",
  "sensor.tabletfullkiosk_browser_path"
]```
I have a group of custom sensors that all have the attribute display_device .  Above is a template that lists the sensor stored in that value.  Can I somehow use these values as a trigger template?  I am looking to see if any of the devices in the returned list has had its state change for the trigger

I am wanting to use this in an automation but thought this might be the more appropriate spot to ask

[tame gust]

Hello, any help with template for sensor changing output ?

[heavy plaza]

hey, so i am trying to create an mqtt event that is triggered when an mqtt message is received i tried this but it doesn't seem to be working and i am not sure where the issue is 😅 . https://pastebin.com/vaewAMnh

[inner mesa]

Is that a thing?

Seems made up

[heavy plaza]

yes it is a thing 😅 but unfortunately the documentation doesn’t have much information https://www.home-assistant.io/integrations/event.mqtt/

[inner mesa]

Indeed. You're not following that format

It shows some example YAML and yours doesn't look like that

[heavy plaza]

thank you. i did not have the for loop part. i was mostly taking reference from the templating documentation and didnt really think the loop was important 🤭

rewrote it as this and now works! https://pastebin.com/1QCQZycF

[torpid crag]

Hey there, i have a template i setup via the Helpers area, but now i cant delete…. https://imgur.com/a/mwgYT7i Any ideas?

[frail dagger]

Try adding a valid template in there and then submit and then reopen it and see if you can delete it.

[torpid crag]

Yea does not work, somehow it does not have any entiry ID.

[atomic blade]

Is there a way to get the "friendly" value of a state in a template? In other words, how it looks on the frontend taking into account it's device class and such? For example, I have a sensor that has duration in hours with a state of 4.5 that I'd like to display as 4:30.

[inner mesa]

Does state_translated() do it?

[lofty mason]

Doubtful, all that formatting is handled by JavaScript.

[mighty ledge]

Duration does t work with that stuff but other sensors do. rounded=true as an argument for the states method

[atomic blade]

I was hoping, but no

I was able to get what I wanted using time_delta(), but yeah didn't find any kind of general purpose method

[humble mortar]

What is the null operator in lambda?

id(volume_status).publish_state(0); <= would like null where the zero is 0

[frail dagger]

None

[humble mortar]

Thank you

[inner mesa]

In ESPHOME?

That's not a Jinja template

[frail dagger]

Derp. lol I thought it was just poorly formatted 🙂

[inner mesa]

Wrong server

https://discord.gg/m7GVSmdK

[verbal yacht]

Hi All. I was wondering if someone can lend a hand and apologies in advance if this was covered earlier.... I have an existing sensor with additional attributes that I would like to create a new sensor of the basis of a calculation. I was able to prove the calculation in developer section of HA, which looks like the following: {{ state_attr('sensor.truenas_datasets_p1','Used')/ state_attr('sensor.truenas_datasets_p1', 'Used' + state_attr('sensor.truenas_datasets_p1', 'Available' )) *100 }}. It seems that this is possible, however, I'm having some challenges in execution, probably due to my inexperience with YAML setup. Ive stubbed out a template.yaml file to do this in and am simply hitting a brick wall. Ive tried countless times and am currently sitting on the following entity setup:- sensor:
p1_percent_free:
friendly_name: "Pool 1 Percent Free"
unit_of_measurement: "percent"
state_class: measurement
state: >-
"{{ state_attr('sensor.truenas_datasets_p1','Used')/ state_attr('sensor.truenas_datasets_p1', 'Used' + state_attr('sensor.truenas_datasets_p1', 'Available' )) *100 }}". Any help would be greatly appreciated!!

[marsh cairn]

You are missing some parentheses. And states and attributes are strings. You have to convert them to integers or float numbers to calculate with them.

And if you are using state: with a >, you don't have to surround the template with quotation marks

[marble jackal]

state_class is not supported in the legacy format you are using, you need to use the modern format

[verbal yacht]

Thanks so much! All excellent suggestions! 😀

[marble jackal]

attributes can be anything, so they are not strings by definition.
States are indeed always strings

[plain magnet]

@sonic pivot I converted your message into a file since it's above 15 lines :+1:

[fickle sand]

The light group doesn’t support templates for the entities iirc

[sonic pivot]

ah dang it

I have started manually putting in the groups but was really hoping to have it be something I wouldnt have to mess around with once I assigned it to an area. oh well - poor use of a few hours but was fun 😛

[dim lodge]

Hi there. I have a template binary sensor that was using Android's presence detection, but some combination of the app + my phone is simply not allowing it to work anymore. So I hacked together a script that SSHs to my DD-WRT router and checks its active associations for my phone's MAC address. I need to add a time trigger and an action to it. Here's what the old templates.yaml looks like:

- binary_sensor:
  - name: "TiZPhone on Home WiFi"
    unique_id: "tizphone_on_home_wifi"
    state: >
      {{ is_state('sensor.tizphone_wifi_connection', "Plush Town 2G") or
         is_state('sensor.tizphone_wifi_connection', "Plush Town 5G") }}
  - name: "TiZ is Home"
    unique_id: "tiz_is_home"
    delay_off: "0:10:00"
    state: >
      {{ is_state('person.tiz', 'home') or
         is_state('binary_sensor.tizphone_on_home_wifi', 'on') }}

I know I need to add this:

  trigger:
    - platform: time_pattern
      minutes: /2
  action:
  - service: shell_command.phone_on_wifi
    data: {}
    response_variable: phone_on_wifi

But I'm not sure where I'm supposed to add it. Because various combinations of where I put it break something or other.

[plain magnet]

@dim lodge I converted your message into a file since it's above 15 lines :+1:

[analog mulch]

It should work if you put it at the same level as the binary_sensor entry — below or above, order doesn’t matter. Just make sure you are not defining multiple binary_sensors in the same key, since they will all only update on this trigger.

[wise cedar]

should this work?

data_template:
  temperature: >-
    {{ state_attr('climate.kjokken', 'temperature') -
    states('input_number.temperature_offset_fellesrom') | float }}
  target:
    area_id: {{ area_id('climate.kjokken') }}```

[compact glen]

fields:
  duration:
    selector:
      time: {}
    default: "00:00:20"
    name: Dauer bis ausschalten
 - service: light.turn_off
   metadata: {}
   data:
     transition: {{ dauer }}
   target:
     entity_id: light.nachttischlampe_licht

How do I insert the fields value in the transistion?

[marble jackal]

the tempalte for area_id should be quoted. But why not target the entity_id? Do you have multiple climate entities in that area?

[marble jackal]

also here, your templates should be quoted

and I assume this is a snippet from the actual script, but your field is named duration, but you use dauer in the template

[wise cedar]

Thanks, I’ll try that. Yes, the idea was to make a reusable automation that alters climate in the area of the sensor (door/window) that triggered the automation 🙂 edit: yes, some areas have multiple

[compact glen]

Will try that, thank you

[compact glen]

Error: expected float for dictionary value @ data['transition']

[marble jackal]

what did you use now?

oh wait

transition should be a duration in seconds

you are providing something like `"00:00:20"

[compact glen]

yes

[marble jackal]

that should simply be 20

[compact glen]

fields:
  duration:
    selector:
      time: {}
    default: "00:00:20"
    name: Dauer bis ausschalten
 - service: light.turn_off
   metadata: {}
   data:
     transition: 
       duration: {{ duration }}
   target:
     entity_id: light.nachttischlampe_licht

Should I use this then?

[marble jackal]

no

your field should be a number type field

https://www.home-assistant.io/integrations/light/#service-lightturn_on There it is indicated that transition expects the following value:

Number that represents the time (in seconds) the light should take to transition to the new state.

[compact glen]

How to convert this?

[marble jackal]

you should use a number selector instead of a time selector
https://www.home-assistant.io/docs/blueprint/selectors/#number-selector

[compact glen]

still expected float for dictionary value @ data['transition']

[marble jackal]

what do you have now?

[mighty ledge]

time wouldn't work for transition

it should be a number selector

[marble jackal]

that's what I alreade said

I suspect he still didn't quote the template

[mighty ledge]

it wouldn't need a template either

just transition: !input abc

[marble jackal]

if it is a blueprint, or does that also work for scripts?

[mighty ledge]

it works for blueprints for scripts, but not scripts themselves

unless something changed

[drifting tapir]

@inner mesa your hint to template states helped! I have now an own slider for my bulbs to dim them

Now I want to update the slider of the brightness changes from another controller

service: input_number.set_value
metadata: {}
data:
value:
{{ states('light.esstischlicht.brightness') }}
target:
entity_id: input_number.dimmer_moes_esstisch

this does not work. can anybody point me in the right direction?

https://imgur.com/a/7ppsj14

expected float for dictionary value @ data['value']. Got None

[mighty ledge]

you're missing multiline yaml indicator >

[drifting tapir]

service: input_number.set_value
metadata: {}
data: >
value: {{ states('light.esstischlicht.brightness') | float }}
target: >
entity_id: input_number.dimmer_moes_esstisch
like this? does not work either

[mighty ledge]

no, it only goes on the value field

where you had it before, please check the pins

[inner mesa]

or surround the template in quotes

on the same line

[drifting tapir]

service: input_number.set_value
metadata: {}
data:
value: {{ states('light.esstischlicht.brightness') | float }}
target:
entity_id: input_number.dimmer_moes_esstisch

now its in one line

expected float for dictionary value @ data['value']. Got None

[mighty ledge]

you didn't do either of our suggestions...

[drifting tapir]

ok sorry misunderstood you

[drifting tapir]

after the value means like this?

value: > {{ states('light.esstischlicht.brightness') | float }}

[mighty ledge]

the template needs to be on a second line if you use the multiline notation

[drifting tapir]

data:
value: >
{{ states('light.esstischlicht.brightness') | float }}

better?

[mighty ledge]

yes, but your template needs to be indented beyond value

[drifting tapir]

ah thanks this looks better

I still have a problem with the int to float conversion

{{ states('light.esstischlicht.brightness') | float }}

is this incorrect?

Error rendering data template: ValueError: Template error: float got invalid input 'unknown' when rendering template '{{ states('light.esstischlicht.brightness') | float }}' but no default was specified

[mighty ledge]

if you're trying to get the brightness from a entity, you need to use state_attr(), not states()

[drifting tapir]

{{ state_attr('light.esstischlicht', 'brightness') | float }}

[inner mesa]

you don't need the |float, but yeah

I think it will be a problem when the light is off, though

[drifting tapir]

ah without float it works fine

[inner mesa]

I don't recall if that was changed to be 0 or None

[drifting tapir]

thanks @inner mesa and @mighty ledge !!!

[marble jackal]

none, so maybe int(0) makes sense then

[unique turret]

I think this maybe better suited here, but How do I shorten last-changed state so it shows as 2hr instead of 2 hours ago?

I want it to apply system wide, not just per card

[marble jackal]

That's not possible using templates, if it's possible (which I doubt) #frontend-archived might know

[inner mesa]

it's going from something explicit to something ambiguous

[unique turret]

Ah okay, I just posted there got no response, will post again thanks

[unique turret]

not possible?

[inner mesa]

🤷

as TheFes said, it's a #frontend-archived thing

I am not aware of anything like that, and it doesn't seem like somethign they would support

because it's going from something obvious to something ambiguous

[unique turret]

Meaning it can only be applied per card, I posted in frontend now

[marble jackal]

No Rob means that the meaning of 2 hours ago is really clear, but with 2 hrs it's not clear what the meaning is

[unique turret]

Ah okay, I guess 2hrs ago would be a better format

[plain magnet]

@lament salmon I converted your message into a file since it's above 15 lines :+1:

[wide grove]

I have a questions:

• {{ is_state(state_attr(rolladen_id, "window"), "on") }}

• {{ is_state_attr(rolladen_id, "window", "on") }}

Why is there a big difference? I saw the python code behind, but it works different here... + Line works as expected, - Line not, but why? I use this as a trigger template for my automation. Have anyone the same behaviour seen?

[inner mesa]

the first one looks wrong

is_state() takes an entity_id and desired state to compare. Does state_attr(rolladen_id, "window") return an entity_id?

[lament salmon]

RobC, what do you think im doing wrong?

[inner mesa]

the second one is assuming that rolladen_id is a variable that refers to an entity_id

[lament salmon]

😭

[wide grove]

yes behind the state_attr(rolladen_id, "window") it is a entitiy_id saved as string (eg. binary_sensor.window_id)

Do i missunderstood this is_state_attr?

[inner mesa]

maybe?

they're referring to two different things

[wide grove]

Hmm ok thank you @inner mesa for your help 🙂 I thought, that are the same

[inner mesa]

the first is checking if the state of that entity in the "window" attibute of rolladen_id is 'on', and the second is checking if the value of the window attribute of rolladen_id is "on"

the latter is clearly wrong because you said it should have an entity_id in it

[wide grove]

Ah ok, the order is not the same, right?

[inner mesa]

has nothing to do with the order

[mighty ledge]

There's something you're miss understanding revilo

not sure what

what does state_attr(rolladen_id, "window") return?

[wide grove]

eg. binary_sensor.window_state

[mighty ledge]

Ok, so will the text binary_sensor.window_state ever equal the text on?

i'm talking the literal text

does b equal o? does i equal n, does nary_sensor.window_state equal ``?

short answer: No, they are not equal

that's what you're doing when you use {{ is_state_attr(rolladen_id, "window", "on") }}

"Is the result of the attribute window from rolladen_id equal to on"

Hopefully that clears things up

[wide grove]

Ahhh now I understand, the status of the string (which is in this case a binary_sensor) is not queried, but only the string is checked 👍

Thank you @mighty ledge for clarification 👍

[dim lodge]

I'm not sure what this means exactly. Like, "multiple binary sensors in the same key", to be specific.

Also, it ended up not working. The binary sensor which is basically just supposed to be the wifi sensor but waits for ten minutes before turning it off

[sick ice]

https://www.toptal.com/developers/hastebin

Could some tell me the value_template format to access the json parameters under channels:

The yaml is for my MQTT: entities. The two shown work perfectly for whole of house production and consumption. I'm now trying to create 3x more entities for consumption on each of my three phases (which to do I need to use the separate channels data). Just don't know hte syntax to use.

[sick ice]

omg i just found this: https://jsonpathfinder.com/

[topaz carbon]

Hi all! I’m struggling making a template fan from for RF remote codes. Does anyone know if the template fan requires a helper select, or is it possible to store state information as attributes?

[viscid sparrow]

I'm trying to read notifications on my Android phone and trigger an automation. But the text in this notification is not always the same except for eg. 123. So some times it will be ABC123, 123XYZ, 123456.
How do I tell HA to run when it contains '123'?

condition: template
value_template: "{{ '123'
entity_id: sensor.pixel_6a_last_notification
enabled: true
state: ""

I'm stuck here

[marble jackal]

{{ '123' in states('sensor.pixel_6a_last_notification') }}

[viscid sparrow]

Still not getting it

condition: template value_template: "{{ '123' in states('sensor.pixel_6a_last_notification') }}" entity_id: sensor.pixel_6a_last_notification state: true

Is that correct?

[marble jackal]

no

condition: template
value_template: "{{ '123' in states('sensor.pixel_6a_last_notification') }}"

that's all

[viscid sparrow]

okay let me try, sorry I know I have a lot to learn

[marble jackal]

you are making a mismatch of a template condition and a state condition

[viscid sparrow]

Great, it works now!

[viscid sparrow]

I see, I think I got confused because I am editing it via the GUI

[severe jungle]

Hi! I've given up on googling my way to figure this one out.

I'm trying to make a value template that retuns true/false depending on if a sensor has returned true at any point over 24 hours.
So if it has been false for 24+ hours, return false.
If it has at any point been true in the last 24h, return true.
I can't check for if the current false state has a duration of 24h+ because I need to check 4 different sensors that all reset at the same time if any of them go true/false.

[mighty ledge]

history stats sensor. Track the state you desire in number of hours. Then make a template sensor that checks the number of hours being greater thatn 0.

[severe jungle]

oh sweet

Thanks!

[thorny snow]

Hi, I have a sensor sensor.double_take_officetable1 that outputs https://i.imgur.com/vXfV3yT.png this data. I want to be able to make a trigger when 'match' == 'true', can someone correct me on how to reference it? I tried state_attr.sensor.double_take_officetable1.matches.match but that didn't work, do I need to reference this a json?

[mighty ledge]

matches is a list

[thorny snow]

I assumed it was a json, that was wrong

[mighty ledge]

{{ state_attr('sensor.double_take_officetable1', 'matches') | selectattr('name', 'eq', 'mike') | selectattr('match', 'eq', True) | list | count > 0 }}

a list is json

[thorny snow]

is the whole thing a list within a list?

[mighty ledge]

it's a list of dictionaries

what I posted above will be a template you can use for the template trigger

if you want to look for any matches, remove | selectattr('name', 'eq', 'mike')

[thorny snow]

selectattr with the pipe acts as filter

but if I wanted to match camera with officetable I wouldnt need to use selectattr?

{{ state_attr('sensor.double_take_officetable1', 'camera') == 'officetable1' }}

[mighty ledge]

no, you still need select attr if it's inside matches

if you're just checking the camera attribute, then you'd just use state_attr

but your parethesis are wrong

and you're missing a quote

[thorny snow]

smh, thanks petro I get what you're saying, I think. Because it's inside a dictionary I need to use selectattr

[mighty ledge]

you have to use selectattr when you're trying to find information in a list of dictionaries

it's only applicable to your matches attribute

[thorny snow]

in the example I linked, is box another dictionary within matches?

[mighty ledge]

no

box is a dictionary

[thorny snow]

okay, I get it. Are dictionaries ever nested?

[mighty ledge]

objects can have any shape

you can have lists of dictionaries which has keys that are a list of dictionaries

whatever the author dreamed up

[thorny snow]

got it, above my paygrade! Thanks for explaining it to me

[plain magnet]

@soft rock I converted your message into a file since it's above 15 lines :+1:

[barren pecan]

Could anyone tell me if there is a table with all the template commands?

[mighty ledge]

No table, but the documents cover it

[inner mesa]

several links in teh channel topic

[plain magnet]

The topic of this channel is:

Become a real Jinja2 Ninja! Don't worry my Genin, we are here to help! You can find general Jinja docs at https://jinja.palletsprojects.com/en/3.1.x/templates/, Home Assistant extensions at https://www.home-assistant.io/docs/configuration/templating/, and trigger variables at https://www.home-assistant.io/docs/automation/templating/

This channel is for support with Jinja templates. Some custom Lovelace cards support other types of templates, such as those written in JavaScript, and #frontend-archived is the right channel for that.

Please use http://pastie.org/, https://dpaste.org/, or https://paste.debian.net/ to share code or logs

[soft rock]

how can i use a template to extract the name (mike) from this example payload? https://imgur.com/vXfV3yT

[mighty ledge]

Are you a bot?

[soft rock]

no - the other user and i both ended up here after trying to figure this out together on the double-take discord.

[mighty ledge]

I suggest you post what you're actually trying to do and I can provide a full example

right now, you keep asking pointed questions

explain the whole scenario and I'll provide a template that does it

[plain magnet]

@soft rock I converted your message into a file since it's above 15 lines :+1:

[soft rock]

so, if match = true, i'd like a notification that says '<name of person> is at the mudroom doorbell.'

[mighty ledge]

gotcha

[soft rock]

sorry, should have elaborated earlier.

[mighty ledge]

I'd approach this differently then

there's a number of ways to handle this, but I'd probably make a template sensor.

template:
- sensor:
  - name: New Double Take
    device_class: timestamp
    state: >
      {% set t = state_attr('sensor.double_take_mudroom_doorbell', 'timestamp') %}
      {{ strptime(t, "%B %d, %Y at %-I:%M:%S %p %Z") }}
    attributes:
      who: >
        {{ state_attr('sensor.double_take_mudroom_doorbell', 'matches') | selectattr('match', 'eq', True) | map(attribute='name') | list }}

then your automation will be

trigger:
- platform: state
  entity_id: sensor.new_double_take
condition:
- condition: template
  value_template: "{{ trigger.to_state.attributes.who | count > 0 }}"
action:
- service: notify.mobile_app_galaxy_s24
  data:
    message: "{{ trigger.to_state.attributes.who | join(', ') }} is at the mudroom doorbell."

sorry, edited again

[soft rock]

is this correct? i've never created a template sensor before: https://imgur.com/a/QBOu9ug

[mighty ledge]

No, you have to create this in YAML

[soft rock]

where is that option? i'm looking under the helper menus.

[mighty ledge]

there is no option, you add the sensor in your configuration.yaml file

have you edited configuration.yaml before?

[soft rock]

yep - just added it and am restarting now.

[mighty ledge]

if the main state of the template is not working, we can adjust it

[soft rock]

is it expected that the sensor is showing as unavailable after restarting?

[mighty ledge]

no

check your log for errors

post the error here

[soft rock]

Double-Take Mudroom Doorbell Helper became unavailable
11:57:07 AM - 2 minutes ago

that isn't very helpful.

[mighty ledge]

go to your actual logs, not the UI

[soft rock]

TemplateError('ValueError: Template error: strptime got invalid input 'None' when rendering template '{% set t = state_attr('sensor.double_take_mudroom_doorbell', 'timestamp') %} {{ strptime(t, "%B %d, %Y at %-I:%M:%S %p %Z") }}' but no default was specified') while processing template 'Template<template=({% set t = state_attr('sensor.double_take_mudroom_doorbell', 'timestamp') %} {{ strptime(t, "%B %d, %Y at %-I:%M:%S %p %Z") }}) renders=4>' for attribute '_attr_native_value' in entity 'sensor.double_take_mudroom_doorbell_helper'

and

Error while processing template: Template<template=({% set t = state_attr('sensor.double_take_mudroom_doorbell', 'timestamp') %} {{ strptime(t, "%B %d, %Y at %-I:%M:%S %p %Z") }}) renders=2>

I don't know - maybe this is more helpful?

homeassistant.exceptions.TemplateError: ValueError: Template error: strptime got invalid input 'None' when rendering template '{% set t = state_attr('sensor.double_take_mudroom_doorbell', 'timestamp') %} {{ strptime(t, "%B %d, %Y at %-I:%M:%S %p %Z") }}' but no default was specified

[mighty ledge]

Sry back

Ok, know what the problem is, hold pls

[inner mesa]

we need some hold music

[mighty ledge]

template:
- sensor:
  - name: New Double Take
    device_class: timestamp
    state: >
      {% set t = state_attr('sensor.double_take_mudroom_doorbell', 'timestamp') %}
      {{ strptime(t, "%B %d, %Y at %-I:%M:%S %p %Z") }}
    attributes:
      who: >
        {{ state_attr('sensor.double_take_mudroom_doorbell', 'matches') | selectattr('match', 'eq', True) | map(attribute='name') | list }}
    availability: >
      {{ state_attr('sensor.double_take_mudroom_doorbell', 'timestamp') is not none }}

[soft rock]

Now just this one error:

TemplateError('ValueError: Template error: strptime got invalid input '2024-04-30T10:23:46.072-05:00' when rendering template '{% set t = state_attr('sensor.double_take_mudroom_doorbell', 'timestamp') %} {{ strptime(t, "%B %d, %Y at %-I:%M:%S %p %Z") }}' but no default was specified') while processing template 'Template<template=({% set t = state_attr('sensor.double_take_mudroom_doorbell', 'timestamp') %} {{ strptime(t, "%B %d, %Y at %-I:%M:%S %p %Z") }}) renders=2>' for attribute '_attr_native_value' in entity 'sensor.double_take_mudroom_doorbell_helper'

[mighty ledge]

interesting

ok

template:
- sensor:
  - name: New Double Take
    device_class: timestamp
    state: >
      {{ state_attr('sensor.double_take_mudroom_doorbell', 'timestamp') }}
    attributes:
      who: >
        {{ state_attr('sensor.double_take_mudroom_doorbell', 'matches') | selectattr('match', 'eq', True) | map(attribute='name') | list }}
    availability: >
      {{ state_attr('sensor.double_take_mudroom_doorbell', 'timestamp') is not none }}

makes the template easier

[soft rock]

no errors this time. testing the automation now.

okay, that works! a few questions:

• the name it sounds over (first last) isn't capitalized. is there a way to do that with the template?
• i received multiple notifications for it. is that something i need to work with the double-take team to resolve?
• the payload also contains a filename that can be appended to a url to view the snapshot from the camera. how would i capture and add this to the notification?

[mighty ledge]

1. You can | map('title') in the who attribute after mapping the name before the | list

2. If the input sensor is changing alot, we'd have to modify the template.

3. Depends on where the snapshot is stored

[soft rock]

it is firing several times, but i'm not sure how to work around that.

[mighty ledge]

what does the state look like each time? What data is changing? The state or the who attribute?

[soft rock]

it looks like it's running the same thing over and over every 10 seconds with new images passed from my nvr (frigate).

seems like i need to work that behavior out with the double-take or frigate teams.

[mighty ledge]

that's how frigate is designed to behave

You should look into the frigate notification blueprint and see hwo they handle it with actionable notifications

[buoyant pine]

https://youtu.be/jM8XdUNhNmU

[soft rock]

good news - i was able to sort out the duplicate notifications. the only thing left is to figure out how to append the the filename from the same payload to a url to be displayed in the notifications.

going to try adding a new attribute to my template to be called in the notification:

`template:

• sensor:
  • name: Double-Take Mudroom Doorbell Helper
    device_class: timestamp
    state: >
    {{ state_attr('sensor.double_take_mudroom_doorbell', 'timestamp') }}
    attributes:
    who: >
    {{ state_attr('sensor.double_take_mudroom_doorbell', 'matches') | selectattr('match', 'eq', True) | map(attribute='name') | map('title') | list }}
    image: >
    {{ state_attr('sensor.double_take_mudroom_doorbell', 'matches') | selectattr('match', 'eq', True) | map(attribute='filename') | list }}
    availability: >
    {{ state_attr('sensor.double_take_mudroom_doorbell', 'timestamp') is not none }}`

update: it doens't like that.

fixed it - tab error.

will this be sufficient?

service: notify.frigate data: message: >- {{ trigger.to_state.attributes.who | join(', ') }} is at the mudroom doorbell. data: attachment: url: >- https://<url>/api/storage/matches/{{trigger.to_state.attributes.snapshot}}

[indigo haven]

hi there, how do i make a custom climate entity from a template?

i saw the generic thermostat template, but that is for making an actual virtual thermostat in home assistant

[lofty mason]

IIRC HA doesn't have a template climate entity. I think there's a custom component that can do it but I don't know how well it works.

[indigo haven]

huh

[pseudo cape]

I am trying to pull an attribute from a command line sensor json, and it is giving me an error, when I run this in dev tools it pulls the correct info

template:
  - sensor:
    - name: "Solar Production"   
      unit_of_measurement: kW
      device_class: power
      state_class: measurement
      state: {{ state_attr('sensor.inergy','Solar_kW') }}

missed comma between flow collection entries. What am I missing?

[mighty ledge]

quotes around the template

[pseudo cape]

always something simple thanks

[inner mesa]

next time you say "give me an error", please also say what the error is

[fallen kernel]

looks like you still have all your attributes in a single sensor? like I said in #energy-archived that's not the right way to do it

[pseudo cape]

yeah, I'm still trying to figure out how exactly to do that, I'm sure I'm missing a key concept.

I think I'm hung up on the value_template:

[fallen kernel]

I linked the post which shows how to do it

Use that

[pseudo cape]

I did and now I just get unknown

or state length 1188 max 255 chars

command_line:
  - sensor:
      name: Inergy
      command: "python /config/inergy3.py"
      value_template: "{{ value_json }}"
      scan_interval: 5
      unique_id: "Inergy Solar"

I can't seam to get the value_template to work

[mighty ledge]

what does ienergy3.py do?

can you post the code?

or at least, post what you used to have for the command_line configuration

[plain magnet]

@pseudo cape I converted your message into a file since it's above 15 lines :+1:

[pseudo cape]

the script connects to my demand controller and pulls the data, which is in a format simular to xml but is not and looks proprietary, It converts it to json and allows HA to pull in the data

[mighty ledge]

ok

So, I think the way you're doing it currently is the best way

command_line isn't set up to run a single command and separate the data into separate sensors

[plain magnet]

@pseudo cape I converted your message into a file since it's above 15 lines :+1:

[mighty ledge]

So, keep your current config, then make template sensors for each attribute in the command_line sensor

[pseudo cape]

but @fallen kernel says its not the best way to do it

[mighty ledge]

that is the best way to do it for the command_line integraiton

[pseudo cape]

ah ok

[mighty ledge]

Yeah, other integrations like rest, can target 1 endpoint and deliver the information to mulitple sensors.

unfortunately, command_line cannot

[fallen kernel]

I meant this https://community.home-assistant.io/t/one-response-for-multiple-sensors/90127/2?u=langestefan

[mighty ledge]

Yes, that's what he was doing

[fallen kernel]

no he's using attributes instead of the state

[spark flicker]

Hey trying to get list card to pull a BBC RSS feed I can't get it pull anything back
type: custom:list-card entity: sensor.topstories title: Top Stories Feed_attribute: entries columns: null

Anyone know what could be wrong

Set up feedreader properly

[mighty ledge]

The post you linked is only possible because the state is less than 254 characters

i.e. he has to use attributes, he has no choice

[fallen kernel]

ah yeah. forgot about that

[plain magnet]

@pseudo cape I converted your message into a file since it's above 15 lines :+1:

[mighty ledge]

Feed_attribute should probably be feed_attribute, outside that, this is a #frontend-archived question

[spark flicker]

Ah my bad

[tidal surge]

Anybody got a Idea, why my auto-entities card wont work with templating the name? I am trying to use templating to set the display name of the entities of my auto-entities card, so I am able to replace some strings. This is my config:

card:
  square: false
  type: entities
filter:
  include:
    - domain: switch
      area: Wohnzimmer
      options:
        name: |
          {{ state_attr('this.entity_id', 'friendly_name') }}
  exclude: null
show_empty: true

The output name of each entity is like the following: {{ state_attr('switch.hmip_ps_00021569971e70', 'friendly_name') }}

So the card fills out the 'this.entity_id' but does not use the template itself

[mighty ledge]

@tidal surge are you sure that supports templates?

I doubt it does

also, this.entity_id shouldn't be in quotes

if it is templateable

secondly, you shouldn't even need to do that

if you're just outputting the friendly name

[tidal surge]

as discussed in this thread here: https://github.com/thomasloven/lovelace-auto-entities/issues/110#issuecomment-1221438175
There should be no problem with using the template for the display name

[tidal surge]

Ive tried with and without quotes, makes no difference

[mighty ledge]

well, that post shows you the correct variable anyways

config.entity

[tidal surge]

yea just for testing, next step would be to attach something like | replace('Switch-Control_', '') to replace part of the name

[tidal surge]

changing it to {{ state_attr(config.entity, 'friendly_name') | replace('Schaltsteckdose', '') }} does also not work

[mighty ledge]

you should have errors in your logs

aobut the templates

[tidal surge]

cant find any logs in settings -> system -> logs, where would i find the template errors?

[mighty ledge]

every time the template renders, you should see an error

open your logs with a text editor

[tidal surge]

the last entries are almost from an hour ago, and I cannot find anything related to templates in the logs from Homeassistant core

do I have to change some kind of log level, to also show lovelace errors in the logs?

[mighty ledge]

Are you 100% sure you can template that field?

All signs on my end point to: No

[tidal surge]

Yea, I mean many other people are using this field with a template, so it should technically work

Only thing I would imagine is that it got removed along the way, but I havent found any info on that

[mighty ledge]

Yes but that's in combination with template-entity-row card

not entities card

So I'm 99% sure you cannot template that

if you want to, you need custom:template-entity-row

[tidal surge]

Jep your right... I just saw this workaround mentioned in another discussion about the topic and I got mislead by there only beeing the options part of the config, which I tried to add

then onto looking for another solution, thanks for your help! 😄

[mighty ledge]

Just get that card

Takes like 2 seconds to add with HACS

You can do it without that custom card too, but I’d probably have to write the template for you

[tidal surge]

problem is I would like to use card type grid and not entities

[mighty ledge]

Grid of what

[tidal surge]

Grid of entities

[mighty ledge]

grid of entity cards?

[tidal surge]

yea

of custom:mushroom-light-card to be exact

I mean i could just use a horizontal card with two custom auto-entity cards inside

[mighty ledge]

try

type: custom:auto-entities
card:
  type: grid
card_param: cards
filter:
  template: >
    [{% for e in area_entities('Wohnzimmer') | select('match', '^switch.') %}
     {{ {'type': 'custom:mushroom-light-card', 'entity': e, 'name': state_attr(e, 'friendly_name') | replace('Schaltsteckdose', '')} }},
     {% endfor %}]
show_empty: True

[tidal surge]

works perfectly!

[pseudo cape]

how does one make a state report 0 if the value goes negative?
state: "{{ state_attr('sensor.inergy','Current_Demand')|float * 1000 }}"

[wanton sapphire]

{% if state_attr('sensor.inergy','Current_Demand')|float > 0 %}
  {{ state_attr('sensor.inergy','Current_Demand')|float * 1000 }}
{% else %}
  0
{% endif %}

[marble jackal]

Or
{{ [state_attr('sensor.inergy','Current_Demand') | float(0), 0] | max * 1000 }}

[languid sandal]

Please help me with the coding of it as i want to convert those brightness values into rgb value or into the rgb tuple

[bitter atlas]

I have a script that uses fields to bring in a custom variable and I am trying to reference one of those variables in a {{ state_attr('camera.{{camera_name}}', entity_picture') }}
what is the correct syntax?

[fossil venture]

{{ state_attr('camera.' ~ camera_name, 'entity_picture') }}

[bitter atlas]

ty, I actually tried ~camera_name~

[marble jackal]

the ~ acts like a + which you could also use here

[bitter atlas]

like in python

[marble jackal]

the difference is that it will convert both parts to a string

1 + 1 # 2
1 ~ 1 # 11
`foo` + 1 # error
'foo' ~ 1 # foo1

[pure plinth]

Is there any way to filter out entities that have a label on them?
I want to make a setup that turns off all lights at night Except the ones labelled as night light. I could just make groups but with many similar exclusions it would get hard to maintain fast

[marble jackal]

https://www.home-assistant.io/docs/configuration/templating/#labels

{{ states.light | map(attribute='entity_id') | reject('in', label_entities('night_light')) | list }}
That's probably what you are looking for

[pure plinth]

ahh reject need to learn this whole template lang a bit more

[fossil venture]

I deliberately don't use + for concatenate precisely because of what it does to numbers.

[pure plinth]

Is there any way to make this into an actual group?
that would dynamically be updated? I saw the solution with automation that updates a group at startup but those seam to be a generic groups and not be usable in other service calls or when placing on the dashboard

[marble jackal]

no, dynamic updates of light groups are not possible

[pure plinth]

Will they some day?

[marble jackal]

nope, group.set is something which wouldn't be allowed nowadays anymore

so it exists because it was created when there were less strict rules. But using service calls to change entity config isn't allowed in core

it could be something for Spook

[pure plinth]

any chance for nonservice based dynamic groups?

[marble jackal]

how would you change them then?

[pure plinth]

like give that template instead of the manual list

like on the UI littel button in the corner to switch to YAML editing or similar

[marble jackal]

You can always file a feature request for it

[pure plinth]

true 🙂

[mighty ledge]

TBH, if you're dynamically labeling a group of entities, there's really no reason to use the label

just skip it and make a template sensor

[marble jackal]

wait, you could of course create a template light instead of a helper light group

I read it as that he wants to apply the labels manually, but wants to create a light group out of that

so all lights exept the labeled ones

[mighty ledge]

Yes that would be nice to have

[pure plinth]

yeah that is the idea
I add a new light and just have to add the labels to define it's behaviour

[marble jackal]

you can do that with a template light

but if you also want to adjust brightness and color temp and such it will require some templating

[coarse dawn]

Hello
I Hope it makes Not to much Problems
@arctic sorrel Haves help me but I dont know what I make wrong

[plain magnet]

@coarse dawn To format your text as code, enter three backticks on the first line, press Enter for a new line, paste your code, press Enter again for another new line, and lastly three more backticks.
```yaml
example: here
```
Don't forget you can edit your post rather than repeatedly posting the same thing.

[coarse dawn]

{{ states("sensor.wr_rs485_leistung_pv_string_1") | float / (10*440) 100 | float | round(0) }}

[arctic sorrel]

Help us help you ☝️

[coarse dawn]

yes i have do it

[arctic sorrel]

What template were you originally given? Before you changed it?

[coarse dawn]

this was the original code

name: "Energy-PercentPV1"
      state : '{{ states("sensor.pv_garage_big_growatt8k_powerpv1") | float / (16420) 100 | float | round(0) }}'
      unit_of_measurement: '%'

[inner mesa]

(16420) 100 🤔

[arctic sorrel]

Either you've missed something, or the person who gave you that never tested it

[coarse dawn]

i think the people have forget the *

[arctic sorrel]

Because that template is, as already said, quite broken

[winter forge]

I'm getting this into an automation: Error: Template rendered invalid entity IDs: "['light.livingroom_window_light', 'light.livingroom_tv_light', 'light.livingroom_behind_tv_light', 'light.livingroom_center_light', 'light.office_tv_light', 'light.quotra_livingroom_light', 'light.livingroom_wall_light']"

When trying to pass this variable

variables:
  on_lights: >
    {{ [area_id(trigger.entity_id)]  | map('area_entities') | sum(start=[]) |
    select('match', '^light.') | select('is_state','on') | unique | list }}

[arctic sorrel]

(and broken in more than one way)

[winter forge]

Oh, this is the service:

service: light.turn_off
metadata: {}
data:
  transition: 60
target:
  entity_id: |
    "{{ on_lights }}"

[inner mesa]

get rid of the quotes

and switch the | to >

[winter forge]

I switched the | to > and it reverted after saving

[coarse dawn]

my plan is
i have PV with string 1 4400W and the People sayd make this and you see the effecienty

[inner mesa]

or get rid of the "|" and put it on the same line

[winter forge]

Let me try that

[inner mesa]

the problem is that it's treating the list as a big string

[winter forge]

Why do I sometimes need the quotes and sometimes not within the HA automations?>

What is the rule about that, it would help me understand!

removing the quotes worked btw

[inner mesa]

you only need quotes if you need to have the YAML parser treat it as a string instead of a malformed dict

[inner pagoda]

basically, { is a special character in yaml, so when it's used in a spot where it could be parsed by yaml you need to quote it

[inner mesa]

in other words, surround the template in quotes if it's on the same line as the key, and don't if it's not

[inner pagoda]

the > and | in yaml start a multi-line string, so they act similarly to quotes

so putting quotes inside a multi-line string double-quotes it :)

[winter forge]

Gotcha

[arctic sorrel]

Try

{{ (states("sensor.wr_rs485_leistung_pv_string_1") | float / (10*440) * 100) | float | round(0) }}

[plain magnet]

When working with templates, don't forget:

• You can test them in Developer tools -> Templates

[mighty ledge]

that second float does nada

[coarse dawn]

What do you mean ?

[mighty ledge]

You already have a number

There’s no point making it more numbery

[marsh cairn]

Converting a float into a float does nothing

Float, floatier, floatiest

Doesn't round do that too? 🤔

[mighty ledge]

Yep

[marsh cairn]

I remembered something

[coarse dawn]

ah yes but i dont know i have become this code XD

[coarse dawn]

thank you i have no error morning i see
thanks

[arctic sorrel]

Yeah... wasn't bothering to fix the rest of that clusterfuck

[scenic verge]

a template is no longer working good since upgrading HAOS it seems: https://i.imgur.com/J77SUpI.png

and my configuration.yaml contains the following: mqtt: sensor: - name: "Living Room Audio Sensor (9=silence)" state_topic: "frigate/living-room/audio/rms" device_class: sound_pressure state_class: measurement value_template: "{{ ((value | float) | round(2)) }}"

anyone have a idea about this?

[mighty ledge]

dude

[marsh cairn]

[frail dagger]

🍿

[marsh cairn]

It's so floaty

[eternal stag]

I'm trying to use a template in the value for a service call, and while I'm not getting any visual errors, I'm not seeing it work as expected. The template I'm using in the dev tools is:

service: climate.set_temperature
target:
  entity_id: climate.thermostat_mode
data:
  temperature: '{{ ( state_attr("climate.thermostat_mode", "temperature") | float ) - 1 }}'

which works fine when tested in HA UI, but when i use the value for temperature, with or without the surrounding single quotes it just doesn't do anything when used in the widget.

I do see a resulting error in the HA logs however:

voluptuous.error.MultipleInvalid: expected float for dictionary value @ data['temperature']

So it's sending something but not the value I'm expecting... What's the correct way to use data templates in the android wiget?

[fossil venture]

Try asking in #android-archived Maybe widgets don't support templates. The template syntax looks correct.

Hmm. Seems they do: https://companion.home-assistant.io/docs/integrations/android-widgets#template

But possibly only for display and not service calls?

[marble jackal]

You can call a script and use the templates in the script

[cosmic hamlet]

how do i test if a trigger.device_id is null?

[mighty ledge]

depends on your device trigger

look in your automation trace

if yo udon't know where to look, post a trace here.

download the trace and post it in dpaste.org

[cosmic hamlet]

https://paste.debian.net/1315935/

i know its null

[mighty ledge]

so what's the problem? you don't know how to check for null?

in jinja it's abc is not none

where abc is whatever you're checking

[cosmic hamlet]

is null is not accepted

[mighty ledge]

null is none

in jinja when testing

[cosmic hamlet]

ah ty

[mighty ledge]

i.e. abs is none or abc is not none

[sonic nimbus]

how to write an template to list all device trackers in zone.home?

[mighty ledge]

{{ states.device_tracker | selectattr('state', 'eq', 'home') | map(attribute='entity_id') | list }}

[languid sandal]

Please help me with this

[tawdry pond]

Is there a cleaner way to write this card mod styling? I'm wanting to color the icon and the text which works when I tell it primary-text-color even though I expected that to not color the icon:

- type: entity entity: sensor.house_temp card_mod: style: | :host { --primary-text-color: {% if (states.sensor.house_temp.state | int <= 65) %} cyan {% elif (states.sensor.house_temp.state | int >= 74) %} orange {% else %} var(--primary-color); {% endif %}; }

As a note this works perfectly. I just want to know if it can be cleaner.

[cosmic hamlet]

how do i convert a date like Fri, May 03 05:34 PM from gmt to amsterdam with daylight savings?

[visual cedar]

Beginner question - I have a template lock; is there a way to create a "locking" or other intermediary status for it? I see only binary states in the lock spec, but yet my non-template ("native?") locks display an intermediate status in dashboards while they're in the process of locking. I'd be interested in recreating that behavior in the template lock, if possible, and even if it's just a fake delay (when the state is toggled, switch to "locking" for five seconds before displaying the toggled state, if that makes sense).

[mighty ledge]

You’d have to build all that logic in your template. It’s a pain in the butt

[visual cedar]

I guess I shoudln't have expected it to be anything but(t) ... still, it's good to know that it's at least (theoretically) possible! That way, I can put it in the to-do list (even if I never get around to doing it). Thanks for the quick reply!

[slate fossil]

The only thing I would probably do with your code is to set the house_temp as a variable at the very beginning even though it is only repeated twice.
Are you trying to avoid repeating the IF statement for the icon and then the text? You could restructure the statement so the IF is on the "outside" and the return variables are in the inside (if that makes sense.) Take a look at this example that I put together: Card modding a button card's icon and icon color. Look at the comparing numbers example.

[vapid sand]

I have a dropdown helper with each day of the week as an option (Monday, Tuesday, etc): input_select.reminder_day
I have a template helper: sensor.day_of_the_week = {{ ['Monday','Tuesday','Wednesday','Thursday','Friday','Saturday','Sunday'][now().weekday()] }}

in the dev tools page I'm trying to figure out how to compare the two which I thought was this: {{ is_state('sensor.day_of_the_week', 'input_select.reminder_day') }}
but that returns false

if i do hard coded comparrision it returns true ( {{ is_state('sensor.day_of_the_week', 'Friday') }} )
so i assume HA doesnt like the type or something but i'm a little lost what else I can do to make it work

[frail dagger]

{{ is_state('sensor.day_of_the_week', states('input_select.reminder_day')) }}

[vapid sand]

oh... it was litterally comparing the text "input_select.reminder_day" wasnt it

[frail dagger]

Your way was just checking the state of the day of the week sensor against the literal string.

Yup

[vapid sand]

sigh thank you

[frail dagger]

No problem 🙂

[vapid sand]

i figured it would be something simple but was hoping it wouldnt be simple AND dumb 😛

[frail dagger]

lmao those are the best ones to flub on though!

[sacred sparrow]

In HA dashboard this shows as "Away" {{ states('person.esperance') | title }} but when I put it in a template it says Not_home. Is there a way I can make it show what the dashboard is showing instead of the state?

[weak breach]

I'm trying to write an automation to send a short command to an RS232 device via a USB/RS232 adapter. The command would have this form:

shell_command:
   serial_command: echo -e -n '{{command template}}\x0D' > /dev/ttyUSB1

The issue I'm running into is the command template itself. Each character of the input string should be converted to the ASCII representation of that character. For example, 'Z' would be \x5A. In theory, it seems like the following would work:

{% for char in command_text %}\x{{ '%02X' % ord(char) }}{% endfor %}

However, when I try this template in Developer tools, it reports:

'ord' is undefined

Anyone have thoughts on whether this might be resolvable?

[weak breach]

Answer:

{% for char in command_text %}\x{{ '%02X' % (char | ord) }}{% endfor %}

[ivory ether]

type: entity
entity: sensor.house_temp
card_mod:
 style: |
  ha-card {
  {% set state = states('sensor.house_temp')|int(0) %}
        {% if state  >= 74 %}  --primary-text-color:orange;--paper-item-icon-color: orange;
        {% elif state >= 64 %}  --primary-text-color: cyan;--paper-item-icon-color: cyan;
        {% else %} --primary-text-color: var(--primary-color);--paper-item-icon-color: var(--primary-color);
        {%- endif -%};

[weak breach]

I'm trying to write an automation to

[edgy umbra]

Any idea why this is not working?

  style:
    mushroom-state-info$: |
      .secondary:before {
        visibility: visible;
        content: |
          {% set status = state_attr(climate.vicare_heating, 'hvac_action') %}
          {% if status == 'heating' %}
            Hallo;
          {% endif %}
      }```

[inner mesa]

are you trying to use "climate.vicare_heating" as an entity_id?

if so, you didn't surround it in quotes

like every other string you have there

[edgy umbra]

Just tested it with quotes surrounded but it still seems not working.

Like this it works fine.

        visibility: visible;
        content: '{{ states('sensor.room_temperature') | round(1) }} °C - {{ states('sensor.room_humidity') | round(0) }} %'
      }```

But i want to return more than one state...

[inner mesa]

you used the same quotes inside and out

[mighty ledge]

and you have a nested template in there