[SOLVED] Template sensor giving unknown but developer template shows true

smile · January 8, 2023, 9:55pm

Template show correct in developer tool template editor, but error in configuration ?

TemplateError('ValueError: Template error: float got invalid input 'unavailable' when rendering template '{{ ((states.sensor.varmepumpe_total_daily_energy.state | float) * (states.sensor.strompris_kwh.state | float)) | round(2) }}' but no default was specified') while processing template 'Template("{{ ((states.sensor.varmepumpe_total_daily_energy.state | float) * (states.sensor.strompris_kwh.state | float)) | round(2) }}")' for attribute '_attr_native_value' in entity 'sensor.varmepumpe_kost_daglig'
TemplateError('ValueError: Template error: float got invalid input 'unavailable' when rendering template '{{ ((states.sensor.varmepumpe_forbruk_mnd.state | float) * (states.sensor.strompris_kwh.state | float)) | round(2) }}' but no default was specified') while processing template 'Template("{{ ((states.sensor.varmepumpe_forbruk_mnd.state | float) * (states.sensor.strompris_kwh.state | float)) | round(2) }}")' for attribute '_attr_native_value' in entity 'sensor.varmepumpe_kost_mnd'
TemplateError('ValueError: Template error: float got invalid input 'unavailable' when rendering template '{{ ((states.sensor.easse_forbruk_kwh_dag.state | float) * (states.sensor.strompris_kwh.state | float)) | round(2) }}' but no default was specified') while processing template 'Template("{{ ((states.sensor.easse_forbruk_kwh_dag.state | float) * (states.sensor.strompris_kwh.state | float)) | round(2) }}")' for attribute '_attr_native_value' in entity 'sensor.ladebil_kost_daily'
TemplateError('ValueError: Template error: float got invalid input 'unavailable' when rendering template '{{ ((states.sensor.easse_forbruk_kwh_mnd.state | float) * (states.sensor.strompris_kwh.state | float)) | round(2) }}' but no default was specified') while processing template 'Template("{{ ((states.sensor.easse_forbruk_kwh_mnd.state | float) * (states.sensor.strompris_kwh.state | float)) | round(2) }}")' for attribute '_attr_native_value' in entity 'sensor.ladebil_kost_mnd'
TemplateError('TypeError: is_state() takes 3 positional arguments but 4 were given') while processing template 'Template("{% if is_state('sensor.washing_machine_status','Running','Finishing') %} Running {% else %} Finishing {% endif %}")' for attribute '_attr_native_value' in entity 'sensor.vaskemaskin_status'

Didgeridrew · January 8, 2023, 9:59pm

Many filters (including float) require assigned defaults as of 2012.10

From Templating Docs:

WARNING

Avoid using states.sensor.temperature.state , instead use states('sensor.temperature') . It is strongly advised to use the states() , is_state() , state_attr() and is_state_attr() as much as possible, to avoid errors and error message when the entity isn’t ready yet (e.g., during Home Assistant startup).

smile · January 9, 2023, 10:59am

Thanks , Seem template is little bit correct now as documentation. what you think ?
How can i manage to only 2 digits after decimal.

{{ states( 'sensor.varmepumpe_total_daily_energy' ) | float * states( 'sensor.strompris_kwh' ) | float | round(2) }}

Troon · January 9, 2023, 11:14am

Extra set of brackets. You’re just rounding the kWh figure. Here it is with the defaults added too:

{{ (states('sensor.varmepumpe_total_daily_energy')|float(0)*states('sensor.strompris_kwh')|float(0))|round(2) }}

smile · January 10, 2023, 10:19pm

Thanks, but still error

Configuration invalid!

Error loading /config/configuration.yaml: invalid key: "OrderedDict([("(states('sensor.gangen_varmeovn_cal_energy_hourly')| float(0)*states('sensor.strompris_kwh')|float(0))|round(2)", None)])"
in "/config/packages/Varmeapparater/ganagen_varmeovn.yaml", line 49, column 0

My Template is:

value_template: {{ (states('sensor.gangen_varmeovn_cal_energy_hourly')|float(0)*states('sensor.strompris_kwh')|float(0))|round(2) }}

Troon · January 10, 2023, 10:26pm

You need to surround a single-line template in double quotes. See the important rules in this page:

Because your template uses single quotes, surround it with double quotes.

smile · January 10, 2023, 10:34pm

Do you mean like

value_template: {{ (states("sensor.gangen_varmeovn_cal_energy_hourly")|float(0)*states("sensor.strompris_kwh")|float(0))|round(2) }}

Troon · January 10, 2023, 10:37pm

No. Like this:

value_template: "{{ (states('sensor.gangen_varmeovn_cal_energy_hourly')|float(0)*states('sensor.strompris_kwh')|float(0))|round(2) }}"

smile · January 10, 2023, 10:54pm

After i use double quotes, an other error popup

Invalid config for [sensor.template]: invalid template (TemplateSyntaxError: unexpected char "'" at 71) for dictionary value @ data['sensors']['gangen_varmeovn_kost_idag']['value_template']. Got "{{ states('sensor.gangen_varmeovn_cal_energy_daily')| float(0)*(states('sensor.strompris_kwh | float(0)) | round(2) }}". (See ?, line ?).
Invalid config for [sensor.template]: invalid template (TemplateSyntaxError: unexpected ')') for dictionary value @ data['sensors']['varmepumpe_time_pris']['value_template']. Got "{{ states('sensor.gangen_varmeovn_cal_energy_hourly')| float(0)*states('sensor.strompris_kwh')|float(0))|round(2) }}". (See ?, line ?).

