I originally wrote a guide on how I setup a Pi Zero W to run headless back in July 2019 but never got round to polishing and publishing it. This guide should work with most Raspberry Pis. Running a Raspberry Pi in headless mode means you set it up so that it can boot and run without needing a display, keyboard and mouse. I was thinking I could achieve this with a seperate script watching the same GPIO pin on its own but realized timing between the script executions with nymea could be an issue.Not quite what you think. Definitely seems to need the hotspot to stop before restarting nymea-networkmanager. (It only lists the name of the currently configured AP). Restarting the service with the button after the pi has rebooted into AP mode prevents BerryLan from being able search for wifi. In this testing I additionally confirmed the second part of my original post. Removing all other connections from the folder, leaving only the AP with autoconnect set to TRUE, the pi does indeed autostart the hotspot.Īs BerryLan is typically for a headless setup, is there a need to store previous Wifi and AP connections? Would it make sense for this folder to be cleared when a new connection is made (or when the button is pressed)? If multiple connections are set in /etc/NetworkManager/system-connections/, any wifi network that it has stored and is available it always seems to pick first regardless of if autoconnect is set to TRUE on any AP setup.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |