Local GUI tour
SkyNode’s local GUI is the day-to-day interface for the on-site operator. It runs as a Tauri window on the SkyNode host, against the same Python backend that the hub talks to over the network — so anything you see in the GUI is exactly what the hub sees, and any manual operation you do here is reflected on the hub.
This page describes the screens of SkyNode’s local GUI.
Page structure
Section titled “Page structure”Before the dashboard, a few full-window screens handle startup and pairing:
| Screen | Purpose |
|---|---|
| Startup | Waits for the Python backend, then asks it where to go: the dashboard when the install is paired and its config is valid, otherwise sign-in and node selection |
| Sign-in | Opens the auth server in your system browser (OAuth with PKCE) and receives the code on a one-shot listener on 127.0.0.1 |
| Node selection | Pair the install: pick the observatory, the node type (telescope or observatory) and, for a telescope node, the telescope; then Bind & continue creates the installation on the hub and pulls the hardware graph |
| Sign-out | Drops your user token and signs you out of the auth server, then returns to sign-in |
The dashboard has a left navigation with six pages:
| Page | What it shows | What you can do |
|---|---|---|
| Overview | The bound telescope (or, on an observatory node, the observatory’s enclosures and weather sensors): automation state and its reasons, control authority, the manual control lease, one panel per device with its status and last update, and constraint actions | Revoke a manual control lease; set or cancel a shutdown lock (Lock opens a dialog that creates a shutdown interlock for the telescope or observatory) |
| Controls | Manual control of the telescope’s devices — available only while SkyNode is in MANUAL control; otherwise the page shows the reason and offers the switch | One tab per device the telescope has: Imaging (a full-page workspace for taking frames), Mount, Focuser, Filter wheel, Rotator, Enclosure (with the OTA mirror covers), Receiver, Radio backend, and Cameras (IP cameras this node drives) |
| Schedule | The telescope’s schedule as the hub projects it, the same one the website shows | Read-only; says so when the node is unbound or offline |
| Files | Every frame from acquisition through transfer to the hub (acquiring, solving WCS, ready for transfer, transferring, ready), with a drill-down into the node’s processing pipeline | Read-only |
| Diagnostics | Pointing-solve history: pointing error and the east/north corrections over the last 24 hours, 7 days, 30 days or all time | Read-only |
| Settings | Node, device, instrument and constraint settings (see below) | Edit and save |
The Controls Enclosure tab sends open and close requests to the enclosure controller — the same requests automation makes — and the controller honors an open only while its policy permits it, showing the reason when it doesn’t. A dome can also be set to follow the slit for a chosen imager. A status-only enclosure driver can’t open at all.
Status bars and banners
Section titled “Status bars and banners”A top status bar carries the automation state and its reason (click a reason to see what it means and where to fix it), the current target and execution phase, any device that is not nominal (slewing, exposing, faulted), the control authority (click to switch between REMOTE and MANUAL, always with a confirmation), the manual control lease, and the hub connection and sync state. While SkyNode is in MANUAL, a banner below it says so.
A bottom status bar shows the bound telescope or observatory, the sun altitude, LST and UTC.
Full-width banners appear when the install has lost its hub credentials, when the backend is unhealthy, and when the config file failed to load (see Troubleshooting).
Settings
Section titled “Settings”Settings (/dashboard/settings) is where you edit the node’s configuration from the GUI rather than the JSON. Fields save as you leave them, with a save indicator at the foot of the settings sidebar. The sidebar groups the pages:
- General — the bound telescope’s name, description and location (saved to the hub and shown on the public site; the slug is read-only), the build identifier and Check for updates, and the Unbind installation danger-zone action, which revokes the installation on the hub, clears the local credentials and signs you out.
- Startup & Shutdown — Start automation / Stop automation, the shutdown sequence and startup action checkboxes (including the dome park azimuth), and what happens when SkyNode quits.
- Local Broker — the MQTT broker: connection, authentication, TLS, reconnect and publish topics.
- Devices — Enclosure, Mount, Cameras, OTAs, Filter Wheels, Focusers, Rotators, Weather Sensors, IP Cameras, Antennas, Receivers, Radio Backends. Each device page starts with a driver section: pick the Driver, Configure driver (the ASCOM drivers open the ASCOM Chooser; other drivers get a form generated from the driver’s config schema), set Managed by (for an enclosure or weather sensor, which node drives it; for a telescope’s own device, whether this node uses it), and Connect / Disconnect, with the connection error shown inline. Below it are the device’s own settings, for example the focuser’s position range with a Use driver value button when the ASCOM driver reports its maximum.
- Instruments — Optical Imagers, Plate Solving, Radio Spectrometers.
- Safety — Operational Constraints.
On an observatory node the telescope-only pages (mount, cameras, imagers and so on) are hidden. A device’s driver and its options can’t be changed while it is connected; disconnect first.
The hub endpoints and OAuth settings are not edited in the GUI; they live in the config file.
Log panel
Section titled “Log panel”A log panel below every page streams the backend log live and can be resized by dragging its top edge — useful for operators who don’t want to find the log file on disk (%LOCALAPPDATA%\SkyNode\logs on Windows).