Equipment

The Equipment page (left nav: Equipment) is the operator-side mission-control view of the whole rig — a live status dashboard. Since v20.91 the page is deliberately read-only: all device control (connect/disconnect and per-device commands) lives on the Console. What Equipment gives you is the telemetry already streaming over the WebSocket, with every device as a proper tile.

Opening the page hydrates from the REST snapshots (/api/state, /api/sequencer/state, /api/scheduler/status, /api/blockscript/status, /api/phd2); after that it is driven live by the WebSocket snapshot and equipment.device events. The header reads live · updated … so you see how fresh the data is.

Page layout

Top to bottom, the page is:

• Safety hero — a big SAFE / WARNING / UNSAFE / UNKNOWN banner with the reasons and the primary safety source. In manual mode (safety monitoring off) it reads MANUAL MODE — an amber/unknown banner, not a fault — noting that the operator is responsible for conditions.
• Sky & weather — the Solo / CloudWatcher card: cloud (sky−ambient), ambient, dew point, humidity, wind and sky brightness, with a row of per-sensor safe/warn/unsafe chips (cloud, wind, rain, humidity, light, pressure) and a stale flag when the source stops reporting. If no weather source is configured, the card says so.
• Activity — what the rig is doing now: the blockscript Supervisor state, the Scheduler state with its current target (project name + the goal's filter), a Sequence line with its plan name, state and a progress bar (step n/total, percent), and the active background Job. When nothing is running it reads Idle.
• Devices — the per-device tile grid (below).
• Guiding and Subsystems — the PHD2 guiding card (app state, RMS total / RA / Dec, SNR, a trend sparkline of RMS total, and star lost / settling chips), and a health grid with a status dot for every module (bus, supervisor, Solo, ASCOM, Alpaca, PHD2, sequencer, scheduler, planetarium, plate solve, all-sky, CCTV, FITS, alerts and web).

Device tiles

Each tile has a connection header (a colored dot + online / offline / fault), a big primary readout, and live values and status chips. There are no buttons here — connect/disconnect and every per-device command live on the Console (its top bar carries Connect all / Disconnect all).

• Mount — hero is altitude (· azimuth); RA / Dec / pier side (West / East), a small alt/az polar indicator (N up, E right, zenith centre), and tracking / slewing / parked / pulse-guiding chips.
• Camera (and Guide cam) — hero is sensor temperature; setpoint and gain, a cooler power bar (with an off note when the cooler is idle), a live exposure progress bar during a capture, and trend sparklines for sensor temperature and for HFR from graded frames.
• Focuser — hero is position in steps; temperature and max travel, with moving / temp-comp chips.
• Filter wheel — hero is the current filter name (or moving while it slews); slot count.
• Rotator — hero is sky PA; mechanical and target angle, with a moving chip.
• Observatory — hero is a status pictogram of the enclosure (roll-off roof or dome, coloured by shutter state: open / closed / opening / closing / error) once connected.
• Power / Flat panel — read-only summaries: the power tile shows sensor readouts (volts/amps/watts) and relay ON/OFF states, with a +N more note when the list overflows — switching lives on the Console power tile.

Guide cam appears as its own tile, but the Console's Connect all / Disconnect all leave it alone — PHD2 owns guiding.

Configured-but-offline devices

Since v20.22 the grid lists every configured slot, not just what is connected. Devices come from two merged sources: the configured slots the server already knows about (the ascom / alpaca slots in the module status, even when offline) and the live equipment.device events, which override with fresh data once a device connects. So your mount, camera, focuser, guide cam, roof and power show up as tiles right away — offline, with their ProgID — and fill with live data the moment they connect. Connect from the Console (top ⚡ Connect all). Only when nothing is assigned does the panel say so, pointing you to add ProgIDs in Settings.