WifiAPMode not working since 20220616 #4118
Comments
TD-er
added
Type: Bug
|
This seems to be an esp8266 only thing... just tested it on an esp32 and there it works. |
|
What core SDK version do you use? (see sysinfo page) |
|
ESP82xx Core 2843a5ac, NONOS SDK 2.2.2-dev(38a443e), LWIP: 2.1.2 PUYA support |
|
OK, that's for sure not a "new" SDK, so it is nothing recently introduced regarding the SDK. |
|
#4186 seemed to fix it. Tank you! Here log from an old build: Thats how it looks now: Edit: i think the issue is that the AP starts with Channel:1 and in order to get reconnected in sta it needs to change the channel afterwards |
|
There is still another issue too. So I'm still looking into this. |
Yep, your log shows it is indeed now running on 2 channels, which is bad. |
|
|
|
What was the behavior in old builds? |
But then you will loose connection when initially doing the setup.
As far as I know there should not be a different behavior. At least not intended. What build do you test against where it was still working? |
|
I used the 24.12.2021 release to compare... |
If the ESP is still connected and has STA active when starting the AP. |
No, i haven’t.... And the disconnect happens after the ap mode so until then the sta channel shouldn’t have changed.. Edit: to be clear:
this is my scenario |
|
Not 100% the disconnect actually happened after starting the AP mode. I will have a look to see whether I can fetch the channel before doing anything regarding starting the AP as you have to set the IP config first and then start the AP. I think the disconnect may happen when I set the AP IP config. |
|
Can you try the last commit? |
|
Not quite... |
The timeout for disabling the AP is 5 minutes. (which may be too long?) |
|
A timeout of 1 minute is too short... 5minutes are fine... but what does it has to do whith the permanent disconnection as sta? |
Working on that right now. |
|
OK, we might be on to something really serious. I now have it working to reconnect to the AP in STA mode when AP is running on the ESP. So not sure what's happening here, but the code I have now, will not (!!) be pushed as I have no idea how seriously damaging this may be. |
|
Ohh. that doesn’t sound good... hope you’ll find a easy fix for that. |
|
OK, pushed a new commit. So please test this on a node that's well reachable as you may need to flash it via serial to get it to work again. |
|
Similar behavior than before with the extra addition of a short boot loop (6x) when i hit reboot. After that the esp boots normal again . |
|
OK, so we're hitting some 20 seconds timeout here. |
|
Is this issue still relevant? If not it should be closed. |
|
Yep, still an issue :( |
|
@chromoxdor I've found and fixed an issue that prevented AP mode from starting when no matching AP was found, you can download form this Actions run for testing. |
|
No luck for me... |
|
Do you have a credential stored with a wrong password? As it tries to match on SSID, and seems to find a match with a stored credential(SSID), but still can't connect... |
What credential do you mean? |
Just found out that calling WifiAPMode causes the Wifi do disconnect entirely and reconnect without beeing able to establish an AP.
Works in prior’s release....
The text was updated successfully, but these errors were encountered: