Chain Node failover not working

[johansealstorage]

If I have 2 Lotus Full Chain Nodes and add both to Curio, there are a few issues:

1. Curio does not always show both Chain Nodes on the Overview screen
2. Curio does not failover to another Chain Node if the currently used Chain Node fails (switched off or loose sync)
3. Curio fails to start up if the last Chain Node it was connected to, is not accessable - even if there are multiple other Chain nodes to try.

My base config contains the api info for two Chain Nodes.
If I stop the Chain Node that curio is using, curio just shows the failed chain connectivity and never kicks over to using the other Chain Node.
I have tested both Chain Nodes from 2 different boosts, and both are accessible. Also using one at a time in Curio, they are both accessible.

I tried to restart the node without the 10.4.10.201 Full Chain Node and it fails with this:

2024-09-10T21:24:10.787Z        WARN    curio/deps      deps/apiinfo.go:51      Not able to establish connection to node with addr: ws://10.4.10.201:9001/rpc/v1, Reason: cannot dial address ws://10.4.10.201:9001/rpc/v1 for dial tcp 10.4.10.201:9001: connect: no route to host: dial tcp 10.4.10.201:9001: connect: no route to host
ERROR: Not able to establish connection to more than a single node

Then, I restarted that 10.4.10.201 Full Chain Node and restarted curio node.
Still only 10.4.10.201 showed in the Chain Connectivity.
Then I hit the little "Move Up" arrow in the base layer config to move 10.4.9.201 to Item 1.
Now it shows 2 Chain Nodes:

Interesting.
If I move 10.4.10.201 into "Item 1", then curio only shows one Chain Connectivity.
If I move 10.4.9.201 into "Item 1", then curio shows both Chain Nodes.

And even when both Chain Nodes shows in Chain connectivity, as soon as I stop the Chain node that is actively being used, Curio does not switch over to the other Chain Node. (even after 10 minutes).
If I then stop and start the curio node, it fails to start with the Chain Node that was last active:

2024-09-10T21:58:15.587Z        WARN    curio/deps      deps/apiinfo.go:51      Not able to establish connection to node with addr: ws://10.4.9.201:9001/rpc/v1, Reason: cannot dial address ws://10.4.9.201:9001/rpc/v1 for dial tcp 10.4.9.201:9001: connect: no route to host: dial tcp 10.4.9.201:9001: connect: no route to host
ERROR: Not able to establish connection to more than a single node