Weather sensor
Weather sensors feed the operational constraint evaluator with sky, wind, temperature, humidity, and (where the sensor supports it) cloud-cover readings. Constraints reference these readings to decide whether observations are eligible to run.
Like enclosures, weather sensors can be bound at the telescope level or at the observatory level — a single sensor that covers the whole site should be bound to an observatory node so multiple telescope nodes don’t fight to read it.
Config shape
Section titled “Config shape”{ "device_type": "weather_sensor", "driver": "weather_sensor.<driver>", "managed_by": "this_node", "driver_configs": { "<driver-id>": { /* driver-specific */ } }}| Field | Meaning |
|---|---|
managed_by |
Which node, if any, reads this sensor. "this_node" — this install owns the sensor and reads it directly. "another_node" (the default) — the owning install publishes readings and this one consumes them (from the local MQTT broker when both nodes use one, otherwise via the hub). "no_node" — the sensor is gone or unused; SkyNode skips it and never reports it as a fault. In the app this is the Managed by selector on the weather-sensor settings card. Older configs’ boolean connect_locally is migrated automatically (true → "this_node", false → "another_node"). |
Drivers
Section titled “Drivers”All weather sensor drivers are experimental today — they work on specific hardware they’ve been tested with, but none is a mainline production target. Talk to the Skynet team before relying on one in production. ASCOM is not currently used for weather sensors; each driver targets the sensor’s native protocol, vendor COM interface, web page or file format. The driver_configs key is the full driver ID (for example weather_sensor.aag_cloudwatcher).
A common parameter across most drivers:
| Key | Meaning |
|---|---|
max_stale_seconds |
Maximum age in seconds before a reading is treated as stale (and the constraint evaluator should ignore it). Defaults vary; raise for sensors that publish infrequently. green_bank and skycanary call it max_stale_sec |
aag_cloudwatcher — experimental
Section titled “aag_cloudwatcher — experimental”For Lunatico AAG CloudWatcher sensors, through the CloudWatcher software’s COM interface.
"weather_sensor.aag_cloudwatcher": { "max_stale_seconds": 3 }SkyNode reads AAG CloudWatcher temperatures from the CloudWatcher software’s COM server (AAG_CloudWatcher.CloudWatcher), which returns them in whichever unit that software is set to display (the temperature Units selection on its Device tab). SkyNode reads that setting on every refresh and converts Fahrenheit readings to Celsius, so either choice works and you can switch it at any time; SkyNode never changes it. If the software reports a unit other than C or F, or the unit changes in the middle of a read, the sensor shows a fault and its readings are dropped until three good reads in a row.
aurora_eurotech — experimental
Section titled “aurora_eurotech — experimental”For Eurotech Aurora cloud sensors, over TCP (host, port, socket_timeout_s, max_stale_seconds).
boltwood_i — experimental
Section titled “boltwood_i — experimental”For first-generation Boltwood Cloud Sensors, through COM (prog_id, use_pywin32, max_stale_seconds).
boltwood_ii — experimental
Section titled “boltwood_ii — experimental”For second-generation Boltwood Cloud Sensors (Clarity II).
"weather_sensor.boltwood_ii": { "prog_id": "ClarityII.CloudSensorII", "use_pywin32": true, "max_stale_seconds": 3}| Key | Meaning |
|---|---|
prog_id |
COM ProgID for the Boltwood II sensor — defaults to ClarityII.CloudSensorII (Diffraction Limited Clarity II software) |
use_pywin32 |
Whether to use pywin32 for COM access (vs. an alternate COM layer) |
cumulus — experimental
Section titled “cumulus — experimental”For weather stations exposed through Sandaysoft Cumulus, by reading its output file (file_path, max_stale_seconds).
davis_weatherlink — experimental
Section titled “davis_weatherlink — experimental”For Davis Instruments stations exposed through WeatherLink.
"weather_sensor.davis_weatherlink": { "base_url": "http://localhost:8080/", "timeout_s": 10.0, "max_stale_seconds": 600}| Key | Meaning |
|---|---|
base_url |
URL of the WeatherLink API endpoint (no default; required) |
timeout_s |
HTTP request timeout in seconds |
max_stale_seconds |
Stale-reading threshold; WeatherLink updates slowly, so the default of 600 is generous |
green_bank — experimental
Section titled “green_bank — experimental”Polls the Green Bank Observatory weather page (station #1) for temperature, humidity, pressure and wind (base_url, poll_interval_sec, timeout_sec, max_stale_sec).
skycanary — experimental
Section titled “skycanary — experimental”A synthetic sensor read from the SkyCanary app (by default on the same computer, http://127.0.0.1:8140), which owns the site location: radar rain distance, cloud cover, lightning proximity and model-nowcast surface weather (base_url, min_dbz, no_strike_distance_km, poll_interval_sec, timeout_sec, max_stale_sec).
simulator — testing only
Section titled “simulator — testing only”Paper weather sensor. Reports configurable static readings.
"weather_sensor.simulator": {}The old_csharp_drivers/ folder in the driver tree is C# source from a previous Skynet generation, kept for reference. It is not a driver and doesn’t appear in the driver list.
Troubleshooting
Section titled “Troubleshooting”- “Constraint says ‘unknown’ or ‘stale’ even though the sensor is alive.”
max_stale_secondsis too tight for the sensor’s update cadence. Check the sensor’s logs to find its typical reading interval and setmax_stale_secondsa few intervals above that. - “Sensor is up but readings are wrong.” Calibration is a hardware-side concern. Verify with the vendor’s own diagnostics tool first.
- “COM-based sensor (Boltwood II) won’t initialize.” Same pattern as ASCOM drivers — check the ProgID with PowerShell, confirm the bitness matches the SkyNode build, and run the vendor’s own software to verify the COM proxy is alive.
- “Two installs report different readings.” The sensor is bound to multiple installs with
managed_by: "this_node". Only the install that owns the sensor should claim it; everything else should be"another_node"and consume the published reading.