SqueezeAMP - can't change wifi network

[Grumpy Bob]

Maybe I'm missing something here, and Philippe_44 can point it out?
I've been trying out a SqueezeAMP driving a pair of tiny speakers. Everything is fine, except now I want to move the speakers to a location where I have to use a WiFi extender.
I can see the extender's SSID in the list, but after selecting that and entering the password, I get the message "You may lose wifi access while the esp32 recalibrates its radio. Please wait until your device automatically reconnects. This can take up to 30s". This message remains indefinitely, and after a while if I refresh the SqueezeAMP configuration page, it's still connected to the original SSID (and functions normally).

Robert

[slimhase]

Maybe I'm missing something here, and Philippe_44 can point it out?
I've been trying out a SqueezeAMP driving a pair of tiny speakers. Everything is fine, except now I want to move the speakers to a location where I have to use a WiFi extender.
I can see the extender's SSID in the list, but after selecting that and entering the password, I get the message "You may lose wifi access while the esp32 recalibrates its radio. Please wait until your device automatically reconnects. This can take up to 30s". This message remains indefinitely, and after a while if I refresh the SqueezeAMP configuration page, it's still connected to the original SSID (and functions normally).

Robert

If I remember correctly, you need to 1st disconnect from the current network (by clicking the current AP in the WiFi tab and then clicking disconnect button)
Then SqueezeAmp will go into AP mode and you can select the new network & enter login credentials via AP webpage.

Hope this works.

Edit:
Oh and if the Extender uses the same SSID as your main network (but runs on a different channel), you need to update this as shown:
Set WiFI scan Mode to "Comprehensive"

(Otherwise, if the channel ID of your main WiFi Net is a lower number than the extender Net, SqueezeAmp will still try to connect to that)

P.S: The edited part might even work w/o the decribed complete disconnect part stated 1st

[Grumpy Bob]

Many thanks slimhase - I was missing the disconnect stage there - it wasn't immediately apparent how to get back to AP mode...

All working well now. This change was made because I've set up my home office in a downstairs bedroom (which is a bit too far from my main wifi network), as I was fed up with working in the living roome. Looks like SE England will be in quite strict lockdown for some time to come...

Robert

[sle118]

Many thanks slimhase - I was missing the disconnect stage there - it wasn't immediately apparent how to get back to AP mode...

All working well now. This change was made because I've set up my home office in a downstairs bedroom (which is a bit too far from my main wifi network), as I was fed up with working in the living roome. Looks like SE England will be in quite strict lockdown for some time to come...

Robert

FYI,

I am rewriting the whole WiFi UI and this is one of the scenarios which I have tried addressing. Hopefully, it will work better when I get to release it. It is taking more ime than anticipated because of competing priorities, but also because I have made a significant change of development and this required a bit of adaptation. Going forward, I think the whole UI will work significantly better overall across platform; I am building the app and libraries using webpack, which is far better at optimization than working by hand. I also took the opportunity to build a better mock framework to help speed up testing changes. Flashing an ESP32 on every change takes a ton of time and eventually lead to killing the flash memory 's cells, so mocking locally is a must.

edit:

for the adventurous, you can have a peek preview at the new wifi ui by downloading the artifacts found here
https://github.com/sle118/squeezelit...runs/436264244