Closed mueller-ma closed 3 years ago
AFAICT the timeout is inevitable (server side thing), so this issue is about reporting SocketTimeoutExceptions differently if they're for a remote connection?
(Ideally the server call would report error instead of timing out)
I already thought this is a server side issue and opened this issue as a reference for an openhab-cloud issue (https://github.com/openhab/openhab-cloud/issues/199)
It's an issue with the cloud connector in the server itself (the component that's loaded into the server and talks to openhab-cloud) ... that's probably more suited for openhab2-addons?
Actual behaviour
The app should show "openHAB cloud is not configured for remote access" or similar.
Expected behaviour
The app loads for a long time until a timeout occurs.
Steps to reproduce
Can you reproduce the issue in demo mode?
No.
Environment data
Client
Server
openHAB Cloud
Logs
App log
openHAB Server log
Reverse Proxy log