Repository navigation
17. Using NodeConnect
NodeConnect is a first-party plugin that keeps the equipment and settings of two or more Galileo computers in step. The usual setup: configure everything once on the observatory computer (the Master), then pair a laptop or a second pier's computer (a spoke) with it, and the spoke picks up the same Observatories, Piers, devices and options. Images can follow too, so the observatory computer ends up with the Library.
A computer is either a spoke or a Master, never both. A computer with neither is simply standalone.
- Installing
- Connect Link
- Pairing a spoke with its Master
- What is kept in step
- Recent syncs and Undo
- Images
- Notifications
- Limitations
Install nodeconnect from Options > Plugins. Its settings are on Options > NodeConnect. It uses Galileo's Connect Link for the network side, so Connect Link must be enabled on the Master (see Connect Link below).
Connect Link is the encrypted link that other Galileo computers, phones and browsers use to reach this one. NodeConnect, MobileConnect and WebConnect all use it, and its settings are on Options > Connect Link.
It is off until you turn it on, and even then it listens only while an installed plugin that needs it is running; with it off, nothing listens and nothing is advertised on your network. The page shows whether it is listening and where, and lets you set the port, how long a pairing request waits, how long the audit log is kept, and whether the computer announces itself on the network. It also shows this computer's certificate fingerprint, so a device can confirm it has reached the right computer.
To add a device, start pairing on the device: it appears under Pairing requests with a six-digit code. Check the code matches the one on the device, then Approve… and choose what it may do (view, control, data transfer; access to settings is left unticked). Revoke stops a paired device at once; Delete removes it so it must pair again. Turning Connect Link off closes everything but keeps your paired devices, so turning it on again needs no new pairing.
The phone app shows alerts only while it is open and connected. To be told about a finished session, lost guiding or a safety stop while the app is closed, set up Notifications, which run on this computer and need no Galileo app. The easy route is a phone alert through the free ntfy app: install ntfy on your phone, press Generate topic on the Notifications page, subscribe to that topic in the ntfy app and press Send test alert. E-mail is the backup, used only if the phone alert cannot be sent. Text messages through a carrier's e-mail gateway are still offered, but US carriers have shut most of those gateways down, so prefer ntfy.
- On the spoke, open Options > NodeConnect, enter the Master's address and press Pair with Master.
- A short confirmation code appears. The same code appears on the Master, under Pairing requests. Compare them, and Approve the request on the Master.
- The spoke syncs straight away, then every few minutes. Sync now runs one at once.
The Master's certificate is remembered at pairing and checked on every connection, and each node has its own token, so a computer that is Revoked loses access immediately.
Equipment profiles (Observatories, Piers, device settings) and your options, with a few deliberate exceptions: settings that only make sense on one computer, and passwords and keys, stay where they are unless you choose otherwise. If the same record was changed on both computers, the later edit wins and the other value is kept so it can be recovered. Changes that arrive while a session is running wait until it ends, so a sync never changes equipment under an exposure.
When the Master changes something it tells the spokes, which then pull it, so a change on the observatory computer reaches the others in seconds rather than at the next interval.
Recent syncs lists what each sync did. Select one for the detail: how many records were added, changed or deleted, anything left to the Master, anything that failed. Undo this sync puts back what that sync replaced or deleted on this computer; the restored records then sync like any other edit. Keep reports sets how many are remembered.
A spoke can send its images to the Master in the background, optionally only in a time window (overnight, say). Each image is checked on arrival and only then marked as on the Master; Remove local images once the Master has them is off by default. An image that is on the Master stays in the Library with its details and thumbnail, and is fetched back when you open or process it, as long as the Master can be reached.
NodeConnect can notify you, through the channels set up in Options > Notifications, when a sync has been failing for a while, when a pairing request is waiting on the Master, and when a conflict was resolved. Each can be switched off separately.
- Two Libraries that grew independently are not merged, and edits to catalog fields are not reconciled.
- The Master and spokes must be on compatible Galileo versions; a spoke on an older database waits and says so.
- Every control has built-in help (press F1 or the ? button).