Supported Devices

This page answers one question: what can I connect to NEQTO.ai? The short answer is “almost anything that can send JSON over MQTT, HTTPS, or WSS.” On top of that, NEQTO.ai natively understands a few specific gateway and sensor families, so they work with little or no payload shaping on your side. This page lists those families and the exact device profiles behind them, drawn from the platform’s parser and integration support.

How NEQTO.ai Supports Devices

Every reading ends up in the same place: a Device with auto-mapped Attributes. What differs is how the raw data gets there. NEQTO.ai recognizes four kinds of inbound message and records the parser profile it matched.

Supported Device Families

These are the gateway and sensor families represented by the current parser and integration support. Region codes (USA, Canada, EU, Japan) reflect the radio frequency of the EnOcean 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.

Minew’s Millimeter Wave Radar Sensor (MSR01-A human presence, MSR01-B people-flow) is not represented in the current parser support and should not be treated as supported yet.

EnOcean IoT devices

These are EnOcean radio sensors represented by the current EEP support set. The EEP column is the profile NEQTO.ai decodes; a device may advertise several EEPs.

PLC

Industrial controllers connect over Ethernet using MQTT and the generic neqtoai-std path.

Native EnOcean Support

When an EnOcean gateway forwards a radio telegram, NEQTO.ai decodes it by its EnOcean Equipment Profile (EEP) and produces named readings, so you do not parse hex yourself. The platform ships decoders for a large set of EEPs.

The EEPs below are commonly used supported profiles from the current parser support set. The parser includes additional EEP implementations beyond this table.

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 decodes the beacon by its advertising frame type, so standard beacons and Minew sensors land as named readings with no payload shaping.

Each scan carries the beacon’s address (used as the device_id), its signal strength (RSSI), and the decoded frame contents. Like EnOcean, BLE support is receive only.

LoRaWAN Support

LoRaWAN devices connect through the generic neqtoai-std path. There is no native LoRaWAN decoder in the platform today, so a LoRaWAN device (or its network server) must forward decoded readings as a neqtoai-std JSON payload over MQTT, HTTPS, or WSS.

Anything Else: the Generic Path

If your device is not on any list above, it is very likely still supported. The rule is simple.

A minimal example, repeated here for convenience:

{
  "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

No matter the path, decoded readings become Attributes you can chart, alert on, and map. The common measurement kinds across the supported families:

• Native means decoded for you. EnOcean telegrams and BLE scans arrive as raw bytes; NEQTO.ai turns them into the readings above.
• Receive only for native protocols. EnOcean and BLE support displays incoming data; it does not control or actuate devices.
• Everything else is bring-your-own JSON. Send neqtoai-std and you are supported, list or no list.
• Regions matter for EnOcean. Pick the model that matches your radio region (902 MHz for USA/Canada, 868 MHz for EU, 928 MHz for Japan).