Skip to content

Wiring devices in SkyNode

This subsection walks through how to bind each device kind to a SkyNode install — what JSON-config block to write, which drivers are available, and what the driver-specific parameters mean.

The model that ties this all together is in Configuration → device_configs. For driver maturity and the support tiers (production vs. experimental), see Driver interfaces.

The canonical reference here is the JSON config block — that’s what gets persisted on disk and what the local GUI reads/writes. The GUI exposes the same settings on each device type’s Settings page (pick the driver, Configure driver, Connect), but the JSON shape is what doesn’t move when the UI changes.

  • Mount — ascom, gbtwenty, simulator.
  • Camera — ascom, maxim, simulator.
  • Filter wheel — ascom, maxim, simulator.
  • Focuser — ascom, simulator.
  • Enclosure — ascom, astrohaven, nmskies_roof, simulator.
  • Weather sensor — aag_cloudwatcher, aurora_eurotech, boltwood_i, boltwood_ii, cumulus, davis_weatherlink, green_bank, skycanary, simulator.

In the JSON the driver is named by its full driver ID, <device type>.<driver> (for example camera.ascom); the mount’s GBTwenty driver is gbtwenty-mount.

ota has two experimental mirror-cover drivers (autoslew, ascom_cover_calibrator) and a simulator; instrument_rotator, receiver and radio_backend have simulators only; IP cameras have the amcrest_cgi and onvif control drivers. None of these has a wiring page yet.

Every page below has the same structure:

  1. What this device is for — one-paragraph framing for someone wiring it up for the first time.
  2. Config shape — the canonical JSON block, with field annotations.
  3. Drivers — one subsection per driver, with the driver_configs keys and what they mean.
  4. Simulator — a config-only “paper” driver for testing.
  5. Troubleshooting — common failure modes specific to that device kind.

If you’re trying to bring a device online for the first time, work through the corresponding page top-to-bottom. The simulator is always a useful safety net — a simulator config will run cleanly without hardware so you can verify the rest of your install before plugging real devices in.