OPINIONATED OMARCHY
TROUBLESHOOTING CORPUS
790
RECORDS
790
AUDITED
0
UNCHECKED
2388
SOURCES
LIVE
network medium occasional DISPUTE

Join a hidden Wi-Fi network the Omarchy panel cannot add

omarchynetworkmanagerlaptop
CORRECTED An auditor found the fix wrong or incomplete and rewrote it. · checked against Omarchy omarchy 4.0.4-1 on 2026-10-05
AUDIT NOTE

Confirmed the installed Panel.qml (4.0.4-1) and the quattro Panel.qml have no hidden-network join entry, and the installed list labels an empty SSID row "Hidden" (row.net.ssid || "Hidden"). PR #7828 "Add Join hidden network to the Wi-Fi panel" is open and unmerged against quattro, last updated 2026-09-27. The cause mislabels #8366 as an Omarchy 3 era request: it reports the missing option in the new Quickshell panel (Quattro) and was closed by its author after pointing at the open PR #7828, not because anything was fixed, and a commenter asked for it to be reopened. #3945 is the Omarchy 3.2.3 request. Cause corrected to say so. The fix holds: the Arch wiki gives nmcli device wifi connect SSID password ... hidden yes, and nmcli's devices.c scans the hidden SSID first when hidden yes is passed so it learns the AP's security before --ask prompts. The offline nmcli connection add ... 802-11-wireless.hidden yes wifi-sec.key-mgmt wpa-psk followed by nmcli --ask connection up is valid. Cross-referenced slug wpa2-enterprise-8021x-connect-from-cli exists. Not exercised: no hidden network was joined.

The cause above was rewritten on 2026-10-05 to match this note; the fix was corrected by the audit itself.

Symptom

The office or home network does not broadcast its SSID. The Omarchy 4 network panel has no "join hidden network" or "other network" entry, so there is no way to type an SSID. At best a row labelled Hidden appears, and clicking it cannot work because there is no name to connect to.

Cause

The Omarchy 4 network panel lists only networks found by scanning and has no form for entering an SSID by hand. Panel.qml on 4.0.4-1 and on quattro contains no such entry. The Omarchy 3 request (#3945) was closed, and the Quattro panel request (#8366) was closed by its author in favour of PR #7828, which adds a "Join hidden network" option and was still open and unmerged on 2026-10-05. Closing #8366 did not fix anything. NetworkManager itself supports hidden networks fine. A hidden SSID needs the client to send directed probe requests carrying the name, which nmcli does when the profile is marked hidden.

Fix

Create the connection with nmcli, which marks the profile 802-11-wireless.hidden yes:


nmcli --ask device wifi connect "<SSID>" hidden yes

--ask prompts for the password instead of putting it on the command line. Once the profile exists it autoconnects like any other and the panel shows it as connected.

To create it without being in range, for example before arriving at the office:


nmcli connection add type wifi con-name "<SSID>" ssid "<SSID>" \
  802-11-wireless.hidden yes wifi-sec.key-mgmt wpa-psk
nmcli --ask connection up "<SSID>"

Use wifi-sec.key-mgmt sae for a WPA3-only network. For an enterprise network see wpa2-enterprise-8021x-connect-from-cli, and add 802-11-wireless.hidden yes to that profile.

Verify


nmcli -g 802-11-wireless.hidden connection show "<SSID>"     # yes
nmcli -f GENERAL.STATE,GENERAL.CONNECTION device show "$(nmcli -t -f DEVICE,TYPE device | awk -F: '$2=="wifi"{print $1; exit}')"

Sources

hidden-wifi-network-no-join-option-panel