How to configure WIFI manually?
Because it doesn’t work with the assistant for me. I tried following the nmcli way - but this won’t work, too (It does not scan for WIFI when integrated AP is active and you are connected with SSH over WIFI). So I’m looking for some way to configure the credentials using a simple configuration file - that’s at least something I can do mounting the SD card on my linux notebook.
Thank you and
regards,
Andreas Weller
Did you install Network Manager?
Did you try:
sudo raspi-config
and then configure network settings? it is very easy that way, it creates the wpa_supplicant.conf file for you…
the other way is the network interfaces file and manually creating wpa_supplicant config but I see no reason for this if you use the raspi-config menu…
Hi.
Unfortunately im still stuck on this issue. Yes I created the config with raspi-config.
But it still boots into AP Mode, creating a random hotspot on the internal WIFI device.
Is there any way to stop the automatic AP creation?
Kind regards,
Andreas
Wait, do you mean the screenly screen that shows up when your device is not configured for wifi? this doesnt work for you? how so?
Unless you connect to that wifi, and then type in your URL browser http://screenly.io/wifi , and configure the SSID of your wifi there, this will always come up as the AP mode, unless you connect an ethernet cable which will then prevent this from coming up since the ethernet connection (if properly working) will establish the connection thus the RPi no longer needs you to give it wifi.
if you want to manually configure the wpa_supplicant.conf then you need to edit this file:
/etc/wpa_supplicant/wpa_supplicant.conf
https://wiki.archlinux.org/index.php/wpa_supplicant
example below is what you keep seeing?
Hi,
is there any way to avoid the WIFI AP mode whenever network connection failed?
Our screen will be visible from the street (like many I think) and I don’t feel good if the AP mode starts only because local WIFI network had a temporal failure.
Otherwise anybody on the street may try to connect to this device…
Thomas
Yes, you would need to SSH into the Pi or with physical keyboard connection get to the console (ctl+alt+f1), and disable the wifi-connect.service with command:
sudo systemctl disable wifi-connect.service
If you are using the new experimental version then this has been temporarily disabled so nothing to do on that branch.
Hello everybody.
Thanks to ealmonte for his insights, really interesting as always.
I would be very interested in having the possibility to disable the AP. I would like it to be bypassed at launch (maybe getting a 169.254.x.y self-attributed IP address instead of what it would have got from an AP or a router) and going to the assets but when I try
sudo systemctl disable wifi-connect.service
then at next launch it is replaced by a “404 not found” nginx error page.
Is there a way to bypass this please ?
Hi, I am trying to understand the request a bit, but not fully getting it.
When you say “Disable the AP”, you dont want the wifi-connect to automatically start up in an Ad-Hoc mode network and let you connect to it in order to configure it? Can you explain why?
If you dont have a valid internal IP then you cannot access it.
I haven’t refreshed my memory on wifi-connect service in a while but from what I remember since everything is connected and conditional, if one service is not running, some other services dont properly run, therefore if you manually disable the wifi service then nginx might not properly run…
Again, we have to go back to the root reasoning of why you need the wifi-connect service to be disabled?
Hi, and thanks for caring !
When you say “Disable the AP”, you dont want the wifi-connect to automatically start up in an Ad-Hoc mode network and let you connect to it in order to configure it?
Exactly. Here is my use case : when my digital sign is being prepared, it is connected to a router and prepared (assets uploading) from a computer connected to same router.
Then, it’s being used in a room where there is no network available (be it wire or wireless). So to start the visual show I have either :
So, in my perspective, the internal AP, coming with good intentions, prevent starting in those conditions.
If there was a way, once the assets uploaded, to tell to my sign either :
That’s what I am also interested by an undisclosed method for this another user found and mentioned here :
https://forums.screenly.io/t/bypass-hotspot-connection/
Any thoughts are welcome !
Is the AP connection working with the latest Anthias build? I imaged an SD card for a Raspberry Pi2 with wifi dongle. I saw the Anthias logo appear, but no AP info.
Our digital signage isn’t located near an Ethernet connection or easy to connect to a keyboard, so I’d like to be able to set it up headless via WiFi if possible.
I tried manually adding wpa_supplicant.conf to the root directory of the SD card before booting, but that didn’t see to work either.
Ah, you want to use it offline, now I understand.
Ok, so you want an easy way to tell the wifi-connect service to go away before deploying it somewhere without connection and then turning it back on whenever you need it.
Before I look into an easy way for you to do this out of scope bypass modification, what happens when you tell Anthias during install that you don’t want it to manage your network by saying No to that line?
Your wpa_supplicant.conf is not working? Are you properly configuring this file?
Try to follow my instructions here and test again: Wifi not working - Anthias - Anthias Forum (screenly.io)
Ah, you want to use it offline, now I understand.
Ok, so you want an easy way to tell the wifi-connect service to go away before deploying it somewhere without connection and then turning it back on whenever you need it.
Yes, that feels good to be understood !
Before I look into an easy way for you to do this out of scope bypass modification, what happens when you tell Anthias during install that you don’t want it to manage your network by saying No to that line?
Well, I am still using Screenly OSE with a purple splash screen and I love it !
Is it possible to tell to an existing installation “I changed my mind since first installation, don’t manage my network” ? Or does this imply I make another, separate installation of the newest version ?
Thinking about it again, I would like it to Manage my Network, but only when I’m OK with that. Or to give up such management when a certain time elapses and no network is to be seen …
you won’t be able to “reinstall” an older version via the bash script that easily since it goes to github and uses the master branch by default, you can get the old releases though manually and use those images to install the old version…
regarding the file that starts the wifi-connect, as far as i know it would be this one:
https://raw.githubusercontent.com/Screenly/Anthias/master/bin/start_wifi_connect.sh
it is in your ./screenly/bin/ folder, if you want to disable it from checking for wifi connectivity, just edit that file and where it says IS_CONNECTED='' you can override it and say ='true' so that it never gets to the part that checks the cloudflare 1.1.1.1 connectivity line… does it make sense?
Has anyone gotten this to work? On my end it simply boots to the Anthias logo, then I get the Internal Sever error and then a Screenly logo.
ctl+alt+f1 won’t work, so I cannot control the Raspberry Pi 3 in any capacity.
I too have the same issue - installed from Rpi imager.
I can install Anthias via installing raspbian OS lite and running the bash script perfectly fine, so I will assume these issues you guys are having are with the balenaOS version?
it’s the image from Rpi Imager. the anthias rpi4 image
As I keep telling other users, there are 3 methods for installing Anthias, if one doesnt work, you can simply try a different one…
Like I explained to this user here just now: I simply can’t get Anthias to work! - Anthias / Balena - Anthias Forum (screenly.io)
And I’ve tried variations of all of them… 