The current pull request development state works fine during an openHAB start-up.
But it fails for a thing update (e.g. if the .things file is modified) and the openHAB system disposes and initializes the binding again.
ToDo:
1) lock / sync Threads and handle multiple dispose/initialize calls
2) "queue and schedule" requests to the Nuki Bridge and handle the 503 responses (Bridge is most likely in use by another request) if possible.
The current pull request development state works fine during an openHAB start-up. But it fails for a thing update (e.g. if the .things file is modified) and the openHAB system disposes and initializes the binding again. ToDo: 1) lock / sync Threads and handle multiple dispose/initialize calls 2) "queue and schedule" requests to the Nuki Bridge and handle the 503 responses (Bridge is most likely in use by another request) if possible.