10-12-2023, 05:57 PM
{@avsfan19
OK, I finally got some time this morning to think about your problem.
While working with the WiFi station and AP modes should be the same irrespective of the RPi model---assuming it can access an appropriate WiFI transceiver---I ran the following exercises on an RPi2B with an outboard CanaKit USB-WiFi transceiver to try more or less to replicate your situation..
_____
First, let's see what happens with no moodecfg.ini file. Flash a fresh moOde 8.3.6 image to a uSD card using the Raspberry Pi Imager (in which settings I enabled SSH and set the default username and password).
Insert the card in the RPi2B and power up. Wait an insufferably long time (I forgot how slow the RPi2B is plus there's a timeout looking for the Ethernet connection which isn't there) and finally an AP with SSID "Moode" shows up on my laptop as an available WiFi Network.
By default, this AP requires the password "moodeaudio". This is a holdover from the good old days (sorry it isn't better documented) and basically is necessary because the Raspberry Pi Imager has no way to deal with AP-mode parameters in situ.
Connect to this network and now you can open moOde's WebUI at IP address 172.24.1.1.
Opening the Network Configuration panel, one gets the popup notice "An Access Point password needs to be set." which reinforces the new security emphasis. At this point, you can set your desired AP SSID "Speakers" and your selected AP password. Save the Access Point settings and reboot. All should be as you want it.
_____
Referring back to the Network Configuration panel, note that either before or after changing the AP SSID and AP password, the Network SSID setting is "None (Activates AP mode)". That's the same as the default setting in /boot/moodecfg.ini.default so let's try it in our second test.
As before, use Raspberry Pi Imager to flash a fresh image of moOde 8.3.6 to a uSD card. This time though---and before booting the card on the RPi2B---copy over the /boot/moodecfg.ini.default file to boot/moodecfg.ini. Leave wlanssid = "None (activates AP mode)" as is but make the desired AP settings under [Network (apd0)]. Save the file and then boot the card on the RPi2B. Shazam! After waiting interminably again, your moOde player should have come up in AP mode with the new SSID/pw.
_____
Finally, try again with a fresh image and this time with your moodecfg.ini file which contains the line wlanssid="". Again, after waiting an insufferably long time, the moOde player should come up in AP mode with SSID "Speakers". The only salient difference I notice is that in the WebUI under Network Configuration, the Network SSID setting is "Nothing selected". Easily changed to "None (Activates AP mode)" if it bothers you.
_____
Sorry for the long-winded response but I figured TMI is better than TLI (too little information).
Regards,
Kent
PS - note that Tim's response contained a trivial typo. The file is /var/log/moode_autocfg.log
OK, I finally got some time this morning to think about your problem.
While working with the WiFi station and AP modes should be the same irrespective of the RPi model---assuming it can access an appropriate WiFI transceiver---I ran the following exercises on an RPi2B with an outboard CanaKit USB-WiFi transceiver to try more or less to replicate your situation..
_____
First, let's see what happens with no moodecfg.ini file. Flash a fresh moOde 8.3.6 image to a uSD card using the Raspberry Pi Imager (in which settings I enabled SSH and set the default username and password).
Insert the card in the RPi2B and power up. Wait an insufferably long time (I forgot how slow the RPi2B is plus there's a timeout looking for the Ethernet connection which isn't there) and finally an AP with SSID "Moode" shows up on my laptop as an available WiFi Network.
By default, this AP requires the password "moodeaudio". This is a holdover from the good old days (sorry it isn't better documented) and basically is necessary because the Raspberry Pi Imager has no way to deal with AP-mode parameters in situ.
Connect to this network and now you can open moOde's WebUI at IP address 172.24.1.1.
Opening the Network Configuration panel, one gets the popup notice "An Access Point password needs to be set." which reinforces the new security emphasis. At this point, you can set your desired AP SSID "Speakers" and your selected AP password. Save the Access Point settings and reboot. All should be as you want it.
_____
Referring back to the Network Configuration panel, note that either before or after changing the AP SSID and AP password, the Network SSID setting is "None (Activates AP mode)". That's the same as the default setting in /boot/moodecfg.ini.default so let's try it in our second test.
As before, use Raspberry Pi Imager to flash a fresh image of moOde 8.3.6 to a uSD card. This time though---and before booting the card on the RPi2B---copy over the /boot/moodecfg.ini.default file to boot/moodecfg.ini. Leave wlanssid = "None (activates AP mode)" as is but make the desired AP settings under [Network (apd0)]. Save the file and then boot the card on the RPi2B. Shazam! After waiting interminably again, your moOde player should have come up in AP mode with the new SSID/pw.
_____
Finally, try again with a fresh image and this time with your moodecfg.ini file which contains the line wlanssid="". Again, after waiting an insufferably long time, the moOde player should come up in AP mode with SSID "Speakers". The only salient difference I notice is that in the WebUI under Network Configuration, the Network SSID setting is "Nothing selected". Easily changed to "None (Activates AP mode)" if it bothers you.
_____
Sorry for the long-winded response but I figured TMI is better than TLI (too little information).
Regards,
Kent
PS - note that Tim's response contained a trivial typo. The file is /var/log/moode_autocfg.log
