claude-botandClaude Opus 5
c8b0d1cd4b
Anything holding a long-lived TCP session to a device outside the cluster keeps a half-open socket when the node under it moves. The peer drops its side; the pod never learns, because no RST arrives and no keepalive fires. This cost real time after the conversion. Home Assistant held seven ESTABLISHED sockets to ESPHome devices that were themselves reporting "not connected". It logged nothing and retried nothing, because as far as it knew the connections were fine — so the search went through logs that were empty by construction. The one device Home Assistant did log was the only one genuinely offline. Records the check that settles it in one command, reading /proc/net/tcp in the pod, and notes that reloading the integration is the lighter fix than restarting the pod. Placed in "Verify and restore" rather than the known-stale list: it is something to check before calling a conversion finished, not a trap in the tooling. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>