What happened?

Hi. I've been hunting weird data delivery dropouts with my onBattery setup and I finally found out why:

In a setup where a wifi spans a large area and multiple access points are avilable, the DTU sometimes decides to connect to the Fritzbox main router, which is by far the furthest away from it (frankly it's impressive that it can connect at all to be honest). In the pictures you see the layout of the network. the one it should (and normally will) connect to is the AX repeater. It's the closest aand with that one everything is rock stable. alternatively the other 2 would still work, they are also much closer than the main router.

I assume this happens when one of the repeaters restarts, there as a short power cut or the Fritzbox runs an update and the Mesh is down briefly. Maaybe the DTU also sometimes just decides to switch into this horribly bad connection.
The only way to fix this then is to manually reboot the DTU via the web interface - if I can still reach it. (which is annoying because this setup is like 300km away from me) Otherwise I have to call and tell somebody to power cycle it.

So I believe we'd need some logic to make sure the DTU switches to a better wifi connection once available and does not get stuck with a much more horrible connection to a wwrong endpoint.

Bad case, stuck with a 10 Mbit connection to a far away endpoint:

Good case after manual reboot - faast endpoint is selected and used:

To Reproduce Bug

mmh. difficult without a similar setup. but not really needed aalso.

Expected Behavior

once a better wifi endpoint is avaailable - use it - do not get stuck with a horrible connection

Install Method

Pre-Compiled binary from GitHub releases

What git-hash/version of OpenDTU-OnBattery?

pretty much latest - but this exists since basically forever, been having this issue for a year noww

What firmware variant (PIO Environment)?

generic_esp32s3_usb

Relevant log/trace output

Anything else?

No response

Please confirm the following

• I believe this issue is a bug that affects all users of OpenDTU-OnBattery, not something specific to my installation.
• I have already searched for relevant existing issues and discussions before opening this report.
• I have updated the title field above with a concise description.
• I have double checked that my inverter does not contain a W in the model name (like HMS-xxxW) as they are not supported.