Hoppa till huvudinnehåll

Connectors

Connectors serve as the interface between Yggio and external data sources by managing the required credentials, endpoints, and subscription topics. They enable seamless data flow into the platform, out from the platform or both in and out from the platform.

Connector setup often involves authenticating with remote systems and configuring appropriate permissions, which demands familiarity with the specific external system architecture. Commonly, REST APIs handle initial provisioning, while MQTT streams live sensor data. Exceptions include legacy IoT protocols like BACnet and Modbus.

For troubleshooting, collaboration between the platform support and the remote system's support team is essential.

Retention Policy​

Defines how long ingested data is stored within the platform's database. This period can be configured from a minimum of 2 days up to indefinite retention (forever), depending on operational requirements and compliance needs.

Flow Identifier​

Defines which Data FLow that should be the default choice for new devices created with the connector.

Creating a Connector​

To create a new connector:

  1. Click Connectors in the top navigation bar.
  2. Select the desired connector type.
  3. Follow the specific setup instructions for that connector, as configuration varies depending on the data source and protocol.

Available Connectors​

LoRaWAN​

  • Actility ThingPark — For the LoRaWAN server ThingPark from Actility.
  • ChirpStack V3 — For the open-source LoRaWAN server ChirpStack v3.
  • ChirpStack V4 — For the open-source LoRaWAN server ChirpStack v4.
  • Loriot — For the LoRaWAN server Loriot. This integration is receive-only.
  • Helium — For the LoRaWAN server Helium. This integration is receive-only.
  • Netmore — For the LoRaWAN server Netmore.
  • TTN – The Things Network — For the LoRaWAN server TTN (The Things Network).

Generic (NB-IoT / Cat-M / WiFi / BLE / Ethernet / etc.)​

  • CoAP — Connector to receive data from CoAP devices.
  • UDP — Connector to receive data from UDP devices.
  • MQTT — Connector for publishing arbitrary data on the platform’s MQTT broker or at an external broker.
  • HTTP — Existing global connector for sending HTTP POST updates. Available through "Channels" on all devices in the device list.
  • BACnet IP — Enables the platform to communicate with a BACnet server (requires direct network access). Contact support to enable.
  • Modbus TCP — Enables the platform to communicate with Modbus devices (requires direct network access). Contact support to enable.

Manufacturer- or Service-Specific​

  • BLE Dusoniot — For connecting to BLE gateways from Dusoniot.
  • Celsiview — For receiving data from Celsiview devices via their portal (typically NB-IoT devices).
  • Delta Controls – BACnet — For integration with Delta Controls BMS via EnteliWeb REST API.
  • Elvaco CME — For receiving multi-sensor data via HTTP from Elvaco CME devices, using Elvaco spec 3108.
  • Klimator RSI — For receiving weather data from Klimator’s road weather stations via their RSI portal.
  • SIA Connect — For connecting to edge gateways from SIA Connect. Enables integration with various BMS platforms (e.g. Siemens, Schneider, Beckhoff).
  • Siemens Desigo CC — For providing sensor data to Siemens Desigo CC via its REST API.
  • Open Weather Map — For receiving weather and forecast data from Open Weather Map. Create weather devices with specific latitude and longitude to retrieve data.

Notes​

Some connectors are only available when creating a device via the "New Device" option in the device list. These are legacy connectors and will be migrated to the Connector UI over time.

Other connectors are only accessible via the API and are undocumented and will get added to the UI in future platform updates.

Connectors are essential for adding and managing devices in Yggio. If your desired connector is not available in the UI please contact your support representative.