Thank you for your donation!


Problem: wpa_suplicant not started automatically
#1
Hi all,
I have been struggling setting up Moode 6.4 on my Raspberry Zero W
The problem is that WiFi is not connected and I have tried creating a wpa_supplicant.conf but it does not fix it.
I tried to configure with

Code:
$ sudo raspi-config
But when trying to access the wireless configuration it throws an error message "Could not communicate with wpa_supplicant"
Then I tried

Code:
$ wpa_supplicant -c/etc/wpa_supplicant/wpa_supplicant.conf -iwlan0
And then it connects to wireless!
There is something avoiding wpa_supplicant to start on boot but it does work when manually launching it.
Any help?
Thanks
Luis
Reply
#2
@luisrosety

You need to read and follow the Setup Guide. Here's the link, which is prominently displayed on the moodeaudio.org homepage: https://github.com/moode-player/moode/bl.../setup.txt

In a nutshell:

Start with a clean copy of moOde on a uSD card and boot your RPi0W. It will come up in AP mode. 

If you prefer to have it come up in WiFi client mode, you'll have to create a moodecfg.txt file in the /root directory of the uSD card with appropriate info in it. Again, read and follow the Setup Guide.

Regards,
Kent
Reply
#3
(12-26-2019, 11:27 PM)TheOldPresbyope Wrote: @luisrosety

You need to read and follow the Setup Guide. Here's the link, which is prominently displayed on the moodeaudio.org homepage: https://github.com/moode-player/moode/bl.../setup.txt

In a nutshell:

Start with a clean copy of moOde on a uSD card and boot your RPi0W. It will come up in AP mode. 

If you prefer to have it come up in WiFi client mode, you'll have to create a moodecfg.txt file in the /root directory of the uSD card with appropriate info in it. Again, read and follow the Setup Guide.

Regards,
Kent

I have followed the instructions but no results.
I find this configuration procedure non easily customizable when some changes need starting from a clean non used SD card.
In any case, my WiFi settings on http://moode configuration menu, show correct values so I find it strange it is not working.
Finally, I really can't understand the added value of configuring the Raspberry Pi as Access Point since for using it one must turn on WiFi on the mobile phone or computer but once you are connected to your home WiFi you have direct access to http://moode server. So, why is that AP for?
In any case, thanks for your explanation.
Reply
#4
AP mode is primarily used to configure a Home network SSID and password. It eliminates the need for users to have to hack in via SSH (most users don't know SSH). AP mode takes a couple of minutes to start on the slower single core ZeroW. If it's not working in your case on a stock image then the issue is external to moOde software.

Also, hacking the wpa_supplicant.conf file will not work because moOde manages it via the Network Config screen which writes out the file and updates a SQL table with the settings. If you want to manually set Home network SSID and password the moodecfg.txt file method must be used.
Reply
#5
I am facing the same issue on 6.4.2 2020-02-12
I am using a raspberry pi 2 and an WIFI USB Dongle which is working fine on every other Rasbian-based system on the very same pi so far.

I followed (https://github.com/moode-player/moode/bl.../setup.txt)
Code:
1. CONFIGURE FOR WIFI CONNECTION   
  - Ethernet mode
   a) Leave eth cable connected
   b) Insert wifi adapter (while Pi running)
   c) http://moode
   d) Menu, Configure, Network
   e) Configure a wifi connection
   f) Menu, Restart, Shutdown
   g) Unplug eth cable
   h) Power on



Without success. 
I am able to find my own wifi (step d) and was entering the correct key.
Restarting the Pi will not automatically connect to my wifi, most likely due the issue with wpa_supplicant.
Reply
#6
There is not generally an issue with wpa_supplicant. A more appropriate title for this thread would have been "I can't get moOde to come up in WiFi client mode". In any case, you really should have started a new thread of your own.

I expect you aren't entering a key but a passphrase (aka password) which is converted into a pre-shared key (PSK) after it is entered. Once you've entered the passphrase, and saved the settings, the computed PSK will be revealed when you click on the eye icon.

moOde's WiFi configuration panel has worked fine for me in all my test cases. Tim did recently fix a bug which bit when MS/Windows line-ends occur in the moodecfg.txt, but that was unrelated to the configuration panel.

Caveat: I live in the USA and use only ASCII characters in my passphrase.

The IEEE spec for WPA2 says

Quote:Each character in the passphrase must have an encoding in the range of 32 to 126 (decimal), inclusive. (IEEE Std. 802.11i-2004, Annex H.4.1)

Does your passphrase by any chance contain non-ASCII characters, perhaps with diacritics such as umlaut, acute, grave, circumflex, diaresis, tilde, cedilla? I ask because some routers ignore the IEEE requirement but some software does not, and diacritics occur frequently in a number of Latin-script alphabets. I have no way of testing this since my AP strictly conforms to the spec.

If your passphrase is strictly ASCII and between 8 and 63 characters long then we have more digging to do to figure out why you player isn't associating with your AP.

Regards,
Kent
Reply


Forum Jump: