You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
when connection to the AP 192.168.4.1 for initial WiFi configuration it shows all networks and when I enter the SSDI and the WiFi password, it always makes the SSID field empty in about 5 seconds and even if I'm fast enough to copy the SSID and password and save it, it does never stores any WiFi settings although it says changes saved but the the SSID slot is always empty.
I have set the correct pins and via the 192.168.4.1 AP, switch on/off works and also voltage readings seems to be ok.
Steps to reproduce
power on and it always shows ESPURNA_ and let me connect and open the Web UI but never allows WiFi settings
Build tools used
I used VS Code and PIO all latest version. Build was successful and also the upload initially via soldered serial adapter
Any relevant log output (when available)
No response
Decoded stack trace (when available)
No response
The text was updated successfully, but these errors were encountered:
Device
AISIRER AWP07L
Version
1.17-dev
Bug description
when connection to the AP 192.168.4.1 for initial WiFi configuration it shows all networks and when I enter the SSDI and the WiFi password, it always makes the SSID field empty in about 5 seconds and even if I'm fast enough to copy the SSID and password and save it, it does never stores any WiFi settings although it says changes saved but the the SSID slot is always empty.
I have set the correct pins and via the 192.168.4.1 AP, switch on/off works and also voltage readings seems to be ok.
Steps to reproduce
power on and it always shows ESPURNA_ and let me connect and open the Web UI but never allows WiFi settings
Build tools used
I used VS Code and PIO all latest version. Build was successful and also the upload initially via soldered serial adapter
Any relevant log output (when available)
No response
Decoded stack trace (when available)
No response
The text was updated successfully, but these errors were encountered: