Closed breboulet closed 3 years ago
Yes, the initial connection attempt after reboot is (very) often failing, and the next retry is 3 minutes later. It seems that NetworkManager is just not ready for the request yet. Comitup should either wait longer on boot, or cut the timeout way down after the initial try.
The exception following a log message saying "Got an exception, returning None" is normal behavior.
I added a 5 second timeout to the start of Comitup - no effect.
Adding a second WiFi device - works flawlessly.
There is a known issue of NetworkManager being not great at identifying a list of available Access Points using a WiFi adapter which is itself an active AP. Comitup can mitigate this by using multiple WiFi adapters, if available, to compile the list.
Possible solutions:
If you are in a position to do this, could you upgrade to the latest states.py in the main branch, and see if it works better?
Fixed in 1.20
I just tried 1.20 and everything works flawlessly! I even tried to power cycle my router, I saw the hotspot coming up, then going away automatically when wifi was back up. Sir, you rock! Many thanks, Bastien
Hi Dave,
First of all, thank you so much for this project and the very nice doc, website, binaries and co you've put in place. That's really great!
I'm running into the following issue: it takes about 3min after the Pi has rebooted to hide the hotspot and connect to my (previously paired/known) wifi network. When there's no comitup and the Pi is configured with stock wpa_supplicant it only takes a few seconds to connect to wifi after reboot.
Here are the steps to reproduce:
Following is the output of
/var/log/comitup.log
with log levels set to DEBUG in comitup.pyI've noticed a bunch of exceptions, not sure if it's normal and/or related to that delay. Also notice the jump inbetween 17:46:xx and 17:49:xx, almost like it's sleeping for 3min. Is there anything I could do (configuration or otherwise) to reduce that delay?
Thanks and Regards, Bastien