Skip to content
NeuralConfig docs
ARRF
▦ All products
StrandCalls R1-MCP ARRF CP-MCP CP Word List ICX Setup Docs coming soon Probe MCP Docs coming soon SZ-MCP Docs coming soon Tangent MCP Docs coming soon NeuralRepo docs.neuralrepo.com
Get Support

Setting up a RUCKUS One account

Connecting a RUCKUS One account lets you survey by venue: ARRF pulls the venue’s access points and fetches each AP’s password automatically, so you never type or maintain per-AP passwords. It’s optional — manual surveying needs none of this.

What you enter

Section titled “What you enter”

Open Settings → RUCKUS One account and fill in:

FieldNotes
RegionNorth America, Europe, or Asia — the RUCKUS One API region for your tenant. Defaults to North America.
Tenant IDYour RUCKUS One tenant identifier.
Client IDThe API client’s ID.
Client secretThe API client’s secret. Stored only in this device’s Keychain; once saved the field shows •••••••• saved in Keychain and the secret is never displayed again.

Get these from RUCKUS One → Administration → Account Management (API credentials). ARRF uses them to mint a short-lived token via the OAuth2 client_credentials grant; the token is cached and refreshed automatically.

Test the connection

Section titled “Test the connection”

Tap Test connection. On success ARRF reports how many venues it found, for example “Connected — 3 venues”. If it fails, ARRF shows a specific reason — see Troubleshooting.

What it enables

Section titled “What it enables”
  • Venue import — the Survey lobby’s Where picker lists your venues; choose one and ARRF surveys its access points.
  • Automatic AP passwords — ARRF fetches each AP’s rkscli password just-in-time by serial, so you never enter one. Fetched passwords are cached in the Keychain until they expire, and a login failure triggers one automatic refetch.
  • Offline-on-LAN — after one fetch, the venue’s AP inventory is cached, so you can survey on the LAN without re-querying RUCKUS One.

Disconnect

Section titled “Disconnect”

Settings → RUCKUS One account → Disconnect RUCKUS One removes the tenant ID, client ID, and secret, forgets the selected venue and its cached AP inventory, and restores the Toolbox sample gallery. Manual AP IPs you added under Connection → APs are kept.

How your credentials are handled

Section titled “How your credentials are handled”

There is no ARRF backend. The OAuth client secret and any fetched AP passwords live only in this device’s Keychain (device-only, not synced to other devices via backup). Region, tenant ID, and client ID are not secrets and are stored in local app settings. Nothing is sent anywhere except your RUCKUS One tenant and your own APs.

Section titled “Related”