Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bugs and Useful Improvements #71

Open
ruky87 opened this issue Jan 27, 2019 · 0 comments
Open

Bugs and Useful Improvements #71

ruky87 opened this issue Jan 27, 2019 · 0 comments

Comments

@ruky87
Copy link

ruky87 commented Jan 27, 2019

I think that with these improvements the app will be a lot mote useful:

  • For me scan is not working (3B+), the list is empty and I need to enter wifi password manually. If the raspberry is unable to connect at boot (tried editing the SSID name of the only one network saved in wpa_supplicant), the host mode is not started and I can not connect anymore. In this case, after a ~30s timeout, an hotspot should be started! I was able to start the host mode only 1 time after the first installation.

  • First add this: Append to a base wpa_supplicant.conf instead of rewriting it from scratch #52 - It's correct to append new networks and use the original file as base. Especially to preserve the COUNTRY CODE. And if I move from a network to another (home/work) everything works as expected

  • Add in the web interface the possibility to load and directly edit/save the current wpa_supplicant file for advanced configuration. This is a must I think! Especially with networks where advanced configuration is needed.

  • Reset to host must not remove the saved networks, just load hotspot. Add in the web interface a button for "reset configuration" (blanks the wpa_supplicant) and a button to reboot in "host mode". Ask the user if reboot or not when adding a new network... Not do it automatically.
    The webserver should be loaded also in client mode, so the user can add other networks or reboot manually in host mode. When loaded in "host mode" the button should be "reboot in client mode". If the network connection fails we will return to host mode.

Others:

  • If possible, change between host and client modes without rebooting the raspberry, reset only the network and start/stop/reload the correct services

  • Add the option in config file / initial configuration to completely disable the GPIO feature, if this pin is needed for other things

  • Add in the webserver a page for changing host mode (config mode) name and password, not only password

I think that with these features the app will be complete and the first really working good on raspberry pi 3 B+. If the app is put behind an nginx proxy with auth feature, it's possible to add the wifi configuration functionality to a bigger project with different executing apps!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants