SkyNode
SkyNode is the agent that runs at your observatory and bridges your local hardware to the Skynet hub. One SkyNode install corresponds to one SkyNode installation record on the hub, which in turn binds to either a single telescope or a whole observatory.
SkyNode handles four things on your behalf:
- Local hardware — connects to your mount, cameras, filter wheels, focuser, enclosure, weather sensors, OTA mirror covers, IP cameras, and so on through pluggable drivers (ASCOM, MaxIm DL, vendor-native, simulator).
- Task execution — pulls observation tasks from the hub when the operator has started automation, the node’s control authority is
remote, and no manual control lease is held; runs them through a per-observation-type executor (optical imaging, optical imaging calibration, radio mapping, radio tracking), and reports results back. - Telemetry — publishes device snapshots, constraint snapshots, manual-control-lease changes, telescope logs, and instrument state to the hub continuously, and (optionally) re-publishes them to a local MQTT broker for in-house monitoring tools.
- Manual operation — exposes a local GUI where the operator at the telescope switches to MANUAL control and drives the devices directly.
Telescope node vs. observatory node
Section titled “Telescope node vs. observatory node”A SkyNode install is configured as one or the other through its node_type field in SkyNodeConfig:
- Telescope node (
node_type: telescope) — bound to a specific telescope, withtelescope_idandobservatory_idboth set. Monitors and controls everything attached to that telescope: mount, cameras, OTAs, filter wheels, focusers, instrument rotators, receivers, radio backends, and (optionally) the enclosure and weather sensors. - Observatory node (
node_type: observatory) — bound to an observatory only, with notelescope_id. Focuses on observatory-level devices: weather sensors, the enclosure (when the enclosure serves multiple telescopes), and site IP cameras.
The split exists because not all observatory devices belong to a single telescope. A dome that protects two telescopes, or a weather sensor that gates the whole site, should be owned by an observatory node — otherwise both telescope nodes would race to control it.
If your observatory has only one telescope under its own enclosure, running a single telescope node with the enclosure attached is fine.
Control authority and manual control leases
Section titled “Control authority and manual control leases”Two controls decide whether SkyNode is taking tasks from the hub or yielding to an operator:
- Control authority is set on the node itself, in the SkyNode local GUI, and reported to the hub in the telescope snapshot. It’s either
remote(the default — SkyNode runs scheduled tasks) ormanual(automation is paused, remote commands are refused, and the operator at the telescope is in charge). - A manual control lease is taken through the hub (the website’s Control tab or the API) by a user with update rights on the telescope: even when control authority is
remote, an active lease pauses automated task execution. When the lease expires or is released, automated execution resumes.
The two are intentionally different tools:
- Use MANUAL control when someone at the telescope needs it for a longer period — engineering, maintenance, manual observing nights, prolonged weather closures.
- Use a manual control lease for short, remote takeovers — a few minutes to slew somewhere by hand, a brief manual focus tweak, a reset of a stuck device. The website takes a three-minute lease and renews it while the page is open, so closing the page doesn’t strand the telescope.
MANUAL control is switched in the SkyNode local GUI. SkyNode shows the lease holder and can revoke a lease at any time. The Operations page has the detail.
How SkyNode talks to the hub and your network
Section titled “How SkyNode talks to the hub and your network”SkyNode connects to two hub endpoints:
- Public API (
api_serverinHubConfig, defaulthttps://api.skynetgo.org/in installed builds) — REST endpoints for task fetch, snapshot publish, file upload, etc. - Gateway API (
gateway_api_server, defaulthttps://node.skynetgo.org/in installed builds) — the sky-node-gateway service, used for the bidirectional command/stream surface.
Authentication is OAuth — see Installation for the pairing flow.
Optionally, SkyNode runs its own MQTT publisher that mirrors device and constraint snapshots to a local broker. Enable it via local_broker.enabled = true in SkyNodeConfig when you want internal observatory tools (status displays, monitoring dashboards) to subscribe directly without going through the hub. Nodes at the same site that share a broker also read each other’s enclosure and weather-sensor snapshots from it first, falling back to the hub.
Where to go next
Section titled “Where to go next”- Installation — install the desktop app, pair it with the hub.
- Configuration — full walkthrough of
SkyNodeConfig. - Driver interfaces — how SkyNode integrates with mount, enclosure, receiver, and radio-backend hardware; what the driver interface looks like.
- Operations — automated observing, MANUAL control, lease workflow, shutdown.
- Local GUI tour — what the dashboard and settings pages expose.
- Troubleshooting — sync monitor, unreadable configs, common failure modes.