[GH-ISSUE #71] Device connection shows as successful in error #20

New issue

Closed

opened 2026-03-04 01:34:09 +03:00 by kerem · 4 comments

kerem commented

2026-03-04 01:34:09 +03:00

Owner

Originally created by @rgov on GitHub (Sep 19, 2022).
Original GitHub issue: https://github.com/spr-networks/super/issues/71

I had a device routinely trying and failing to authenticate to the network. I waited for the auth failure popup and copied the MAC address, then used the Add Device flow to add a new entry with the same MAC address and (it turned out) the wrong password.

On the QR code screen, the connection status immediately changed to "Success" even though there was no successful attempt. And when the device did attempt to connect a moment later, I got the PSK failure alert.

Originally created by @rgov on GitHub (Sep 19, 2022). Original GitHub issue: https://github.com/spr-networks/super/issues/71 I had a device routinely trying and failing to authenticate to the network. I waited for the auth failure popup and copied the MAC address, then used the Add Device flow to add a new entry with the same MAC address and (it turned out) the wrong password. On the QR code screen, the connection status immediately changed to "Success" even though there was no successful attempt. And when the device did attempt to connect a moment later, I got the PSK failure alert.

kerem closed this issue

2026-03-04 01:34:10 +03:00

kerem commented

2026-03-04 01:34:10 +03:00

Author

Owner

@lts-rad commented on GitHub (Sep 19, 2022):

Was it actually successful in the end? Hostap has to trigger a succesful association event for that popup to appear

@lts-rad commented on GitHub (Sep 19, 2022): Was it actually successful in the end? Hostap has to trigger a succesful association event for that popup to appear

kerem commented

2026-03-04 01:34:10 +03:00

Author

Owner

@rgov commented on GitHub (Sep 19, 2022):

in this case the device had the wrong psk so no it didn’t successfully auth at this moment. Later I recreated it with the correct psk and had the same immediate success message, but the device really successfully authed maybe 30 seconds later.

@rgov commented on GitHub (Sep 19, 2022): in this case the device had the wrong psk so no it didn’t successfully auth at this moment. Later I recreated it with the correct psk and had the same immediate success message, but the device really successfully authed maybe 30 seconds later.

kerem commented

2026-03-04 01:34:11 +03:00

Author

Owner

@lts-rad commented on GitHub (Sep 19, 2022):

Could be a UI state glitch in that case, can try to reproduce later.

@lts-rad commented on GitHub (Sep 19, 2022): Could be a UI state glitch in that case, can try to reproduce later.

kerem commented

2026-03-04 01:34:11 +03:00

Author

Owner

@rgov commented on GitHub (Sep 19, 2022):