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

lockin lock loock.lock.fcl201 cannot display opertion_id when disable_away #1568

Open
gx19970920 opened this issue Feb 15, 2025 · 1 comment
Labels
question Further information is requested

Comments

@gx19970920
Copy link

Model:loock.lock.fcl201
Gateway3 version:4.0.8
Problem description:
After I set it to enable_away, when I opened the door again outside the door, lock_activoin switched from enable_away to disable_away, but the opertion_id did not switch (still remained 0) and the method did not change. However, in the Mi Home app, it can be seen that the door lock changed to unlock and the operator and corresponding unlocking method were displayed.
I think gateway3 did not recognize the unlocking status of the door lock (lock action changed from 9-Disable The Away From Home Mode to 2-Unlock). May I ask if there is any solution to this situation?

Historical records in Home Assistant:
Image

Door lock status in the Mi Home app at the same time

Image

@AlexxIT AlexxIT added the question Further information is requested label Feb 16, 2025
@AlexxIT
Copy link
Owner

AlexxIT commented Feb 16, 2025

Check debug logs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants