WebSocket implementation fix
A WebSocket fix
Looks like that 'null' must be written different in the WebSocket implementation as reported in #124. With the new release the code will write python 'None' value (instead of the string 'null').
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