Bridge 020.218 (firmware version: 2.14.0) with Keyturner 010.318: After changing the bridge’s settings using the Android/Bluetooth App, the bridge no longer responds to HTTP requests until it gets an powercycle (unplug/plug back to power) or several minutes (10+) have passed.
Bridge and lock set up and connected, HTTP API active, bridge is connected to the lock and wifi with internet.
API requests work fine:
Open Android App and use “manage bridge”, connect to bridge.
TCP stack works fine but HTTP server no longer responds to requests:
(image removed due to forum limitation)
The App also cannot display the lock status anymore.
The API and App both work again after a powercycle or pressing the back button in the opened Android app (which seems to restart the bridge), but not if the App is simply closed.
It seems that the App block the HTTP server on the bridge and not properly terminate its own connection when the App gets closed?
The timeout is really long, it would be great if the API+App would resume working immediately after a settings change or at least after the App is closed using the Android close button.
While changing settings on the Nuki Bridge the Bridge is operating in a different mode and is not able to connect to the Smart Locks.
You need to finish configuration within the Nuki App by pressing the check icon in the upper right or leave Bridge settings screen with the back key.
Otherwise it will take 5 minutes of inactivity for the Bridge to leave this mode automatically.
You’ll notice it once it stops the constant blinking.
Actually there is no “Android close button”.
If the app is exited by pressing the Home button the app moves into the background.
This could be detected but the user might also just be switching to another app to e.g. copy the WiFi credentials and when moving back to the Bridge configuration to paste the password the Bridge settings would already be closed.
Android apps can be closed in various ways: Find, open & close apps on Android - Android Help
which should be detectable with onPause/onStop/onDestroy. But I understand that this may not be distinguishable from the app only being in the background.
We at homee ( http://hom.ee/ ) did have problems with users that could not add their Nuki to our smart home system since the Nuki Bridge did not answer the HTTP requests. So we are searching for a solution to make setting up and connecting the Nuki as simple as possible.
We plan to tell the user that they need to save/go back in the Nuki Android app and in case the Bridge is still not responding, unplug and plug it back to manually reset it.
While you guide the users through the setup just tell them to leave the settings screen by either touching the Check icon in the upper right or simply by pressing the back key on the phone before testing the homee integration.
