Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WiFI disconnects / stability problem when WPA3 is enabled (transition Mode from WPA2) within Mesh #1072

Closed
tp1de opened this issue Feb 21, 2023 · 0 comments

Comments

@tp1de
Copy link
Contributor

tp1de commented Feb 21, 2023

I am using a Mesh-Network based on AVM products. There are 3 active WiFi components:

  1. Cable-Router far way from ems-esp (-90db) - Mesh master
  2. old Router acting as Mesh access point - next room to ems-esp (-60 db)
  3. a WiFi Repeater close to ems-esp (50 cm) (- 38 db)

All WiFi attributes are set central on Mesh master are then identically set to all Mesh devices.
AVM is recommending to select a WPA2/WPA3 transition mode for WiFi security. (WPA2 and WPA3 enabled).

With this mode all my devices run stable but ems-esp does not. The ems-esp firmware is changing regularly the access points to be connected to. This is not the strongest one !
I could see that quite often the connection is made to the far away master.

Being away from home two weeks ago I could not connect anymore to the WebUI - but MQTT connection to HA was still working.
After 6 hours another access point was selected and connection to WebUI was possible again.

When using the WPA2/WPA3 transition mode the ems-esp WiFi network scan does not show the right security attributes for the mesh repeaters - only for the master. I might believe that this causes the connection problems.

Selecting fixed WPA2 for WiFi security is recognized for all access points by ems-esp and connection seems to be stable now.
(even changing the access points to be connected to a couple of times per day !)

@emsesp emsesp locked and limited conversation to collaborators Feb 21, 2023
@proddy proddy converted this issue into discussion #1073 Feb 21, 2023

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant