Ingest

What it is

Ingest is the part of Adaptr Cloud that listens. Your gateways publish to our broker. Ingest checks which gateway sent each message, finds the battery it belongs to and stores what it says.

Raw CAN and RS-485 frames are stored as they arrived, and a decoder turns them into readings afterwards. Messages in the Battery Emulator format also arrive here, already decoded.

A message from a gateway nobody has registered is not stored as a reading. It is held for the owner to claim or reject.

Who it is for

• Fleet operators who want readings from batteries they already run.
• Integrators who connect gateways and need to know where a frame goes.

How it works

1. A gateway publishes. The gateway connects to the broker with its own credentials and publishes on its own topics.
2. Ingest places the message. Ingest works out the gateway and the battery, and refuses what it cannot place.
3. The frame is kept, then decoded. A raw frame is written first. A decoder then reads it into a reading, which is stored beside the frame's source.

What it does not do yet

• The wires Ingest reads today are raw CAN, raw RS-485 and the Battery Emulator's MQTT format. See Decode for which protocols are read.
• SunSpec is read only over Modbus RTU on RS-485. Modbus TCP and manufacturer clouds are not connected.
• Raw frames are stored, but no screen or download returns them yet.
• A reading's time is when we received it, not when the device measured it.

Related services

• Gateway — Register the devices that report for your batteries. Each gets its own credentials and can publish only on its own topics.
• Decode — Decoders turn raw battery frames into readings. One shared library serves every customer, and a new decoder is added for everyone.
• Monitor — Live readings for your batteries, and rules that alert you by webhook, email or Slack when one needs attention. See pricing for the charge.