---
title: "LoconIQ Connector"
slug: "loconiq-connector"
tags: ["Library"]
status: "update"
updated: 2026-10-20T14:05:51Z
published: 2026-10-20T14:05:51Z
canonical: "support.tulip.co/loconiq-connector"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://support.tulip.co/llms.txt
> Use this file to discover all available pages before exploring further.

# LoconIQ Connector

*Bring live tag locations from your LoconIQ system into Tulip apps.*

LoconIQ is an ultra-wideband (UWB) real-time location system. It tracks tags on bins, carts, people and robots, and computes their positions on an on-premise Edge. With a Connector to the Edge, your apps can show where things are and react when something leaves an area. This guide covers connecting to the Edge, reading tag positions and zone states, and an example alert. It's for app builders setting up location-aware apps.

![20261020_092153.jpg](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/20261020_092153.jpg)

## Required

- A LoconIQ environment (Edge, access points and tags) set up in the LoconIQ Admin App
- An Edge API key
- An on-premise connector host that can reach the Edge
- Familiarity with Connectors and Triggers

## App Configuration

### Create the connector

1. Go to **Apps > Connectors** and create an **HTTP** connector.
2. Select your on-premise connector host.
3. Enter the Edge's IP address as the server, port 80, with TLS off.
4. Under **Headers**, add `x-edge-api-key` with your Edge API key.

![Pasted image 20261020093253.png](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Pasted%20image%2020261020093253.png)

### Add functions

| Function | Method and path | Returns |
| --- | --- | --- |
| Get Positions | GET `/v1/locis/positions` | Each active tag's `id`, `x`, `y`, `z` (cm) and `lastPositionUpdate` |
| Get Zone States | GET `/v1/zones/locis?zoneIds={zoneId}` | Each tag's `state` in the zone: `INSIDE` or `OUTSIDE` |

Run **Get Positions** to test. Each active tag should appear with its position.

![Pasted image 20261020095142.png](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Pasted%20image%2020261020095142.png)

### Read positions in an app

LoconIQ doesn't push data, so your app polls the Edge.

1. Add a **Timer** Trigger to the step that runs **Get Positions** every few seconds.
2. Store the result in a Variable.
3. Use the variable in widgets or triggers, for example to show a tag on a floor plan.

### Example: alert when a bin leaves its work area

1. In LoconIQ, create a zone around the work area and copy its ID.
2. In the same Timer trigger, run **Get Zone States** with that zone ID.
3. If the bin's tag is `OUTSIDE`, show a message or turn a banner red. If it is `INSIDE`, clear it.

![Pasted image 20261020100252.png](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Pasted%20image%2020261020100252.png)

## Required Set Up

- **Fixed IP:** give the Edge a static IP address. If it changes, the connector stops working.
- **Zone IDs:** zone IDs are 18 digits. Store them as text, not numbers.
- **Devices:** LoconIQ tags and access points are configured only in the LoconIQ Admin App on an iPhone.
- **After a restart:** if the Edge or access points restart, move the tags so they rejoin, then restart the app.

## Extend this App

- Link a tagged bin or cart to a work order and track it across stations
- Show mobile robots or carts live on a dashboard
- Combine zone events with Andon lights or notifications

## Further Reading

- [LoconIQ developer documentation](https://developer.loconiq.com)

**Connectors**

**Connectors** enable real-time connectivity between your Tulip solution and a transactional system (e.g. an ERP). The output of a Connector Function can be used in Tulip Apps, Automations, and Functions.

- **HTTP Connectors** utilize HTTP API endpoints.
- **SQL Connectors** can enable connectivity with certain SQL databases.
- **MQTT Connectors** can connect to MQTT brokers for machine monitoring.

![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/connector.gif)

**Trigger**

**Triggers** are groups of logic that are tied to an app event, such as step open, timer, widget interaction, etc. App builders can add triggers to **widgets**, **machines**, **devices**, **apps**, and **steps**.

**Triggers** can contain **actions**, **transitions**, and **conditions**.

**Variable**

**Variables** are a location to store app information. Variables have a specific type that must match the contents they can store.

Variables are only accessible within a single application and are cleared when the app is restarted or completed.