This PR is important because in ESP32 the maximum number of sockets is around 8 or 10, so if the old sockets are not explicitly closed or garbage-collected, they pile up until no new connections are possible.
QUERY · ISSUE
How to use the umqtt.simple in other socket
I am use the esp32 and w5500 eth module. But I am using a third-party driver().
The socket of third-party drivers does not include the read and write method
How can I make umqtt.simple support this socket
CANDIDATE · PULL REQUEST
umqtt.simple: Close old socket on connect
This closes the old socket of the client if one is present during a connection attempt to prevent the initialization of multiple sockets when the function is called repeatedly. It comes in handy if properly disconnecting from the broker isn't possible.
1 comment
Have you checked this discussion https://github.com/orgs/micropython/discussions/11474? Since MicroPython version 1.20.0 the W5500 is supported by MicroPython (from Espressif ESP-IDF implementation). So I think that if you use that, everything else (like as mqtt client and any other protocol, including ssl) will be transparent because that espressif W5500 implementation (and micropython support) is using a raw ethernet implementation.
Can anyone confirm if what I did write is correct?
I have reviewed the discussion, but I have only succeeded with the code in the discussion once. Even if the same code is used after the second attempt, it cannot connect to the network and can cause SPI blocking. I do not understand why this is the case. Even if SPI is available after a power outage and restart, ETH still cannot obtain the IP, so I can only try using a third-party driver
Under the same code, there will always be an OSError prompt: Ethernet enable failed. I guess it's a problem with SPI blocking. How can I avoid this problem.
When I am in the shell, I can obtain the IP address, but when I use thorny to actually execute it, it cannot work