Nautilus NXT relay#

Self Hosted Cloud Hosted

A Nautilus NXT relay can forward iSpindel-format readings to BrewGraph. This page shows how to set up the relay’s HTTP service so that the readings arrive on an iSpindel device in BrewGraph.

What you need#

  • An iSpindel device added in BrewGraph under Devices. BrewGraph shows its device token on the device page.

  • A Nautilus NXT relay that forwards your iSpindel’s readings.

The relay has been tested against both a staging environment and the hosted production service.

Configure the relay#

In the relay’s HTTP service configuration, fill in:

Field

Value

Select service type

HTTP

TOKEN

The device token from the BrewGraph device page, for example YOUR-DEVICE-TOKEN. See Device Tokens.

Server Address

Cloud Hosted: ingest.brewgraph.com. Self Hosted: your own ingest host. Enter the host only, without http:// or https://.

PATH/URI

/ingest/ispindel

Sending interval (seconds)

Cloud Hosted: not shorter than the reporting interval of your plan. In the free beta this is about 900. Self Hosted: any interval.

On Cloud Hosted, a reading that arrives faster than your plan’s reporting interval is answered with 429 and is not stored.

The relay sends the iSpindel payload described under iSpindel in Device Ingest API: name, ID, token, angle, temperature, temp_units, battery, gravity, interval and RSSI.

Check that it works#

  1. Save the configuration on the relay and wait for one sending interval.

  2. Open the device in BrewGraph. The latest reading, with its gravity, temperature and battery, should appear on the device page.

  3. Assign the device to the batch that is fermenting to see the readings on the batch chart.

Troubleshooting#

  • Nothing appears and the relay reports 401: the token is missing or mistyped. Copy it again from the device page.

  • 404: check that PATH/URI is exactly /ingest/ispindel.

  • 429 on Cloud Hosted: raise the sending interval to at least your plan’s reporting interval.

  • 502, 503 or 504: check Server Address. It must be the ingest host, not the address you use to open the app, and must not include a scheme.

For every status code and what to do about it, see Ingest error codes.

Limitations#

The relay forwards every reading with the relay’s own token and does not pass on the token of the iSpindel. Only one iSpindel per relay can be connected.

With two iSpindels behind one relay, both report to the same BrewGraph device. Because the reporting interval is checked per device, a reading that arrives inside the interval after another is answered with 429 and is not stored (about 900 s in the Cloud Hosted free beta).

Identifying forwarded devices by their own ID is not yet supported.