-
Notifications
You must be signed in to change notification settings - Fork 19
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
bleak.exc.BleakDBusError: [org.bluez.Error.InProgress] In Progress #24
Comments
Hi, |
heyho |
hey there Do you have any idea on this issue? We encountered also another issue, maybe depending on each other, but not sure
|
Looking at the logs and all the lines repeated 3 or 4 times (or more) at the same time it seems the lock is trying to process more than one requests at a time. The library should reply with a proper error message but right now this is not implemented. How are you sending the requests? Is it possible that you are sending more requests at the same time? |
yep, thats also our knowledge status rn. We've build another service, that is sending the request to the bridge (pi) and waits for a response from the bridge. Sending a second request even a couple of minutes later sometimes leads to this behaviour but not always ... it's really weird - thats why i asked for some input &/ experiences from your side :D |
Do you have any logs where it happens that you perform the request and there is no reply? |
hey there
The second request then looks like the logs in my initial post... a lot of error messages but the door opens |
Hey there (again),
we have some weird issues with our setup when we trigger the API calls at some time but not always.
Mostly the error occured after the lock / api was unused for some time (~ hours / days)
The following Logging shows the error message.
Do you have any idea what that could be and how to fix it?
As i mentioned this is not always the behaviour, sometimes it works quite fast, but sometimes the lock keeps unresponsive and shows those messages in the log
Thx in advance
BR
technotroll
The text was updated successfully, but these errors were encountered: