Open artgodwin opened 3 months ago
Thanks, can you make a PR?
It's the Spark Analyzer Datasheet.pdf that needs to change, I think, unless there is an option in the Wifi Management library. Does that need to be edited directly or are there sources in for it ? I wasn't able to find any in a brief look.
Also, I've wrongly titled this issue SPA access point when I should have written WPA access point.
Ok, I'll check it out.
On Sun, 4 Aug 2024 at 23:30, artgodwin @.***> wrote:
It's the Spark Analyzer Datasheet.pdf that needs to change, I think, unless there is an option in the Wifi Management library. Does that need to be edited directly or are there sources in for it ? I wasn't able to find any in a brief look.
— Reply to this email directly, view it on GitHub https://github.com/tooyipjee/Spark-Analyzer/issues/8#issuecomment-2267811405, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADKZGTCS3QQDGBXDLTSYTELZP2TRJAVCNFSM6AAAAABL55P7DOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRXHAYTCNBQGU . You are receiving this because you commented.Message ID: @.***>
-- Sincerely,
Jason Too
@artgodwin , I guess SPA is a typo, no? Should be WPA!?
Yes, it is!
On Mon, 5 Aug 2024, 22:43 doniks, @.***> wrote:
@artgodwin https://github.com/artgodwin , I guess SPA is a typo, no? Should be WPA!?
— Reply to this email directly, view it on GitHub https://github.com/tooyipjee/Spark-Analyzer/issues/8#issuecomment-2269971458, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADKZGTEEZUMTTMDYJSMFFATZP7WZTAVCNFSM6AAAAABL55P7DOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRZHE3TCNBVHA . You are receiving this because you commented.Message ID: @.***>
My access point was configured for WPA security only. This is probably not the default on most routers nowadays but was used here at some point (possibly for an earlier ESP32!). I could connect OK to the Spark Analyzer AP from a phone and my AP was visible, but would not connect with the error 'No AP found''. After enabling WPA/WPA2 on the AP, connection worked OK.
This possibly doesn't need fixing (or might be too deeply buried in the WiFi Management library) but should be documented.