Skip to content

Installing SkyNode

SkyNode is a Tauri desktop app — a single binary that wraps a Python backend and a React GUI. Install it on a machine that can talk to your hardware drivers (ASCOM on Windows, vendor SDKs on whatever platform the vendor supports, plain TCP/serial for native drivers).

The install path covers four things:

  1. Provision the telescope (or observatory) record on the hub.
  2. Install the SkyNode app on the SkyNode host machine.
  3. Sign in and pair the install with the hub — this creates the SkyNode installation record that ties the install to your telescope/observatory.
  4. (Optional) Set up the local MQTT broker if you want internal observatory tools to subscribe to device telemetry directly.

The configuration values you’ll set during these steps are described in detail in Configuration. This page focuses on the order of operations.


You can’t pair SkyNode with the hub until the record it’ll bind to exists. Make sure of one of:

  • Telescope node: the telescope’s record exists in Skynet, owned by your organization. See Telescope.
  • Observatory node: the observatory’s record exists, owned by your organization. See Observatory.

For brand-new observatories, follow Onboarding through step 4 first; come back here once the records are in place.


Download the installer from your organization’s Software page in the Skynet web app: Organization → Settings → Software. The page shows the current version and a signed Windows installer, and lists the SkyNode installations paired with your organization and which telescope each one runs. See Software downloads for what else is there (SkyCanary, SkyDesk) and who can see it.

One build serves every telescope you operate — there is no per-telescope installer.

The installer links are not published anywhere else on purpose. Please don’t repost them; send colleagues to the Software page instead.

Run the installer on the SkyNode host machine. After the first install, updates are pulled from inside the app (Settings → General → About → Check for updates) and only applied after you confirm — a node that may be mid-observation never restarts on its own.

System requirements:

  • OS — Windows is the most-tested platform because ASCOM is Windows-only. macOS and Linux work for native and simulator drivers.
  • Python — managed via uv for the backend; bundled in the packaged release.
  • Network — outbound HTTPS to your hub’s API and gateway endpoints. If you’ll use the local MQTT broker, also reserve the broker’s TCP/WebSocket port.

On first run, SkyNode walks you through sign-in and node selection (see Local GUI tour). The hub it talks to is set under hub in SkyNodeConfig; an installed build defaults to the production Skynet hub:

{
"hub": {
"hub_id": "Skynet Global Telescope Network",
"api_server": "https://api.skynetgo.org/",
"gateway_api_server": "https://node.skynetgo.org/",
"auth": {
"method": "oauth",
"auth_server": "https://auth.skynetgo.org/",
"client_id": "skynode-client",
"redirect_uri": "skynode://auth/callback",
"scopes": []
}
}
}

The pairing flow:

  1. SkyNode opens the auth server in your system browser using the OAuth authorization-code flow with PKCE.
  2. You sign in as the owner: the user who personally owns the observatory, or an Owner of the organization that owns it (pairing needs the organization’s settings.manage permission, which only the Owner role has; see Roles and permissions).
  3. The auth server redirects to a one-shot listener SkyNode opens on 127.0.0.1 with a short-lived code; SkyNode exchanges the code for your user token.
  4. SkyNode then walks you through node selection: pick the observatory, pick the node type (telescope or observatory), and for a telescope node pick the telescope. Binding creates the SkyNode installation record on the hub, stores the installation’s own access and refresh tokens (your user token is then discarded), and sets node_type, observatory_id, and (for telescope nodes) telescope_id in SkyNodeConfig.
  5. SkyNode pulls the hardware graph for that telescope/observatory — observatories, telescopes, instruments, devices (IP cameras included), sites, filters, operational constraints — and caches it locally under hardware in SkyNodeConfig. This is what the settings pages later edit drivers against.

The installation record is what tells the hub “this install is alive and bound to that telescope.” Subsequent task fetches, snapshot publishes, and file uploads all carry the install’s bearer token. Pairing a new install to a telescope signs out any earlier install bound to the same telescope.


If you want to publish device, constraint, and operational snapshots to a local MQTT broker (so on-site tools — dashboard PCs, status TVs, dome-control panels — can subscribe without going through the hub), configure the local_broker section.

The broker itself isn’t shipped with SkyNode; you run your own (Mosquitto is a common choice). SkyNode connects as a client.

Minimal config:

{
"local_broker": {
"enabled": true,
"host": "127.0.0.1",
"port": 1883,
"transport": "tcp"
}
}

The defaults publish three channels:

  • device_snapshot — QoS 0, retained
  • constraint_snapshot — QoS 1, retained
  • operational_snapshot — QoS 1, retained

For TLS, auth, websocket transport, last-will configuration, and per-channel QoS overrides, see Configuration → Local broker.


5. Connect the devices and start automation

Section titled “5. Connect the devices and start automation”

No restart is needed after pairing: SkyNode connects to the hub and opens the dashboard. A freshly bound node comes up held — nothing connects on its own and automation does not run until you have proven the setup:

  • In Settings, open each device’s page, pick its driver, set the driver options (Configure driver), and click Connect. The first successful connect you make arms that device’s auto-connect, so it reconnects on its own after restarts and drops. Changing the driver or its options disarms it until you connect again.
  • In Settings → Startup & Shutdown, click Start automation. The choice persists: the node resumes automation on every boot until you stop it there or unbind the install.

Then check, in the local GUI:

  • The devices show as connected (or fail with explicit error messages per device).
  • Constraint snapshots populate.
  • The hub indicator in the status bar reports a healthy connection and a recent sync.

The website-side telescope detail page should now show the install as paired, with current snapshots flowing in.

If anything’s failing, jump to Troubleshooting.