Skip to content

Configuration model

AryaOS has a simple, layered configuration model. A single site file sets defaults for the whole device. Each sensor service can override those defaults locally. Understanding this one rule tells you where every setting lives and which surface to edit.

The inheritance model

flowchart TD
  site["/etc/aryaos/aryaos-config.txt<br/>(site config)"]
  svc1["/etc/default/adsbcot"]
  svc2["/etc/default/aiscot"]
  svc3["/etc/default/..."]
  ct["/etc/cotbridge.ini<br/>(lanes)"]
  site -->|EnvironmentFile, read first| svc1
  site -->|EnvironmentFile, read first| svc2
  site -->|EnvironmentFile, read first| svc3
  svc1 -->|overrides site| gw1[adsbcot service]
  svc2 -->|overrides site| gw2[aiscot service]
  ct --> cotbridge[cotbridge service]

Each gateway's systemd unit loads the site config first, then its own /etc/default/<svc> file. Because the per-service file is read second, a value set per-service wins. Anything left unset falls through to the site default.

One place sets the CoT hub for everyone

The site config sets COT_URL=udp+wo://127.0.0.1:28087. Every feeder inherits it and sends Cursor on Target (CoT) to the COTBridge hub without per-service configuration. This is the AryaOS routing invariant: feeders > cotbridge > Mesh SA / TAK Server.

Where each thing lives

What File Edit in
Site-wide TAK destination, decoder, roles, identity, Bluetooth PAN /etc/aryaos/aryaos-config.txt AryaOS Site page
Site-wide TLS client certs /etc/aryaos/tls/ AryaOS Site page
Upstream CoT lanes (Mesh SA, TAK Server, tools) /etc/cotbridge.ini COTBridge lane editor
Per-gateway tuning /etc/default/<svc> Gateway pages
Onboarding hotspot /etc/comitup.conf AryaOS Site page

Edit in the UI, not the files

You can edit all these values in the web console. You do not need SSH or a text editor for normal configuration.

Each editor writes the file and preserves comments and unmanaged keys. If you edit a file directly, restart the affected units. For example, run sudo systemctl restart cotbridge adsbcot aiscot lincot.

The three configuration references

  • Site configuration - Every key in /etc/aryaos/aryaos-config.txt: the TAK/CoT destination, ADS-B decoder, network binding, Bluetooth PAN, role, and device identity. Reference

  • Device roles - The five roles, exactly which sensor units each enables, and how the CoT core always stays up. Roles

  • Radios & SDRs - The stx:1090:0 / stx:978:0 serial convention, re-serializing dongles, decoder selection, and multi-SDR setups. Radios