Platform Documentation

You can connect devices that send JSON over MQTT, HTTPS, or WSS. NEQTO.ai also parses several gateway and sensor families with little or no payload shaping. This page lists those families and the device profiles covered by the platform’s parser and integration support.

How NEQTO.ai supports devices

Each path creates a Device with auto-mapped Attributes. The difference is how NEQTO.ai parses the incoming data. The platform recognizes four inbound message profiles and records the one it matches.

Supported device families

These gateway and sensor families are covered by the current parser and integration support. For EnOcean devices, the USA, Canada, EU, and Japan region codes identify the radio-frequency variant.

Gateways

A gateway is the bridge between your sensors and NEQTO.ai. BLE gateways relay beacon scans; EnOcean gateways relay radio telegrams.

BLE IoT devices

These beacon-style sensors match the BLE frame support above. Their measurements arrive after the gateway relays the scan.

The current parser does not support Minew’s Millimeter Wave Radar Sensor models MSR01-A for human presence or MSR01-B for people flow.

EnOcean IoT devices

The current EEP support set covers these EnOcean radio sensors. The EEP column identifies the profile that NEQTO.ai decodes. A device may advertise several EEPs.

PLC

Industrial controllers connect over Ethernet using MQTT and the generic JSON path; neqtoai-std is the recommended envelope.

Native EnOcean support

When an EnOcean gateway forwards a radio telegram, NEQTO.ai decodes it by its EnOcean Equipment Profile, or EEP, and produces named readings. You do not need to parse the hexadecimal data. The platform includes decoders for many EEPs.

The neqtoai-enocean envelope carries the raw telegram as a hex string:

{
  "payload_format": "neqtoai-enocean",
  "timestamp": 1716806400000,
  "data": "55..."
}

The data field is the raw EnOcean packet in hexadecimal. The timestamp field is optional. If you omit it, the platform uses the message’s arrival time.

The table lists commonly used EEPs from the current parser support set. The parser also supports EEPs that are not listed here.

Profile reference: the EnOcean Alliance EEP catalog at enocean-alliance.org/products/eeps/.

Native BLE gateway support

A BLE gateway listens for nearby Bluetooth Low Energy beacons and relays their advertising packets to NEQTO.ai. The platform uses the advertising frame type to decode standard beacons and Minew sensors into named readings. This path does not require payload shaping.

Each scan carries the beacon’s address, which becomes the device_id. It also carries the signal strength, or RSSI, and the decoded frame contents. Like EnOcean, BLE support is receive only.

LoRaWAN support

LoRaWAN devices connect through the generic JSON path. There is no native LoRaWAN frame decoder in the platform today, so a LoRaWAN device or network server must forward decoded readings over MQTT, HTTPS, or WSS. The recommended envelope is neqtoai-std. The platform also accepts supported vendor topics and flexible decoded JSON shapes. See Endpoints & Devices → MQTT topic options for the accepted shapes and limits.

Other devices and the generic path

A device does not need to appear in the tables above to use the generic JSON path.

Recommended neqtoai-std payload:

{
  "payload_format": "neqtoai-std",
  "timestamp": 1716806400000,
  "device_id": "my-device-01",
  "data": {
    "temperature": { "value": 22.4, "unit": "c" },
    "humidity":    { "value": 62.3, "unit": "%" }
  }
}

What you get after ingestion

Every path turns decoded readings into Attributes that you can chart, alert on, and map. The supported families commonly provide these measurements:

• Native means decoded for you. EnOcean telegrams and BLE scans arrive as raw bytes. NEQTO.ai turns them into the readings above.
• Native protocol support is receive only. EnOcean and BLE support displays incoming data. It does not control or actuate devices.
• Other devices use JSON. Use the recommended neqtoai-std envelope or another supported JSON shape, whether or not the device appears in this page’s tables.
• Regions matter for EnOcean. Pick the model that matches your radio region: 902 MHz for USA and Canada, 868 MHz for the EU, or 928 MHz for Japan.