## Introduction
The Xiaomi Home Assistant integration is designed to provide real-time updates on various events, including door lock status. However, a recent issue has been reported where the integration fails to update event information and door lock status in real-time. This article aims to describe the issue, provide steps to reproduce it, and outline the expected behavior.
## Issue Description
The issue begins with the failure of the Xiaomi Home Assistant integration to update event information and door lock status. Although the Mi Home app has obtained the door lock events, the integration only updates when the system is reloaded. Moreover, the obtained event information is outdated, showing events from several seconds ago when, in reality, the events occurred one or two hours prior. After a thorough restart of the Home Assistant system, the integration starts to update events automatically, but the door lock status remains stuck on 'unlocked,' and event updates only display 'event detected' without specifying the type of event.
## Steps to Reproduce
1. Use the Xiaomi Home Assistant integration normally.
2. Observe the event updates and door lock status in the Home Assistant dashboard.
## Expected Behavior
The expected behavior of the Xiaomi Home Assistant integration is to update the door lock status in real-time, reflecting the current state of the door (e.g., unlocked, locked, or ajar). Additionally, event updates should display detailed information about the type of event detected.
## Reproduce Time
The issue was first observed on July 7, 2025, at 13:52.
## System Logs
Unfortunately, the system logs are not available at this time.
## Log Timezone
The timezone of the system logs is unclear, and there is a discrepancy between the actual event time and the log time.
## Home Assistant Core Version
The Home Assistant core version is 2025.7.1.
## Home Assistant Operation System Version
The Home Assistant operation system version is 15.2.
## Xiaomi Home Integration Version
The Xiaomi Home integration version is v0.3.3.
## Additional Context
The system logs show an incorrect timestamp, with actual events occurring at 13:52 on July 7, 2025, but the logs display times after 14:00. The logs have been sent to the email for further analysis.