Wifi not recovering after changing initial WiFi SSID

Hi there,

While setting up my PiFi (kit) on a Raspberry Pi 4 I am running into an issue I cannot seem to fix.

While setting up the device for the first time using the app I run into an issue where the PiFi SSID is not broadcast after changing it from the pre-set ‘PiFi 4’ SSID.

The gist appears to be that the pyy-1-ap0 device doesn’t re-enable after resetting the SSID (using ‘pifi’ all-lowercase, no special characters or hidden space). The final few lines of terminal code:

Last section of initial boot sequence, after reboot to new SSID:

rt188x2bu 2-2:1.0 phy1-ap0: renamed from wlan4
start_addr=(0x20000), end_addr=(0x40000), buffer_size=(0x20000), smp_number_max=(16384)
br-lan: port 1(pyi1-ap0) entered blocking state
br-lan: port 1(pyi1-ap0) entered disabled state
device phy1-ap0 entered promiscuous mode
brcmfmac mmc1:---1:1 phy1-sta0: renamed from wlan0
br-lan: port 1(pyi1-ap0) entered blocking state
br-lan: port 1(pyi1-ap0) entered forwarding state

Followed, after configuring using the PiFi-app (Android), upon changing the PiFi network SSID to ‘pifi’:

device phy1-ap0 left promiscuous mode
br-lan: port 1(pyi1-ap0) entered disabled state

And now no new SSID is broadcast (deduced by no network named ‘pifi’ showing up on my phone).

The first time I experienced this I ended up reflashing the SD-card and uninstalling the app (completely, incl. cache etc). After reflash I run into the same issue.

What can I do to fix this? Any help would be greatly appreciated.

Thanks in advance.

Ok firstly sorry to see the issue you’re having with SSID change - will investigate the logs provided.

One thing re: reflashing though - that shouldn’t be necessary.

If I encountered not broadcasting, I’d firstly reboot (power cycle).

If it still doesn’t show you can actually remove the USB adapter and after 1-2 minutes it’ll revert to PiFi 4 Setup then reinsert the adapter and after 1 minute or so it will show as PiFi 4

This is the reset procedure on the device to avoid having to re-flash.

That being said, the SSID issue should not have occurred so I’ll go through the logs and see if I can recreate it at my end.