WebSocket reviewed (fix)

WebSocket enhancements/changes

In #105 it had been reported, that in some special conditions the websocket implementation could not establish a connection with the bridge (for more or less unknown reasons). I took this issue as an opportunity to review the current WebSocket implementation and have adjusted:

• Access WebSocket via ws:// (instead of http://)

• Use aiohttp standards to provide basic auth

• Indicate the WebSocket connection status (✅ = connected | ⛔= not connected) in the device model information

• connect to WebSocket with compress=0 setting

Fixed Polling Version

A tiny colon , had messed up the Device Information, preventing the Integration to show a device when you disabled the websocket implementation in the settings.

Please consider supporting me

Thanks to those who have already supported me in the past weeks or month that is highly appreciated! To the other users: I am putting quite an amount of energy and passion into this integration. Perhaps you could give yourself a little push (if you can afford it) and become a sponsor.

If you haven't starred this integration in Github yet - please do so - TIA