Even if you set priority in wpa_supplicant.conf, it will connect to the
highest priority that it finds first. Once connected if a higher
priority SSID becomes available, it will not automatically switch. I
don't believe pi based hardware has the capability of defining minimum
connection rates
I resolved my SSID issue with a mesh Wifi network using Ubiquiti Unifi
AP's. No more SSID switching.
Current:
Windows 10 - LMS Server 7.9.3 8TB RAID 10 Media Drive
Office - Windows 10 - Squeezelite-X
Living Room - 2x RPiZeroW w/ Allo MiniBoss each running a Logitech Z623
System
Family Room -
jemhayward wrote:
> Wow, that is several nights bedtime reading...
I should perhaps add that in my experience Pi based players dont roam
very well. If you use the same SSID on all APs and point a Pi at that
what happens when you reboot APs is that the Pi connects to the first
one it sees which
paul- wrote:
> Of course. You just need to specify the priority.
> https://w1.fi/cgit/hostap/plain/wpa_supplicant/wpa_supplicant.conf
Wow, that is several nights bedtime reading...
jemhayward's Profile:
d6jg wrote:
> Another way to approach this is to have multiple SSIDs on your APs.
>
>
That is sort of what we have now... we have to APs with the same SSID -
I'm not sure if the two others support multiple SSID, but that may be a
way to go...
paul- wrote:
> Of course. You just need to specify the priority.
> https://w1.fi/cgit/hostap/plain/wpa_supplicant/wpa_supplicant.conf
Another way to approach this is to have multiple SSIDs on your APs.
For example I have 2 APs one in my house and one in my office.
On the office one I
jemhayward wrote:
> I tried that on a different PiZero used for a completely different
> purpose, but it didn't work. It only would connect to the first SSID in
> the file. That was a couple of years ago, and a different core linux.
> Has anyone actually got this working via a manually
Greg Erskine wrote:
> For multiple networks you need to edit wpa_supplicant.conf manually.
>
> Change # Maintained by piCorePlayer to # Maintained by user otherwise
> pCP will change wpa_supplicant.conf
I tried that on a different PiZero used for a completely different
purpose, but it didn't
For multiple networks you need to edit wpa_supplicant.conf manually.
Change # Maintained by piCorePlayer to # Maintained by user otherwise
pCP will change wpa_supplicant.conf
Greg Erskine's Profile:
I have PiCorePlayer running on a PiZero and set up the WiFi, via
wpa_supplicant.conf with manual config. It works fine, but I have three
different WiFi networks at home, and this is a portable device, so it
would be nice if it would just connect to whichever SSID it found,
rather then struggle
10 matches
Mail list logo
