MQTT Disconnect socket write then close
When there are network issues and I want to disconnect from mqtt client, the socket writes are blocking and cannot be changed (I havent been successful) so it will just hang on the self.sock.write(b"\xe0\0") line in the disconnect function of simple.py. Is this a necessary action, or can I not write that byte array and just close the socket so that I do not have to worry about hanging on the write indefinitely?
umqtt.simple: add force_close parameter to disconnect() to ensure soc…
Add force_close argument to umqtt.simple.MQTTClient.disconnect() that, when set, ensures socket.close() is called even if there's an error while sending the disconnect message to the MQTT server.
The default behavior is the same as before - I'm tempted to change it; I believe it would be a better default, but I don't want to break any backward compatibility.