Fix infinite loop of "Should be read", Disconnect about homeswitch-api

[davidfoliveira]

Happened again:

2020-11-12 11:54:51.259158Z: [DBUG] We can send next command for bf4a36374de4!!!
2020-11-12 11:54:51.259189Z: [DBUG] Sending to bf4a36374de4...
2020-11-12 11:54:51.261395Z: [DBUG] Sending 183 bytes to 192.168.10.182:6668 (fd: 7)
2020-11-12 11:54:51.261635Z: [DBUG] Got header (prefix: 21930, seq: 0, cmd: 7, size: 12)
2020-11-12 11:54:51.269574Z: [DBUG] Got header (prefix: 21930, seq: 0, cmd: 8, size: 75)
2020-11-12 11:54:51.270981Z: [DBUG] Got device bf4a36374de4 status: {u'dps': {u'1': False}, u't': 1605182089}
2020-11-12 11:54:51.271080Z: [INFO] Got a status update about device bf4a36374de4. Device status has NOT changed (False)
2020-11-12 11:54:51.271125Z: [INFO] Device bf4a36374de4 status is False
2020-11-12 11:54:51.271182Z: [DBUG] We can send next command for bf4a36374de4!!!
2020-11-12 11:54:51.271207Z: [DBUG] No more commands in the queue...
2020-11-12 11:54:51.271226Z: [INFO] Disconnecting as command queue is empty
2020-11-12 11:54:51.271246Z: [INFO] Disconnecting from device bf4a36374de4...
2020-11-12 11:54:51.271271Z: [DBUG] Closing connecting socket to 192.168.10.182:6668 (fd: 7)
2020-11-12 11:54:51.271428Z: [INFO] Connection to 192.168.10.182:6668 was closed.
2020-11-12 11:54:51.271480Z: [INFO] Successfully disconnected from device bf4a36374de4
2020-11-12 11:54:51.274980Z: [INFO] Socket (192.168.10.182:6668) read can happen
2020-11-12 11:54:51.275052Z: [INFO] Socket for device's bf4a36374de4 has data and should be read
2020-11-12 11:54:51.275137Z: [INFO] Connection to 192.168.10.182:6668 was closed.
2020-11-12 11:54:51.275187Z: [INFO] Successfully disconnected from device bf4a36374de4
2020-11-12 11:54:51.275374Z: [INFO] Socket (192.168.10.182:6668) read can happen
2020-11-12 11:54:51.275420Z: [INFO] Socket for device's bf4a36374de4 has data and should be read
2020-11-12 11:54:51.275489Z: [INFO] Connection to 192.168.10.182:6668 was closed.
...

Looks like socket.close() is actually being called but for some reason the socket remains in socket_map{}