Atlas WiFi socket not being closed if remote device powers off

This is mainly with my dash project, but I have been able to replicate with TS as well now.

If the Wi-Fi connection is ended without a socket closure (power cycling my dash) or (force closing TS or the laptop sleeping), the connection can not be resumed until the ECU has been power cycled.

Potentially showing the need for a timeout in the implementation on the atlas, to reset the state machine.
I believe it's keeping the connection open even after the remote device has dropped off.

Start by reproducing the Atlas WiFi failure with the remote device power-cycled, TS force-closed, or the laptop put to sleep. Trace the Atlas socket handling and state machine after the connection drops, then verify that the ECU can resume the connection without a power cycle.

Written by the indexing model from the issue text.