Get temperature from yesterday

[petro]

Because that template sensor clears the value out every time states(‘sensor.total_kwh’) changes. If the time is 11:55pm, then it stores the value. Any other time it changes, it clears the value. You’d need to add an else for it to work properly. I’m not sure how his was working in the first place.

- platform: template
  sensors:
    yesterdays_kwh:
      friendly_name: "Yesterday's kWh"
      entity_id: []
      value_template: >-
        {% if now().hour == 23 and now().minute == 59 -%}
          {{ states('sensor.total_kwh') }}
        {%- else %}
          {{ states('sensor.yesterdays_kwh') }}
        {%- endif %}
      unit_of_measurement: "kWh"

[hirschy]

Super, seems to work now - thank you, petro. One other question is: what happens, if the “triggering” sensor does not change exactly within that hour and minute?

[petro]

then nothing gets stored. You’d have to add sensor.time into the template.

[Bollux]

I know i’m reacting to a quite old post, but it is almost the thing i’m looking for.

Is it possible to get the value for the last day of a specific month, but without hardcoding the specific date?

[krash (Harry)]

Hey everyone, kind of late to the party but, here is the query I used, in case it helps anyone:

[SOLVED]Calculate sensor Increment / Difference in set time intervals (1h, 6h, 12h, 24h)

Here is how I did it by querying the database (mariaDB): - platform: sql db_url: !secret hassioslave_db_link queries: - name: history_1h query: SELECT * FROM states WHERE entity_id = 'sensor.my_sensor' AND created < DATE_ADD(NOW(), INTERVAL -3-1 HOUR) ORDER BY state_id DESC LIMIT 1; column: 'state' db_url: !secret hassioslave_db_link : I have an external DB, so i needed to declare the link, if you are on default recorder settings i think this can be ommited. c…

[HAuserSince2019]

Hi is it possible the syntax should be

  - platform: template
    sensors:
      verwachte_temperatuur:
        friendly_name: "Temperatuur vandaag"
        value_template: >-
          {% if now().hour == 23 and now().minute == 59 -%}
          {{ states('sensor.buienradar_temperature_1d') }}
          {%- endif %}
        unit_of_measurement: "°C"

I get an error when using the part:

entity_id: []

I also want to have/port the yesterday predicted expected temperature to be available today. Because when I look at the today temperature, it displays the current temperature (which in the morning can be totally off what it is gonna be today). And in the morning i’d like to know what the expected temperature is gonna be today so I can dress to it properly (simple question isnt’ it haha). And the only place to find that is in the history of what was predicted yesterday.

[petro]

his template never worked, see my comment below solving the issue. entity_id is also deprecated, the good news is that you don’t need it and the template will still work.

EDIT: Also, that template requires you to wait until after midnight to see the actual sensor change occur. If you use @krash’s link, it doesn’t have that problem.

[HAuserSince2019]

So @krash link query is not putting a draw on resources like mentioned above?

Just for fun-sake. I was wondering why the template wouldn’t work. Indeed you’re right. If I enter it in the config.yaml under sensors it doesn’t work…
But if I enter it in the developer templating-test-tool. It does work… why??? Is it because the reboot should occur at exactly that that timeframe? But would the template be useful if I put it in an automation or script? I like the simplicity of it…

[petro]

It won’t work in the template editor either because your times won’t match. If it’s working for you, you’re doing something wrong. That template will only work once it passes midnight once. Then it will stay that value until the next midnight if you use the updated template I posted awhile ago. The template you posted in this post will only work from 23:59 to 00:00. All other times it will be unavailable.

[petro]

FYI, an updated version of the template using the new template sensor integration would be:

template:
- trigger:
  - platform: time
    at: "00:00:00"
  sensor:
  - name: Temperatuur vandaag
    unique_id: verwachte_temperatuur
    state: "{{ states('sensor.buienradar_temperature_1d') }}"
    unit_of_measurement: °C

Just keep in mind that it will be unavailable until the trigger fires. You can add a home assistant startup trigger in there too if you want it to refresh at startup. However, it will not be the midnight time.

[krash (Harry)]

I have 6 sensors querying this way. I have not noticed any delay.
Nothing big enough to be noticeable at least.

[petro]

Because you don’t place it in sensor.yaml. it goes in the template section.

@petro

template:

[miguelpucela]

I’ve found this old thread.

Just in case anybody is interested in getting last day’s sensor data every hour, you can check this post: https://community.home-assistant.io/t/maintain-an-array-with-last-values-of-a-sensor/368806/6.

The related part to this post is the automation, where I maintain last 25 values of a sensor (every hour since yesterday at this hour) with an first-in first-out buffer made with an input_text.

In the template sensor I extract values of the buffer and process them to get a simple estimation of next hours linear-weighted average temperature.

[miljbee]

I made it using the sql integration. The suggested queries didn’t worked for me, so I wrote my own: Here it is:

SELECT state FROM states WHERE entity_id = 'sensor.YOURSENSOR' AND CAST(strftime('%s', last_updated) AS integer) > (CAST(strftime('%s', 'now') AS integer) - 86400) ORDER BY last_updated LIMIT 1

And I don’t think this one will have troubles with TZ or DST. The compare is done on unix time stamps (%s).

What I still don’t know is how to control the refresh rate of this sensor. If you have any tip, let me know

[tom_l]

When I try to use that I get:

1305 - FUNCTION homeassistant.strftime does not exist

[koying (Chris B)]

STRFTIME is specific to sqlite. That 1305 comes from MySQL, doesn’t it?

[tom_l]

Yeah I’m using MariaDB. I think I’ve got it:

SELECT state FROM states WHERE entity_id = 'sensor.total_cost_today' AND HOUR(TIMEDIFF(UTC_TIMESTAMP(), last_updated))>=24 ORDER BY last_updated DESC LIMIT 1

[Nick4 (Nick)]

I started using Grafana for this (and other reasons).
It’s strange that nobody mentions the existence of it?

EDIT: this is mainly addressed to those looking for a way to have data from the past

[tom_l]

I needed a sensor not a graph.

[bartland]

@miljbee

What I still don’t know is how to control the refresh rate of this sensor. If you have any tip, let me know

The querying of the DB indeed takes a lot of CPU power; my Pi4 increased from 30% CPU usage to 50%, which really slows the overall experience of HA.

Solution: disable the updates for the SQL sensor and update it via an automation at the frequency you want.

see: SQL - Home Assistant scan interval
In summary: disable the updates in the SQL integration (via the 3 dots and system options).
Next: make an automation to update the sensor, eg. every 10 minutes.

Example:

- alias: update van zonneproductie gisteren op dit uur
  id: "6f18655a-e923-46b5-9a83-8d3340458e83"  
  description: ""
  trigger:
    - platform: time_pattern
      minutes: /10
  condition: []
  action:
    - service: homeassistant.update_entity
      data: {}
      target:
        entity_id: sensor.zonneproductie_gisteren_op_dit_uur
  mode: single

Note: I defined the SQL sensor in the configuration.yaml file and saw that the sensor was mentioned 2 times in the SQL integration. I have the impression that you have to define the SQL sensor via the GUI only instead of the configuration.yaml because you cannot disable the updates via the config file.