frontend icon indicating copy to clipboard operation
frontend copied to clipboard

Entity history flatlines/freezes

Open tombadog99 opened this issue 2 years ago • 4 comments

Checklist

  • [X] I have updated to the latest available Home Assistant version.
  • [X] I have cleared the cache of my browser.
  • [x] I have tried a different browser to see if it is related to my browser.

Describe the issue you are experiencing

Climate entity history graph freezes/flatlines. This seems to be caused by a caching issue as refreshing the browser page or completely closing and reopening the HA Android app causes the entity graph to be reloaded properly.

Describe the behavior you expected

Climate entity graph loads and displays correct graph information.

Steps to reproduce the issue

  1. Open climate entity history on a specific entity
  2. Leave browser window open/don't force close Android app
  3. Return to Android app/browser window, graph reloads but has flatlined. ... Screenshot_20221113-075002

What version of Home Assistant Core has the issue?

2022.11.2

What was the last working version of Home Assistant Core?

No response

In which browser are you experiencing the issue with?

Google Chrome Version 107.0.5304.107 / latest HA Android companion app

Which operating system are you using to run this browser?

Windows 11/Android 13

State of relevant entities

No response

Problem-relevant frontend configuration

No response

Javascript errors shown in your browser console/inspector

No response

Additional information

No response

tombadog99 avatar Nov 15 '22 16:11 tombadog99

Observe flatline graphs rather often (at least once a week). Sensors are still being updated, graphs are flatlined. Only HA reboot helps - curves on graphs again are "curved", but old data are still flatlined. Happens with history-graph & custom:mini-graph-card. My case seems to be a Recorder's issue.

HA in container. Client - Win10x644+Chrome; same flatlines on iOS devices.

ildar170975 avatar Nov 16 '22 14:11 ildar170975

I am having the same issue, so I looked at the websocket messages and it looks like the history is correctly requested, but nothing is received from the server.

Opening History the first time at 10:13:41 Request: {"type":"history/history_during_period","start_time":"2022-12-10T10:13:41.870Z","end_time":"2022-12-11T10:13:41.870Z","significant_changes_only":false,"include_start_time_state":true,"minimal_response":true,"no_attributes":false,"entity_ids":["climate.otgw"],"id":34} Received: {"id":34,"type":"result","success":true,"result":{"climate.otgw": ***

Opening History the second time at 10:43:34 Request: {"type":"history/history_during_period","start_time":"2022-12-11T10:13:41.870Z","end_time":"2022-12-11T10:43:34.002Z","significant_changes_only":false,"include_start_time_state":false,"minimal_response":true,"no_attributes":false,"entity_ids":["climate.otgw"],"id":35} Received: [{"id":35,"type":"result","success":true,"result":{}},{"id":36,"type":"result","success":true,"result":[{"id":"7f3517c495a54672b733428fe719364d","username": ***

Opening History the third time at 10:50:33 Request: {"type":"history/history_during_period","start_time":"2022-12-11T10:47:27.480Z","end_time":"2022-12-11T10:50:33.181Z","significant_changes_only":false,"include_start_time_state":false,"minimal_response":true,"no_attributes":false,"entity_ids":["climate.otgw"],"id":42} Received: {"id":42,"type":"result","success":true,"result":{}}

Full log: climate.otgw.txt

PierreAronnax avatar Dec 11 '22 11:12 PierreAronnax

I think this is a duplicate of https://github.com/home-assistant/frontend/issues/13214

lubosjerabek avatar Dec 19 '22 11:12 lubosjerabek

Yes, think that may be the case - didn't find that issue before posting this issue.

tombadog99 avatar Dec 19 '22 12:12 tombadog99

fixed in 2022.2.x via #15112

bdraco avatar Jan 22 '23 07:01 bdraco