-
Notifications
You must be signed in to change notification settings - Fork 49
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
WiFi Connect Issue #142
Comments
@Tissy when you are connected to the WiFi AP, what does it show if you access 192.168.42.1:8181 in a browser? |
Hi @shawaj , thank you for your reply. When I connect to that IP, the screen is just blank, so nothing is displayed. |
Ah ok. Maybe it was a result of #130 🤔 Are you using a raspberry pi with onboard WiFi? |
That looks to be a different issue as all the code is deploying and the service runs, just no portal page. Yes, RaspberryPi 4 with onboard WiFi. |
What I meant was, that change moved the WiFi connect to a local implementation rather than upstream. And #114 changed it from kiosk. This is a new install? Or it's updating a previous one? For the time being, you can auto-add the WiFi credentials to the balena image using their "Deploy with Balena" dialog... If you toggle the advanced toggle... You should then be able to add pre-configured WiFi credentials. |
@Tissy did you modify the WiFi AP name? As yours seems to be AS1-L_WiFi instead of balenaWiFi? Anyway, I have managed to reproduce the same issue... No idea why it's happening but will poke around |
Think this is the issue: balena-os/wifi-connect#588 (comment) Will find a working version and hard-code something |
It seems v4.4.6 is the latest working version currently... https://github.com/balena-os/wifi-connect/releases/tag/v4.4.6 however this is quite old. So I've created a forum post here... https://forums.balena.io/t/balena-wifi-issue/371182 And I think what I'll do is copy the repo UI folder into the correct location as a temporary fix |
Ok created #143 as a temporary fix until this upstream PR gets pulled in... balena-os/wifi-connect#566 I tested locally and was able to setup wifi and captive portal showed correctly. |
Temporary fix for ketilmo#142 - pull in required changes from balena-os/wifi-connect#566 - increase timeout from 120 seconds to 180 seconds Closes: ketilmo#142
That's absolutely brilliant @shawaj , I do indeed now have the portal web page running, thank you very much! |
@Tissy you can either go into the "host OS" container and type Or you can go to the wifi-connect container and enter |
Anyone seen or aware of this issue with
wifi-connect
please?The WiFi AP is broadcast as it should, I appear to be able to connect to the WiFI, however no landing page is displayed which would enable me to select the access point.
This is what am I seeing in the logs...
Many thanks :)
The text was updated successfully, but these errors were encountered: