AAG CloudWatcher (Solo)

The AAG CloudWatcher Solo is Starship's primary safety source. It's a self-contained weather station with a built-in web server that exposes a CGI endpoint returning the current readings (cloud, rain, wind, temperature, humidity, sky brightness, pressure) together with the Solo's own safe/unsafe verdict.

Starship reads the Solo but never commands it. The Solo has a relay output (its switch field) that Starship deliberately leaves alone — the Solo's own logic, and the hardwired interlock between the Solo and your roof, stay authoritative.

Connecting to the Solo

The Solo hosts its CGI at a .local or fixed-IP address. On most networks it's reachable by the hostname aagsolo, which maps via mDNS / local DNS to the Solo's IP.

In Settings → AAG CloudWatcher (Solo) (the [solo] section of the config), set:

Starship polls http://<host>/cgi-bin/cgiLastData on the configured interval, parses the key=value text payload, and publishes solo.reading events on the internal bus (with solo.stale and solo.error events when a reading is old or the fetch fails).

What the Solo reports

The Solo returns its own per-sensor verdicts, each of which is SAFE, WARNING, or UNSAFE:

The Solo's overall verdict is SAFE only when every sub-sensor is SAFE. Starship trusts that headline verdict for the Solo's own sensors.

What it contributes to the Safety Supervisor

The Safety Supervisor is the only part of Starship allowed to declare the overall safety state; the Sequencer, Scheduler, and scripting all act on its verdict. The Supervisor treats the Solo as its primary source and adds its own meta-rules on top of the Solo's verdict:

Any of unsafe / stale / no-contact pushes the Supervisor verdict toward UNSAFE (or UNKNOWN, which is treated the same for gating).

Sustained-loss escalation (on by default)

A short loss of the Solo link gives an UNSAFE that auto-recovers once the link returns. A long one does not: after safety.weather_loss_emergency_s seconds of continuous loss or silence (default 1800 = 30 minutes) the Supervisor escalates to a latched EMERGENCY (park + close, manual reset) instead of auto-recovering, so a dead weather link can't leave the rig working under unknown skies all night. This counts only loss/silence — a plain reported-unsafe (rain, cloud) still auto-recovers on the dwell.

Poll-thread watchdog

Because the Supervisor is event-driven, it only ticks when the Solo driver publishes an event. A separate health-monitor watchdog ([health] → solo_heartbeat_enabled, on by default) notices if the Solo poll thread has gone silent — no solo.reading or solo.error for a few poll intervals — and drives the same emergency safe-state, so a silently dead poll thread can't leave the rig unguarded. Tune the silence threshold with solo_heartbeat_poll_multiple (multiple of the poll interval, default 3×) and solo_heartbeat_min_age_s (an absolute floor).

Other weather sources: ASCOM / Alpaca SafetyMonitor and ObservingConditions

New in v23. A rig is no longer limited to the CloudWatcher Solo. An ASCOM or Alpaca SafetyMonitor or ObservingConditions device can feed the Safety supervisor too, beside the Solo or instead of it.

Setting one up

These are set in config.toml; there is no Settings page for them yet. Restart Starship after changing them.

  1. Give the device its role, the same way as any other device: [ascom.safetymonitor] or [ascom.observingconditions] with a prog_id, or [alpaca.safetymonitor] or [alpaca.observingconditions] with host and port.
  2. Set auto_connect = true for that device, and make sure the transport itself ([ascom] or [alpaca]) is enabled. If it is not, the log warns that the source is NOT watching the sky.
  3. For an ObservingConditions device, set at least one limit under [weather] (below).

The device then joins the supervisor as an additional source, like an extra CloudWatcher: if it reports unsafe, the verdict is UNSAFE. Coming back to SAFE needs every source safe for the whole dwell.

What each device gives

Limits for ObservingConditions: [weather]

The rules:

When the device stops answering

A device that cannot be read is never published as safe.

A rig with no Solo: [safety] primary_source

primary_source says which source is the primary one: the source whose loss is always UNSAFE and to which the sustained-loss escalation above applies.

With one of the last two, the Solo is not polled unless [solo] extra_hosts lists it. If the chosen device is not set up, safety stays UNKNOWN, which is not safe. The dashboard's safety card shows which source is the primary.

These sources are new in v23. Before you rely on one, check it the simple way: make the device report unsafe (or unplug it) with the roof closed, and see that the verdict goes UNSAFE.

Manual mode (monitoring off)

For a portable / no-observatory / no-weather-sensor rig where a person is present, set safety.enabled = false. In this mode the Supervisor doesn't arm, the Solo isn't polled, and the verdict reads DISABLED — which never blocks anything (roof-open included). The UI shows "MANUAL MODE / monitoring off" rather than a red UNSAFE, and it's the operator's job to keep the rig safe.

Current readings on the dashboard

The Status / Safety page shows the latest Solo reading, live-updated over the WebSocket (solo.reading) and available at GET /api/solo/last:

Notes

The driver is read-only and straightforward Python. If the Solo's behaviour ever needs adjusting for your firmware or units, it's a small module you can fork, fix, and send back as a PR.

Astroworx Starship v23.1.2 · this page is the in-app help of that buildDownload · HTTP API