Logbook missing state changes

[JonLaliberte]

The problem

https://community.home-assistant.io/t/logbook-missing-generic-thermostat-entry/525114

I’ve seeing this same issue with a bunch of zigbee devices (zha, devices are Aqara door sensors). They will sometimes show open even though closed(or vice versa). So the logbook will show closed closed with no open between them.

However automations are working properly for the given state trigger.

I’m seeing this on two separate instances of HA starting sometime after 2022.01 I believe, but it’s possible that it started earlier.

What version of Home Assistant Core has the issue?

2022.02.0

What was the last working version of Home Assistant Core?

2021.12

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Logbook, ZHA

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

On mobile but I can try to get more diagnostics tomorrow and add them if needed.

Images below show an example where the door opened at 10:17pm (the traces on the automation confirm this), but it doesn’t show up in the logbook.

[home-assistant]

Hey there @home-assistant/core, mind taking a look at this issue as it has been labeled with an integration (logger) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of logger can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Change the title of the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign logger Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

---

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

[issue-triage-workflows]

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.