I dont know why i have to use 2 different syntax in same type template ? one is valid with float(0)) and other is valid with float(0)

if i delete extra ) like float(0) then then template is valid

value_template: "{{ states('sensor.varmepumpe_forbruk_mnd')|float(0)*states('sensor.strompris_kwh')|float(0))|round(2) }}"

ERROR

Invalid config for [sensor.template]: invalid template (TemplateSyntaxError: unexpected ')') for dictionary value @ data['sensors']['varmepumpe_kost_mnd']['value_template']. Got "{{ states('sensor.varmepumpe_forbruk_mnd')|float(0)*states('sensor.strompris_kwh')|float(0))|round(2) }}". (See ?, line ?).

if i add extra ) like float(0)) then then template is valid

value_template: "{{ (states('sensor.gangen_varmeovn_cal_energy_hourly')|float(0)*states('sensor.strompris_kwh')|float(0)|round(2) }}"

ERROR

Invalid config for [sensor.template]: invalid template (TemplateSyntaxError: unexpected '}', expected ')') for dictionary value @ data['sensors']['gangen_varmeovn_time_pris']['value_template']. Got "{{ (states('sensor.gangen_varmeovn_cal_energy_hourly')|float(0)*states('sensor.strompris_kwh')|float(0)|round(2) }}". (See ?, line ?).

Troon · January 11, 2023, 7:11am

Please post the entire code of the sensor. If this is a template sensor using the modern format, you should use state not value_template — but without the whole code we’re wasting time guessing.
Have a look at the excellent documentation (here, for example).

For the template itself, the brackets aren’t just something you randomly sprinkle in to see if it works. It can help to space things out a bit to understand what’s going on. Here’s the template from my prior post, and then again spaced out:

{{ (states('sensor.gangen_varmeovn_cal_energy_hourly')|float(0)*states('sensor.strompris_kwh')|float(0))|round(2) }}

{{
  (
    states('sensor.gangen_varmeovn_cal_energy_hourly') | float(0) *
    states('sensor.strompris_kwh') | float(0)
  )  | round(2)
}}

Each sensor is converted to a float then multiplied together, then the result, contained in the outermost brackets, is rounded.

In your second post above (#36), you were missing those outermost brackets, so the round was only applied to the price sensor.

tomsr · April 8, 2023, 2:23pm

So after giving up on this, I thought I’d have another go. Wrote some errors in to see what the issue is.

What state do I still get? “unknown”

So painful. Any clues?

template:
  - sensor:
      name: test
      device_class: timestamp
      state: >
        {% set datetime_attr = state_attr('input_datetime.time', 'timestamp') %}
        {% if datetime_attr is defined %}
          {% set timestamp = datetime_attr | float %}
          {% if timestamp %}
            {% set formatted_time = timestamp | timestamp_custom('%H:%M', False) %}
            {{ formatted_time }}
          {% else %}
            {{ 'Error: Invalid timestamp' }}
          {% endif %}
        {% else %}
          {{ 'Error: input_datetime.time not defined' }}
        {% endif %}

Edit.

I thought I’d rewrite this using strftime instead. Results? “unknown”

template:
  - sensor:
      name: test
      device_class: timestamp
      state: "{{ state_attr('input_datetime.time', 'timestamp') | float | timestamp | strftime('%H:%M') }}"

petro · April 8, 2023, 3:12pm

What is your goal with this? Both template sensors have errors, but they are also pointless because you’re using a datetime entity which already mirrors a timestamp sensor in regards to automations.

tomsr · April 8, 2023, 3:19pm

Because this blueprint only allows sensor inputs for alarm time. The other option is a manual time which means editing the automation every day.

petro · April 8, 2023, 3:51pm

Ok,

{{ today_at(states('input_datetime.time')) }}

tomsr · April 8, 2023, 7:35pm

Thank you! I now get a result that isn’t “unknown”.

Should today_at use my system time or local time? It’s showing an hour earlier than the input which would be GMT. I’m in London and we’re now at BST, one hour ahead.

My system is set to London and it shows the correct current time.

I’ve tried adding local and as_local but neither resolve it.

petro · April 8, 2023, 9:31pm

today_at does use local time. If you’re timestamp isn’t showing up correctly then you aren’t using the correct time somewhere on your system. There were bugs in older versions of home assistant related to today_at, but they were fixed. So make sure you’re on the latest HA.

tomsr · April 8, 2023, 10:28pm

It does indeed display correctly in anything UI:

But when you check what it’s showing in the backend, via Developer / States it’s wrong:

tomsr · April 10, 2023, 11:04pm

Based on another post from you @petro (clearly very in demand) I believe the +0000 at the end of the sensor is showing that it’s ignoring my local time zone and is reporting UTC.

Shouldn’t today_at handle that? If not, is there something I can add to your code above to fix?

petro · April 10, 2023, 11:08pm

The backend is UTC. If you’re in a +1 timezone then 22:36 +00:00 is correct as that’s the same as 23:36+01:00

Today at only works with “00:00:00” or “00:00” time formats. You should use

{{ states('input_datetime.time') | as_datetime | as_local }}

because you have a fully fleshed out timestamp, not just time.

tomsr · April 13, 2023, 8:11pm

This did it. Thanks very much for your help.