-
Notifications
You must be signed in to change notification settings - Fork 10
Cloudlog Integration
Basic rig CAT integration with Cloudlog is possible. When enabled and operating, open890 will update Cloudlog with the current operating frequency and mode.
In general, approximately 1/2 second after the radio "settles", open890 will push frequency and mode information into Cloudlog.
Cloudlog integration is managed on a per-connection basis, on the connection edit screen.
You need two pieces of information for Cloudlog integration - the root URL of the Cloudlog instance, and an API key.
The Cloudlog URL should be everything in the URL up to, but not including the /index.php, so if the URLs in your browser look like https://<callsign>.cloudlog.co.uk/index.php/logbook, the Cloudlog URL would be https://<callsign>.cloudlog.co.uk
Sign into your Cloudlog instance. Once signed in click your callsign in the upper right, and choose "API Keys"
Click "Create a read & write key"
Copy and paste the new API key into the appropriate field on the Edit Connection screen in open890.
Once started, open890 will start sending frequency information into Cloudlog.
On the QSO screen in Cloudlog, click the Station tab, and change the Radio dropdown. You should see a radio named <connection name> via open980 in the list, and changing frequency/mode should be reflected in the Band/Mode fields in the QSO tab, as well as the Frequency field on the Station tab.
If it seems like Cloudlog isn't receiving frequency information, check the open890 console window, and if needed, ask for help on the open890 Discussion Group.
If you see e.g. [debug] Cloudlog response: %{"status" => "success"}, then Cloudlog is receiving updates, but you most likely have the incorrect radio selected in Cloudlog.