I want to access point or ad-hoc to remain the main option, this is how I got the best results with OSC. I’ve briefly tried Balena WiFi connect (also using Network manager) but once it recognizes an ssid it connects to it automatically and that’s not what I want. Is there a script or install procedure that you can recommend ? I tried to set something using Network Manager and its command line tool but I failed to connect to the “hotspot” created and I don’t know yet how to store configurations and switch between two configurations with nmcli. How would you do that on a headless setup ? There would also be a possibility to switch and connect to a known network connected to internet when an update is needed (or if the user wants to permanently use the home network fo example). Ideally I would like to set the following up:īy default the RPI Zero W would advertise an “access point” or create an ad-hoc network used for OSC communication and eventually accessing a local webpage served by Node.js to adjust a few settings. If it was for me only, I would probably keep this solution even if it’s not very handy, but since I plan to share the project with other users, I would like to provide an easy way to manage WiFi, either via command line or via a webpage or a variable set in config.txt, or a wpa supplicant containing multiple configs, I don’t know. I need to revert the script each time I need to connect the RPi to internet for an update or take the Pi out of the Eurorack case and connect the pi via Ethernet.
For the project I’m working on (OSC and Ble midi to I2C ), I’m looking for a solution to provide a user-friendly WiFi configuration for an headless Raspberry Pi Zero W.Īt the moment I’m using a script that creates an ad-hoc network when the pi boots up but it’s difficult to connect the Pi back to another network (connected to Internet) once it’s installed.
0 kommentar(er)
