-
-
Notifications
You must be signed in to change notification settings - Fork 317
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
On Try Again spell if local or remote connection is retried #3417
Comments
This already happens if the current network type is eligible for using a local connection. If not, it doesn't apply, only remote is tried in that case.
At the time of pressing 'retry', it doesn't even know that yet (see above). |
Once the programme knows, it shall show it, using a snackbar or however it was called. |
If you configured both local and remote connections, it already does. |
Yes, it does show it on start. But from the above screenshot state it did not show it. I observed this several times and I will not be soon in that network to retry it again. |
With openhab-Android 3.7.0 I changed the remote URI to unresolvable name and created random local URI (http://192.168.168.168). I connect over public Wi-Fi. The error message is “Cannot connect to the domain”. (The error message in the screenshot above is: The connection with the host is unsuccessful. So not exactly the same) I click on Try again. The system does not show a hint, whether it tries to connect first to the local and then to the remove address. |
The screenshot says: The connection with the host was not successful. [Try again]
In openhab-Android I have a local and a remote connection. When I am in the home network, I cannot connect to the remote connection. This is not an openHab problem, but a matter of routing fact.
When in this state, and I click on [Try again] openhab-Android tries to reconnect, but does not spell, whether it tries to reconnect fist to the local and then to the remote connection. My colclusion is, that it tries to connect only to the remote connection.
The text was updated successfully, but these errors were encountered: