frontend
frontend copied to clipboard
Duplicate entries in logbook
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
The new logbook seems to sometimes display duplicate entries. I don't have a solid procedure to reproduce, but it's happened to me with a custom date range and entity filter set, switching between a bunch of tabs in the browser window and eventually coming back to the HASS window.
Describe the behavior you expected
No duplicate events in the logbook.
Steps to reproduce the issue
- Open logbook, set an entity filter and a custom date range, switch active tab for the window, come back later. May need new events to occur while the tab is inactive?
What version of Home Assistant Core has the issue?
2022.6.6
What was the last working version of Home Assistant Core?
No response
In which browser are you experiencing the issue with?
Safari Version 16.0 (18614.1.14.1.15)
Which operating system are you using to run this browser?
macOS Ventura Version 13.0 Beta (22A5266r)
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
Hey there @home-assistant/core, mind taking a look at this issue as it has been labeled with an integration (logbook) you are listed as a code owner for? Thanks!
(message by CodeOwnersMention)
logbook documentation logbook source (message by IssueLinks)
This is very likely fixed in 2022.7.x via #12878 which is scheduled for release on July 6th
I'll leave this open in the mean time
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.