[Feature Request]: Automatically reconnect to a node that reboots (or for other reason is temporary disconnected)

[geirgp]

Prerequisites

• I have searched existing issues to ensure this feature hasn't already been requested
• I have checked the documentation to verify this feature doesn't already exist

Problem Statement

Web client doesn't reconnect to a node after it has rebooted, instead the node becomes unresponsive in the UI and the user doesn't get any feedback that it's disconnected (though possible to see in dev console log). On several occations I've found my self clicking around for some time before realising the bt/serial connection is dead.

The only way i've found to work around (reconnect) it is to do a complete refresh of the client. Inherently i lose connection to any other node i'm currently connected to which is rather frustrating when working with multiple nodes and applying changes to them all (multiple saves, multiple rebeoots). Its a real workflow disruptor.

Proposed Solution

Acceptance Criteria

1. Open web client and connect to more than one node.
2. Save a configuration change to one of the nodes which forces a reboot of that node.
3. (optional) Verify that there is a visual indicator showing that the reebooting node is unavailable/disconnected.
4. Wait for the node to complete the reboot sequence.
5. (optional) Verify that the visual indicator now shows the node as normal (connected).
6. Verify that all nodes are still connected (e.g send a message from the rebooted node to another of the connected nodes, change to that other node in web client and verify the message is displayed).

The (optional) indicators are nice, but not necessary. Here are some ideas when disconnected:

• in the node list (where short name is displayed in a circle, under the home icon): overlay a symbol (e.g X or a disconnected icon), or apply faded color, or short name text in gray/red.
• for a selected node in the node info section: display "Disconnected", for example replacing "Charging". could also add a X disconnected icon.

Current Alternatives

Full reload of the client application, and reconnect to the node. Inherently also losing connection to other nodes that were connected (super annoying).

Importance

Very Nice to have - the current workaround is a efficiency killer. The feature that allows connections to multiple nodes loses a lot of its value when you have to reconnect all of them manually (3-4 clicks each) after reloading the page to get one of them back after a disconnect (usually due to reboot, but also usb disconnect/reconnect or BT out of range->back in range suffers).

Additional Context

No response