Suppress connection retries when network is unavailable

[Tampa]

In recent history the Gloebit api has had occurrences of being unavailable. This has shown that as soon as the network becomes unavailable the module attempts to reconnect constantly. This causes a message of the failure to connect to be sent across the region. The error is not conclusively and does not point to Gloebit as the cause, which ultimately yields to users freaking out.

Ideally the module, upon encountering a failure to connect to the remote api handles the error itself and produces a proper error message that is more descriptive of the problem at hand.