Esp-homekit-devices: Setup mode: Force WiFi BSSID

[i3laze]

Roaming decisions in WiFi stack are made solely by clients. Network can only assist by using technologies like 802.11k,r,v or just kick a client from an AP.

Any support of these standards in current ESP implementation?
Is there generic polling and roaming currently happening based on a signal strength?

What will happen if a nearest AP goes down when Force BSSID is enabled?
Without waiting an answer, I suggest adding a third mode:

• Force BSSID, while AP is online.
• When AP goes offline, connect to nearest AP with same SSID and try reconnecting to main AP every 5/10 min.

[yusufd1]

In the latest 6.1.4 now device searches for best wifi signal (not necessarily only based on rssi) and connects to that signal so no real use case for force bssid anymore unless user wants his device to connect to a specific AP.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[i3laze]

Right now I'm troubleshooting WiFi with Sonoff Basic and latest HAA 2.3.1..

Force BSSID mode Enabled but AP isn't reachable (I've put a fake BSSID):
no WiFi found, reconnect after 1s reconnect scandone no WiFi found, reconnect after 1s reconnect scandone
How long it takes the device start broadcasting HAA-SSID?

UPD: Seems, a power reset is required to enter Emergency Setup Mode, for HAA SSID to be displayed.