-
Notifications
You must be signed in to change notification settings - Fork 11
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
Inconsistent/slow updates from locks #22
Comments
@stevearmitage I think I'll need more data from you to dig into this. My suspicion is that the data is just not coming through TTLock's cloud reliably, but if you could turn on debug mode for the extension your home assistant logs should have the raw events as they are received via the webhook. If you see an event come in, but it's not being processed can you share those logs and I can take a look. |
This is probably the cause This error originated from a custom integration. Logger: custom_components.ttlock.api Received bad state for <custom_components.ttlock.api.ApiLock object at 0xffff576f53f0> state={'errcode': -3003, 'errmsg': 'The gateway is busy. Please try again later.', 'description': '网关正忙,请稍后再试。'} |
What is that in response to?
Are you interacting with your gateway at the same time with anything else?
|
For the record, I think this was addressed by the changes for #34 so I'm going to mark this as closed but please feel free to re-open it if you still see these issues. |
I've played a little more and It's getting some of the status updates, some take over a minute to come through. Is there anything i can do to improve this?
Originally posted by @stevearmitage in #1 (comment)
The text was updated successfully, but these errors were encountered: