umqtt (with tls): check_msg() / wait_msg() - how to know connection is gone? timeout?

I'm using the umqtt module - on conjunction with ussl_mbedtls - within the UNIX port with mbedtls.
When I re-route the traffic originally going to my MQTT broker to /dev/null (e.g. 127.0.0.1), check_msg() as well as wait_msg() continue behaving as before. No different return value, no exception thrown.
From the umqtt.robust implementation I figure that should be the case though.
I also thought this might be due to an overly long timeout, so I called settimeout(X) on the underlying socket, but then wait_msg() throws an exception right after X seconds - no matter what - which I also appears weird to me.

What's the way to go to catch network issues and potentially reconnect automatically when using umqtt.{simple,robust} with TLS?

Comienza leyendo las implementaciones de umqtt.simple y umqtt.robust, centrándote en check_msg(), wait_msg() y en cómo manejan el socket subyacente. Reproduce el comportamiento en el puerto UNIX con ussl_mbedtls, incluido settimeout(X), y compara los resultados observados con el comportamiento esperado de pérdida de conexión y reconexión descrito en el issue.