Aside from through the Starling's web interface, you may wish to communicate with it in other ways. This can be done through the Starling's API, which comprises a series of commands that can be sent via HTTP to it (and are in fact the ones used by the public Starling panel). These should have the following structure:

http://starling/api/v1/command_group/command/param1/param2

Where:

  • "starling" may be replaced by the appropriate name or IP address.
  • "api/v1" is for the first version of the API.
  • The commands are SLP commands—if you're familiar with our devices, you may already know the Seletek Line Protocol; this is explained in the next section.

SLP commands

All Lunático products can be accessed and programmed in a number of ways. Scripting, directly or via ASCOM, is always available for Windows, and there are also several options for lower-level integration.

When it comes to Seletek-related products (this means almost all of them, including the Starling), the protocol is the same—we call it "SLP" (standing for Seletek Line Protocol). In this section we will cover a few commands relevant to the Starling, all in the context of HTTP. If you're after more specific information, please email us.

The following table includes commands per group, with parameters (here separated by forward slashes) and notes. Please note that extra parameters will be ignored and missing parameters will default to 0.

As an example, the first command could be sent to the Starling as:

http://starling/api/v1/relio/relayreadall

And may return something like:

!relio relayreadall:20#

Where 20 in binary is 0001 0100, i.e. all relays are open except for the third and the fifth.

GroupCommandParametersReturns
relio
(Relay and sensor box)
relayreadallByte with 8 values — relay status
sensorreadalldigByte with 8 values — sensor status
seletek
(System)
getdhcp
setdhcp0 for on, 1 for off
gettipThe IP address
settipThe new IP address (in text format)
seletekapplynetcApplies the main network parameters (including the ones above) and makes them persistent
shutteropen
close
abort
physstatusActual status of the roof (as opposed to the curated status for driver compatibility)
statusASCOM-compliant status