Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

history-graph is "one change" delayed #16996

Closed
3 tasks done
ildar170975 opened this issue Jun 22, 2023 · 3 comments
Closed
3 tasks done

history-graph is "one change" delayed #16996

ildar170975 opened this issue Jun 22, 2023 · 3 comments
Labels

Comments

@ildar170975
Copy link
Contributor

Checklist

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

Describe the issue you are experiencing

Here is a more-info for input_number entity:

aa1

Note that the graph is "one change" delayed.

Same with a history-graph card:
aa2

Describe the behavior you expected

Graph must reflect the latest change.

Steps to reproduce the issue

As above

What version of Home Assistant Core has the issue?

2023.6.2

What was the last working version of Home Assistant Core?

No response

In which browser are you experiencing the issue with?

Chrome 114.0.5735.134

Which operating system are you using to run this browser?

Win10

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

@karwosts
Copy link
Contributor

Hm this is not my experience.

number-change

@ildar170975
Copy link
Contributor Author

ildar170975 commented Jun 22, 2023

This is really strange.
Tried to reproduce it:

  1. Create a new helper (number_2).
  2. Duplicate the previously used card, then replaced with number_2.
  3. And it works as expected!
  4. Checked again with a number - same glitch.
  5. Cleared cache - works OK.

Could it be a really caching issue???
I never heard that history-graph uses cache.

@github-actions
Copy link

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the stale label Sep 20, 2023
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Sep 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants