Possible History Bug

Configuration
1

I have a total runtime calculator based on a binary switch that all of a sudden jumped by ~400,000 hours. No idea why, could this be bug?

Screenshot 2024-07-06 at 13.11.00
Screenshot 2024-07-06 at 13.11.002570×1366 227 KB

CONFIG

sensor:
  - platform: history_stats
    name: RO Pump Run Time
    entity_id: binary_sensor.ro_pump
    unique_id: f420a137-4568-4beb-861d-c89bd140c715
    state: "on"
    type: time
    start: "{{as_datetime(0)}}"
    end: "{{now()}}"

I suspect this has something to do with the fact that I started counting from 0 epoch. But the binary sensor didn’t exist then, so it couldn’t possible be on, and why would this have suddenly changed

2

Check this post. Your recorder may have problems following the recent update. This causes all sorts of problems related to the history. Upgrading the integrations and disabling auto-purge made things better for me.