Open kornpow opened 6 years ago
I recommend using the --activity-timeout
command line argument for cases where the network is unavailable when the application is started. WiFi Connect will exit after the specified number of seconds if no user activity is detected. This will unblock the rest of the start script - e.g. starting the main application.
The issue with the visible single wifi network is a known one that I plan to address very soon.
The refresh button is a very nice idea though. I think we should add this anyway. Thanks for the feedback!
Thanks. I'm already using the activity-timeout, but not having network available isn't my real problem it just comes up in my testing a lot. Great to hear on the other fronts however, I'll keep checking back!
@majorz Will wifi-connect
ever attempt to rescan if there are no networks available?
@majorz Any idea of when we will have the refresh button?
@majorz Adding a button to refresh WiFi networks would be amazing!
Thanks for the bump y’all. This software is really great but maybe I’m being dramatic by saying it’s non-functional without this button. I’m dreading explaining in a manual (or to my boss) how if the network isn’t seen on first go the only solution is “try turning it off and back on again”. Especially with Linux we are taking about a minute or two.
@majorz Any updates to this issue?
This would be useful for debugging or "fixing" #327 as well.
Yes, will do.
[anujdeshpande] This issue has attached support thread https://jel.ly.fish/b2d505ca-7d2a-470e-a6e1-ef48c7ea9257
@majorz Does the newly updated react-based ui offer additional approaches for building something like this in?
@majorz @sradevski friendly nudge for this issue!
Hey everyone, I'll try to look into adding a refresh button soon (hopefully, if time permits).
[gelbal] This issue has attached support thread https://jel.ly.fish/fe776c67-e05f-405d-bcab-0dea56552275
For whatever reason the user's WiFi network might not be up when wifi-connect is initially run. In addition there are situations where wifi-connect only see's a single wifi network when scanning. To assist with my own debugging, and for user experience, I feel this button should be something available on the captive portal. It would be nice to easily determine if it was just did a bad scan, which happens often, even to my own PC vs the WiFi network actually not being there. Would prevent a lot of debugging tips like "reboot and see if it works this time"