A disconnect() function is now added that correctly closes the websocket to the ZMEventNotification server. Also the other worker thread is being closed.
An unexpected server side websocket disconnect is now better handled, by closing the websocket and creating a new WebSocketApp again
Fixed a problem with an additional argument in the '_on_close' lambda
Renamed 'ready' to 'connected' which is a more logical name