Trying to read a not used ID server cause reset about atproto HOT 2 OPEN

Hi,
As I mentioned on ESP8266 forum, I have that same behavior after CIPCLOSE=conn-context-id , I have updated (added manual control connection 😄 ) my TCP-UDP-Sender app (published at github) and now I was able to pinpoint moment when the reboots happens:
ESP get stuck/hung-up in moment that new connection is being created to server.
And wdt_reset happens also, when I want release connection handle (context/etc) from 2nd connection (because I didn't do it just after reading data from that conn-context). So calling CIPCLOSE=0 and next CIPCLOSE=1 make ESP to wdt_reset too...

from atproto.

Yes, I agree with you. It looks like a same issue.
I hope Igrr fix it.
Igrr, thanks for your precious time.

from atproto.