History_stats stopped working

henry8866 · May 10, 2022, 3:28am

I have a wyze motion sensor named wyzem02 and made a history_stats like below

platform: history_stats
name: Wyze2Motion5m
entity_id: binary_sensor.wyzem02
state: “on”
type: count
end: “{{ now() }}”
duration: 00:05:00

This entity Wyze2Motion5m records the number of times the motion sensor is “on” for the past 5 minutes.

It works perfect for long time, but suddenly it stopped working today after I pulled the latest home assistant container (Home Assistant Core 2022.5.3). When the motion sensor is triggered, it doesn’t change from 0 to 1. Anyone know what could be the issue in the latest HA container?
There is no error in log.

tom_l · May 10, 2022, 4:33am

So this is an issue with your motion sensor not the History Stats integration?

henry8866 · May 10, 2022, 12:39pm

Motion sensor triggered ok. But the history_stats Wyze2Motion5m didn’t change from 0 to 1.

tom_l · May 10, 2022, 12:41pm

Do you have any errors related to the recorder in your log?

Have you excluded the motion sensor from the recorder?

sebby · May 10, 2022, 12:47pm

hate to hijack a thread, but i am having similar issues where i am not getting any data on history_stats sensors… I created a sensor to see if my AC was on heat or cool. here is what i have as that sensor sensor.

    - name: "HVAC Activity Upstairs"
      unique_id: ui_template_hvac_activity_upstairs
      state: > 
        '{{ state_attr("climate.upstairs_thermostat", "hvac_action") }}'

Looking at the developer tools, it is capturing the states as either ‘idle’, ‘heating’, or ‘cooling’:

I also looked at the history for it and i see it is capturing data:

i then created the daily sensors for ‘heating’ and ‘cooling’ as below:

# Thermostat Day
  - platform: history_stats
    name: Thermostat Heating Today Upstairs
    entity_id: sensor.hvac_activity_upstairs
    state: 'heating'
    type: time
    start: '{{ now().replace(hour=0, minute=0, second=0) }}'
    end: '{{ now() }}'

  - platform: history_stats
    name: Thermostat Cooling Today Upstairs
    entity_id: sensor.hvac_activity_upstairs
    state: 'cooling'
    type: time
    start: '{{ now().replace(hour=0, minute=0, second=0) }}'
    end: '{{ now() }}'

they always show 0.0 on the stats, i would expect them to be showing some rolling total throughout the day. I am sure i am missing something on my end, but i can’t figure out what it is.

tom_l · May 10, 2022, 12:50pm

Looks like there might be an issue. Could you folks please add your configurations (correctly formatted) to this:

github.com/home-assistant/core

History Stats doesn't work

opened 01:20PM - 09 May 22 UTC

MikaelHoogen

integration: history_stats

### The problem Since the update to 2022.5 the history stats integration doesn'…t work properly. The first day it counted up time constantly regardless of the state of the entity_id. After midnight it stopped counting completely. When I restart HA it is updated the first minutes. Then it stops again. ### What version of Home Assistant Core has the issue? 2022.5.3 ### What was the last working version of Home Assistant Core? 2022.4.x ### What type of installation are you running? Home Assistant OS ### Integration causing the issue History Stats ### Link to integration documentation on our website https://www.home-assistant.io/integrations/history_stats/ ### Diagnostics information _No response_ ### Example YAML snippet ```yaml - platform: history_stats name: heatpump_compressor_today entity_id: binary_sensor.heatpump_compressor_state state: "on" type: time start: "{{ now().replace(hour=0, minute=0, second=0, microsecond=0) }}" end: "{{ now().replace(microsecond=0) }}" ``` ### Anything in the logs that might be useful for us? ```txt Nothing in the logs ``` ### Additional information _No response_

petro · May 10, 2022, 12:58pm

I don’t think so, look at his states, they have quotes. There shouldn’t be quotes.

Normal string states do not have quotes inside the state. It’s just the word.

tom_l · May 10, 2022, 1:01pm

Oh. Good eyes.

@sebby This:

      state: > 
        '{{ state_attr("climate.upstairs_thermostat", "hvac_action") }}'

Should be:

      state: > 
         {{ state_attr("climate.upstairs_thermostat", "hvac_action") }}

Quotes outside the template are only required when using single line templates, like this:

      state: '{{ state_attr("climate.upstairs_thermostat", "hvac_action") }}'

henry8866 · May 10, 2022, 1:08pm

No I didn’t see any errors from the log. Also it is not excluded from recorder.
It was working fine for more than 1 year. It stopped working since I did the update of the latest container. No change on the configuration.

petro · May 10, 2022, 1:11pm

post a screenshot of your binary sensor in developer tools → states page. You have @sebby have different issues.

henry8866 · May 10, 2022, 1:20pm

Here is the screenshot for the motion sensor.

petro · May 10, 2022, 1:21pm

can you post a screenshot of it in the table below, not in the set state box

sebby · May 10, 2022, 1:24pm

sebby:

  - platform: history_stats
    name: Thermostat Heating Today Upstairs
    entity_id: sensor.hvac_activity_upstairs
    state: 'heating'
    type: time
    start: '{{ now().replace(hour=0, minute=0, second=0) }}'
    end: '{{ now() }}'

@petro & @tom_l thank you!!! you guys are amazing, really appreciate all you do!

henry8866 · May 10, 2022, 1:24pm

ok here it is

petro · May 10, 2022, 1:30pm

Based on your current configuration and the screenshots, it should be working. Are you positive it’s not working? It’s only looking at the last 5 minutes. The only other suggestion I could see causing the problem is that your duration is not in quotes.

henry8866 · May 10, 2022, 9:12pm

After further checking carefully, I found that it is actually working but with delay on the updating Wyze2Motion5m.

Here are the trigger entries on the motion sensor:

Cleared (no motion detected)
8:46:16 AM - 8 seconds ago

Detected motion
8:45:34 AM - 1 minute ago

Cleared (no motion detected)
8:43:11 AM - 3 minutes ago

Detected motion
8:42:29 AM - 4 minutes ago

Below is the history graph on Wyze2Motion5m:

As can see there is delay about 40+ seconds.
I have same setup for two motion sensors, they all behave same (delay updating on the history_stats entities).

nemezis336 · May 12, 2022, 11:47am

I have a similar problem, after updating to version 2022.5.3 history stats stopped counting

  - platform: history_stats
    name: Ogrzewanie dzisiaj Pompa
    entity_id: switch.pompa_ciepla_t06
    state: "on"
    type: time
    start: "{{ now().replace(hour=0, minute=0, second=0) }}"
    end: "{{ now() }}"

other similar entities in history stats are also silent

13.05.2022 - it’s working

henry8866 · May 17, 2022, 6:04pm

Do you notice any delay on the history_stats entities?

syl2042 · December 22, 2022, 11:25am

Excuse me Guys
I try to do the same thing with my Netatmo Thermostat. Have the daily duration of heating mode.
I have

- platform: history_stats
  name: Thermostat Actif
  entity_id: sensor.statut_netatmo
  state: "heating"
  type: time
  start: "{{ now().replace(hour=0, minute=0, second=0) }}"
  end: "{{ now() }}"

And

- sensors:
    - name: "statut_netatmo"
      friendly_name: 'Statut Thermostat'
      unique_id: 9dd89288-41d4-46ca-acc5-d03e462ae987
      value_template: "{{ state_attr('climate.salon', 'hvac_action') }}"

And i have always

What’s wrong?
Is there a syntax problem?

petro · December 22, 2022, 12:44pm

Have you Restarted HA? Is recorder: in configuration.yaml?