Lost WiFi connection on a raspberry and lo and behold my router was not listed
Reset to factory and my router is listed…
Think this behaviour has to do with the amount of files I’m asking it to see and it saw it fine when and hadn’t directed it to look at any files yet…
on which channel is your wifi router (12 or 13 for instance)?
You may have a REGDOMAIN / CRDA issue: maybe you can set it to your region under SSH as Volumio has no UI yet for that (activate SSH before…see doc link in signature).
It’s on Channel 11 as 1-10 are full of others people’s routers
Can’t understand how to get to ssh as per your link… nevermind, i’ll just limit the files the wireless raspberry can see as that one is not my main listening system.
I had the same problem like dangermouse. My Volumio (on RPi3 with in-built WiFi, fresh SD image, Volumio v2.296, No DAC attached) always showed a lot of available WiFi networks around me but never my own one and also manual WiFi configuration was ignored. LAN was always working. I tried a lot of things but finally I obviously found the root cause (at least for my setup)
My router is an AVM Fritz!Box with WiFi currently running on standard 2.4 GHz, 802.11n+g+b, WPA2 encryption and using automatic channel selection incl. channels 12/13 (to minimize interference with neighbour networks). The typically selected and active main channel was 13 (2,472 GHz) so far. In this setup the Pi with Volumio was never able to see my WiFi.
Then I deactivated the automatic channel selection and selected channel 1 or 6 as a fixed setting. In this setup suddenly my home WiFi became visible and I was able to select and succesfully attach to it. In a next step I activated again the automatic channel selection (without the channel 12/13 option) and this was still working! (active main channel was also in this mode either 1 or 6).
When I then activated again the channel 12/13 option and triggered a new channel selection that led to a setting of channel 13 as main active, then Volumio lost the connection and enabled the internal hotspot instead (without further recovery).
=> My conclusion: Either Volumio or the Pi3 in general (I haven’t tried another distro on it yet) does have a problem with this high WiFi channel 13! So try to avoid them and you may have better success
And keep in mind if you play around with your WiFi router settings to test this behaviour: After applying a change you may need to restart the Volumio WiFi network as well (either via the network menu while connected to the internal hotspot or by a full reboot).
I hope this helps some of you who have similar problems.
@RD07a: if you just read carefully few posts before yours, you have the solution so that higher channel # can be used.
…and also read the manual to enable SSH so that you can make required changes.
Thanks for the hint macmpi. In fact I have read the earlier posts but as the other users in the related posts didn’t see any change to their problem I haven’t tried it out for myself. But I will do it now and will report if it helps for my situation
Thanks again @macmpi Obviously for my problem the “correct” solution is indeed the adaption of the regional WiFi settings (using DE for German frequencies). With that now also channel 13 is properly scanned and used and my private network appears as expected in the network search of the Volumio UI
Great to have such supporting experts in this forum
Just had the same problem and after a few hours I worked out that the standard setup does not include any optional wi-fi channels that are country dependent. The standard base band channels are scanned by default so that is why some networks are listed.
For me, here in Australia, I needed to manually set the country code appropriately to scan all available channels.
Edit the wpasupplicant.config file and add/change the country code as appropriate
sudo nano /etc/wpa_supplicant/wpa_supplicant.conf
country=AU
(ISO for Australia, edit/change as appropriate)
I just installed the latest version of Volumio on a RPi 3B+ and I can’t get the WiFi to work either.
It sees my router and it works fine hard wired but the WiFi will not connect.
I have reviewed this thread but a lot of them are pretty old and may not apply any longer. Also I don’t know how to access the config files to check the settings? How do I bring up a terminal so I can check the config files?
@jackcf you need to learn how to ssh into your device to edit config files … straightforward from Linux or Mac, with Windows you will have to use something like Putty. Also, you need to set up your device to allow ssh access