mirror of
https://github.com/esphome/esphome.git
synced 2026-10-10 13:33:06 +00:00
J. Nick Koston
9a5aab63d5
The connections-free retry left its sibling asymmetric: on the same full buffer the slot could report free while the device still read as connected, with nothing resending the connected=false. A one-deep latch (address + error) drains at the same 100 ms cadence and re-latches on a repeat failure; a re-reservation of the address clears it, since the client re-requesting the connect has already acted on the disconnect and a late resend would shadow the new connection. A lost connected=true stays client-timeout territory.
