I am using the BLE API to directly connect an ESP32 to a Nuki lock.
When I execute multiple commands after each other and one of them fails I get an error report with an unknown error (00 12 00 ff 10 00).
I am not looking for the reason why the error occurred but I want to know why the next command is not picked up anymore and how to handle this.
After getting an error report I send a new command and I see the command being sent but I do not get any more messages back (also no error).
(And eventually I get a ble disconnected notification but I do not know when the disconnect actually happened or if it was due to the error or due to inactivity).
Does the lock close the connection on error? Is this standard behavior after every error?
So After an error I should always reconnect BLE or is there a better/different way to handle this?