-
Notifications
You must be signed in to change notification settings - Fork 785
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
Exception when several commands arrive in a short time #1424
Comments
Thanks for pointing this. With immediate:false the BT action will go to a queue and be processed at the next connect time. In the meantime I will check how this mechanism can be improved. |
My current workaround is that I have a fixed delay between both curtains of 10 seconds via the home automation. I also experimented with
Thank you 🙏🏼 |
More details with the same sending of two successive WRITE commands, with decoded backtrace
|
This looks to be caused by the bleconnect loop still iterating when the command arrives which then swaps the queue when immediate is used. A semaphore or other blocking mechanism my be required. |
This issue is stale because it has been open for 30 days with no activity. |
This bug is still present in the current version 1.6.0... #unstale |
This issue is stale because it has been open for 90 days with no activity. |
Bump |
https://docs.openmqttgateway.com/upload/troubleshoot.html
Describe the bug
If several
ble_write_address
commands are sent in a too short time interval, I get an exception and the command is not executed.To Reproduce
Steps to reproduce the behavior:
Expected behavior
Since both write requests have the
immediate
flag set, I would expect both requests to be written to a queue, the scan to be interrupted, and then both requests to be processed in sequence.Environment:
Library version related to the problem you have (if you have troubles with RF provide the version of RCSwitch library)For IR and RF clarify if you tested with the basic examples given with these librariesAdditional context
esp32dev-ble
)The text was updated successfully, but these errors were encountered: