Logbook does not show a state for a newly created sensor

[ildar170975]

The problem

(moved from Frontend https://github.com/home-assistant/frontend/issues/16533)

I just created a sensor with a state "xyz". And a Logbook card (and a Logbook page as well) does not show a history for this sensor:

Assume that Logbook card only shows CHANGES. That means that for ANY sensor which was not changed within hours_to_show the Logbook will be empty - and this is true (and logical):

This "only show changes" logic is correct since for every state a "time of state change" is displayed; if this time is beyond hours_to_show - nothing to report. A simple test: go to Dev tools and manually set sun.sun to anything else, then restore a previous state - these entries will be displayed in the Logbook:

But a sensor's creation is also a state CHANGE, that is why it is logical to show this very 1st state in the Logbook.

One more example: Here is a new created entity:

The history shows a correct graph - the sensor was created at ~23:25.

And same is for History page - the graph is OK:

But the logbook is EMPTY, and I find it inconsistent:

What version of Home Assistant Core has the issue?

2023.11.2

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Container

Integration causing the issue

logbook

Link to integration documentation on our website

https://www.home-assistant.io/integrations/logbook/

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant[bot]]

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!

Code owner commands

Code owners of `logbook` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign logbook` Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

---

logbook documentation logbook source _{^{(message by IssueLinks)}}

[issue-triage-workflows[bot]]

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.

[ildar170975]

up

[issue-triage-workflows[bot]]

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.

[ildar170975]

up

[issue-triage-workflows[bot]]

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.

[ildar170975]

up