Closed jango22 closed 1 month ago
I am running headless on a zero 2 w with wifi as the primary intended connection no ethernet is connected.
I think this may be fixed by increasing the priority of the wifi connection.
nmcli connection modify SSID connection.autoconnect-priority 10
I'll need to test if auto hotspot is even enabled at the moment I might have ended up with it staying disabled. it takes some fiddling to know if its working when the ssid is available.
@jango22 I had to re-write all the auto-hotspot stuff for Raspbian 12, given the changes. The automatic fallback is now handled by NetworkManager as it has the capability.
The hotspot priority is set to 1. I think there was some logic to it being set, but I can't recall what. Either way any profiles created has to have a priority set higher than the hotspot. If I leave it at default, and new SSIDs are created without a priority, then I don't think it's predictable what profile will be applied (hotspot needs to be the lowest priority).
That's likely the issue. I'll make sure the docs/readme, and installer both spell that out clearly, I'm pretty sure I forgot to highlight that important detail after the overhaul for Raspbian 12.
Ah I gotcha. It seems to work as intended once I added the priority value so that makes sense. Thanks for the confirmation. :)
Marking this as a bug, the AutoHotspot template for NetworkManager installs should have the autoconnect-priority=-999
. NetworkManager defaults to priority 0, but allows for negative priority, using a negative number will ensure any user created connections are attempted prior to falling back to hotspot.
I have installed the script on fresh raspbian installs twice now, initially with the wireless network configured in the image creation tool and the other time with the wireless network configured using nmtui after booting and both ways the autohotspot script seems to either skip attempting to connect to the configured network manager ssid or it doesnt wait long enough. also nothing shows in the log file at /var/log/ConsolePi/Consolepi.log about the attempt to connect to the configured SSID so I can't see if its failing or connecting and getting removed after.
here is all that is present in the consolepi.log: