I have installed Anthias on a Pi 3 using the latest Raspberry Pi imager and the Anthias option.
A wifi ot spot was not created. So I have plugged into an ethernet network and all is working ok. But I need it to be on wifi.
ctrl+alt+f1 does nothing (esc blanks the screen then when pressed again goes to the Anthias logo).
I have tried creating an ssh and ssh.txt file on the resin-boot partition on the ssd, but get “Connection Refused”.
All help welcome.
@backfour94, let me take a look on this one. It could be that the service responsible for setting up the Wi-Fi hotspot is not starting.
Thanks, I’m also a bit confused about how to get SSL running which would help to get resolved, as would breaking out to a command prompt.
The Anthias image (from the Raspberry Pi Imager) is based off of balenaOS. Given that, SSH/CLI access is not possible. If you like to have more control over your Anthias instance, I would suggest that you install Anthias (via the installer) on top of Raspberry Pi OS Lite (Bookworm).
I only really wanted to use SSH to get the wifi working. Do you think installing by this other route could fix the wifi issue?
We’re still in the process of fixing bugs. With that route, you could set up your Wi-Fi manually by using this documentation as a guide.
OK will do. Thanks for the quick response
You’re welcome. Let me know if you still have issues.
All done. For info it didn’t ask me to reboot, it just started and worked fine. SSH is working fine. ctrl+alt+f1 does nothing.
@backfour94, thanks. It’s good that you’re now able to SSH into the device. It looks like switching to console mode (via Ctrl+Alt+F1) is disabled. Having an SSH access should be fine to enable Wi-Fi.
Hi all, a quick update for anyone landing on this thread: we’ve brought back WiFi setup via a captive portal in Anthias, in PR #3399. When a screen has no working network, it raises its own access point and shows the network name and passphrase on screen. You join it from your phone or laptop and pick the WiFi network to connect to. No SSH, keyboard, or nmcli needed.
It’s merged into master and we’re calling for testers. If no issues turn up, it’ll ship in the next release, but we’d really appreciate the community’s help putting it through its paces first. The easiest way to try it is with the installer script, choosing the latest option (installs from master). Please report how it went (Pi model, OS, wired or WiFi, anything odd) here or on the PR.
For the more technically curious: the old integration was built on balena’s wifi-connect, which had quietly stopped working for us (among other things, no ARMv6 binary since v4.4.6). So we wrote our own implementation from scratch in Rust as a replacement: Screenly-Labs/wifi-connect. It talks to NetworkManager directly, works out on its own whether a screen actually needs setup (so wired or already-connected screens are left alone), and backs off on sites where there’s nothing to join. Bug reports and PRs on that repo are very welcome too.